I agree with:
- /dev/5s approve adding a repo to the OpenMRS org
- /dev/2+ have privs to carry out the action
- need to document explicit guidance of what belongs under the OpenMRS github org
Also:
- my preference is that adding a repo under the OpenMRS org implies that OpenMRS project management will actively try to corral volunteer resources to maintain the repo (I.e. just “multiple community devs want to work on this repo” is not sufficient.)
- I agree with Burke that we should push to have less in the “official” OpenMRS repo, including moving some existing stuff out, but that we’d need another alternative repo to make this happen. (I don’t like his proposed names, but that should go in another thread.)