CONTRIBUTING.md

Contributing

Welcome to wd_fw_update contributor's guide.

This document focuses on getting any potential contributor familiarized with the development processes, but other kinds of contributions are also appreciated.

If you are new to using git or have never collaborated in a project previously, please have a look at contribution-guide.org. Other resources are also listed in the excellent guide created by FreeCodeCamp ¹.

Please notice, all users and contributors are expected to be open, considerate, reasonable, and respectful. When in doubt, Python Software Foundation's Code of Conduct is a good reference in terms of behavior guidelines.

Issue Reports

If you experience bugs or general issues with wd_fw_update, please have a look on the issue tracker. If you don't see anything useful there, please feel free to fire an issue report.

:::{tip} Please don't forget to include the closed issues in your search. Sometimes a solution was already reported, and the problem is considered solved. :::

New issue reports should include information about your programming environment (e.g., operating system, Python version) and steps to reproduce the problem. Please try also to simplify the reproduction steps to a very minimal example that still illustrates the problem you are facing. By removing other factors, you help us to identify the root cause of the issue.

Documentation Improvements

You can help improve wd_fw_update docs by making them more readable and coherent, or by adding missing information and correcting mistakes.

wd_fw_update documentation uses Sphinx as its main documentation compiler. This means that the docs are kept in the same repository as the project code, and that any documentation update is done in the same way was a code contribution.

:::{tip} Please notice that the GitHub web interface provides a quick way of propose changes in wd_fw_update's files. While this mechanism can be tricky for normal code contributions, it works perfectly fine for contributing to the docs, and can be quite handy.

  If you are interested in trying this method out, please navigate to
  the `docs` folder in the source [repository], find which file you
  would like to propose changes and click in the little pencil icon at the
  top, to open [GitHub's code editor]. Once you finish editing the file,
  please write a message in the form at the bottom of the page describing
  which changes have you made and what are the motivations behind them and
  submit your proposal.

:::

When working on documentation changes in your local machine, you can compile them using make.

cd docs
pip install -r requirements.txt

make html

Submit an issue

Before you work on any non-trivial code contribution it's best to first create a report in the issue tracker to start a discussion on the subject. This often provides additional considerations and avoids unnecessary work.

Create an environment

Before you start coding, we recommend creating an isolated virtual environment to avoid any problems with your installed Python packages.

conda create -n wd_fw_update python=3 six virtualenv
conda activate wd_fw_update

Clone the repository

1. Create an user account on GitHub if you do not already have one.

2. Fork the project repository: click on the Fork button near the top of the page. This creates a copy of the code under your account on GitHub.

3. Clone this copy to your local disk:

   git clone [email protected]:YourLogin/wd_fw_update.git
   cd wd_fw_update
   

4. You should run:

   pip install -U pip setuptools -e .
   

   to be able to import the package under development in the Python REPL.

5. Install pre-commit:

   pip install pre-commit
   pre-commit install
   

   wd_fw_update comes with a lot of hooks configured to automatically help the developer to check the code being written.

Implement your changes

1. Create a branch to hold your changes:

   git checkout -b my-feature
   

   and start making changes. Never work on the main branch!

2. Start your work on this branch. Don't forget to add docstrings to new functions, modules and classes, especially if they are part of public APIs.

3. Add yourself to the list of contributors in AUTHORS.rst.

4. When you’re done editing, do:

   git add <MODIFIED FILES>
   git commit
   

   to record your changes in git.

   Please make sure to see the validation messages from pre-commit and fix any eventual issues. This should automatically use flake8/black to check/fix the code style in a way that is compatible with the project.

   :::{important} Don't forget to add documentation in case your contribution adds an additional feature and is not just a bugfix.

   Moreover, writing a descriptive commit message is highly recommended. In case of doubt, you can check the commit history with:

   git log --graph --decorate --pretty=oneline --abbrev-commit --all
   

   to look for recurring communication patterns. :::

Submit your contribution

1. If everything works fine, push your local branch to the remote server with:

   git push -u origin my-feature
   

2. Go to the web page of your fork and click "Create pull request" to send your changes for review.

   Find more detailed information in creating a PR. You might also want to open the PR as a draft first and mark it as ready for review after the feedbacks from the continuous integration (CI) system or any required fixes.

Maintainer tasks

Releases

If you are part of the group of maintainers and have correct user permissions on PyPI, the following steps can be used to release a new version for wd_fw_update:

1. Make sure all unit tests are successful.
2. Tag the current commit on the main branch with a release tag, e.g., v1.2.3.
3. Push the new tag to the upstream repository, e.g., git push upstream v1.2.3
4. Clean up the dist and build folders with tox -e clean (or rm -rf dist build) to avoid confusion with old builds and Sphinx docs.
5. Run tox -e build and check that the files in dist have the correct version (no .dirty or git hash) according to the git tag. Also check the sizes of the distributions, if they are too big (e.g., > 500KB), unwanted clutter may have been accidentally included.
6. Run tox -e publish -- --repository pypi and check that everything was uploaded to PyPI correctly.

Footnotes

1. Even though, these resources focus on open source projects and communities, the general ideas behind collaborating with other developers to collectively create software are general and can be applied to all sorts of environments, including private companies and proprietary code bases. ↩