On 3/26/17, Stephan Beal <sgb...@googlemail.com> wrote:
> 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

Reply via email to