Skip to content

Latest commit

 

History

History
141 lines (93 loc) · 3.66 KB

CONTRIBUTING.rst

File metadata and controls

141 lines (93 loc) · 3.66 KB
Raw

Contributing

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

Report bugs at https://github.com/eghuro/dcat-dry/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.

Fix Bugs

Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it.

Implement Features

Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it.

Write Documentation

DCAT DRY could always use more documentation, whether as part of the official dcat-dry docs, in docstrings, or even on the web in blog posts, articles, and such.

Submit Feedback

The best way to send feedback is to file an issue at https://github.com/eghuro/dcat-dry/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 :)

Get Started!

Ready to contribute? Here's how to set up DCAT DRY for local development.

  1. Fork the dcat-dry repo on GitHub.

  2. Clone your fork locally:

    $ git clone git@github.com:your_name_here/dcat-dry.git

  3. Install dcat-dry and its requirements. Poetry will create a virtual environment automatically, but if preferred, it can be created in a different way. You need libxml2 and libxslt on your system.

    cd dcat-dry
pip install --upgrade pip
pip install poetry
poetry install --no-root

  1. Create a branch for local development:

    $ git checkout -b name-of-your-bugfix-or-feature

    Now you can make your changes locally.

  2. When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:

    $ flake8 dcat-dry tests
$ python setup.py test or py.test
$ tox

    To get flake8 and tox, just pip install them into your virtualenv.

  3. 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

  4. Submit a pull request through the GitHub website.

Pull Request Guidelines

Before you submit a pull request, check that it meets these guidelines:

  1. Execute included pre-commit hooks
  2. The pull request should include tests.
  3. 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.
  1. The pull request should work for Python 3.8 onwards.

Tips

To run a subset of tests:

$ python -m unittest tests.test_atenvironment

Deploying

A reminder for the maintainers on how to deploy. Make sure all your changes are committed (including an entry in HISTORY.rst). Then run:

$ bumpversion patch # possible: major / minor / patch
$ git push
$ git push --tags

Jenkins will then deploy to PyPI if tests pass.

Generating Sphinx documentation

From docs directory:

sphinx-apidoc -f -o . ../tsa  # generate rst files from docstrings
make html  # generate html docs