Donald,
This is slightly different than I expected, but looks workable to me.
All,
What do you think of trying this out in a new branch tree, say
something like the following?
/new-process/{mainline,/patch-tracking/<patch_set>}
Note, I mainline to disambiguate with the real master.
Once Martin has the bi-direction mirror running we can try using
github and pull requests to facilitate.
Thoughts?
Lou
On 5/19/2016 7:47 AM, Donald Sharp wrote:
>
> Adjusted proposal based upon feedback.
>
> ---------------------
>
> 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.
>
> Anyone can ACK/NACK code by sending mail to the submitter and the
> quagga-dev alias substantiating the basis for dissent.
>
> Proposal for going forward:
>
> 1. Patch Submitted
> 1. Automatic testing is being applied to incoming patches on
> quagga-dev. If testing indicates a failure then the patch
> must be fixed and resubmitted.
> 2. If Acked goes in immediately to a development branch, by current
> maintainer.
> 3. If no-one says anything after 2 weeks, code get’s put into a
> development branch by one of the current maintainers.
> 4. If Nacked, dissenter and submitter must publicly work the issue
> out on the quagga-dev alias, 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. Simple Majority of those attending meeting is required for
> decision. Decision results can be: Inclusion of the Nak’ed patch,
> further discussion( step #4 above ), or exclusion of the patch.
> 2. Scheduling of a special meeting details must be worked out
> publicly on quagga-dev alias.
> 3. A Patch cannot be a meeting topic more than 2 times in a 12 month
> period.
>
>
> On Tue, May 17, 2016 at 11:45 AM, Donald Sharp
> <[email protected] <mailto:[email protected]>> 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.
>
> 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 a development branch by current maintainer.
> 4. If Nacked, dissenter and submitter must publicly work the
> issue out, 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.
> 2. Simple Majority of those attending meeting is required for
> decision. 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.
>
> donald
>
>
>
>
> _______________________________________________
> Quagga-dev mailing list
> [email protected]
> https://lists.quagga.net/mailman/listinfo/quagga-dev
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
