On Mon, 2007-10-01 at 05:30 +0000, Mike Frysinger wrote: > This is your monthly friendly reminder ! Same bat time (typically > the 2nd Thursday at 2000 UTC / 1600 EST), same bat channel > (#gentoo-council @ irc.freenode.net) ! > > If you have something you'd wish for us to chat about, maybe even > vote on, let us know ! Simply reply to this e-mail for the whole > Gentoo dev list to see. > Two topics: The first substantive, the second procedural.
Substantive ----------- It is not clear whether or not Gentoo currently has a Code of Conduct or even if the Council wishes it to. As you know, we do have a draft of one, at least, but it is not complete. Now, that in itself is not a problem because a final Code requires an iterative process based on experience and feedback. If we start with a "final" Code of Conduct, it will be wrong and subject to revision anyway. What are not clear are (1) whether the Code of Conduct is in effect; (2) if so, how we enforce it. Code of Conduct explicitly calls out a Proctors group as its executive arm, but previous Council disbanded the proctors. So as it stands, if we are serious about a Code of Conduct, we have to resurrect the proctors or some equivalent enforcement mechanism. If we are not serious about having a Code of Conduct, I'd like Council to explain why not. (As an aside, I will mention that devrel does receive complaints on occasion which would properly fall under the Code of Conduct and proctor control --- either because any policy violation complained of falls under the Code of Conduct better than under a devrel problem, or because it is a user/developer issue, or because by the time it gets to us it's stale, or .... You might get the idea.) Anyway, Code of Conduct status needs clarification and action. I can go on with this at length, but perhaps this reply is not the place for it. Procedural ---------- The election for this Council and its aftermath shows that we are not sure how to handle a situation in which it appears a candidate will not be able to serve if elected. As a more extreme example than the one we faced this time, suppose a candidate resigns or is suspended. I am still not sure, for example, who are actually Council members right now. > Keep in mind that every GLEP *re*submission to the council for review > must first be sent to the gentoo-dev mailing list 7 days (minimum) > before being submitted as an agenda item which itself occurs 7 days > before the meeting. Simply put, the gentoo-dev mailing list must be > notified at least 14 days before the meeting itself. > > For more info on the Gentoo Council, feel free to browse our homepage: > http://www.gentoo.org/proj/en/council/ Flames to someplace else, please. Otherwise, as always, comments, corrections, additions, etc. welcome. Regards, Ferris -- Ferris McCormick (P44646, MI) <[EMAIL PROTECTED]> Developer, Gentoo Linux (Devrel, Sparc)
signature.asc
Description: This is a digitally signed message part
