Code Integrity, Access Control, Change Management
Operators want to know who has access/authority to commit code to the OSDU Data Platform. This doesn't need to be complex or long. But they need to know who can commit and how those permissions are handled. The process for accepting pull requests/commits and making changes to the code should also be documented.
Operator Inputs
- Shell lists this as a requirement.
Definition of Done
Documentation and/or a link is probably sufficient. E.g., a link to the current list of approved committers, and a statement like "The OSDU OMC approves committers based on X, Y, Z". A statement about which workstream has authority over change management will satisfy that requirement, too.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information