|
|
![image.png](uploads/.attachments/image-e924746f-a9db-4a8a-97ad-38d8ac3f01be.png)
|
|
|
|
|
|
## Scope:
|
|
|
- Each project is established by the PMC, with OMC approval and with a clearly defined, non-overlapping technical scope.
|
|
|
- Will be headed by a Project Manager appointed by the PMC Leader.
|
|
|
- Each Project will execute according to sound and documented software practices
|
|
|
- Each Project will embrace Meritocracy for community contributions
|
|
|
- Any OSDU technical material/information required to open source the project can be contributed, regardless of prior OSDU confidentiality restrictions to meet Apache 2 license requirements.
|
|
|
## Members:
|
|
|
- Any individual whether an OSDU Forum member or not can join an OSDU Open Source Software Project as a Contributor
|
|
|
- Contributors who are OSDU Forum members can become Committers by majority approval of the existing active Committers (and can be removed in the same way).
|
|
|
- The Project Manager must be a Committer for that project
|
|
|
## Voting:
|
|
|
- If consensus is not reached, Project Manager calls for a simple majority vote among active committers (committers contributing in the last 6 months)
|
|
|
## Escalation:
|
|
|
- Escalates issues that cannot be address in Project to the PMC
|
|
|
|
|
|
## Definitions:
|
|
|
#### Contributor:
|
|
|
- A contributor is anyone who contributes to an Open Source project. These contributions can take any form; including code, documentation, tests, feedback
|
|
|
#### Committer:
|
|
|
- A committer is a contributor that is trusted to make direct changes “commits” to the Open Source project central repository. To be a committer, one has to demonstrate that they understand the project goals & scope, the process, coding standards, quality/security /reliability requirements, and the implications of making the change.
|
|
|
|
|
|
|