Skip to content

project-governance: Make voting more generic#2

Open
wking wants to merge 1 commit intophilips:release-approval-processfrom
wking:generic-voting
Open

project-governance: Make voting more generic#2
wking wants to merge 1 commit intophilips:release-approval-processfrom
wking:generic-voting

Conversation

@wking
Copy link

@wking wking commented Jun 25, 2016

This is useful for more than release approval. For example, it's useful for updating the project governance document itself.

I've also tried to address Jason's other points, except for defining a "breaking change" (since that is tied up in opencontainers#16).

New wording about motions and whatnot is pulled from Roberts', see proposing a motion (RRoO I.4, p33) and seconding a motion (RRoO I.5, p36).

The subject templates I just made up on my own after thinking over the initial proposal emails (e.g. this one). I also pulled in the one-sentence pattern since I was touching so much.

Feel free to pick and choose from this commit, since it isn't particularly atomic. You can also tell me which portions you like (or don't) and I'll work to isolate them in separate PRs.

This is useful for more than release approval.  For example, it's
useful for updating the project governance document itself [1].

I've also tried to address Jason's other points, except for defining a
"breaking change" (since that is tied up in [2]).

New wording about motions and whatnot is pulled from Roberts' [3], see
proposing a motion (RRoO I.4, p33) and seconding a motion (RRoO I.5,
p36).

The subject templates I just made up on my own after thinking over the
initial proposal emails (e.g. [4]).  I also pulled in the one-sentence
pattern [5] since I was touching so much.

[1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/ik3MIDWq4Us/Zx1JUStXBAAJ
     Subject: Re: Vote Required: OCI Image Spec Release Process
     Date: Fri, 24 Jun 2016 16:58:58 -0700
     Message-ID: <CAFi6z1HAkKbnMoAXubyGusQJ_MromgpQ4qHCQ3R9_NwZNYBX5w@mail.gmail.com>
[2]: opencontainers#16
[3]: http://archive.org/details/Robertsrulesofor00robe_201303
[4]: https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/ik3MIDWq4Us
     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>
[5]: opencontainers#15 (comment)

Signed-off-by: W. Trevor King <wking@tremily.us>
@wking
Copy link
Author

wking commented Jun 25, 2016

When porting this to project-template or getting it adopted by a project, I'd suggest splitting the generic “project governance” rules into GOVERNANCE.md or some such with an initial bootstrapping vote on just the generic procedure.

Once that's adopted (assuming it is), you can use it to propose the release rules as a separate motion. I'd store those in project-template under motions/ or policy/ or some such.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant