[fpc-other] Git & SVN
Graeme Geldenhuys
mailinglists at geldenhuys.co.uk
Thu May 25 00:44:57 CEST 2017
On 2017-05-24 21:21, Marco van de Voort wrote:
> Even a limited change is already a massive operation, let's keep it
> managable.
So how large is the FPC team really? I'm talking about active developers
on a day-to-day basis who have commit access to Trunk.
Oh wait, I can answer that very accurately myself... using git.
$ cd /data/devel/fpc-3.1.1/src
[src (master)]$ git shortlog -s -n --since=4.months
191 Michael Van Canneyt
147 Mattias Gaertner
140 nickysn
83 svenbarth
73 Florian Klaempfl
62 pierre
52 Joost van der Sluis
39 maciej
30 karoly
26 Marco van de Voort
23 Jonas Maebe
22 yury
7 lacak
5 marcus
3 Sergei Gorelkin
2 hajny
So that's 16 developers - a nice size, but also not a large team (say
compared to the KDE project that moved from SubVersion to Git, or LLVM
seeing as that was mentioned earlier). The amount of commits are also
not huge - so they most likely have a day job. ;-)
And the two developers with the most commits (by a large margin) work
primarily in the RTL and FCL. That's development work like any other
project I have worked on. Nothing special or "rocket science" about that
(sorry Florian).
As for the 3rd person "nickysn"... I see he/she actually worked on the
compiler/* tree. How do I know this?
$ git log --name-only --oneline --since=2.months --author=nickysn
Randomly picking some other authors, it seems most work is primarily in
the RTL and FCL. A few small exceptions like Sven and Florian who mostly
work in the compiler tree.
So this definitely doesn't convince me that compiler development is so
different to other projects. And definitely doesn't rule out that Git
couldn't work, or that an improved workflow couldn't be applied (freeing
up time in the long run).
But I get in now. You guys are set in your ways - good or bad, and
currently not willing to change. So I'll leave it at that.
Regards,
Graeme
More information about the fpc-other
mailing list