Requesting /dev/4 stage for Bahmni team members

[burke (Burke Mamlin)]

@darius

@burke, how do you want to approach giving /dev/3s push access to openmrs-core, while communicating expectations around this?

How about a new “temporary-core” team in github with write access to openmrs-core using the following convention?

@Proposed temporary-core Conventions

When someone who is not a /dev/4 or /dev/5 needs temporary access to push to core (e.g., working on a project/feature under the direction of a /dev/4 or /dev/5 for which they need to push to core or merge pull requests):

1. A /dev/5 or repo admin, addresses a post within Repo Management to the person(s) getting temporary write access to core and CC’ing the sponsoring devs, listing the github username(s) granted temporary access and for what purpose, and labeling the topic with temporary-core to make these easier to find.

2. He/she then adds these github account(s) are added to the temporary-core team in GitHub. Those granted temporary access are expected to only push changes or merge pull requests relevant to the specific task and to coordinate these changes with other devs through daily scrum on IRC.

3. Those granted access (or sponsoring dev) are asked to reply to the topic when they no longer need access, at which time we remove them from the temporary-core team.

And we add temporary-core team membership to our dev dashboard so we’re always aware of when this is being used.