Skip to content

Commit 4bd3d4a

Browse files
committed
first commit
0 parents  commit 4bd3d4a

28 files changed

+1017
-0
lines changed

AUTHORS.rst

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
=======
2+
Credits
3+
=======
4+
5+
Development Lead
6+
----------------
7+
8+
* Marcin Spoczynski <[email protected]>
9+
10+
Contributors
11+
------------
12+
13+
None yet. Why not be the first?

CONTRIBUTING.rst

+112
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
============
2+
Contributing
3+
============
4+
5+
Contributions are welcome, and they are greatly appreciated! Every
6+
little bit helps, and credit will always be given.
7+
8+
You can contribute in many ways:
9+
10+
Types of Contributions
11+
----------------------
12+
13+
Report Bugs
14+
~~~~~~~~~~~
15+
16+
Report bugs at https://github.com/sandlbn/django_bootstrap_calendar/issues.
17+
18+
If you are reporting a bug, please include:
19+
20+
* Your operating system name and version.
21+
* Any details about your local setup that might be helpful in troubleshooting.
22+
* Detailed steps to reproduce the bug.
23+
24+
Fix Bugs
25+
~~~~~~~~
26+
27+
Look through the GitHub issues for bugs. Anything tagged with "bug"
28+
is open to whoever wants to implement it.
29+
30+
Implement Features
31+
~~~~~~~~~~~~~~~~~~
32+
33+
Look through the GitHub issues for features. Anything tagged with "feature"
34+
is open to whoever wants to implement it.
35+
36+
Write Documentation
37+
~~~~~~~~~~~~~~~~~~~
38+
39+
django-bootstrap-calendar could always use more documentation, whether as part of the
40+
official django-bootstrap-calendar docs, in docstrings, or even on the web in blog posts,
41+
articles, and such.
42+
43+
Submit Feedback
44+
~~~~~~~~~~~~~~~
45+
46+
The best way to send feedback is to file an issue at https://github.com/sandlbn/django_bootstrap_calendar/issues.
47+
48+
If you are proposing a feature:
49+
50+
* Explain in detail how it would work.
51+
* Keep the scope as narrow as possible, to make it easier to implement.
52+
* Remember that this is a volunteer-driven project, and that contributions
53+
are welcome :)
54+
55+
Get Started!
56+
------------
57+
58+
Ready to contribute? Here's how to set up `django_bootstrap_calendar` for local development.
59+
60+
1. Fork the `django_bootstrap_calendar` repo on GitHub.
61+
2. Clone your fork locally::
62+
63+
$ git clone [email protected]:your_name_here/django_bootstrap_calendar.git
64+
65+
3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development::
66+
67+
$ mkvirtualenv django_bootstrap_calendar
68+
$ cd django_bootstrap_calendar/
69+
$ python setup.py develop
70+
71+
4. Create a branch for local development::
72+
73+
$ git checkout -b name-of-your-bugfix-or-feature
74+
75+
Now you can make your changes locally.
76+
77+
5. When you're done making changes, check that your changes pass flake8 and the
78+
tests, including testing other Python versions with tox::
79+
80+
$ flake8 django_bootstrap_calendar tests
81+
$ python setup.py test
82+
$ tox
83+
84+
To get flake8 and tox, just pip install them into your virtualenv.
85+
86+
6. Commit your changes and push your branch to GitHub::
87+
88+
$ git add .
89+
$ git commit -m "Your detailed description of your changes."
90+
$ git push origin name-of-your-bugfix-or-feature
91+
92+
7. Submit a pull request through the GitHub website.
93+
94+
Pull Request Guidelines
95+
-----------------------
96+
97+
Before you submit a pull request, check that it meets these guidelines:
98+
99+
1. The pull request should include tests.
100+
2. If the pull request adds functionality, the docs should be updated. Put
101+
your new functionality into a function with a docstring, and add the
102+
feature to the list in README.rst.
103+
3. The pull request should work for Python 2.6, 2.7, and 3.3, and for PyPy. Check
104+
https://travis-ci.org/sandlbn/django_bootstrap_calendar/pull_requests
105+
and make sure that the tests pass for all supported Python versions.
106+
107+
Tips
108+
----
109+
110+
To run a subset of tests::
111+
112+
$ python -m unittest tests.test_django_bootstrap_calendar

HISTORY.rst

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
.. :changelog:
2+
3+
History
4+
-------
5+
6+
0.1.0 (2013-08-15)
7+
++++++++++++++++++
8+
9+
* First release on PyPI.

LICENSE

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
Copyright (c) 2013, Marcin Spoczynski
2+
All rights reserved.
3+
4+
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
5+
6+
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
7+
8+
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
9+
10+
* Neither the name of django-bootstrap-calendar nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
11+
12+
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

MANIFEST.in

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
include AUTHORS.rst
2+
include CONTRIBUTING.rst
3+
include HISTORY.rst
4+
include LICENSE
5+
include README.rst
6+
recursive-include django_bootstrap_calendar *.html *.png *.gif *js *jpg *jpeg *svg *py

README.rst

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
=============================
2+
django-bootstrap-calendar
3+
=============================
4+
5+
.. image:: https://badge.fury.io/py/django_bootstrap_calendar.png
6+
:target: http://badge.fury.io/py/django_bootstrap_calendar
7+
8+
.. image:: https://travis-ci.org/sandlbn/django_bootstrap_calendar.png?branch=master
9+
:target: https://travis-ci.org/sandlbn/django_bootstrap_calendar
10+
11+
.. image:: https://pypip.in/d/django_bootstrap_calendar/badge.png
12+
:target: https://crate.io/packages/django_bootstrap_calendar?version=latest
13+
14+
15+
simple calendar based on the calendar of http://bootstrap-calendar.azurewebsites.net/
16+
17+
Documentation
18+
-------------
19+
20+
The full documentation is at http://django_bootstrap_calendar.rtfd.org.
21+
22+
Quickstart
23+
----------
24+
25+
Install django-bootstrap-calendar::
26+
27+
pip install django_bootstrap_calendar
28+
29+
Then use it in a project::
30+
31+
import django_bootstrap_calendar
32+
33+
Features
34+
--------
35+
36+
* TODO

django_bootstrap_calendar/__init__.py

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
__version__ = '0.1.0'

django_bootstrap_calendar/models.py

Whitespace-only changes.

django_bootstrap_calendar/static/css/django_bootstrap_calendar.css

Whitespace-only changes.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Images go here

django_bootstrap_calendar/static/js/django_bootstrap_calendar.js

Whitespace-only changes.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
2+
{% comment %}
3+
As the developer of this package, don't place anything here if you can help it
4+
since this allows developers to have interoperability between your template
5+
structure and their own.
6+
7+
Example: Developer melding the 2SoD pattern to fit inside with another pattern::
8+
9+
{% extends "base.html" %}
10+
{% load static %}
11+
12+
<!-- Their site uses old school block layout -->
13+
{% block extra_js %}
14+
15+
<!-- Your package using 2SoD block layout -->
16+
{% block javascript %}
17+
<script src="{% static 'js/ninja.js' %}" type="text/javascript"></script>
18+
{% endblock javascript %}
19+
20+
{% endblock extra_js %}
21+
{% endcomment %}

0 commit comments

Comments
 (0)