On 17 May 2016, at 8:45, 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.
Can only maintainers ACK or NACK in your proposal? Can you clarify the
influence a “normal” community member (i.e. anyone on quagga-dev)
should
have?
Proposal for going forward:
1. Patch Submitted
1b. Patch needs to be tested. If tests fail, then it’s back to
submitter
to update. Basically test fails -> reject
(Excluding case where it’s assume the test itself is believed to be
broken or there is a good reason why the patch should break the
tests)
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.
Would appreciate some thoughts/discussion on when the “development
branch”
from a maintainer goes into the shared (master?) branch. Should this be
up to the individual maintainer to decide?
- Martin
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
