If the url http://github.com/openmrs-modules/htmlformentry seems fine with every one, we need to create openmrs-modules organisation. Michael - can you help with this and give me collaborator access. I can push htmlformentry module from "openmrs" to "openmrs-modules".
Regarding the already cloned/forked repositories- we have two options - Change the local repo remote url to track new 'openmrs-modules' repo Ex: git remote add "[email protected]:OpenMRS-Modules/htmlformentry.git" - If much work is not yet done on the forked repo, ignore/delete it and reclone/fork from the new repo. On Wed, Nov 9, 2011 at 10:49 PM, Burke Mamlin <[email protected]>wrote: > Yup, OpenMRS, OpenMRS Modules, and OpenMRS Contrib, essentially matching > what we currently have at http://source.openmrs.org now. > > Something like this: http://github.com/openmrs-modules/htmlformentry > > -Burke > > > On Wed, Nov 9, 2011 at 12:01 PM, Rowan Seymour <[email protected]>wrote: > >> Wouldn't that mean that there would have to separate GitHub organizations >> for OpenMRS-Trunk, OpenMRS-Modules and OpenMRS-Contrib ? >> >> >> On 9 November 2011 18:40, Darius Jazayeri <[email protected]>wrote: >> >>> Kishore and I were talking and we think it should be: >>> https://github.com/OpenMRS-Modules/htmlformentry >>> >>> Is that right? >>> >>> -Darius >>> >>> >>> On Wed, Nov 9, 2011 at 7:23 AM, Burke Mamlin <[email protected]>wrote: >>> >>>> On Wed, Nov 9, 2011 at 8:49 AM, Rowan Seymour >>>> <[email protected]>wrote: >>>> >>>>> There doesn't seem any way to organize or label repositories like >>>>> "module" or "contrib"... should we integrate that into the repository >>>>> name, >>>>> e.g. *module.htmlformentry* ? >>>>> >>>> >>>> Perhaps a convention in the README.txt file – e.g., starting with a >>>> line like "# /openmrs-modules/moduleid" vs. "# /openmrs-contrib/mycontrib" >>>> >>>> I dunno. I was happing for labels in GitHub, but didn't find them. >>>> The most important thing is that there's some insanely trivial/easy way >>>> for devs to mark their work as an OpenMRS module or contrib that a >>>> non-human process (script, bot, whatever) can find and to organize any >>>> OpenMRS-related work for the community. I'm not a Git guru, but my hunch >>>> is that some conventions in a README.txt (title, id, description, etc.) >>>> would suffice and could work across repository types (svn, git, mercurial, >>>> etc.). >>>> >>>> Question for the Git gurus... what happens when you rename a Github >>>>> repository? Will forked repositories be updated? >>>>> >>>> >>>> I believe anybody using the repository would need to issue a git >>>> remote set-url remotename git://github.com/new/path.git.[1] >>>> >>>> Cheers, >>>> >>>> -Burke >>>> >>>> [1] http://help.github.com/remotes/ >>>> ------------------------------ >>>> Click here to >>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>>> OpenMRS Developers' mailing list >>>> >>> >>> ------------------------------ >>> Click here to >>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >>> >> >> >> >> -- >> *Rowan Seymour* >> tel: +250 783835665 >> http://twitter.com/rowanseymour >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list >> > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > -- Regards, Kishore Kumar Yekkanti. _________________________________________ 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]
