Changes between Version 8 and Version 9 of PSC

Timestamp:

Nov 8, 2007, 1:54:20 AM (17 years ago)

Author:

ticheler

Comment:

--

PSC

@@ -7 +7 @@
 During the Second !GeoNetwork Workshop in April 2006, held in Rome - Italy, an Advisory Board (AB) was established. The AB meets on a yearly basis to discuss the requirements of the participating agencies and to define a work plan for the following year. The meeting is open to all members & interested parties of the !GeoNetwork opensource Community. Working group sessions are organized to gather project requirements and to come up with a work plan. The workshop will also provide technical sessions around the !GeoNetwork opensource software and where possible around related software.
 
-The day to day management of the project is left to the Technical Steering Committee (TSC). The TSC will seek consensus within the developer and user community and is responsible for the implementation of the work plan. 
+The day to day management of the project is left to the Project Steering Committee (PSC). The PSC will seek consensus within the developer and user community and is responsible for the implementation of the work plan. 
 
 A goal set out by the AB is to make the community building process and inclusive, consensus based effort. At the Rome meeting, the AB agreed to have the project go through the incubation process of the OSGeo Foundation to establish it as a full OSGeo project.
@@ -21 +21 @@
  * Pierre Lagarde ([http://www.brgm.fr BRGM])
 
-= Technical Steering Committee =
+= Project Steering Committee =
 
 Author: Jeroen Ticheler[[BR]]
@@ -29 +29 @@
 == Summary ==
 
-This document describes how the !GeoNetwork Technical Steering Committee (TSC) determines membership, and makes decisions on !GeoNetwork opensource project issues.
+This document describes how the !GeoNetwork Project Steering Committee (PSC) determines membership, and makes decisions on !GeoNetwork opensource project issues.
 
 In brief the committee votes on proposals on the [https://lists.sourceforge.net/mailman/listinfo/geonetwork-devel geonetwork-dev] mailinglist. Proposals are available for review for at least two days, and a single veto is sufficient to delay progress though ultimately a majority of members can pass a proposal.
@@ -40 +40 @@
  4. Respondents may vote "-1" to veto a proposal, but must provide clear reasoning and alternate approaches to resolving the problem within the two days.
  5. 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. 
- 6. Anyone may comment on proposals on the list, but only members of the Project Management Committee's votes will be counted. 
+ 6. Anyone may comment on proposals on the list, but only members of the Project Steering Committee's votes will be counted. 
  7. A proposal will be accepted if it receives +2 (including the proposer) and no vetos (-1). 
  8. 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. 
  9. Upon completion of discussion and voting the proposer should announce whether they are proceeding (proposal accepted) or are withdrawing their proposal (vetoed). 
  10. The Chair gets a vote.
- 11. The Chair is responsible for keeping track of who is a member of the Project Management Committee. 
+ 11. The Chair is responsible for keeping track of who is a member of the Project Steering Committee. 
  12. 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 selection of a new Chair also requires approval of the OSGeo board. 
  13. The Chair adjudicates in cases of disputes about voting.
@@ -57 +57 @@
  * When releases should take place.
  * Anything that might be controversial. 
+ * Add a new member to the PSC
 
 == Observations ==