[Moose-dev] Re: Moving to GIT?

Hi, Please don't move source code to git, only bug tracker (or even try Bitbucket before or something else). I try to evade git as hell. Yep, I'm in a minority, but after trying git, svn, arch, bazaar, mercurial, trac and fossil I will keep the last one only (kind of a "GiHub in a box" on only 1.5 Mb self-contained simple to use and install binary). For the curious about Fossil at [1] you can find the workflow and at [2] some (biased) quotes about it versus git :-) (of course you could find this biased versus thing all the time for anything, but at least is a call to have a panoramic view before any choosing of a tool). [1] http://fossil-scm.org/index.html/doc/trunk/www/concepts.wiki#workflow [2] http://fossil-scm.org/index.html/doc/trunk/www/quotes.wiki One of the main reason that made git so popular was undoubtedly the Linux kernel community, but I don't understand why a tool that is suited for a thousand developers community and project should be forced into every development project and community. Its like a bazooka for killing mosquitoes with gratuitous complexity most of the times. I really like the integration, fine grained control and smoothness of Monticello in Pharo/Smalltalk for working with objects, not files. The only thing I'm missing is named and visual branches. But having a tool that has a cumbersome work flow, is difficult to install and all the time gets in your way is precisely the opposite of Monticello or any improvement we should be looking for on what we have now. Monticello (or fossil for that matter) is newbie friendly, Git is not. Please, only migrate to file based control system when it has the same smoothness of Monticello and hopefully with Git as an option, not before. Thanks, Offray El 07/04/15 a las 10:44, stephan escribió: _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev