GOVERNANCE: Allow dev@ or PR votes for non-spec projects #35
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Email-based voting seems to be a blocker for Michael, who prefers PR-based voting for non-spec projects [1]. And the image-tools maintainers had a PR-only vote to add Aleksa as a maintainer [2]. Specifications are still recommended to only use dev@ (for increased visibility among folks with only peripheral involvement, e.g. spec consumers). But non-spec projects can backtrack more easily from decisions which have negative impacts, so we don't have to push them towards dev@ as firmly. Adopting this more-relaxed approach should help reduce barriers to non-spec projects adopting the vanilla governance procedures, which may move us towards more consistency between OCI projects [3]. [1]: http://ircbot.wl.linuxfoundation.org/eavesdrop/%23opencontainers/%23opencontainers.2017-03-20.log.html#t2017-03-20T19:54:38 [2]: opencontainers/image-tools#118 (comment) Subject: MAINTAINERS: add Aleksa Sarai [3]: opencontainers#4 Subject: Apply consistent project template across OCI Signed-off-by: W. Trevor King <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Email-based voting seems to be a blocker for @crosbymichael, who prefers PR-based voting for non-spec projects. And the image-tools maintainers had a PR-only vote to add @cyphar as a maintainer (opencontainers/image-tools#118).
Specifications are still recommended to only use
dev@(for increased visibility among folks with only peripheral involvement, e.g. spec consumers). But non-spec projects can backtrack more easily from decisions which have negative impacts, so we don't have to push them towardsdev@as firmly.Adopting this more-relaxed approach should help reduce barriers to non-spec projects adopting the vanilla governance procedures, which may move us towards more consistency between OCI projects (#4).