Skip to content

Github Team Management

David Waltermire edited this page May 9, 2024 · 13 revisions

Summary

This page documents how FedRAMP PMO manages the on-boarding and off-boarding of developers, including internal FedRAMP developers, partner developers from other with federal agencies (e.g. GSA, NIST), or contractor teams (e.g. badged contractors for 10x working on the ASAP Project) actively contracted to continue work on artifacts in this repository.

Organization and Team Structure

Per TTS guidance recommended in ADR 3, the FedRAMP Automation work and repository use intentionally configured in the Github organization for GSA project. Within that organization, there is a hierarchy of teams.

  • GSA organization
    • fedramp-automation team as a container for specific child teams below:
      • fedramp-automation-admins team to maintain administrative control and overall continuity for different partner developers. This group includes federal employees in the FedRAMP PMO, in addition to the OSCAL support developer, with that goal in mind.
      • fedramp-oscal-contributors team for developers that need write access to manage issues and feature branches. These users need to be a member of the GSA organization first.

Standard Operating Procedures

Repository Permissions

Developer On-boarding

Developer Off-boarding

  • At the conclusion of a particular project, remove or request on your behalf that a member of fedramp-automation-admins team remove the user from the fedramp-oscal-contributors or a relevant project-specific team.
  • If the user is a contractor or external partner, and all contract or inter-agency work is complete, email GSA Github Support at [email protected] to request the user be removed from the GSA organization.
Clone this wiki locally