|
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
|
|
* All Project charters, plans, technical documents, source code and reports are publicly available
|
|
* All Project charters, plans, technical documents, source code and reports are publicly available
|
... | @@ -11,6 +12,7 @@ The PMC is expected to ensure that: |
... | @@ -11,6 +12,7 @@ The PMC is expected to ensure that: |
|
* 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
|
|
* Providing assistance and support to the developers working on the Project by removing obstacles, solving problems, and resolving conflicts
|
|
* Providing assistance and support to the developers working on the Project by removing obstacles, solving problems, and resolving conflicts
|
... | @@ -49,6 +51,7 @@ Active participation in the user newsgroups and the appropriate developer mailin |
... | @@ -49,6 +51,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.
|
|
|
|
|
|
Each Project must identify, and make available on its web site, the requirements and prioritizations it is working against in the current release cycle. In addition, each Project must post a release plan showing the date and content of the next major release, including any major milestones, and must keep this plan up to date.
|
|
Each Project must identify, and make available on its web site, the requirements and prioritizations it is working against in the current release cycle. In addition, each Project must post a release plan showing the date and content of the next major release, including any major milestones, and must keep this plan up to date.
|
... | @@ -111,6 +114,7 @@ Ideally, a Project Lead would be the original author of the Project charter. On |
... | @@ -111,6 +114,7 @@ Ideally, a Project Lead would be the original author of the Project charter. On |
|
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.
|
|
* Source Repository - One or more repositories containing all the software for the Projects.
|
|
* Source Repository - One or more repositories containing all the software for the Projects.
|
... | @@ -122,6 +126,7 @@ The PMC works with the OSDU OMC to ensure the required infrastructure resources |
... | @@ -122,6 +126,7 @@ The PMC works with the OSDU OMC to ensure the required infrastructure resources |
|
* 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
|
|
0.3 – Added feedback from Johan Krebbers |
|
0.3 – Added feedback from Johan Krebbers |