|
17 | 17 |
|
18 | 18 | ## Introduction |
19 | 19 |
|
20 | | -Welcome to Project MONAI Deploy Application SDK (MONAI App SDK)! We're excited you're here and want to contribute. This documentation is intended for individuals and institutions interested in contributing to MONAI App SDK. MONAI App SDK 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. |
| 20 | +Welcome to Project MONAI Deploy App SDK! We're excited you're here and want to contribute. This documentation is intended for individuals and institutions interested in contributing to MONAI Deploy App SDK. MONAI Deploy App SDK 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. |
21 | 21 |
|
22 | 22 | ### Communicate with us |
23 | 23 |
|
24 | | -We are happy to talk with you about your needs for MONAI App SDK 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. If you are looking for an issue to resolve that will help Project MONAI App SDK, see the [*good first issue*](https://github.com/Project-MONAI/monai-deploy-app-sdk/labels/good%20first%20issue) and [*Contribution wanted*](https://github.com/Project-MONAI/monai-deploy-app-sdk/labels/Contribution%20wanted) labels. |
| 24 | +We are happy to talk with you about your needs for MONAI Deploy App SDK 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. If you are looking for an issue to resolve that will help Project MONAI Deploy App SDK, see the [*good first issue*](https://github.com/Project-MONAI/monai-deploy-app-sdk/labels/good%20first%20issue) and [*Contribution wanted*](https://github.com/Project-MONAI/monai-deploy-app-sdk/labels/Contribution%20wanted) labels. |
25 | 25 |
|
26 | 26 | ## The contribution process |
27 | 27 |
|
28 | 28 | _Pull request early_ |
29 | 29 |
|
30 | 30 | 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]` and/or [create a draft pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests) until it is ready for formal review. |
31 | 31 |
|
32 | | -Please note that, as per PyTorch, MONAI App SDK uses American English spelling. This means classes and variables should be: normali**z**e, visuali**z**e, colo~~u~~r, etc. |
| 32 | +Please note that, as per PyTorch, MONAI Deploy App SDK uses American English spelling. This means classes and variables should be: normali**z**e, visuali**z**e, colo~~u~~r, etc. |
33 | 33 |
|
34 | 34 | ### Preparing pull requests |
35 | 35 |
|
36 | | -To ensure the code quality, MONAI App SDK relies on several linting tools ([flake8 and its plugins](https://gitlab.com/pycqa/flake8), [black](https://github.com/psf/black), [isort](https://github.com/timothycrosley/isort)), |
| 36 | +To ensure the code quality, MONAI Deploy App SDK relies on several linting tools ([flake8 and its plugins](https://gitlab.com/pycqa/flake8), [black](https://github.com/psf/black), [isort](https://github.com/timothycrosley/isort)), |
37 | 37 | static type analysis tools ([mypy](https://github.com/python/mypy), [pytype](https://github.com/google/pytype)), as well as a set of unit/integration/system tests. |
38 | 38 |
|
39 | 39 | This section highlights all the necessary preparation steps required before sending a pull request. |
@@ -87,7 +87,7 @@ If you intend for any variables/functions/classes to be available outside of the |
87 | 87 |
|
88 | 88 | #### Unit testing |
89 | 89 |
|
90 | | -MONAI App SDK tests are located under `tests/` (it has `unit`/`integration`/`performance`/`system` subfolders.) |
| 90 | +MONAI Deploy App SDK tests are located under `tests/` (it has `unit`/`integration`/`performance`/`system` subfolders.) |
91 | 91 |
|
92 | 92 | - The unit test's file name currently follows `test_[module_name].py` or `test_[module_name]_dist.py`. |
93 | 93 | - The `test_[module_name]_dist.py` subset of unit tests requires a distributed environment to verify the module with distributed GPU-based computation. |
@@ -120,10 +120,10 @@ or (for new features that would not break existing functionality): |
120 | 120 | _If it's not tested, it's broken_ |
121 | 121 |
|
122 | 122 | All new functionality should be accompanied by an appropriate set of tests. |
123 | | -MONAI App SDK functionality has plenty of unit tests from which you can draw inspiration, |
| 123 | +MONAI Deploy App SDK functionality has plenty of unit tests from which you can draw inspiration, |
124 | 124 | and you can reach out to us if you are unsure of how to proceed with testing. |
125 | 125 |
|
126 | | -MONAI APP SDK's code coverage report is available at [CodeCov](https://codecov.io/gh/Project-MONAI/monai-deploy-app-sdk). |
| 126 | +MONAI Deploy App SDK's code coverage report is available at [CodeCov](https://codecov.io/gh/Project-MONAI/monai-deploy-app-sdk). |
127 | 127 |
|
128 | 128 | #### Building the documentation |
129 | 129 |
|
@@ -152,7 +152,7 @@ Before submitting a pull request, it is recommended to: |
152 | 152 | - [MyST with Sphinx](https://myst-parser.readthedocs.io/en/v0.15.2_a/sphinx/index.html) |
153 | 153 | - check the auto-generated documentation (by browsing the generated documents after executing `./run gen_docs_dev`) |
154 | 154 | - build HTML documentation locally (`./run gen_docs`) |
155 | | -- execute `./run gen_docs_dev` to clean temporary and final documents. |
| 155 | +- execute `./run clean_docs` to clean temporary and final documents. |
156 | 156 |
|
157 | 157 | #### Automatic code formatting |
158 | 158 |
|
|
0 commit comments