Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways.
Although django-dingos is generic, in the near future its further development will occur mostly within the further development of the Django Mantis Cyber-Threat Intelligence Management Framework. So, for the time being, please use https://github.com/siemens/django-mantis/issues as issue tracker for bugs, feature requests and other feedback regarding django-dingos.
Report bugs at https://github.com/siemens/django-mantis/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues (https://github.com/siemens/django-mantis/issues) for bugs. Anything tagged with “bug” is open to whoever wants to implement it.
Look through the GitHub issues (https://github.com/siemens/django-mantis/issues) for features. Anything tagged with “feature” is open to whoever wants to implement it.
Djangos could always use more documentation, whether as part of the official Djangos docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue at https://github.com/siemens/django-mantis/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
In your contribution, you may want to either modify/add to existing code or create a new Django application that interacts with the existing applications that are part of the Mantis framework.
DINGOS profitted a lot from the advice provided in Two Scoops of Django. Unless you are an absolute Django expert (and maybe even then), please read Daniel Greenfield’s and Audrey Roy’s excellent Two Scoops of Django. Even though it provides best practices for Django 1.5, most of its advice is also valid for Django 1.6, and likely to be very relevant for quite a few minor revisions to come.
Here’s how to set up a repository for local development.
Fork the relevant repository repo on GitHub.
Clone your fork locally:
$ git clone email@example.com:your_name_here/<repository>.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ mkvirtualenv <your_mantis_environment> $ cd <repository_folder> $ python setup.py develop
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
Commit your changes and push your branch to GitHub:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
Do yourself a favor and set up the directory structure of your
Django application in the right way from the very start.
The easiest way to do so is to use Daniel Greenfield’s cookiecutter-djangopackage template
(which uses Audrey Roy’s excellent Cookiecutter for creating the directories): this
layout has a very sensible directory structure with out-of-the-box configuration of
easy build, submission to PyPi, etc., as well as the start of a Sphinx documentation tree.
Once you have the directory structure created, initialize a fresh git repository with it
and get to work...
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests.
- If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
- The pull request should work for Python 2.7.