Document GitHub moderation policies#8882
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: arnab-logs The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @arnab-logs. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/unassign will let better, more experienced minds handle this |
|
cc: @kubernetes/owners for review. |
|
/ok-to-test |
|
cc: @BenTheElder |
BenTheElder
left a comment
There was a problem hiding this comment.
thanks, really glad to see this, on first pass, minor comments only
FYI @kubernetes/steering-committee , while I think this falls in the sig contribex charter, I think this is an important gap to close for the community.
| @@ -0,0 +1,78 @@ | |||
| # GitHub Moderation | |||
|
|
|||
| Contributions to Kubernetes GitHub repositories must meet legal, technical, and behavioral standards. Submissions that fail to meet these expectations, whether due to copyright violations, low-quality automated generation, spam-like behavior, or bad-faith engagement may be moderated, restricted, or escalated according to established project processes. | |||
There was a problem hiding this comment.
What's the situation where copyright violations would result in a ban?
There was a problem hiding this comment.
I think we can elaborate a bit more on the "copyright violations" part below in the document.
For all Kubernetes project github repositories - we follow the kubernetes Repository Guidelines, and per that, our copyright attribution requirements are:
-
per our latest boilerplate header text, all kubernetes code files must include:
Copyright The Kubernetes Authors. -
in the case of donated repositories, if existing contributors have not signed the CLA and cannot be reached, the following attribution is also acceptable, accompanied by a matching NOTICE file:
Copyright <Project Authors>
anything not following the above guidelines would be considered a copyright violation.
so, we can summarize the above bit and put a link to our repo guidelines doc.
Also per our latest AI policy, attributing copyright ownership of code contributions to AI tools/systems/vendors would be considered non-compliant and fall under copyright violations.
| - Meet project quality standards. | ||
| - Be responsive to review feedback. | ||
|
|
||
| Contributions that appear automated, mechanically generated, or submitted without understanding may be closed if: |
There was a problem hiding this comment.
I think we should also mention if the submitter continues to refuse to abide by the documented policies (and link to them? e.g. https://www.kubernetes.dev/docs/guide/pull-requests/#ai-guidance)
|
/assign kubernetes/owners |
|
/cc |
This PR adds a github moderation section to document contribution standards and moderation practices for Kubernetes github repo.
@kubernetes/owners would appreciate a review when you have the time. Happy to iterate based on feedback.
Fixes #8439