Try http://progit.org/book/ and http://www.spheredev.org/wiki/Git_for_the_lazy
I've tried Egit (the Eclipse plugin available in the market place) but really the command line isn't so bad (I find it easier than SVN), and there's great github client for OSX. Just downloading the m2e connector for git right now to see how that works.. On 10 November 2011 17:06, Lara Kellett <[email protected]> wrote: > Does anyone have a good dummies guide to Git, in particular what is the > easiest way to use Git with Eclipse? > > Thanks, > > Lara > ________________________________________ > From: [email protected] [[email protected]] On Behalf Of Mark Goodrich [ > [email protected]] > Sent: Thursday, November 10, 2011 4:50 PM > To: [email protected] > Subject: Re: [OPENMRS-DEV] FW: HTML form entry changes > > 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]<mailto: > [email protected]>> wrote: > After some discussion on IRC, we landed on this: > > One organization: OpenMRS > > Core: github.com/openmrs/openmrs-core/< > http://github.com/openmrs/openmrs-core/> > > Modules: github.com/<http://github.com/>{account}/openmrs-module-moduleid/ > > Contribs: github.com/<http://github.com/>{account}/openmrs-contrib-foobar/ > > So, for example, we have 2 repositories to start: > > github.com/openmrs/openmrs-module-htmlformentry/< > http://github.com/openmrs/openmrs-module-htmlformentry/> > github.com/openmrs/openmrs-contrib-modulerepository/< > http://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] > <mailto:[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]<mailto: > [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] > <mailto:[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] > <mailto:[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] > <mailto:[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]<mailto: > djazayeri%[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] > <mailto:[email protected]>> wrote: > On Wed, Nov 9, 2011 at 8:49 AM, Rowan Seymour <[email protected] > <mailto:[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< > http://github.com/new/path.git>.[1] > > Cheers, > > -Burke > > [1] http://help.github.com/remotes/ > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > > > > -- > Rowan Seymour > tel: +250 783835665<tel:%2B250%20783835665> > http://twitter.com/rowanseymour > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > > > > -- > Regards, > Kishore Kumar Yekkanti. > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > > > > -- > Rowan Seymour > tel: +250 783835665<tel:%2B250%20783835665> > http://twitter.com/rowanseymour > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > > > > -- > Rowan Seymour > tel: +250 783835665<tel:%2B250%20783835665> > http://twitter.com/rowanseymour > ________________________________ > Click here to > unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> > from OpenMRS Developers' mailing list > ________________________________ > Click here to > unsubscribe<mailto:[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] > -- *Rowan Seymour* tel: +250 783835665 http://twitter.com/rowanseymour _________________________________________ 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]
