Re: [mb-style] How the Style Council Works (Was: RFV: Adding some AR attributes)
On Mon, 12 Jun 2006 00:26:28 +0200, Chris Bransden wrote: On 11/06/06, Don Redman <[EMAIL PROTECTED]> wrote: If you propose a very minor change, you can skip steps 1 to 3 and request a veto right away. define 'minor' :) personally i think if you are going to skip the RFC stage, the veto period should be longer - just so as many people can see it as possible. 48 hrs is too soon for everyone to see something if it's the first time the issue has been brought up. Yes, you are right. I think the veto period should be 48 hours of silence _after the discussion has ebbed out_. And if the dicussion took longer, then this was a clear sign, that the RFC stage would have been appropriate. DonRedman -- Words that are written in CamelCase refer to WikiPages: Visit http://wiki.musicbrainz.org/ the best MusicBrainz documentation around! :-) ___ Musicbrainz-style mailing list Musicbrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] How the Style Council Works (Was: RFV: Adding some AR attributes)
On Jun 11, 2006, at 12:29 PM, Don Redman wrote: Question to the Style Council (i.e. everybody involved in mb-style): Do you feel that this process is too formalized or too complicated? I think we're finally hitting some sweet spot between too formalized and utter chaos. I'm happy. Is it impossible to actually use, because people forget the topics once the discussions have ebbed out? The list archives don't forget -- I think letting a discussion die down before reformulating makes a lot of sense to me. In a lot of cases a cool-down period can be very useful for letting people's emotions cool down. -- --ruaok Somewhere in Texas a village is *still* missing its idiot. Robert Kaye -- [EMAIL PROTECTED] --http://mayhem-chaos.net ___ Musicbrainz-style mailing list Musicbrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] How the Style Council Works (Was: RFV: Adding some AR attributes)
On 11/06/06, Don Redman <[EMAIL PROTECTED]> wrote: If you propose a very minor change, you can skip steps 1 to 3 and request a veto right away. define 'minor' :) personally i think if you are going to skip the RFC stage, the veto period should be longer - just so as many people can see it as possible. 48 hrs is too soon for everyone to see something if it's the first time the issue has been brought up. ___ Musicbrainz-style mailing list Musicbrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
[mb-style] How the Style Council Works (Was: RFV: Adding some AR attributes)
On Sun, 11 Jun 2006 14:31:03 +0200, Simon Reinhardt wrote:
I just called it RFV because it does not ask for a bigger change nor
touch more general issues. There have been threads labelled with RFV
which did that - perhaps you want to step on their toes too.
Whooa, sorry. I did not want to step on your toes at all. The reason I
asked the question now, is your comment:
However, is that an addition, an agreement or a veto? ;-)
This made me notice that, within the last few requests, the name "RFV" has
turned from a pretty strict and formal mechanism ("I will do this if noone
sais 'veto' within 48 hours") to a rather informal mechanism.
I do not even say that this is a bad thing, and I do not want to force
some protocol upon the community.
I hope we can stay on topic now and not let this drift into a
"Sommerloch"-discussion about form questions.
OK, instead of opening up a Sommerloch, I will use this to clearly
document the way the StyleCouncil works (something which I have never
done, shame on me).
I am open for suggestions (and vetoes :-) ) and will put this on the wiki,
if there are no objections:
1. Present your issue and the changes you propose to mb-style in a new
thread.
2. Let there be a discussion, see if consensus emerges, or pick up those
changes that make sense to you
3. Once the discussion has ebed out, or stopped from being productive,
reformulate your changes and request a veto. The veto should include a
_short_ note pointing to the past discussion and a relatively specific
description of your proposal.
4. If no veto was issued for 48 hours, go ahead and make your changes.
If you propose a very minor change, you can skip steps 1 to 3 and request
a veto right away. In this case you should include a short note saying
that you skipped the request for comments. This means that anybody can
veto if they think a detailed discussion is necessary. Similarly you
should extend the veto period if the discussion takes longer than two days.
Question to the Style Council (i.e. everybody involved in mb-style):
Do you feel that this process is too formalized or too complicated? Is it
impossible to actually use, because people forget the topics once the
discussions have ebbed out?
DonRedman
--
Words that are written in CamelCase refer to WikiPages:
Visit http://wiki.musicbrainz.org/ the best MusicBrainz documentation
around! :-)
___
Musicbrainz-style mailing list
Musicbrainz-style@lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
