[Kde-scm-interest] KDE Git hosting status update

[Sitaram Chamarty]

[I was pointed to this thread via URL by someone, so I
joined the list to reply!]

This is re Esben's concern[1] about me being the only developer
of gitolite.

Eike's response[2] already answers a lot, so I'll just add this:

  - there have been people who've sent me patches, and I've
    even accepted many of them.  Any of these folks could
    pick up the project if something happened to me

  - we use it at work, so someone at $DAYJOB may even pick
    it up :-)

It may help to realise that gitolite consists of the
following pieces:

  - the config file is "compiled" into a perl hash; this
    "compiler" is 620 lines approx

  - the access check is in two parts.  The part that kicks
    in right away (*before* git is called) is 220 lines
    approx.  The part that kicks in *after* git is called is
    the "update hook"; this is only applicable for a push
    operation and is about 120 lines
  - there's a common library of about 660 lines

That's a total of about 1600 lines.  If you leave out the
"compiler" it's about a 1000 lines -- this is the code that
runs "on each access".

The rest is just scaffolding and warm fuzzies ;-)

It really isn't very complex; anyone who knows perl can pick
it up quickly enough.  I'd guess even a *complete*
understanding of all these pieces might take no more than an
hour or two.  There are no funky tricks and the data
structures are fairly obvious.

I also tend to write a lot in the commit messages; coupled
with "git gui blame", they ought to help a lot.

Regards,

-- 
Sitaram

[1]: http://www.mail-archive.com/kde-scm-interest@kde.org/msg01279.html
[2]: http://www.mail-archive.com/kde-scm-interest@kde.org/msg01284.html