... | @@ -2,7 +2,7 @@ |
... | @@ -2,7 +2,7 @@ |
|
|
|
|
|
This document defines the OSDU Project Management Committee (PMC) goals, objectives, roles and responsibilities. Further, this document establishes the operating model for all OSDU Projects, as well as how the PMC will provide vision, leadership and governance for all OSDU PMC Projects, under governance of the OSDU Management Committee (OMC).
|
|
This document defines the OSDU Project Management Committee (PMC) goals, objectives, roles and responsibilities. Further, this document establishes the operating model for all OSDU Projects, as well as how the PMC will provide vision, leadership and governance for all OSDU PMC Projects, under governance of the OSDU Management Committee (OMC).
|
|
|
|
|
|
**PMC Goals & Objectives**
|
|
### PMC Goals & Objectives
|
|
|
|
|
|
The PMC is expected to ensure that:
|
|
The PMC is expected to ensure that:
|
|
* All Projects operate effectively by providing leadership to guide the Project's overall direction, and, by removing obstacles, solving problems, and resolving conflicts
|
|
* All Projects operate effectively by providing leadership to guide the Project's overall direction, and, by removing obstacles, solving problems, and resolving conflicts
|
... | @@ -13,7 +13,7 @@ The PMC is expected to ensure that: |
... | @@ -13,7 +13,7 @@ The PMC is expected to ensure that: |
|
* All Projects deliver software products that can be licensed under Apache version 2.0
|
|
* All Projects deliver software products that can be licensed under Apache version 2.0
|
|
* Project reporting and communication to OMC, and subsequently to the OSDU community are done in a timely and effective manner
|
|
* Project reporting and communication to OMC, and subsequently to the OSDU community are done in a timely and effective manner
|
|
|
|
|
|
**PMC Responsibilities**
|
|
### PMC Responsibilities
|
|
|
|
|
|
The PMC has the following responsibilities:
|
|
The PMC has the following responsibilities:
|
|
* Providing the vision and leadership to guide the overall direction for all PMC projects, in a manner consistent with the OSDU roadmap and OSDU Reference Architecture principles
|
|
* Providing the vision and leadership to guide the overall direction for all PMC projects, in a manner consistent with the OSDU roadmap and OSDU Reference Architecture principles
|
... | @@ -35,15 +35,15 @@ The PMC has the following responsibilities: |
... | @@ -35,15 +35,15 @@ The PMC has the following responsibilities: |
|
* Providing regular progress reports to OMC
|
|
* Providing regular progress reports to OMC
|
|
* Providing technical support to OSDU Developers bootcamps
|
|
* Providing technical support to OSDU Developers bootcamps
|
|
|
|
|
|
**PMC Roles**
|
|
### PMC Roles
|
|
|
|
|
|
*PMC Lead*
|
|
#### *PMC Lead*
|
|
* The initial PMC Lead is selected by the OSDU OMC. The PMC Chair will serve a two-year term.
|
|
* The initial PMC Lead is selected by the OSDU OMC. The PMC Chair will serve a two-year term.
|
|
|
|
|
|
*PMC Vice-lead*
|
|
#### *PMC Vice-lead*
|
|
* The PMC Vice-lead is elected by the OSDU membership. The PMC Vice-lead will serve a two-year term. However, PMC Lead and PMC Vice-lead will not be replaced at the same time but as a minimum there must be 9 months in between.
|
|
* The PMC Vice-lead is elected by the OSDU membership. The PMC Vice-lead will serve a two-year term. However, PMC Lead and PMC Vice-lead will not be replaced at the same time but as a minimum there must be 9 months in between.
|
|
|
|
|
|
*PMC At-Large Member*
|
|
#### *PMC At-Large Member*
|
|
* The remainder of the PMC will be made up from the Project Leads (see definition below). Initially, Project Leads will be selected by the PMC Lead and Vice-lead. Thereafter, Project Leads can be nominated by any other member of the PMC, and via or majority voting approved by all PMC members.
|
|
* The remainder of the PMC will be made up from the Project Leads (see definition below). Initially, Project Leads will be selected by the PMC Lead and Vice-lead. Thereafter, Project Leads can be nominated by any other member of the PMC, and via or majority voting approved by all PMC members.
|
|
|
|
|
|
The work of the PMC is shared by the PMC members. All PMC members are expected to contribute actively. In particular, PMC members are expected to take responsibility for overseeing certain areas of work within a particular Project, and reporting to the PMC on these areas. Because of the diversity amongst individual projects, PMC members are not expected to maintain anything other than general currency with a Project that is outside their assigned technical areas.
|
|
The work of the PMC is shared by the PMC members. All PMC members are expected to contribute actively. In particular, PMC members are expected to take responsibility for overseeing certain areas of work within a particular Project, and reporting to the PMC on these areas. Because of the diversity amongst individual projects, PMC members are not expected to maintain anything other than general currency with a Project that is outside their assigned technical areas.
|
... | @@ -52,7 +52,7 @@ Active participation in the user newsgroups and the appropriate developer mailin |
... | @@ -52,7 +52,7 @@ Active participation in the user newsgroups and the appropriate developer mailin |
|
|
|
|
|
In the unlikely event that any member of the PMC becomes disruptive to the process, or ceases to contribute for an extended period, that member may be removed by unanimous vote of remaining PMC members. PMC members may resign at any time by delivering notice of their resignation to the PMC Lead.
|
|
In the unlikely event that any member of the PMC becomes disruptive to the process, or ceases to contribute for an extended period, that member may be removed by unanimous vote of remaining PMC members. PMC members may resign at any time by delivering notice of their resignation to the PMC Lead.
|
|
|
|
|
|
**Projects**
|
|
## Projects
|
|
|
|
|
|
All PMC Projects are operated as meritocracies -- the more you contribute, and the higher the quality of your contribution, the more you can do.
|
|
All PMC Projects are operated as meritocracies -- the more you contribute, and the higher the quality of your contribution, the more you can do.
|
|
|
|
|
... | @@ -83,16 +83,16 @@ If a Project wishes to divide into components, commit privileges are normally gr |
... | @@ -83,16 +83,16 @@ If a Project wishes to divide into components, commit privileges are normally gr |
|
|
|
|
|
In cases where new Projects are being created, either by splitting or by merging, the usual procedures for the establishment of a new Project are followed. In particular, Contributors will not necessarily have the same rights after an organizational change that they enjoyed in the previous structure.
|
|
In cases where new Projects are being created, either by splitting or by merging, the usual procedures for the establishment of a new Project are followed. In particular, Contributors will not necessarily have the same rights after an organizational change that they enjoyed in the previous structure.
|
|
|
|
|
|
**Project Roles**
|
|
### Project Roles
|
|
|
|
|
|
*Project Contributor*
|
|
#### Project Contributor
|
|
There are a couple of types of Project Contributors.
|
|
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 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.
|
|
* 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*
|
|
#### 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 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
|
|
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
|
... | @@ -109,13 +109,13 @@ Committers are required to track, participate in, and vote on, relevant discussi |
... | @@ -109,13 +109,13 @@ 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.
|
|
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*
|
|
#### 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 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*
|
|
#### 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 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.
|
|
|
|
|
|
**Project Infrastructure**
|
|
### Project Infrastructure
|
|
|
|
|
|
The PMC works with the OSDU OMC to ensure the required infrastructure resources are provided for all PMC Projects. The Project infrastructure will include, at minimum:
|
|
The PMC works with the OSDU OMC to ensure the required infrastructure resources are provided for all PMC Projects. The Project infrastructure will include, at minimum:
|
|
* Bug Database - Bugzilla database for tracking bugs and feature requests.
|
|
* Bug Database - Bugzilla database for tracking bugs and feature requests.
|
... | @@ -127,7 +127,7 @@ The PMC works with the OSDU OMC to ensure the required infrastructure resources |
... | @@ -127,7 +127,7 @@ The PMC works with the OSDU OMC to ensure the required infrastructure resources |
|
* Component Mailing Lists - Mailing list for technical discussions related to the component. This mailing list is open to the public.
|
|
* Component Mailing Lists - Mailing list for technical discussions related to the component. This mailing list is open to the public.
|
|
* Newsgroups - Newsgroups where users, developers, and committers can interact regarding general questions and issues about the project. The newsgroup is open to the public.
|
|
* Newsgroups - Newsgroups where users, developers, and committers can interact regarding general questions and issues about the project. The newsgroup is open to the public.
|
|
|
|
|
|
**Version History:**
|
|
### Version History:
|
|
|
|
|
|
0.1 – Initial Draft – PMC team w/inputs from Stephen Whitley/OMC
|
|
0.1 – Initial Draft – PMC team w/inputs from Stephen Whitley/OMC
|
|
0.2 – Feedback from Phillip Jong
|
|
0.2 – Feedback from Phillip Jong
|
... | | ... | |