<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.14">
<TITLE>Projetc Steering Committee (PSC): proposed process and structure (request for comment)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>
<P><FONT SIZE=2 FACE="Arial">Bellow is the past propsed project Steering guidelines. Follow the source links for more….</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Perhaps this is a good venue to seek comment.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">The Concentric model is a fantastic idela and hits the nail on the head. But maybe right now (as in today, this minute and second) we are experiencing a doughnut affect. The questions is how big is the hole.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">The detailed process could be what's scaring people… what about a streamlined version that achieves the same goal?</FONT>
</P>
<BR>
<P><B><FONT SIZE=5 FACE="Arial">Users, Developers and Steering Committee</FONT></B>
<BR><FONT SIZE=2 FACE="Arial">Source:<A HREF="http://mpa.itc.it/markus/grass61progman/rfc/rfc1_psc.html">http://mpa.itc.it/markus/grass61progman/rfc/rfc1_psc.html</A></FONT>
</P>
<P><FONT FACE="Arial">GRASS is developed by people organized in three concentric circles:</FONT>
</P>
<UL>
<LI><FONT FACE="Arial">The GRASS Steering Committee members are in the innermost circle. They make strategic decisions and manage the project. </FONT></LI>
<LI><FONT FACE="Arial">The GRASS Developers are the second circle and contribute to source code, documentation, testing, and packaging. They have write access to the GRASS source code repository (CVS). This group votes for the members of the GRASS PSC. Developers are also encouraged to closely peer-review code submissions. </FONT></LI>
<LI><FONT FACE="Arial">The GRASS Users are the third circle and are the largest group. They contribute to the code, documentation and discussion on existing and new features through the various mailing lists, the Wiki and the bug/wish tracker. </FONT></LI>
<BR>
</UL>
<P><FONT FACE="Arial">In brief, the PSC votes on proposals on the GRASS Developers mailing list ("grass-dev"). Proposals are available for review for at least two business days, and a single veto is sufficient to delay progress though ultimately a majority of committee members can pass a proposal.</FONT></P>
<P><B><FONT SIZE=5 FACE="Arial">Detailed Process</FONT></B>
</P>
<P><FONT SIZE=2 FACE="Arial">Source:<A HREF="http://mpa.itc.it/markus/grass61progman/rfc/rfc1_psc.html">http://mpa.itc.it/markus/grass61progman/rfc/rfc1_psc.html</A></FONT>
</P>
<UL>
<LI><FONT FACE="Arial">Proposals are written up and submitted on the "grass-dev" mailing list for discussion and voting, by any interested party, not just committee members.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">Proposals need to be available for review for at least two business days before a final decision can be made.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">Respondents may vote "+1" to indicate support for the proposal and a willingness to support implementation.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">Respondents may vote "-1" to veto a proposal, but must provide clear reasoning and alternate approaches to resolving the problem within the two business days.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">A vote of -0 indicates mild disagreement, but has no effect. A 0 indicates no opinion. A +0 indicate mild support, but has no effect.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">Anyone may comment on proposals on the list, but only members of the Project Steering Committee's votes will be counted.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">A proposal will be accepted if it receives +2 (including the proposer) and no vetoes (-1).</FONT></LI>
<BR>
<LI><FONT FACE="Arial">If a proposal is vetoed, and it cannot be revised to satisfy all parties, then it can be resubmitted for an override vote in which a majority of all eligible voters indicating +1 is sufficient to pass it. Note that this is a majority of all committee members, not just those who actively vote.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">Upon completion of discussion and voting the proposer should announce whether they are proceeding (proposal accepted) or are withdrawing their proposal (vetoed).</FONT></LI>
<BR>
<LI><FONT FACE="Arial">The PSC Chair gets a vote.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">The Chair is responsible for keeping track of who is a member of the Project Steering Committee.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">Addition and removal of members from the committee, as well as selection of a Chair should be handled as a proposal to the committee.</FONT></LI>
<BR>
<LI><FONT FACE="Arial">The Chair adjudicates in cases of disputes about voting.</FONT></LI>
<BR>
<BR>
</UL>
</BODY>
</HTML>