Skip to content

Latest commit

 

History

History
168 lines (131 loc) · 9.31 KB

CONTRIBUTING.md

File metadata and controls

168 lines (131 loc) · 9.31 KB

Introduction

This documentation is intended for individuals and institutions interested in contributing to MONAI. MONAI is an open-source project and, as such, its success relies on its community of contributors willing to keep improving it. Your contribution will be a valued addition to the code base; we simply ask that you read this page and understand our contribution process, whether you are a seasoned open-source contributor or whether you are a first-time contributor.

Communicate with us

We are happy to talk with you about your needs for MONAI and your ideas for contributing to the project. One way to do this is to create an issue discussing your thoughts. It might be that a very similar feature is under development or already exists, so an issue is a great starting point.

Does it belong in PyTorch / Ignite instead of MONAI?

MONAI is based on the Ignite and PyTorch frameworks. These frameworks implement what we consider to be best practice for general deep learning functionality. MONAI builds on these frameworks with a strong focus on medical applications. As such, it is a good idea to consider whether your functionality is medical-application specific or not. General deep learning functionality may be better off in PyTorch; you can find their contribution guidelines here.

The contribution process

Pull request early

We encourage you to create pull requests early. It helps us track the contributions under development, whether they are ready to be merged or not. Change your pull request's title to begin with [WIP] until it is ready for formal review.

Submitting pull requests

All code changes to the master branch must be done via pull requests.

  1. Create a new ticket or take a known ticket from the issue list.
  2. Check if there's already a branch dedicated to the task.
  3. If the task has not been taken, create a new branch in your fork of the codebase named [ticket_id]-[task_name]. For example, branch name 19-ci-pipeline-setup corresponds to issue #19. Ideally, the new branch should be based on the latest master branch.
  4. Make changes to the branch (use detailed commit messages if possible). If the changes introduce new features, make sure that you write unit tests.
  5. Create a new pull request from the task branch to the master branch, with detailed descriptions of the purpose of this pull request.
  6. Check the CI/CD status of the pull request, make sure all CI/CD tests passed.
  7. Wait for reviews; if there are reviews, make point-to-point responses, make further code changes if needed.
  8. If there're conflicts between the pull request branch and the master branch, pull the changes from the master and resolve the conflicts locally .
  9. Reviewer and contributor may have discussions back and forth until all comments addressed.
  10. Wait for the pull request to be merged.

Coding style

Coding style is checked by flake8, using a flake8 configuration similar to PyTorch's.

License information: all source code files should start with this paragraph:

# Copyright 2020 MONAI Consortium
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

Utility functions

MONAI provides a set of generic utility functions and frequently used routines. These are located in monai/utils and in the module folders such as networks/utils.py. Users are encouraged to use these common routines to improve code readability and reduce the code maintenance burdens.

Notably,

  • monai.module.export decorator can make the module name shorter when importing, for example, import monai.transforms.Spacing is the equivalent of monai.transforms.transforms.Spacing if class Spacing defined in file monai/transforms/transforms.py is decorated with @export("monai.transforms").

Building the documentation

To build documentation via Sphinx indocs/ folder:

# install the doc-related dependencies
pip install --upgrade pip
pip install -r docs/requirements.txt

# build the docs
cd docs/
make html

The above commands build html documentation. Type make help for all supported formats, type make clean to remove the current build files.

When new classes or methods are added, it is recommended to:

  • build html documentation locally,
  • check the auto-generated documentation from python docstrings,
  • edit relevant .rst files in docs/source accordingly.

Unit testing

MONAI tests are located under tests/.

  • The unit test's file name follows test_[module_name].py.
  • The integration test's file name follows integration_[workflow_name].py.

A bash script (runtests.sh) is provided to run all tests locally Please run ./runtests.sh -h to see all options.

To run a particular test, for example tests/test_dice_loss.py:

python -m tests.test_dice_loss

Before submitting a pull request, we recommend that all linting and unit tests should pass, by running the following commands locally:

flake8 . --count --statistics
./runtests.sh --coverage

If it's not tested, it's broken

All new functionality should be accompanied by an appropriate set of tests. MONAI functionality has plenty of unit tests from which you can draw inspiration, and you can reach out to us if you are unsure of how to proceed with testing.

MONAI's code coverage report is available at CodeCov.

The code reviewing process

Reviewing pull requests

All code review comments should be specific, constructive, and actionable.

  1. Check the CI/CD status of the pull request, make sure all CI/CD tests passed before reviewing (contact the branch owner if needed).
  2. Read carefully the descriptions of the pull request and the files changed, write comments if needed.
  3. Make in-line comments to specific code segments, request for changes if needed.
  4. Review any further code changes until all comments addressed by the contributors.
  5. Merge the pull request to the master branch.
  6. Close the corresponding task ticket on the issue list.

Admin tasks

Release a new version

  • Prepare a release note.
  • Checkout a new branch releases/[version number] from the master branch.
  • Create a tag, for example git tag -a 0.1a -m "version 0.1a".
  • Push the tag to the codebase, for example git push origin 0.1a. This step will trigger package building and testing. The resultant packages are automatically uploaded to TestPyPI. The packages are also available for downloading as repository's artifacts (e.g. the file at https://github.com/Project-MONAI/MONAI/actions/runs/66570977).
  • Check the release test at TestPyPI, download the artifacts when the CI finishes.
  • Upload the packages to PyPI. This could be done manually by twine upload dist/*, given the artifacts are unzipped to the folder dist/.
  • Publish the release note.

Note that the release should be tagged with a PEP440 compliant semantic versioning number.

If any error occurs during the release process, first checkout a new branch from the master, make PRs to the master to fix the bugs via the regular contribution procedure. Then rollback the release branch and tag:

  • remove any artifacts (website UI) and tag (git tag -d and git push origin -d).
  • reset the releases/[version number] branch to the latest master:
git checkout master
git pull origin master
git checkout releases/[version number]
git reset --hard master

Finally, repeat the tagging and TestPyPI uploading process.