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#

Test Data#

Test data is always welcome. We are looking for recordings of different AM firmware versions and different configurations.

If you have a AudioMoth recordings that you would like to share, please open an issue and attach the file. All files will be licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.

Report Bugs#

Report bugs at https://github.com/mbsantiago/metamoth/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#

metamoth could always use more documentation, whether as part of the official metamoth 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/mbsantiago/metamoth/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 metamoth for local development.

  1. Fork the metamoth repo on GitHub.

  2. Clone your fork locally:

    $ git clone git@github.com:your_name_here/metamoth.git

  3. Install your local copy into a virtualenv. Using venv is recommended:

    $ cd metamoth/
$ python3 -m venv env
$ source env/bin/activate
$ pip install -e .

  4. Create a branch for local development:

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

    Now you can make your changes locally.

  5. Install the development requirements:

    $ pip install -r requirements-dev.txt

  6. When you’re done making changes, check that your changes pass the linting and unit tests, including testing other Python versions with tox. We use make to run the tests:

    $ make lint
$ make test-all

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

  8. Submit a pull request through the GitHub website.

Pull Request Guidelines#

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

  1. The pull request should include tests.

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

  3. The pull request should work for Python 3.8, 3.9, 3.10 and 3.11.