... | ... | @@ -53,4 +53,76 @@ The PSC is responsible for addressing any issue about copyright or licensing tha |
|
|
# How does the PSC work?
|
|
|
This section describes how the PSC works.
|
|
|
|
|
|
## |
|
|
\ No newline at end of file |
|
|
## PSC members
|
|
|
All members have equal standing and voice in the PSC. The PSC seats are non-expiring. PSC members may resign their position, or be asked to vacate their seat after a unanimous vote of no confidence from the remaining PSC members.
|
|
|
|
|
|
The expectations on PSC members are:
|
|
|
|
|
|
* Be willing to commit to the iota2 development effort,
|
|
|
* Be responsive to requests for information from fellow members,
|
|
|
* Be able and willing to attend on-line meetings,
|
|
|
* Act in the best interests of the project.
|
|
|
|
|
|
It is important to note that the PSC is not a legal entity.
|
|
|
|
|
|
## Roles
|
|
|
Members can be assigned roles corresponding to each category of the PSC scope described above.
|
|
|
|
|
|
Being assigned a role does not mean undertaking all necessary actions, but rather ensuring that actions will be undertaken.
|
|
|
|
|
|
In addition to their specific roles, members of the PSC commit to participate actively in discussions and votes.
|
|
|
|
|
|
One member of the PSC is designated as the Chair and is the ultimate adjudicator in case of deadlock or irretrievable break down of decision-making, or in case of disputes over voting.
|
|
|
|
|
|
## When is a PSC vote required ?
|
|
|
A vote of the PSC is required in the following cases:
|
|
|
|
|
|
1. Requests for changes
|
|
|
2. Addition or removal of PSC members (including the selection of a new Chair)
|
|
|
3. Release process
|
|
|
|
|
|
In addition, a vote can be summoned for:
|
|
|
|
|
|
1. Changing PSC rules and processes
|
|
|
2. Anything else that might be controversial
|
|
|
|
|
|
## Requests for changes
|
|
|
A Request for Changes describes a change in iota2 code, API, infrastructure or processes that need to be submitted to the PSC vote:
|
|
|
|
|
|
* Anything that could cause backward compatibility issues,
|
|
|
* Adding substantial amounts of new code,
|
|
|
* Changing inter-subsystem APIs, or objects.
|
|
|
|
|
|
It should describe :
|
|
|
|
|
|
* What changes will be made and why they will make a better iota2,
|
|
|
* When will those changes be available (target release or date),
|
|
|
* Who will be developing the proposed changes.
|
|
|
|
|
|
Those elements should be provided in an email to the developer list, with subject starting by "Request For Changes: ". If the proposer is not able to develop the changes by himself, he should inquire the developer list to see if someone can. No Request For Changes will be submitted to vote without evidence of appropriate means of achievement.
|
|
|
|
|
|
## Add or remove PSC members
|
|
|
To be eligible for membership in the PSC, a person should demonstrate a substantial and ongoing involvement in iota2. The PSC is not only composed of iota2 developers as there are many ways to join and contribute to the project. Anyone is eligible to be nominated to the iota2 PSC. Ideally, nominees would be iota2 users or developers who have a deep understanding of the project. In addition, nominees should meet the qualifications set forth in this document. Anyone can submit a nomination.
|
|
|
|
|
|
## Release phases
|
|
|
The release manager (the PSC member in charge of release planning) submits to vote the following release decisions:
|
|
|
|
|
|
1. Date of the next release
|
|
|
2. Codename of the next release
|
|
|
3. Date and revision of Release Candidate
|
|
|
4. Date and revision of Final Release
|
|
|
5. Date and revision of bug-fixes Release
|
|
|
|
|
|
## Process
|
|
|
1. Proposals are written up and submitted on the otb-developers mailing list for discussion and voting, by any interested party, not just committee members. Proposals are available for review for at least three days before a vote can be closed. It is acknowledged that some more complex issues may require more time for discussion and deliberation.
|
|
|
2. Respondents may vote "+1" to indicate support for the proposal and a willingness to support implementation.
|
|
|
3. Respondents may vote "-1" to veto a proposal, but must provide argumented reasoning and alternate approaches to resolve the problem within the two days.
|
|
|
4. A vote of -0 indicates mild disagreement, but has no effect. A 0 indicates no opinion. A +0 indicates mild support, but has no effect.
|
|
|
5. Anyone may comment and vote on proposals on the list, but only members of the PSC's votes (including the Chair) will be counted ("eligible voters").
|
|
|
6. A proposal will be accepted if it receives at least +2 (including the proponent) and no vetos (-1)
|
|
|
7. 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.
|
|
|
8. Upon completion of discussion and voting the proposers should announce whether they are proceeding (proposal accepted) or are withdrawing their proposal (vetoed).
|
|
|
9. The Chair adjudicates in cases of disputes about voting.
|
|
|
|
|
|
# Current members and roles
|
|
|
TBC |
|
|
\ No newline at end of file |