Everyone,
I need to make a final decision on the version control system the developers will use. It comes down to git and svn. What are your preferences and why? Thanks! Noel -- ------------------------------------------------------------------ Noel Henson www.noels-lab.com Chips, firmware and embedded systems www.vimoutliner.org Work fast. Think well. _______________________________________________ VimOutliner mailing list [hidden email] http://www.lists.vimoutliner.org/mailman/listinfo |
Noel Henson wrote:
> Everyone, > > I need to make a final decision on the version control system the > developers will use. It comes down to git and svn. What are your > preferences and why? Repository choices usually come down to what the developers will enjoy using. Not being an actual developer myself, and an infrequent repo user, both git and svn hold equal mystery for me. It's also worth considering which CVS will be easier to integrate with the new website. djp _______________________________________________ VimOutliner mailing list [hidden email] http://www.lists.vimoutliner.org/mailman/listinfo |
David J Patrick wrote:
> Noel Henson wrote: >> Everyone, >> >> I need to make a final decision on the version control system the >> developers will use. It comes down to git and svn. What are your >> preferences and why? I might consider outright emulation/duplication of the tasktools.org approach, or at least the parts that make sense for VO. It seems to be working brilliantly and I'm sure that team would be happy to provide advice in setting it up. djp _______________________________________________ VimOutliner mailing list [hidden email] http://www.lists.vimoutliner.org/mailman/listinfo |
In reply to this post by Noel Henson
On Monday 08 February 2010 10:46:39 Noel Henson wrote:
> Everyone, > > I need to make a final decision on the version control system the > developers will use. It comes down to git and svn. What are your > preferences and why? > > Thanks! > > Noel Personally I prefer the old way -- emailing the file to the maintainer. I know nothing about svn and the only thing I know about git is it was invented by Linus to manage a huge project very different from VO, and it's supposed to be an albatross. Personally I'd vote for the one that's most intuitive to the guy who might use it three times a year, but of course that's not your target audience so I just ask whichever you go with, you put basic level instructions for its use on the website. Thanks SteveT Steve Litt Author: Universal Troubleshooting Process books and courseware http://www.troubleshooters.com/ (Legal Disclaimer) Follow these suggestions at your own risk. _______________________________________________ VimOutliner mailing list [hidden email] http://www.lists.vimoutliner.org/mailman/listinfo |
In reply to this post by Noel Henson
git.
* it's fast * it's excellent for working with volunteers / 3rd-party contributors _______________________________________________ VimOutliner mailing list [hidden email] http://www.lists.vimoutliner.org/mailman/listinfo |
In reply to this post by Noel Henson
On Mon, Feb 08, 2010 at 07:46:39AM -0800, Noel Henson wrote:
> I need to make a final decision on the version control system the > developers will use. It comes down to git and svn. The main difference between svn and git is that the svn is centralized and git is a distributed VCS. The difference between both concepts is explained on [1]. Especially the paragraph "Organizing a Distributed Project" should be interesting for vimoutliner. The image in this paragraph shows a project where the maintainer has only one branch, for vimoutliner I could image an additional staging area or an experimental branch to test things before you merge them into your stable branch. A possibly biased comparison between git and svn can be found on [2]. [3] shows how git looks in practice using an other open source project of comparable size (though more rapidly developed in the last few months) as example. Everyone can create forks/branches at any time, the maintainer of the main branch can chose which patches from other peoples branches he or she wants to pull into his official branch. The whole merging and branching is optional, one can also use git as one would use svn, so if you choose git you could also use it like you would use an centralised vcs, but make it more easy for others to follow your development and maintain their non-official patches. Those who don't want to or don't know how to use a vcs could still send patches per mailing list. Since this is often used in the linux development, there are git subcommands that support this, although one can of course still send and apply patches using the known traditional commands. > What are your preferences and why? I think, especially since this is not a fulltime project for you and you might need time to review some contributed patches because you are busy doing more important things, vimoutliner could greatly benefit from using a distributed VCS. Imagine you are really busy for one or two months and someone posts a bigger patch to the list. When others merge this patch and some add fixes or improvements to their branches, these improvements could be shared and further improved as easily as the original patch. This could lead to an already matured and more clean patch series even before you find time to review it and thus save your time. With a centralized VCS, the development would probably stagnate if the main maintainer is busy. Regards Carsten [1] http://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/ [2] http://git.wiki.kernel.org/index.php/GitSvnComparison [3] http://github.com/Dieterbe/uzbl/network _______________________________________________ VimOutliner mailing list [hidden email] http://www.lists.vimoutliner.org/mailman/listinfo |
Free forum by Nabble | Edit this page |