Created Steering Committee (markdown)
@@ -0,0 +1,40 @@
|
|||||||
|
# OpenLayers Project Steering Committee (PSC)
|
||||||
|
|
||||||
|
*see original [OL2 document](https://trac.osgeo.org/openlayers/wiki/SteeringCommittee)*
|
||||||
|
|
||||||
|
## Summary
|
||||||
|
|
||||||
|
This document describes how the OpenLayers Project Steering Committee determines its membership, and makes decisions on OpenLayers project issues.
|
||||||
|
|
||||||
|
In brief, the committee votes on proposals on the OpenLayers [dev mailing list](https://lists.osgeo.org/listinfo/openlayers-dev). 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.
|
||||||
|
|
||||||
|
## Detailed Process
|
||||||
|
|
||||||
|
Proposals are written up and submitted on the OpenLayers [dev mailing list](https://lists.osgeo.org/listinfo/openlayers-dev) 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 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 vetos (-1) except in the case where the issue requires a unanimous approval (see below).
|
||||||
|
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 Committee Chair is responsible for facilitating discussion of proposals, and 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.
|
||||||
|
|
||||||
|
## When is a Vote Required?
|
||||||
|
|
||||||
|
Before any changes that could cause backward compatibility issues or changes the published API.
|
||||||
|
Before adding substantial amounts of new code.
|
||||||
|
Issues of procedure.
|
||||||
|
When releases should take place.
|
||||||
|
Anything that might be controversial.
|
||||||
|
|
||||||
|
## Issues Requiring Unanimous Approval
|
||||||
|
|
||||||
|
Changing the License for the project or repositories
|
||||||
|
|
||||||
|
## Members
|
||||||
|
|
||||||
|
For an updated committee membership list, see SteeringCommitteeMembers.
|
||||||
Reference in New Issue
Block a user