Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • H Home
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Security and Compliance
  • Home
  • Issues
  • #18
Closed
Open
Issue created May 22, 2020 by Paco Hope (AWS)@pacohopeDeveloper

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
Assignee
Assign to
Time tracking