Re: [fossil-users] GitLab v. Fossil. Was: Eric Raymond (a.k.a. ESR) has published an SCM
On Sun, 26 Mar 2017 13:18:08 -0400 Richard Hippwrote: > > http://esr.ibiblio.org/?p=7448 > > http://www.catb.org/esr/src/ > > Thanks for pointing this out, Stephan. > > What intrigues me most here is not ESR's python-script wrapper around > RCS/SCCS, but rather the GitLab interface. I had heard of GitLab, but > had never before taken the time to look into it. My first impression > is that it seems much nicer than GitHub. [...] JFTR GitLab is written in Ruby, so it's not at all self-hosting. Fossil has a clear upper hand in this. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] GitLab v. Fossil. Was: Eric Raymond (a.k.a. ESR) has published an SCM
On 03/26/17 19:18, Richard Hipp wrote: [---] > (i) With Fossil, one can click on two nodes of the graph to see a > diff between those two nodes. With GitLab, you apparently have to go > to the separate "Compare" screen, then many type in (or paste in) hash > name prefixes of the two check-ins you want to compare. This seems > rather clumsy. But maybe I'm missing something. This is the same in Bitbucket. I use the version compare feature in the timeline in Fossil *a lot*; I'd almost be willing to stretch to say "literally daily", but I'm sure there's been a day when I haven't used it -- but you get the point. When I helped install a development environment based on the Atlassian products a while ago I was quite shocked that Bitbucket didn't support the feature. Considering how useful it is, I had never occurred to me that a modern UI _wouldn't_ have it. Anyway, I searched around to see if it was available in an alpha version or something somewhere, and quickly realized others wanted the feature as well. However, no good news on that front: The idea was apparently "No, you use tool X for that.". (As it happens, this tool X was a desktop application for the local checkout, which - in my mind - kind of defeated the purpose). Maybe this is tangentially related to the cathedral vs bazaar discussion; with Fossil, you typically have a central point where "all" the useful checkins end up. -- Kind regards, Jan Danielsson ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] GitLab v. Fossil. Was: Eric Raymond (a.k.a. ESR) has published an SCM
On 3/26/17, Stephan Bealwrote: > It seems that ESR has published his own SCM: > > http://esr.ibiblio.org/?p=7448 > http://www.catb.org/esr/src/ Thanks for pointing this out, Stephan. What intrigues me most here is not ESR's python-script wrapper around RCS/SCCS, but rather the GitLab interface. I had heard of GitLab, but had never before taken the time to look into it. My first impression is that it seems much nicer than GitHub. I mirrored a snapshot of ESR's GitLab repo using Fossil here: https://www.fossil-scm.org/tmp/esr-src (As you might infer from the "/tmp/" term in the URL, this is not a permanent link.) I think it is useful to compare the two interfaces, GitLab vs. Fossil. In particular, compare: https://www.fossil-scm.org/tmp/esr-src https://gitlab.com/esr/src/tree/master Two big questions: (1) What can Fossil learn from GitLab's interface? What ideas are there that can be copied from GitLab in order to improve Fossil? (2) What can GitLab learn from Fossil's interface? What ideas are there in Fossil that GitLab might copy for its benefit. I CC'ed "commun...@gitlab.com" on this reply with the hopes that they might join in the discussion. Under question (2) I'd like to make the following suggestions, in case somebody from gitlab actually reads this: (i) With Fossil, one can click on two nodes of the graph to see a diff between those two nodes. With GitLab, you apparently have to go to the separate "Compare" screen, then many type in (or paste in) hash name prefixes of the two check-ins you want to compare. This seems rather clumsy. But maybe I'm missing something. (ii) The timeline in Fossil is a lot faster than the graph of GitLab. (iii) I could not find any way to download tarballs of specific check-ins. Maybe I'm just not seeing it, but I could not find a way to get at the source code without cloning the repository. Under question (1) I offer the following: (iv) The "Branches" page seems to be busted. I think this is probably due to some kind of problem with the "fossil import" command that was used to convert the original Git repo. A general question to which I do not know the answer: How difficult would it be to stand up a GitLab community-edition instance for ESR's project? How does this compare with standing up a Fossil instance. I, of course, find Fossil a lot easier since I am familiar with it. But what do people say who do not have a bias one way or the other. What can Fossil and/or GitLab do to make it easier for newbies to set up new project instances on their own private servers? (See https://www.fossil-scm.org/fossil/doc/trunk/www/server.wiki for the documentation on how to create a server instance for Fossil.) -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users