Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report bugs at 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.
Implement your own option¶
You can easily extend pkglts by implementing your own option as a plugin. There are two types of plugins:
- options that implement a new feature useful for everybody. Don’t hesitate to contact us or submit a pull request if you want to insert it into the main pkglts repo.
- plugins that implement a way to create packages specific to your organization. Don’t hesitate to make your life easier if you always create projects with the same options.
Look through the GitHub issues for bugs. Anything tagged with “bug” is open to whoever wants to implement it.
Look through the GitHub issues for features. Anything tagged with “feature” is open to whoever wants to implement it.
pkglts could always use more documentation, whether as part of the official pkglts 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 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 :)
Ready to contribute? Here’s how to set up pkglts for local development.
Fork the pkglts repo on GitHub.
Clone your fork locally:
$ git clone firstname.lastname@example.org:your_name_here/pkglts.git
3. Install your local copy into a virtualenv. Assuming you have virtualenv installed, this is how you set up your fork for local development:
$ virtualenv dvlpt $ dvlpt/script/activate (dvlpt)$ python setup.py develop
Create a branch for local development (wip stands for work in progress):
(dvlpt)$ git checkout -b wip_name-of-your-bugfix-or-feature
Now you can make your changes locally.
5. When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:
(dvlpt)$ cd pkglts (dvlpt) pkglts$ flake8 (dvlpt) pkglts$ nosetests (dvlpt) pkglts$ tox To get flake8 and tox, just pip install them into your virtualenv.
Commit your changes and push your branch to GitHub:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin wip_name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
Pull Request Guidelines¶
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, 3.4, and 3.5. Check Travis-CI and make sure that the tests pass for all supported Python versions.
To run a subset of tests:
$ nosetests test/test_XXX