|
|
This is the main page for the Project Management Committee (PMC) governance information. The following links provide detailed information:
|
|
|
- The PMC [**Charter**](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Charter)
|
|
|
- The PMC [**Members**](https://osduforum.org/project-management-committee-pmc/)
|
|
|
- The PMC [**Projects**](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Directory), [**Release Plan**](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Plan-R3), [**Risk Register**](R3-Risk-Register) and [**Status**](https://opensdu.slack.com/archives/C010VA9RD25)
|
|
|
- Please see [here](https://community.opengroup.org/osdu/home/-/wikis/Gitlab_Structure) for alignment of GitLab to projects
|
|
|
- Please refer to [proposed taxonomy](PMC-Issue-Taxonomy) of Platform issues and how PMC program management uses GitLab boards for management
|
|
|
- Frequently asked questions around PMC charter and examples based on R3 project layouts and organization - **[FAQ](PMC FAQ)**
|
|
|
- For significant design and technology selections - the teams are advised to use (**LADR**) Lightweight architecture decision record methodology as described [here](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions), [here](https://www.thoughtworks.com/radar/techniques/lightweight-architecture-decision-records) and [here](https://hub.packtpub.com/what-are-lightweight-architecture-decision-records/). The intent of ADRs is to ensure the collaborative development of OSDU architecture with transparency. The article [here](https://martinfowler.com/articles/scaling-architecture-conversationally.html) explains quite elegantly how architecture can be scaled conversationally minimizing approval bottlenecks.
|
|
|
- An example for reference from OSDU is shown [here](https://community.opengroup.org/groups/osdu/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=Issue%3A%3AArchitecture%2FTechnology&first_page_size=20) and over [here](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Possible-Friction-Points/OSDU-OpenDES-Possible-Friction-Points)
|
|
|
|
|
|
- Standards
|
|
|
- [Low level design](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Writing-Code)
|
|
|
- [Language and technology](https://community.opengroup.org/osdu/documentation/-/wikis/Language-and-technology-support)
|
|
|
- [CI-CD pipeline/Contributor & Committer branch](https://osdu.pages.opengroup.org/platform/ci-cd-pipelines/)
|
|
|
- [API specs and project documentation](https://community.opengroup.org/osdu/documentation/-/wikis/Core-Services-Overview)
|
|
|
- [Release Strategy](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Strategy)
|
|
|
- [Environments - Build, QA, and preship](./Environments)
|
|
|
- [InfoSec](https://osdu.projects.opengroup.org/subcommittees/info-sec/work-products/public-security-documentation/html/OSDU-InfoSec.html)
|
|
|
|
|
|
- PMC Policies
|
|
|
- [Issue prioritization/triaging process](https://community.opengroup.org/osdu/platform/home/-/issues/49)
|
|
|
- [MR approval process](https://community.opengroup.org/osdu/platform/home/-/wikis/Merge-Request-Approval-Process)
|
|
|
- [API deprecation process](https://community.opengroup.org/osdu/documentation/-/wikis/API-deprecation-process)
|
|
|
|
|
|
OSDU platform is designed in a manner that clearly identifies the system core services as the hub that ties together the various other top-level projects as satellites to this hub. The hub provides services around schema, identity, storage, notifications, DDMS registry to ensure that all associated projects have the core services necessary to integrate and expand from OSDU R2 defined the first cut version of these and the system itself will be evolving in a calculated manner to support the addition of the satellites.
|
|
|
|
|
|
The satellites are projects that either extend the system capabilities by providing support for services for ingestion, enrichment, delivery including search/discovery, helper services for frame-of-reference handling including units, coordinate systems, elevation references, etc., or by extending the system and providing domain-specific extensions to OSDU to optimize the storage, access, and delivery of meta and array data for different domains such as wellbore, seismic, reservoir, well planning, production, etc.
|
|
|
|
|
|
This [**Projects page**](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Directory) illustrates the projects and the relationship to the OSDU System.
|
|
|
|
|
|
[PMC Project Reviews](/PMC Project Reviews) provide weekly status on the projects contributing to the OSDU Data Platform.
|
|
|
|
|
|
# Post R3 Development
|
|
|
* [Tentative Milestone dates](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Strategy#development-timeline-for-milestones) |
|
|
We are in the process of migrating all PMC best practices and documents to a new portal - please check out [here](https://osdu.projects.opengroup.org/pmc/work-products/pmc-portal/pmc-policies/main/home-page.html) |