Darius, Regarding conventions for git repository locations… either is fine. I'm fine with repositories "earning" their way into (or out of) the openmrs account through use or lack of use. The only potential downside of moving repositories around is breaking links (from wiki pages, emails, OpenMRS Answers, CI/maven scripts, etc.), but that's a minor/trivial issue. The ability for developers to be more agile is way more important, IMHO. Over time, if yours or any other module becomes largely managed by OpenMRS, then folks may prefer moving it into the openmrs organization in order to share the management burden; but, starting out under personal accounts is a more natural DCVS approach.
Cheers, -Burke On Sun, Mar 11, 2012 at 2:13 PM, Darius Jazayeri <[email protected]>wrote: > Hi Burke, > > I'm working on moving the 2.x UI Framework code into a module, and I > started using git for this, as I was working on the plane and wanted to be > able to locally commit, etc. > > Question: what's the right convention for where should I initially publish > this? > > Option 1: I put it at github.com/djazayeri/openmrs-module-uiframework. At > some point OpenMRS may actively decide to own this module, and clones it. > > Option 2: I put it at github.com/openmrs/openmrs-module-uiframework, > assuming that OpenMRS is going to want to own this. > > I think option 1 is right (and this would work equally well for me as for > non-core-devs), but wondering if you have any thoughts? > > -Darius > _________________________________________ 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]
