1) Is the list both comprehensive and compulsory? Are these actions
ones which require a vote? If so, that should be clarified.
2) Then we should remove actions that describe reinstatement, as they
make no sense if removal is not possible.
3) Mike's language seems reasonable.
4) See forked thread for detailed discussion, but in short, I agree
with the value of having a release manager. The question is whether or
not it requires a vote, since it's a brand new thing. This is related
to #1 above. I think it's safe to say that there is not yet consensus
that this action should require a vote, so if the actions listed are
intended to indicate those actions for which a vote is required, then
we should omit this for the acceptance of the initial bylaws. I also
think that "release plan" is ill-defined here, so it's hard to make
voting to establish one mandatory. We can always add it later (and I'd
probably be in favor of doing so), pending the results of the detailed
discussions in the forked thread, but I'd hate to have that one action
hold up the initial bylaws, so I don't think it should be included in
the first version.
Christopher L Tubbs II
On Tue, Mar 11, 2014 at 2:17 PM, Mike Drob <[EMAIL PROTECTED]> wrote: