Skip to content

Commit f562576

Browse files
committed
*: clarify how security issues are handled
The [email protected] mailing list is for *maintainers only*, and is to be used for technical discussion about potential security issues. It is not a place for the TOB to have votes about specification-related business, simply because it is not sane to include people who are not maintainers of projects in critical security discussions of said projects. If in the future we discover that we need to have a place to vote on security issues, the TOB can do that on their own private mailing list. For now, we should focus on making sure that security disclosures on *actual shipping code* is actually done properly. Signed-off-by: Aleksa Sarai <[email protected]>
1 parent 3eec2a6 commit f562576

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

CONTRIBUTING.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,12 @@
11
## Contribution Guidelines
22

3+
### Security issues
4+
5+
If you are reporting a security issue, do not create an issue or file a pull
6+
request on GitHub. Instead, disclose the issue responsibly by sending an email
7+
to [email protected] (which is inhabited only by the maintainers of
8+
the various OCI projects).
9+
310
### Pull requests are always welcome
411

512
We are always thrilled to receive pull requests, and do our best to

GOVERNANCE.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -31,13 +31,6 @@ A quorum is established when at least two-thirds of maintainers have voted.
3131

3232
For projects that are not specifications, a [motion to release](#release-approval) MAY be adopted if the tally is at least three LGTMs and no REJECTs, even if three votes does not meet the usual two-thirds quorum.
3333

34-
## Security issues
35-
36-
Motions with sensitive security implications MUST be proposed on the [email protected] mailing list instead of [email protected], but should otherwise follow the standard [proposal](#proposing-a-motion) process.
37-
The [email protected] mailing list includes all members of the TOB.
38-
The TOB will contact the project maintainers and provide a channel for discussing and voting on the motion, but voting will otherwise follow the standard [voting](#voting) and [quorum](#quorum) rules.
39-
The TOB and project maintainers will work together to notify affected parties before making an adopted motion public.
40-
4134
## Amendments
4235

4336
The [project governance](#project-governance) rules and procedures MAY be amended or replaced using the procedures themselves.

0 commit comments

Comments
 (0)