From 0bb1af505b6f4e5428617fe88323cf39fbe63d03 Mon Sep 17 00:00:00 2001 From: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> Date: Mon, 7 Sep 2026 16:30:33 +0100 Subject: [PATCH 1/4] Add Tool-Assisted Contribution Policy Signed-off-by: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> --- CONTRIBUTING.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1fb68b4b58..4944cb635c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -27,6 +27,20 @@ We are happy to talk with you about your needs for MONAI and your ideas for cont MONAI is part of [PyTorch Ecosystem](https://pytorch.org/ecosystem/), and mainly based on the PyTorch and Numpy libraries. These libraries implement what we consider to be best practice for general scientific computing and deep learning functionality. MONAI builds on these 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](https://pytorch.org/docs/stable/community/contribution_guide.html). +## Tool-Assisted Contribution Policy + +Contributions generated wholly or in part by generative tools, whether AI-based or not, are acceptable in MONAI so long as the submitting author can take responsibility for the content as if they wrote it themselves. This implies that submitters must review all submitted content, understand the content, and ensure the content is appropriate and fit for purpose. + +Contributors must therefore take responsibility such that they can honestly sign the Developer Certificate of Origin (discussed below). All submitted code and data must fall under open source/data licensing conditions which the contributor is required to verify, and no other legal constraints are present for the proposed content. Additionally, care must be take with AI and agentic systems to ensure code standards are adhered to, hallucinations are not being introduced into the code, and that existing open work from other contributors is not being duplicated. + +Attribution of AI-generated content should be included, for example with trailers in commit messages such as `Assisted-by: Some-Tool `. AI-generated comments or other content in issues or PRs should be clearly labelled as such, but there is the expectation that discussion in the review process is with the submitter themselves. + +Code review and analysis can be assisted through the use of tools, for example linting or formatting tools. Output from such tools does not form part of the submission but should be clearly labelled. The key emphasis is that these tools assist and do not replace human review, so submitters and reviewers must consider what might be missed by these tools, or what might be hallucinated. It might be helpful to review code with a different tool from one used for generation. + + + + + ## The contribution process *Pull request early* From 573ce28d52bad243c6d49fe275caf3b2a185ed94 Mon Sep 17 00:00:00 2001 From: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> Date: Mon, 7 Sep 2026 16:34:18 +0100 Subject: [PATCH 2/4] Cleanup Signed-off-by: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> --- CONTRIBUTING.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4944cb635c..aff04f8ad0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -37,10 +37,6 @@ Attribution of AI-generated content should be included, for example with trailer Code review and analysis can be assisted through the use of tools, for example linting or formatting tools. Output from such tools does not form part of the submission but should be clearly labelled. The key emphasis is that these tools assist and do not replace human review, so submitters and reviewers must consider what might be missed by these tools, or what might be hallucinated. It might be helpful to review code with a different tool from one used for generation. - - - - ## The contribution process *Pull request early* From 5a87afc54b7b4b03d0ccdc60e5ca4d4e38c17e63 Mon Sep 17 00:00:00 2001 From: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> Date: Mon, 7 Sep 2026 16:54:25 +0100 Subject: [PATCH 3/4] Update Signed-off-by: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index aff04f8ad0..a2b2a7e86e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -29,13 +29,13 @@ MONAI is part of [PyTorch Ecosystem](https://pytorch.org/ecosystem/), and mainly ## Tool-Assisted Contribution Policy -Contributions generated wholly or in part by generative tools, whether AI-based or not, are acceptable in MONAI so long as the submitting author can take responsibility for the content as if they wrote it themselves. This implies that submitters must review all submitted content, understand the content, and ensure the content is appropriate and fit for purpose. +Contributions generated wholly or in part by generative tools, whether AI-based or not, are acceptable in MONAI so long as the submitting author can take responsibility for the content as if they wrote it themselves. This implies that contributors must review all submitted content, understand the content, ensure the content is appropriate and fit for purpose, and write the documentation and other information materials themselves. -Contributors must therefore take responsibility such that they can honestly sign the Developer Certificate of Origin (discussed below). All submitted code and data must fall under open source/data licensing conditions which the contributor is required to verify, and no other legal constraints are present for the proposed content. Additionally, care must be take with AI and agentic systems to ensure code standards are adhered to, hallucinations are not being introduced into the code, and that existing open work from other contributors is not being duplicated. +Contributors must therefore take responsibility such that they can honestly sign the Developer Certificate of Origin (discussed below). All submitted code and data must be available through open source/data licensing conditions which the contributor is required to verify, and which permits integration into MONAI. No other legal constraints can be present for the proposed content. Additionally, care must be taken with AI and agentic systems to ensure code standards are adhered to, hallucinations are not being introduced into the code, and that existing open work from other contributors is not being duplicated. Attribution of AI-generated content should be included, for example with trailers in commit messages such as `Assisted-by: Some-Tool `. AI-generated comments or other content in issues or PRs should be clearly labelled as such, but there is the expectation that discussion in the review process is with the submitter themselves. -Code review and analysis can be assisted through the use of tools, for example linting or formatting tools. Output from such tools does not form part of the submission but should be clearly labelled. The key emphasis is that these tools assist and do not replace human review, so submitters and reviewers must consider what might be missed by these tools, or what might be hallucinated. It might be helpful to review code with a different tool from one used for generation. +Code review and analysis can be assisted through the use of tools, for example linting or formatting tools. Diagnostic output from such tools does not form part of the submission but should be clearly labelled. The key emphasis is that these tools assist and do not replace human review, so contributors and reviewers must consider what might be missed by these tools, or what might be hallucinated. It might be helpful to review code with a different tool from one used for generation. ## The contribution process From 2802c592f81184e73b86c2ab2567395d439bd765 Mon Sep 17 00:00:00 2001 From: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> Date: Mon, 7 Sep 2026 16:57:55 +0100 Subject: [PATCH 4/4] Update CONTRIBUTING.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Eric Kerfoot <17726042+ericspod@users.noreply.github.com> --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a2b2a7e86e..f29014e2c0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -31,7 +31,7 @@ MONAI is part of [PyTorch Ecosystem](https://pytorch.org/ecosystem/), and mainly Contributions generated wholly or in part by generative tools, whether AI-based or not, are acceptable in MONAI so long as the submitting author can take responsibility for the content as if they wrote it themselves. This implies that contributors must review all submitted content, understand the content, ensure the content is appropriate and fit for purpose, and write the documentation and other information materials themselves. -Contributors must therefore take responsibility such that they can honestly sign the Developer Certificate of Origin (discussed below). All submitted code and data must be available through open source/data licensing conditions which the contributor is required to verify, and which permits integration into MONAI. No other legal constraints can be present for the proposed content. Additionally, care must be taken with AI and agentic systems to ensure code standards are adhered to, hallucinations are not being introduced into the code, and that existing open work from other contributors is not being duplicated. +Contributors must therefore take responsibility such that they can honestly sign the Developer Certificate of Origin (discussed below). All submitted code and data must be available through open-source/open-data licensing conditions which the contributor is required to verify, and which permit integration into MONAI. No other legal constraints can be present for the proposed content. Additionally, care must be taken with AI and agentic systems to ensure code standards are adhered to, hallucinations are not being introduced into the code, and that existing open work from other contributors is not being duplicated. Attribution of AI-generated content should be included, for example with trailers in commit messages such as `Assisted-by: Some-Tool `. AI-generated comments or other content in issues or PRs should be clearly labelled as such, but there is the expectation that discussion in the review process is with the submitter themselves.