Skip to content

Commit e503beb

Browse files
committed
GOVERNANCE: Fix broken security-issue links
Catch up with f562576 (*: clarify how security issues are handled, 2016-11-30, opencontainers#22). Signed-off-by: W. Trevor King <[email protected]>
1 parent 8e4c7e3 commit e503beb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

GOVERNANCE.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ This section describes generic rules and procedures for fulfilling that mandate.
88

99
## Proposing a motion
1010

11-
A maintainer SHOULD propose a motion on the [email protected] mailing list (except [security issues](#security-issues)) with another maintainer as a co-sponsor.
11+
A maintainer SHOULD propose a motion on the [email protected] mailing list (except [security issues](CONTRIBUTING.md#security-issues)) with another maintainer as a co-sponsor.
1212

1313
## Voting
1414

15-
Voting on a proposed motion SHOULD happen on the [email protected] mailing list (except [security issues](#security-issues)) with maintainers posting LGTM or REJECT.
15+
Voting on a proposed motion SHOULD happen on the [email protected] mailing list (except [security issues](CONTRIBUTING.md#security-issues)) with maintainers posting LGTM or REJECT.
1616
Maintainers MAY also explicitly not vote by posting ABSTAIN (which is useful to revert a previous vote).
1717
Maintainers MAY post multiple times (e.g. as they revise their position based on feeback), but only their final post counts in the tally.
1818
A proposed motion is adopted if two-thirds of votes cast, a quorum having voted, are in favor of the release.

0 commit comments

Comments
 (0)