Donald,
I think this is good, I have some suggested tweaks.
On 5/17/2016 11:45 AM, Donald Sharp wrote:
> Golden Rule applies to everything we do.
>
> A person who Submit's code cannot be the person who commits it into
> quagga. Assume that this can be worked out amongst the maintainers.
>
> A maintainer can Ack or Nack code he plans to commit.
how about:
A maintainer can Ack code he/she plans to commit.
Anyone can object/Nack code by sending mail to the
submitter and the quagga development mail list
substantiating the basis for their dissent.
> Proposal for going forward:
>
> 1. Patch Submitted
> 2. If Acked goes in immediately to a development branch, by current
> maintainer.
> 3. If no-one says anything after 2 weeks, immediately get's put into
it's not immediate, so:
s/immediately/code
> a development branch by current maintainer.
assuming there's more than one:
s/by current maintainer./by one of the current maintainers.
> 4. If Nacked, dissenter and submitter must publicly work the issue out,
add "on the quagga development mail list" before the comma
> and going back to step 1 after working issue out.
> 5. If after 2 weeks, from Submittal, dissenter and submitter cannot
> figure the problem out either Dissenter or Submitter can ask for
> agenda item to be added to next monthly meeting. If disagreement
> is large enough a special meeting can be asked for as well.
>
> Format for Resolution during Meeting:
>
> 1. Discussion on alias( See #4 ) must be sufficient for Meeting to
> resolve the issue. Meeting attendees are within their rights to
> say we can't make a decision from fact's presented at the meeting.
I think you should drop this as it is covered by 4 and 5 above, and may
lead to unnecessary process arguments.
> 2. Simple Majority of those attending meeting is required for
> decision.
to cover the additional point you perhaps were making in 1 and to cover
patches that won't die, add:
A decision may be: to include the Nack'ed patch; to discuss further
(i.e., go back to 4 or schedule an additional meeting); or to not
include the patch. A Nack'ed patch may be updated and resubmitted to
address concerns raised, but cannot be a Meeting topic more than 2 times
in a 12 month period.
I suggest dropping the next line:
> Â If you can't be bothered to attend then the
> decision wasnât important to you.
> 3. Scheduling of a special meeting details must be worked out publicly
> on quagga-dev alias.
>
>
> Please discuss this on alias, and we'll finalize in a meeting for 11 am
> EDT next tuesday. If you are interested in attending please let me
> know. I'm auto inviting everyone currently on the quagga-dev monthly
> meeting.
I'll be there.
Thanks,
Lou
> donald
>
>
>
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
