Skip to content

Contributing

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/bgraedel/arcos-gui/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.

Submit Feedback

The best way to send feedback is to file an issue at https://github.com/bgraedel/arcos-gui/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 arcos-gui for local development.

  1. Fork the arcos-gui repo on GitHub.
  2. Clone your fork locally

    git clone git@github.com:your_name_here/arcos-gui.git
    
  3. Install dependencies and arcos-gui:

    pip install napari[all]
    pip install -e .[testing]
    
    If you are using conda for virtual environments, consider installing tox-conda.

  4. Create a branch for local development:

    git checkout -b 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 the tests, including testing other Python versions, with tox:

    tox
    
  6. 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
    
  7. 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.md.
  3. The pull request should work for Python 3.8, 3.9, and 3.10. Check https://github.com/bgraedel/arcos-gui/actions and make sure that the tests pass for all supported Python versions.

Deploying

A reminder for the maintainers on how to deploy:

  • Change version numbers in "init.py" and "setup.cfg".
  • Make sure all your changes are committed.
  • Create a version tag. The tag will be used as the version string for your package.

make it meaningful: https://semver.org/

git tag -a v0.1.0 -m "v0.1.0"

# make sure to use follow-tags so that the tag also gets pushed to GitHub
git push --follow-tags

GitHub Actions will then deploy to PyPI if tests pass.