The Transit Operational Data Standard is an open standard for representing the transit schedules used by drivers, dispatchers, and planners to carry out transit operations.
NOTE: Admin Team can also override branch protection rules if necessary for writing to main
Contributors
Who: All registered ODS ontributors
What can they do per governance? create issues, discussions, and pull requests in the ODS repository
Suggested Organization Role: member
Suggested Repo Team: Write
NOTE: this is more access than is strictly defined in the governance. I think this is ok so long as we have branch-protection rules for main (just implemented) so that not too much damage can be done.
Realign Github Teams to be consistent with the ODS governance once approved:
Teams:
ODS Board
Who: ODS Board What can they do per governance? Anything
Suggested Organization Role: owner Suggested Repo Team: Admin
NOTE: Admin Team can also override branch protection rules if necessary for writing to main
Program Manager
Who: Program Manager What can they do per governance? Anything
Suggested Organization Role: member + "team maintainer" privileges Suggested Repo Team: Admin
NOTE: Admin Team can also override branch protection rules if necessary for writing to main
Contributors
Who: All registered ODS ontributors What can they do per governance? create issues, discussions, and pull requests in the ODS repository
Suggested Organization Role: member Suggested Repo Team: Write
NOTE: this is more access than is strictly defined in the governance. I think this is ok so long as we have branch-protection rules for main (just implemented) so that not too much damage can be done.