... | ... | @@ -97,27 +97,27 @@ There are a couple of types of Project Contributors. |
|
|
* Users who contribute software, documentation, or other materially useful content become developers. Developers are encouraged to participate in the user newsgroup(s), and should monitor the developer mailing list associated with their area of contribution. When appropriate, developers may also contribute to development design discussions related to their area of contribution. Developers are expected to be proactive in reporting problems in the bug tracking system.
|
|
|
|
|
|
#### PMC Project Committer
|
|
|
Developers who give frequent and valuable contributions to a Project, or component of a Project (in the case of large Projects), can have their status promoted to that of a "Committer" for that Project or component respectively. A Committer has “write access” to the source code repository for the associated Project (or component), and gains voting rights allowing them to affect the future of the Project (or component).
|
|
|
Developers who give frequent and valuable contributions to a Project, or component of a PMC Project (in the case of large Projects), can have their status promoted to that of a "Committer" for that PMC Project or component respectively. A Committer has “write access” to the source code repository for the associated Project (or component), and gains voting rights allowing them to affect the future of the PMC Project (or component).
|
|
|
|
|
|
In order for a Developer to become a Committer on a particular Project (overseen by the PMC), another Committer for the same Project (or component as appropriate) can nominate that Developer or the Developer can ask to be nominated. Once a Developer is nominated, the
|
|
|
In order for a Developer to become a Committer on a particular PMC Project (overseen by the PMC), another Committer for the same PMC Project (or component as appropriate) can nominate that Developer or the Developer can ask to be nominated. Once a Developer is nominated, the
|
|
|
|
|
|
Committers for the Project (or component) will vote for a PMC-designated voting period, and that period shall be no less than one week. If there are at least 3 positive votes from different OSDU member organization representatives other than the Developer’s organization and no negative votes within the voting period, the Developer is recommended to the PMC for commit privileges. The PMC may waive the 3 vote minimum requirement in exceptional cases (e.g., there are fewer than 3 active committers on the project). If the PMC also approves, and the Developer signs the appropriate Committer agreements established by the PMC, the Developer is converted into a Committer and given write access to the source code and/or web repository for that Project (or component). Becoming a Committer is a privilege that is earned by contributing and showing discipline and good judgment. It is a responsibility that should be neither given nor taken lightly.
|
|
|
Committers for the PMC Project (or component) will vote for a PMC-designated voting period, and that period shall be no less than one week. If there are at least 3 positive votes from different OSDU member organization representatives other than the Developer’s organization and no negative votes within the voting period, the Developer is recommended to the PMC for commit privileges. The PMC may waive the 3 vote minimum requirement in exceptional cases (e.g., there are fewer than 3 active committers on the project). If the PMC also approves, and the Developer signs the appropriate Committer agreements established by the PMC, the Developer is converted into a Committer and given write access to the source code and/or web repository for that Project (or component). Becoming a Committer is a privilege that is earned by contributing and showing discipline and good judgment. It is a responsibility that should be neither given nor taken lightly.
|
|
|
|
|
|
At times, Committers may become inactive for a variety of reasons. The decision making process of the Project relies on active committers who respond to discussions and vote in a constructive and timely manner. The PMC is responsible for ensuring the smooth operation of the Project. A Committer who is disruptive, does not participate actively, or has been inactive for an extended period may have his or her commit status revoked by the PMC.
|
|
|
At times, Committers may become inactive for a variety of reasons. The decision making process of the Project relies on active committers who respond to discussions and vote in a constructive and timely manner. The PMC is responsible for ensuring the smooth operation of the PMC Project. A Committer who is disruptive, does not participate actively, or has been inactive for an extended period may have his or her commit status revoked by the PMC.
|
|
|
|
|
|
Active participation in the user newsgroup and the appropriate developer mailing lists is a responsibility of all Committers, and is critical to the success of the Project. Committers are required to monitor and contribute to the user newsgroup.
|
|
|
Active participation in the user newsgroup and the appropriate developer mailing lists is a responsibility of all Committers, and is critical to the success of the PMC Project. Committers are required to monitor and contribute to the user newsgroup.
|
|
|
|
|
|
Committers are required to monitor the mailing lists associated with all Projects and components for which they have commit privileges. This is a condition of being granted commit rights to the Project or component. It is mandatory because committers must participate in votes (which in some cases require a certain minimum number of votes) and must respond to the mailing list in a timely fashion in order to facilitate the smooth operation of the Project. When a Committer is granted commit rights, they will be added to the appropriate mailing lists. A Committer must not be unsubscribed from a Developer mailing list unless their associated commit privileges are also revoked.
|
|
|
Committers are required to monitor the mailing lists associated with all PMC Projects and components for which they have commit privileges. This is a condition of being granted commit rights to the PMC Project or component. It is mandatory because committers must participate in votes (which in some cases require a certain minimum number of votes) and must respond to the mailing list in a timely fashion in order to facilitate the smooth operation of the PMC Project. When a Committer is granted commit rights, they will be added to the appropriate mailing lists. A Committer must not be unsubscribed from a Developer mailing list unless their associated commit privileges are also revoked.
|
|
|
|
|
|
Committers are required to track, participate in, and vote on, relevant discussions in their associated Projects and components. There are three voting responses: +1 (yes), -1 (no, or veto), and 0 (abstain).
|
|
|
Committers are required to track, participate in, and vote on, relevant discussions in their associated PMC Projects and components. There are three voting responses: +1 (yes), -1 (no, or veto), and 0 (abstain).
|
|
|
|
|
|
Committers are responsible for proactively reporting problems in the bug tracking system, and annotating problem reports with status information, explanations, clarifications, or requests for more information from the submitter. Committers are responsible for updating problem reports when they have done work related to the problem.
|
|
|
|
|
|
#### PMC Project Lead
|
|
|
Ideally, a Project Lead would be the original author of the Project charter. Once a Project has been approved and the Project Lead has been officially appointed by the PMC, the Project Lead must produce: a development plan for the release cycle, where the development plan must be approved by a majority of Committers of the Project. The plan must be submitted to the PMC for review. The PMC may provide feedback and advice on the plan but approval rests with the Project Committers.
|
|
|
Ideally, a PMC Project Lead would be the original author of the PMC Project charter. Once a PMC Project has been approved and the PMC Project Lead has been officially appointed by the PMC, the PMC Project Lead must produce: a development plan for the release cycle, where the development plan must be approved by a majority of Committers of the PMC Project. The plan must be submitted to the PMC for review. The PMC may provide feedback and advice on the plan but approval rests with the PMC Project Committers.
|
|
|
|
|
|
#### Component Lead
|
|
|
When a component is deemed necessary by the Project Committers for a particular project, the Component Lead must produce: a development plan for the release cycle, where the development plan must be approved by a majority of Committers of the Component. The plan must be submitted to the Project Committers and the PMC for review. Both the Project Committers and the PMC may provide feedback and advice on the plan but approval rests with the Component Committers.
|
|
|
When a component is deemed necessary by the PMC Project Committers for a particular project, the Component Lead must produce: a development plan for the release cycle, where the development plan must be approved by a majority of Committers of the Component. The plan must be submitted to the PMC Project Committers and the PMC for review. Both the PMC Project Committers and the PMC may provide feedback and advice on the plan but approval rests with the Component Committers.
|
|
|
|
|
|
### Project Infrastructure
|
|
|
|
... | ... | |