On Thu, Feb 9, 2012 at 11:54 AM, Darius Jazayeri <[email protected]> wrote: > Mark was trying to push to the new htmlformentry19ext repository on github, > and didn't have privileges. I addressed this by adding the "Module: HTML > Form Entry" team to htmlformentry19ext. Does this seem right (i.e. because > this is effectively a child module of htmlformentry, so it should have the > same users)? Or would it be more appropriate to put Mark in "Core > Developers" (which already had access to hfe19ext)? Or some other approach?
>From earlier conversations we seemed to settle (maybe I'm wrong?) on the idea that the only repositories in the OpenMRS project would be the core application, core/bundled modules, and any of the (relatively few) modules that the core team was "adopting" to do maintenance. With that in mind, it might be enough to have more a 2-level (full/partial) team permission structure for the OpenMRS organization/project similar to what we have now. On a more general level, we want to remember that in a DVCS model we'll have lots of people forking to work on things and then send pushes back, so we shouldn't have to manage as many permissions for people who are more casual contributors. We should consider whether or not this equates to "partial committers" in our SVN model. Thoughts? Michael _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
