... | @@ -4,7 +4,6 @@ This is the main page for the Project Management Committee (PMC) governance info |
... | @@ -4,7 +4,6 @@ This is the main page for the Project Management Committee (PMC) governance info |
|
- 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)
|
|
- 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 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
|
|
- Please refer to [proposed taxonomy](PMC-Issue-Taxonomy) of Platform issues and how PMC program management uses Gitlab boards for management
|
|
- Initial steps for PMC team to start up R3 are documented [here](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/R3Initial%7CR3-Initial-Steps)
|
|
|
|
- Frequently asked questions around PMC charter and examples based on R3 project layouts and organization - **[FAQ](PMC FAQ)**
|
|
- 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 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.
|
|
- 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 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/osdu/documentation/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=LADR) and over [here](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Possible-Friction-Points/OSDU-OpenDES-Possible-Friction-Points)
|
|
- An example for reference from OSDU is shown [here](https://community.opengroup.org/osdu/documentation/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=LADR) and over [here](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Possible-Friction-Points/OSDU-OpenDES-Possible-Friction-Points)
|
... | | ... | |