GOVERNANCE: Drop the co-sponsor requirement #19
Conversation
This file contains 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
In OCI votes to date [1–11], I have only seen a co-sponsor in [9]. I haven't been able to turn up local motivation for this requirement, and don't expect rogue maintainers to flood the list with spam motions now that the co-sponsor requirement has been lifted ;). [1]: https://groups.google.com/a/opencontainers.org/d/msg/tob/WXk1uTgfXrs/-xICOdi1BwAJ Subject: Proposal for a new project: OCI Image Format Spec Date: Fri, 26 Feb 2016 00:33:07 +0000 Message-ID: <CAD2oYtPCZRUXOER-Fz7WKsnNwYA-PoPmCG59jD1i3=xgYnGLZw@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/tob/h2x5aLVX2PY/qpry5QXABAAJ Subject: Proposal for a new project: OCI Image Format Spec (v2) Date: Fri, 18 Mar 2016 05:01:17 +0000 Message-ID: <CAD2oYtMRhJhGBDwt77_L7Ac4LJ22Zsys+Q=zJLvYA1dwcmLE0w@mail.gmail.com> [3]: https://groups.google.com/a/opencontainers.org/d/msg/tob/KGyPpu8YfNk/JnOvOEdSBQAJ Subject: ACTION: Proposal for a new project: OCI Image Format Spec (v3) Date: Sun, 20 Mar 2016 01:41:27 +0000 Message-ID: <CAD2oYtNiOgCgLgZk--4bfrdywTmwP=bqSxvkSJ-rv=PTEoaTag@mail.gmail.com> [4]: https://groups.google.com/a/opencontainers.org/d/msg/dev/XXxKY7w4YA4/KLgQX6iSAQAJ Subject: Proposal: Rename Image Spec milestone v1.0.0-rc1 to v0.3.0 Date: Wed, 15 Jun 2016 23:35:12 +0000 Message-ID: <CAD2oYtPoAvY8JTrz2Yi1zwjOyOuRR5faY=9jH=_QmsS_rwwbFA@mail.gmail.com> [5]: https://groups.google.com/a/opencontainers.org/d/msg/dev/ik3MIDWq4Us/AqS5GUfuAwAJ Subject: Vote Required: OCI Image Spec Release Process Date: Thu, 23 Jun 2016 15:56:40 +0000 Message-ID: <CAD2oYtNnW+hP7Q3NPBdYHOKfigU0pvbgcphKPhRB=ZfQBwX8VA@mail.gmail.com> [6]: https://groups.google.com/a/opencontainers.org/d/msg/dev/a90Nx4Md6R4/KG2WiSr3AwAJ Subject: Vote Required: OCI runC Release Process Date: Thu, 23 Jun 2016 18:39:32 +0000 Message-ID: <CAD2oYtOOB7zn-Bhp2Xgt+Wv4u=+_RAgEt=ic+60Qf=Z3j0WbQQ@mail.gmail.com> [7]: https://groups.google.com/a/opencontainers.org/d/msg/dev/FoYcImNQg4c/Re0guPPHBQAJ Subject: [image-spec VOTE]: Tag ca58cdf as v0.3.0 (closes 2016-07-06 17:00 UTC) Date: Wed, 29 Jun 2016 16:36:49 +0000 Message-ID: <CAD2oYtNUMZ_E=NyvCq9_N=SLW75aR1QkLsb0+Uz6aSQr8c0-0Q@mail.gmail.com> [8]: https://groups.google.com/a/opencontainers.org/d/msg/tob/ftfzwhD6DpA/QFCi3siaDQAJ Subject: [project-template VOTE]: Merge governance and release docs at 56abe12 (closes 2016-07-19 19:00 UTC) Date: Tue, 12 Jul 2016 19:26:40 +0000 Message-ID: <CAD2oYtOVOGJFPG43eXty_dWudywXpWVQAa1vXQT004TrQ8ze5w@mail.gmail.com> [9]: https://groups.google.com/a/opencontainers.org/d/msg/dev/XwIb5czltSE/GKs-6FkGCgAJ Subject: [image-spec VOTE]: Tag 2bae0dc as v0.4.0 (closes 2016-08-07 16:20 UTC) Date: Wed, 10 Aug 2016 12:22:33 -0400 Message-ID: <CAN6Zp5wJX9+7GFdf0=8A9Ms8grvo9sk0wE16wBbci5qUPXXFag@mail.gmail.com> [10]: https://groups.google.com/a/opencontainers.org/d/msg/dev/fiDgBKTR9f4/a6B3C-F6DAAJ Subject: [runc VOTE]: Tag 6df383c2f881fbdeb as 1.0.0-rc2 Date: Thu, 18 Aug 2016 09:20:25 -0700 Message-ID: <CADe0YkvxkFwF_HepCmz2iWENh3v2TVuYSECStdjeVgnGXKLM8Q@mail.gmail.com> [11]: https://groups.google.com/a/opencontainers.org/d/msg/dev/5qj2hATVxew/T9xFOcO-EAAJ Subject: [runtime-spec VOTE]: Tag d3c3763b as v1.0.0-rc2 (closes 2016-09-08 13:47 UTC) Date: Thu, 1 Sep 2016 09:49:24 -0400 Message-ID: <CANcsyS7exPPW17=o0qn6XHKesWm1h_599Fic5rBefkQgTdf4kA@mail.gmail.com> Signed-off-by: W. Trevor King <wking@tremily.us>
wking
force-pushed
the
drop-co-sponsor-requirement
branch
from
56a7c93 to
5c5a822
Compare
|
I recommend batching this with #18 for an all-maintainer vote. |
wking
added a commit
to wking/ocitools-v2
that referenced
this pull request
Nov 17, 2016
…late into merge-project-template To fulfill the TOB's [1]: Both of the proposed projects would incorporate the Governance and Releases processes from the OCI project template: https://github.com/opencontainers/project-template. which was approved with this vote [2]. Generated with: $ git pull git://github.com/opencontainers/project-template.git master $ git checkout --ours .pullapprove.yml README.md $ git checkout --theirs CONTRIBUTING.md LICENSE MAINTAINERS_GUIDE.md $ git add .pullapprove.yml CONTRIBUTING.md LICENSE MAINTAINERS_GUIDE.md README.md $ git commit I think there are a few improvements we could make to these template docs [3,4,5], but the TOB vote happened before I'd floated those. If/when they land, we can pull the updated versions into this repository via a follow-up merge. * 'master' of git://github.com/opencontainers/project-template: (33 commits) .pullapprove.yml: Reset on push, ignore authors, and require sign-offs GOVERNANCE.md: fix typo GOVERNANCE and RELEASES: split the files project-governance: Make voting more generic proposals: release approval process explain security@ email proposal: fix a typo proposals: release-approval-process fix a grammar thing release-approval: Add non-spec unanimous quorum reduction release-approval: Shuffle to make more DRY proposals: release-approval-process: fixup additional typos proposals: release approval process: improve REJECT feedback proposals: release approval process: add information to projects proposals: release approval process: add language about mailing list proposals: release approval process: add quorum language proposals: release-approval-process: add voting members language proposals: release approval process: clarify utility of GitHub proposals: release approval process: use consistent language for rejects proposals: release approval process: one month pre-releases proposals: release approval process 3 rcs required proposals: release approval process to one week for apps ... Conflicts: .pullapprove.yml CONTRIBUTING.md LICENSE MAINTAINERS_GUIDE.md README.md [1]: https://github.com/opencontainers/tob/blob/8997b1aa221b3b61d4305bede41c257b879bdeeb/proposals/tools.md#governance-and-releases [2]: https://groups.google.com/a/opencontainers.org/forum/#!topic/tob/rZ4luMa-pxY Subject: VOTE Required: approve new projects: image-tools, runtime-tools Date: Wed, 07 Sep 2016 22:37:32 +0000 Message-ID: <CAD2oYtMLMFQouEVU7HTO-EKnW6vKu82dGT+0mziXZzCyqngj=A@mail.gmail.com> [3]: opencontainers/project-template#18 Subject: GOVERNANCE: Proposing a motion is a LGTM by default [4]: opencontainers/project-template#19 Subject: GOVERNANCE: Drop the co-sponsor requirement [5]: opencontainers/project-template#20 Subject: MAINTAINERS_GUIDE|CONTRIBUTING: Make generic enough for all OCI Projects
wking
added a commit
to wking/ocitools-v2
that referenced
this pull request
Nov 17, 2016
…late into merge-project-template To fulfill the TOB's [1]: Both of the proposed projects would incorporate the Governance and Releases processes from the OCI project template: https://github.com/opencontainers/project-template. which was approved with this vote [2]. Generated with: $ git pull git://github.com/opencontainers/project-template.git master $ git checkout --ours .pullapprove.yml README.md $ git checkout --theirs CONTRIBUTING.md LICENSE MAINTAINERS_GUIDE.md $ git add .pullapprove.yml CONTRIBUTING.md LICENSE MAINTAINERS_GUIDE.md README.md $ git commit I think there are a few improvements we could make to these template docs [3,4,5], but the TOB vote happened before I'd floated those. If/when they land, we can pull the updated versions into this repository via a follow-up merge. * 'master' of git://github.com/opencontainers/project-template: (33 commits) .pullapprove.yml: Reset on push, ignore authors, and require sign-offs GOVERNANCE.md: fix typo GOVERNANCE and RELEASES: split the files project-governance: Make voting more generic proposals: release approval process explain security@ email proposal: fix a typo proposals: release-approval-process fix a grammar thing release-approval: Add non-spec unanimous quorum reduction release-approval: Shuffle to make more DRY proposals: release-approval-process: fixup additional typos proposals: release approval process: improve REJECT feedback proposals: release approval process: add information to projects proposals: release approval process: add language about mailing list proposals: release approval process: add quorum language proposals: release-approval-process: add voting members language proposals: release approval process: clarify utility of GitHub proposals: release approval process: use consistent language for rejects proposals: release approval process: one month pre-releases proposals: release approval process 3 rcs required proposals: release approval process to one week for apps ... Conflicts: .pullapprove.yml CONTRIBUTING.md LICENSE MAINTAINERS_GUIDE.md README.md [1]: https://github.com/opencontainers/tob/blob/8997b1aa221b3b61d4305bede41c257b879bdeeb/proposals/tools.md#governance-and-releases [2]: https://groups.google.com/a/opencontainers.org/forum/#!topic/tob/rZ4luMa-pxY Subject: VOTE Required: approve new projects: image-tools, runtime-tools Date: Wed, 07 Sep 2016 22:37:32 +0000 Message-ID: <CAD2oYtMLMFQouEVU7HTO-EKnW6vKu82dGT+0mziXZzCyqngj=A@mail.gmail.com> [3]: opencontainers/project-template#18 Subject: GOVERNANCE: Proposing a motion is a LGTM by default [4]: opencontainers/project-template#19 Subject: GOVERNANCE: Drop the co-sponsor requirement [5]: opencontainers/project-template#20 Subject: MAINTAINERS_GUIDE|CONTRIBUTING: Make generic enough for all OCI Projects Signed-off-by: W. Trevor King <wking@tremily.us>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In OCI votes to date (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11), I have only seen a co-sponsor in 9.
I haven't been able to turn up local motivation for this requirement, and don't expect rogue maintainers to flood the list with spam motions now that the co-sponsor requirement has been lifted ;).