Skip to content

Commit 2ec91e2

Browse files
committed
docs(governance): how maintainers welcome new contributors and handle sanctions
Maintainers had no written guidance for a first-time contributor, or for the rare case where a contributor is clearly covered by US sanctions. The first section sets the basics: a timely reply, help with DCO, a safety look before approving CI, honest reviews, and no questions about nationality or employer. The second follows the Linux Foundation OFAC guidance: no screening, act only on what is apparent, accept a patch on its merits without working with the author, and ask LF legal. Assisted-by: LLM Signed-off-by: tym83 <[email protected]>
1 parent 6144805 commit 2ec91e2

1 file changed

Lines changed: 49 additions & 0 deletions

File tree

‎GOVERNANCE.md‎

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,55 @@ If a maintainer is no longer interested in or cannot perform the duties
8989
listed above, they should move themselves to emeritus status.
9090
If necessary, this can also occur through the decision-making process outlined below.
9191

92+
### Welcoming new contributors
93+
94+
A first contribution is often the moment someone decides whether to stay.
95+
When a new contributor opens an issue or a pull request:
96+
97+
* Respond within two working days, even if only to say who will review it
98+
and when.
99+
* Point to the contributing guide and help with the mechanics. If the DCO
100+
check fails, explain how to fix it: `git commit --amend --signoff` for the
101+
last commit, or `git rebase --signoff main` for several.
102+
* Before approving CI runs for a first-time contributor, read the diff and
103+
make sure it does not touch workflows, secrets or release tooling in a way
104+
that could run untrusted code with project credentials.
105+
* Review against the same standards as any other change, and explain the
106+
reason behind each requested change. If the change is not going to be
107+
accepted, say so early and say why, rather than leaving it open.
108+
* Suggest a good next step: a `good first issue`, a related bug, or a
109+
documentation gap.
110+
* Do not ask contributors about their nationality, location or employer.
111+
Contributions are judged on their merit.
112+
113+
### Sanctions compliance
114+
115+
Cozystack is a Linux Foundation project and follows the Linux Foundation's
116+
guidance on US sanctions (OFAC). Maintainers do not screen contributors or
117+
ask where they live or who they work for; they act only on what is already
118+
apparent, for example from a GitHub profile, an email domain or a
119+
`Signed-off-by` line.
120+
121+
If it is apparent that a contributor is on the OFAC SDN list, works for or on
122+
behalf of an organisation on that list (including organisations 50% or more
123+
owned by listed parties), or is located in a comprehensively sanctioned
124+
region:
125+
126+
* Do not work with them back and forth on the change: no joint debugging,
127+
no iterative review of their patch, no tailored support.
128+
* A patch they submitted may still be evaluated on its technical merit,
129+
modified and merged by maintainers on their own.
130+
* Do not grant them project roles (reviewer, approver, maintainer) and do
131+
not make payments to them.
132+
* Do not discuss the case in public. Tell the other maintainers privately
133+
and ask the Linux Foundation for advice at [email protected].
134+
135+
Public channels stay open to everyone. Answer questions there in general
136+
terms that are useful to all readers.
137+
138+
See the Linux Foundation guide on OFAC sanctions and open source:
139+
https://bestpractices.linuxfoundation.org/regulatory/ofac/
140+
92141
### Becoming a Maintainer
93142

94143
Anyone can become a Cozystack maintainer. Maintainers should be extremely

0 commit comments

Comments
 (0)