Re: Github?
"Ing. Daniel TIHELKA Ph.D." <[email protected]> Mon, 20 Feb 2012 08:26:55 +0100
| Newsgroups | gmane.comp.java.cruise-control.devel |
|---|---|
| Message-ID | <2a78-4f41f580-b-5b384580@180482549> |
On Sunday, February 19, 2012 20:59 CET, Julian Simpson <[email protected]> wrote: > On 5 February 2012 09:55, Ing. Daniel TIHELKA Ph.D. <[email protected]>wrote: > > > Hi all, > > I am also not against moving to GitHub. > > > > However, as Dan Rollo said: > > > Downsides are that any existing patches in Jira against svn become > > harder to apply. > > > > And I have few patches prepared (asked for revision). > > > > So, I would suggest to open "pre-migration" window, in which paches still > > waiting for revision will be checked and considered for being applied. To > > get the list of such patches, let their authors sent JIRA issue codes (or > > the patches directly) to this list.This will allow to solve waiting > > requests for all those actively folowing the development. Having such list, > > we can decide which patches/requests can go in and which will wait until > > moving to GitHub. > > > > Do you think it would be manageable? > > > > I'm wondering what the difference is between applying a patch to a SVN > sandbox vs. applying a patch to a Git repository. I'd assumed that both > used a tool like patch [1] to apply the diff. Do we do anything different? > Actually yes, applying patches is the same (I suppose). I just wanted to save slight amount of my spare time :-)). Moving to git mans (for me) to lear to use it, which I suppose is not difficult, it just needs to make some time for it ... So again, I am not against moving. Dat T. > Julian. > > > > > > Regards, > > Dan T. > > > > > > > > On Saturday, February 4, 2012 18:47 CET, Dan Rollo <[email protected]> > > wrote: > > > > > I'm not against a move to GitHub. > > > > > > Downsides are that any existing patches in Jira against svn become > > > harder to apply. That said, I recognize there has not been a lot of > > > patch activity, so maybe that is not a blocker. I would ask that we do > > > not make such a move until I at least get to a couple patches that have > > > been on my plate for a while. > > > > > > If a move to github occurs, it should be done in a way that preserves > > > the history (and tags/branches) from svn (as described in the git docs). > > > > > > Some might argue that git is still a slightly higher learning curve for > > > new users than svn, but the power of git can't be ignored. > > > > > > I'm fine with the idea of moving to git. Any thoughts from the lists? > > > > > > Dan > > > > > > > > > From: Paul Julius <[email protected]> > > > Subject: Re: [Cruisecontrol-devel] Github? > > > > > > +1 > > > > > > But I would be most interested in hearing Dan Rollo's feedback. > > > > > > - PJ > > > > > > On Feb 2, 2012, at 2:14 PM, Julian Simpson <[email protected]> > > wrote: > > > > > > > > Hello, > > > > > > > > > > I was talking to Jeffrey Fredrick the other day about putting the > > > CruiseControl source code on GitHub. I said I'd raise the question on > > > the mailing list. > > > > > > > > > > My thinking is that the project is more likely to get pull requests > > > from GitHub users, than it is to get diffs via JIRA. CruiseControl may > > > get some more love by doing this: IMHO using GitHub lowers the bar to > > > participation. Sure, some people will fork the project and never give > > > back, but it's done in an overt way. > > > > > > > > > > Naturally, all the committers keep their roles, just on a different > > > system. > > > > > > > > > > Any comments? > > > > > > > > > > Sincerely > > > > > > > > > > Julian. > > > > > > > > > > > > > > > -- > > > > > Julian Simpson > > > > > The Build Doctor Ltd. > > > > > http://www.build-doctor.com > > > > > [email protected] > > > > > (+44) 207 183 0323 > > > > > > > > ------------------------------------------------------------------------------ > > > Try before you buy = See our experts in action! > > > The most comprehensive online learning library for Microsoft developers > > > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > > > Metro Style Apps, more. Free future releases when you subscribe now! > > > http://p.sf.net/sfu/learndevnow-dev2 > > > _______________________________________________ > > > Cruisecontrol-devel mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Try before you buy = See our experts in action! > > The most comprehensive online learning library for Microsoft developers > > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > > Metro Style Apps, more. Free future releases when you subscribe now! > > http://p.sf.net/sfu/learndevnow-dev2 > > _______________________________________________ > > Cruisecontrol-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel > > > > > > -- > Julian Simpson > The Build Doctor Ltd. > http://www.build-doctor.com > [email protected] > (+44) 207 183 0323 ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2