In general, I am on board with this as you outlined it. Let me make a couple more suggestions (inline)
Brad >>> On 9/15/2008 at 5:22 PM, in message <[EMAIL PROTECTED]>, "Jesse Becker" <[EMAIL PROTECTED]> wrote: > A few of us (Bernard, Brad Nicholes, and myself) were musing on IRC > about the etiquette of STATUS file edits. We decided that this is > better discussed on the wider list, and I was volunteered to broach > the issue (lucky me). So to get things started, here are a few things > that *I* think would be useful. These are suggestions only--I'm in no > position to dictate anything to anyone. > > Suggestion 1) The +1, +0 and -1 votes get one line apiece, for a > total of 3 lines. See below for an example. > +1, this is how the status file started out and what we need to move back to. > Suggestion 2) Don't mess with other people's votes. > +1, even when a proposal is modified, the existing votes need to remain. However we do need to somehow put a procedure in place that allows for a re-review. I don't have any suggestions for that yet. > Suggestion 3) A vote of +1 does not need comment. If committing a > vote of +0 or -1, a comment as to why is *strongly* encouraged. The > comment can be either on the voting line, or immediately after the > stanza. See below for an example. > +1, the only modification here would be that a comment for a +0 is *strongly* encouraged but a technical justification for a -1 is mandatory. > Suggestion 4) When a backport has been accepted, move the entire > stanza into a CHANGES file (or something similar), along with a date > stamp.. This should be done when the changes are actually committed > to that branch, not when the votes are cast. This also means that a > CHANGES file needs to be created. > +1 again, another suggestion would be to just move the stanza to lower section with the same STATUS file. But I am good with this either way. > > So, any thoughts or comments? These are, as a I said, suggestions > only. I'm quite willing to be convinced of other behavior. > Thanks for the proposals. I like them. > > Example for #1 and #3 above: > > * gmond: Frobnicate the quazzle before inducticating the bibblebop. > http://ganglia.svn.sourceforge.net/viewvc/ganglia?view=rev&revision=-9999 > +1: hawson > -1: Tom, Dick, Harry > +0: Mr. Bill > Tom: Inducitacting should happen before the frobnication. > Harry: The quazzle should be checked for extra widgets before > frobnication. > Mr. Bill: Oh no! > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
