I would favor mimicking the approach we learned from Subversion about managing repository access – i.e., address it socially, not technically. Of course, we'll have to work with what GitHub offers, but ideally within the OpenMRS organization in GitHub there would be a handful of core folks who can administrate repositories (rename them, delete them, create them) and then a large pool of devs (any of our partial/full committers in the SVN world) who could pull/push against any of our repositories, and then anyone in the world could pull from them.
Managing teams & access on a repository-by-repository basis seems like something that will be a lot more effort to scale & manage. But GitHub might not give us the option. -Burke On Thu, Nov 10, 2011 at 11:04 AM, Mark Goodrich <[email protected]> wrote: > It probably makes sense just to create a core-devs team for now, and then > we can create specific teams for modules as needed if we find we want to > give someone commit access to a module who isn’t a core-dev.**** > > ** ** > > Mark**** > > ** ** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Rowan > Seymour > *Sent:* Thursday, November 10, 2011 10:09 AM > > *To:* [email protected] > *Subject:* Re: [OPENMRS-DEV] FW: HTML form entry changes**** > > ** ** > > Remember this is github functionality - not plain old git. There are > organization "owners" who can administer/push/pull any repository in that > organization. Then you can create as many teams as you want > with administer/push/pull permissions and you can as many teams to a > repository as you want. Unfortunately teams can't have owners and > repositories can't have arbitrary owners either. But you could make sure > that all the core devs are in a team which is added to every module project. > **** > > ** ** > > So taking HTML form entry as an example, it might have the following teams: > **** > > ** ** > > Owners (this is implicit and they have administer/push/pull access)**** > > core-devs (these guys are added to every repos with push/pull access)**** > > htmlformentry-devs (these guys have explicit push/pull access on this > repos)**** > > ** ** > > It would be a apin managing all those teams, but it would keep the push > access nicely locked down**** > > ** ** > > On 10 November 2011 16:50, Mark Goodrich <[email protected]> wrote:**** > > I’m not familiar with Git yet, but I could see the pluses and minuses of > having one team versus multiple teams. Would it be possible for a team > owner to add a team member, or does it have to be an organization owner? > It would be nice to maintain control over commit access to module, but we > don’t want to introduce too much operational overheard that would, for > instance, prevent a core Openmrs developer to commit a quick bug fix to a > module.**** > > **** > > Mark**** > > **** > > **** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Rowan > Seymour > *Sent:* Thursday, November 10, 2011 3:36 AM > *To:* [email protected] > *Subject:* Re: [OPENMRS-DEV] FW: HTML form entry changes**** > > **** > > I think this good - it means that even when you fork a project into a > different account or organization you can still see right away that it's an > OpenMRS module or contrib project just from the repo name.**** > > **** > > I took the liberty of renaming the OpenMRS repo and our EHSDI fork. For > anyone with a local copy of the OpenMRS repo you will need to run this git > command:**** > > **** > > git remote set-url origin [email protected]: > OpenMRS/openmrs-module-htmlformentry.git > > We should take some time to think about teams. Do we want just one global > set of permissions (i.e. one team) for module developers (like SVN world) > or do we want separate teams for each module? The latter would mean that if > I want to push commits to a module then I have to be added to a specific > developer team for that module, by an organization owner.**** > > **** > > E.g. for the HFE module we'd have a team like...**** > > **** > > openmrs-module-htmlformentry-devs**** > > **** > > Thoughts?**** > > **** > > On 9 November 2011 22:03, Burke Mamlin <[email protected]> wrote:*** > * > > After some discussion on IRC, we landed on this:**** > > **** > > One organization: OpenMRS**** > > **** > > Core: github.com/openmrs/openmrs-core/**** > > **** > > Modules: github.com/*{account}*/openmrs-module-moduleid/**** > > **** > > Contribs: github.com/*{account}*/openmrs-contrib-foobar/**** > > **** > > So, for example, we have 2 repositories to start:**** > > **** > > github.com/openmrs/openmrs-module-htmlformentry/**** > > github.com/openmrs/openmrs-contrib-modulerepository/**** > > **** > > While "openmrs" may feel redundant within the OpenMRS organization's > repository, it establishes the convention (for everyone) of prefixing > OpenMRS modules with "openmrs-module-" and prefixing other contributions > with "openmrs-contrib-". Of course, people can do whatever they want, but > if they want their work to be recognized as, for example, an OpenMRS > module, then they can add the prefix.**** > > **** > > This may not be the perfect solution, but it feels like a fairly > straightforward switch from our SVN conventions and could get us by for the > near term.**** > > **** > > Thoughts/concerns?**** > > **** > > @Kishore – could you rename the HTML-Form-Entry repository to > openmrs-module-htmlformentry?**** > > **** > > -Burke**** > > **** > > On Wed, Nov 9, 2011 at 2:09 PM, Rowan Seymour <[email protected]> > wrote:**** > > I'm with Downey - why is it so important that the URL of htmlformentry has > "openmrs-modules" in it? What if GitHub adds a mechanism for organizing > repositories tomorrow after we've split the organization?**** > > **** > > How about we investigate using the Github API to parse either names, > descriptions or READMEs to generate our own lists of modules / contribs etc? > **** > > **** > > On 9 November 2011 20:27, Michael Downey <[email protected]> wrote:**** > > Perhaps I've missed it as this thread is now over 50 messages long, but > what is the justification for splitting OpenMRS into multiple > organizations? As far as i know there is only one OpenMRS community. > Forking the organization seems to be making things unnecessarily complex, > especially at this early point, unless I'm missing some actual problem > (which is certainly possible).**** > > Anyway, if not, I object to such obfuscation as a misuse of GitHub > organizations.**** > > -- > Michael Downey > * Sent from my mobile phone**** > > On Nov 9, 2011 1:06 PM, "Yekkanti Kishore Kumar" <[email protected]> > wrote:**** > > 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.**** > ------------------------------ > > 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 > **** > > > > **** > > **** > > -- > *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 > **** > > > > **** > > ** ** > > -- > *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 > _________________________________________ 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]
