Bellow is the past propsed project Steering guidelines. Follow the source links for more….
Perhaps this is a good venue to seek comment.
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.
The detailed process could be what’s scaring people… what about a streamlined version that achieves the same goal?
Users, Developers and Steering Committee
Source:http://mpa.itc.it/markus/grass61progman/rfc/rfc1_psc.html
GRASS is developed by people organized in three concentric circles:
- The GRASS Steering Committee members are in the innermost circle. They make strategic decisions and manage the project.
- 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.
- 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.
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.
Detailed Process
Source:http://mpa.itc.it/markus/grass61progman/rfc/rfc1_psc.html
-
Proposals are written up and submitted on the “grass-dev” mailing list for discussion and voting, by any interested party, not just committee members.
-
Proposals need to be available for review for at least two business days before a final decision can be made.
-
Respondents may vote “+1” to indicate support for the proposal and a willingness to support implementation.
-
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.
-
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.
-
Anyone may comment on proposals on the list, but only members of the Project Steering Committee’s votes will be counted.
-
A proposal will be accepted if it receives +2 (including the proposer) and no vetoes (-1).
-
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.
-
Upon completion of discussion and voting the proposer should announce whether they are proceeding (proposal accepted) or are withdrawing their proposal (vetoed).
-
The PSC Chair gets a vote.
-
The Chair is responsible for keeping track of who is a member of the Project Steering Committee.
-
Addition and removal of members from the committee, as well as selection of a Chair should be handled as a proposal to the committee.
-
The Chair adjudicates in cases of disputes about voting.