Contributing#

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

Types of Contributions#

Report Bugs#

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#

You can never have enough documentation! Please feel free to contribute to any part of the documentation, such as the official docs, docstrings, or even on the web in blog posts, articles, and such.

Submit Feedback#

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 nemed for local development.

  1. Download a copy of nemed locally.

  2. Install poetry

    • poetry is changing the way dependencies are managed, so as of July 2022, install v1.2.0b2 (we will transition to v1.2.0 once it is released)

    • The command below applies to UNIX systems. For Windows, refer to the poetry docs

      $ curl -sSL https://install.python-poetry.org | python3 - --version 1.2.0b2

  3. Install nemed using poetry:

    • Developers should install additional poetry groups for development:

      • docs for documentation dependencies

      • lint for linters. nemed uses flake8 and mypy for type annotations

      • test for testing utilities

      • (optional) debug for debugging tools

    $ poetry install --with=docs,lint,test

  4. Use git (or similar) to create a branch for local development and make your changes:

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

  5. When you’re done making changes, check that your changes conform to any code formatting requirements and pass any tests.

  6. Commit your changes and open a pull request.

Pull Request Guidelines#

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

  1. The pull request should include additional tests if appropriate.

  2. If the pull request adds functionality, the docs should be updated.

  3. The pull request should work for all currently supported operating systems and versions of Python.

Code of Conduct#

Please note that the nemed project is released with a Code of Conduct. By contributing to this project you agree to abide by its terms.