Re: [limesurvey-developers] Usage of GIT -what do you think?
The leading Open Source survey tool
Brought to you by:
c_schmitz
From: Andrie de V. <apd...@ya...> - 2012-01-21 15:56:14
|
Thomas I don't think you *need* to do move the bug tracker system. It's just that the whole GIThub "thing" is about having the browsing of repositories and issue tracking all in the same place. This makes code review reasonably easy (although there are probably much better tools for this, judging by some online comments.) As for your other questions, about porting to/from Mantis, and interaction with Mantis: I'm sorry but I have no idea. My point was more to highlight the fact that this decision should be about more than just adopting a new VCS. What's equally important is the decisions and strategy for adopting a whole different way of working (or not). Since I have built my websites on Drupal, I followed the Drupal migration from CVS to GIT with half an eye. Drupal is an enormous project, so spent a lot of time planning for the migration. It might be useful to review some of their planning, documentation and communication about this. See the page and links at http://drupal.org/community-initiatives/git Andrie On 21/01/2012 15:46, Thomas White wrote: > Andrie- > > Why would we need to move the bug tracker off of Mantis and to GIThub? > What are the pros/cons of GIThub's bug-tracking system? Can we import > from Mantis? Or, would we simply run Mantis on the GITHub hosting > environment? > > /Tom > > On Sat, Jan 21, 2012 at 10:37 AM, Andrie de Vries > <apd...@ya... <mailto:apd...@ya...>> wrote: > > Hi > > I have been using GIT and GIThub for all of my (public) projects, > since > November 2010. Github works just fine, online availability is > extremely > high and I find the online interface very easy to use. > > For most practical aspects, there isn't much difference between using > SVN or GIT (at least for my usage needs). I like GIT because I can > very > easily create local repositories and then clone them to GIThub > later, if > I wish. > > If you are used to using Tortoise to interact with SVN, then you will > find that the TortoiseGit client is very similar. Some terminology is > different, e.g. you push and pull in GIT, rather than update and > commit > in SVN. > > The fact that it is very easy to create a branch is no problem at all. > This doesn't have to change the way you work. In other words, you can > still allow people to push directly to your mainline. But, it is > also an > easy way for new people to get involved. So I think that's mainly > a good > thing. > > As part of the decision whether to move to GIThub or not, you need to > decide whether you are going to move the bug tracking and ticketing > system to GIThub. If you don't, I don't see much point of selecting > GIThub rather than staying with the existing SVN. > > My view: go for it. > > Andrie > > On 21/01/2012 15:26, Thibault Le Meur wrote: > > Hi everyone, > > > > I like SVN, but I think that, given the basic use we have of it, GIT > > would do the job equally. > > > > I just have 2 points that are worth dealing with before we jump > to GIT: > > * Is there an easy GUI to it. Our translators are used to have their > > friend "TortoiseSVN" do all the dirty work for them. > > * Will there be an easy way to get the changelog in XML format > or any > > easilly parsed format so that we can adapt the release script ? > > > > Thibault > > > > > > I'm not against switching to Git, but it will require time > before the > > automated release svripts be adapted. > > > > ----- Message de tom...@gm... > <mailto:tom...@gm...> --------- > > Date : Sat, 21 Jan 2012 09:50:16 -0500 > > De : Thomas White<tom...@gm... > <mailto:tom...@gm...>> > > Répondre à : lim...@li... > <mailto:lim...@li...> > > Objet : Re: [limesurvey-developers] Usage of GIT -what do you > think? > > À : lim...@li... > <mailto:lim...@li...> > > > > > >> I've never used Git, but in reading about it last night, it sounds > >> interesting. Especially the part about being able to tell that > you've > >> renamed files and/or refactored code. That would certainly be > helpful for > >> 1.9x to 2.x transition, if it works. > >> > >> I also like the idea of being able to maintain my own copy > (like the > >> equivalent of limesurvey_dev_tms branch) without interfering > with anyone > >> else, yet being sure it can stay stable during active > development. I'm > >> less keen about the idea of forked copies - it would be nice to > ensure that > >> people had flexibility, but would contribute back and not > truly fork the > >> project. > >> > >> The workflow also sounds a bit different, but potentially > manageable - > >> especially if there is an auto-push feature after local commit > to a bare > >> shared public repository. > >> > >>> From and IDE perspective, I see that Netbeans 7.1 should > support it (I'm a > >> Netbeans person - never really liked PHPEdit or Eclipse), but > I've never > >> tried it, so don't know how it will look/feel/behave. > >> > >> So, before making a decision, I'd like to see it in action with > LimeSurvey > >> code. So, why don't we load the full SVN history to Git (say > on GitHub) in > >> a private git instance so that the developers can give it a try > for a week > >> or two. In the meantime, let's continue to use SVN. If it > really works as > >> well as it is supposed to, we can make a decision in a few > weeks and create > >> a new Git repository with the newest SVN history. That seems > the safest > >> path. I did something similar in converting from CVS to SVN > many years ago > >> - the fact that I could safely revert made the decision much > easier. > >> > >> So, I'm cautiously supportive of moving to GIT, but want us to > do our due > >> diligence first. > >> > >> /Tom > >> > >> > >> On Fri, Jan 20, 2012 at 11:37 PM, Jason > Cleeland<ja...@cl... <mailto:ja...@cl...>> wrote: > >> > >>> Hi everyone, > >>> > >>> While I don't find Subversion to be lacking anything I need at > the moment, > >>> I > >>> am aware that the overall thrust across OpenSource development > is to move > >>> towards GIT. > >>> > >>> In that regard, I think it's worth moving across to GIT if > only to make > >>> sure > >>> we don't fall behind. > >>> > >>> I've also been to quite a few conferences where GIT has > presented and it > >>> looks like there are some nice features to it that will be > useful - > >>> particularly for crazy people like me who have a few forks of > LimeSurvey > >>> for > >>> various clients and for personal use. > >>> > >>> So, in that regard, I think it may be worth moving across to > GIT too. > >>> > >>> On the down side, I really don't like having to learn new > tools, so I don't > >>> look forward to that part. > >>> > >>> Overall, consider my opinion to be in favour of moving to GIT. > >>> > >>> Jason > >>> > >>> -----Original Message----- > >>> From: Carsten Schmitz [mailto:car...@li... > <mailto:car...@li...>] > >>> Sent: Saturday, 21 January 2012 9:50 AM > >>> To: lim...@li... > <mailto:lim...@li...> > >>> Subject: [limesurvey-developers] Usage of GIT -what do you think? > >>> > >>> Hi everyone! > >>> > >>> In the past I was asked repeatedly ba different persons if we > would move > >>> our > >>> repository to GIT and maybe even GITHub, too. So far I felt we > never would > >>> get a majority for this but recently these voices got louder, > last not > >>> least > >>> by our former GCI/GSOC students. > >>> > >>> So I would like to ask around who from our team would > support/oppose such a > >>> decision. I am fairly neutral about this, and I am not sure what > >>> advantages/disadvantages such a move would bring. > >>> > >>> I would also like to exclude from this discussion a partial > move (like host > >>> only LimeSurvey 2 on GIT) because I don't want split > repositories and I > >>> don't want to loose our history from Subversion. So IF we move > to GIT it > >>> must be a complete move. > >>> > >>> I know that social coding like GITHub is the current big > thing. Frankly I > >>> am > >>> a little scared about it, because I don't want 30 forks on > GITHub - in the > >>> other hand I know that 30 forks on GITHub (assuming that > people will be > >>> able > >>> to easier fork LimeSurvey, work and new features and ask per > Pull request > >>> to > >>> incorportate their changes) would be a great thing because it > is chance for > >>> LimeSurvey to easily pull in new developers. > >>> > >>> So, let the discussion begin. Adress my concerns, voice yours. > State what > >>> you would like to do. Move or no move to GIT - pros and cons. > >>> > >>> Thank you > >>> > >>> Carsten > >>> > >>> > >>> > >>> > >>> > >>> > ---------------------------------------------------------------------------- > >>> -- > >>> 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 > >>> _______________________________________________ > >>> limesurvey-developers mailing list > >>> lim...@li... > <mailto:lim...@li...> > >>> https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> 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 > >>> _______________________________________________ > >>> limesurvey-developers mailing list > >>> lim...@li... > <mailto:lim...@li...> > >>> https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > >>> > > > > ----- Fin du message de tom...@gm... > <mailto:tom...@gm...> ----- > > > > > > > > > ------------------------------------------------------------------------------ > > 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 > > _______________________________________________ > > limesurvey-developers mailing list > > lim...@li... > <mailto:lim...@li...> > > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > > > ------------------------------------------------------------------------------ > 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 > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > <mailto:lim...@li...> > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > > > > ------------------------------------------------------------------------------ > 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 > > > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers |