Thierry and Offray ...
I don't have the time to personally dig into Fossil (at the moment), but I am in favor of leveraging the "best SCM for the job" FileTree is an SCM neutral disk format so supporting alternate SCMs is more of a "tools issue" ...
Git/Github was targeted initially, because one had to start somewhere... the [GitHub collaboration tools][1] are pretty darn good up on GitHub and that is another of the major appeals for me ... Haven't looked closely at Fossil so I can't comment on the state of their collaboration tools ...
With regards to bitbucket ... I added bitbucket:// support to Metacello for doing direct downloads of repositories from a Metacello project references (ala github://), however with bitbucket being picked up by gitlab, it's not quite as easy to implement a gitlab:// ... The github:// feature means that developers can load code from a github-based repository without having to install git first .... a definite advantage in the days (even now) when git/hg/fossil/svn aren't widely installed by pharo/gemstone/squeak users ...
Dale
[1] https://help.github.com/categories/collaborating/ [2] https://github.com/dalehenrich/metacello-work/issues/287#issuecomment-598152...
On 04/07/2015 12:11 PM, Thierry Goubier wrote:
Hi Offray,
reading through Fossil... I think one could turn GitFileTree in a FossilFileTree in a matter of hours, at most days. If you want to work with Fossil, I would encourage you to explore this way.
Thierry
Le 07/04/2015 19:54, Offray Vladimir Luna Cárdenas a écrit :
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ó:
On 07-04-15 16:53, Alexandre Bergel wrote:
We will soon have to change our bug trackers. What about taking this opportunity and moving to GIT?
I very much like using git and github for doing small commits to text repositories like PFTE. I would love to have a nicely integrated workflow for source code too. The work by (a.o) Thierry makes me confident that we'll be able to achieve that in the not too far future. At the moment however, we are not even able to reliably find the git executable on all platforms.
Stephan
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev