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/ _________________________________________ 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]
