... | ... | @@ -89,14 +89,14 @@ In cases where new Projects are being created, either by splitting or by merging |
|
|
|
|
|
### PMC Project Roles
|
|
|
|
|
|
#### Project Contributor
|
|
|
#### PMC Project Contributor
|
|
|
There are a couple of types of Project Contributors.
|
|
|
|
|
|
* Users are the people who use the output from the Project. Output will typically consist of software in form of extensible frameworks and exemplary tools. Software in this context means intellectual property in electronic form, including source and binary code, documentation, courseware, reports and whitepapers.
|
|
|
|
|
|
* 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.
|
|
|
|
|
|
#### Project Committer
|
|
|
#### 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).
|
|
|
|
|
|
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
|
... | ... | @@ -113,7 +113,7 @@ Committers are required to track, participate in, and vote on, relevant discussi |
|
|
|
|
|
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.
|
|
|
|
|
|
#### Project Lead
|
|
|
#### 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.
|
|
|
|
|
|
#### Component Lead
|
... | ... | |