[OSGeo-Discuss] OSGeo guidelines for code hosting ?
andrea.aime at geo-solutions.it
Sun Oct 18 12:26:13 PDT 2015
On Sun, Oct 18, 2015 at 12:08 PM, Sandro Santilli <strk at keybit.net> wrote:
> How does that diagram counts contributors ?
> With SVN it's very unlikely that a bot can recognize contributors
> other than the committers, while with GIT it's easier to make the
> actual contributor visible to a machine (being there an "author"
> field in addition to the "committer" field).
Indeed, it counts the committers, and it's true that it can be skewed,
but I assure you the overall effect is negligible.
Before pull requests we used to add a "patch by xyz" in the commit
message to give credit to the actual author. I looked at the year right
before the github switch, there are 4 commits like that in total (I searched
for just "by" to make sure not to skip stuff written with slight
If I look at the last year and ask for a contributor count I get:
> git shortlog -nsu --since "one year ago" | wc -l
Github tells me there are 34 developers with direct commit access, but I
who made a commit in the last year. we are down to only 24 people.
Sometimes devs commit from another computer and
they don't have their mail setup, which makes for a two lines in that
one with the username, one with the mail
e.g. in that list we have for example Mauro listed twice (and so is mine):
27 Mauro Bartolomeoli
So that reduces the number of actual unique contributorsq a bit, let's say
down to 75-80...
it's still 50 random people contributing to GeoServer without commit access
in the last year, or, in other words, 10 times more external contributions
compared to before the switch to Github.
The thing is, we still have patches in the bug tracker that are a few years
old, and they will likely never be merged: when they came in they probably
were either dirty, or core devs were too busy, and after a few months
applying them becomes rather challenging, so there they stay: the merge
was too high, too domanding on the core devs.
With the current pull request mechanism we have a much improved ability
to handle contributions, in part because people are reminded of the
contribution rules the moment they make the pull request, in part because
the build servers inform the submitter about a problem in the pull request
but also because we can comment in a more social way about the pull
request (before reviewing the patch was a one man job), and also because
are always nicely grouped and in front of our eyes at every PSC meeting
(we check the pull request queue like that every two weeks, to see
if there is anything that merits special attention).
> I'm not trying to negate the possible benefits in terms of number
> of contributors, but I'd be careful about the correctess of available
> > There is another benefit of moving to Github, which is build checks on
> > requests,
> Yes, this is something we unfortunately lost on OSGeo.
> We used to have buildbot running to that extent, but lack of volunteers
> made that experience come to an end.
Mind, here I'm talking about a special integration, not the normal
continuous build for commits that are integrated, but a custom build for the
pull request, which tells you whether or not merging that pull request
will break the build (to clarify, by build I mean both compiling and running
all automated tests save for OGC CITE compliance ones).
The pull request build status, along with an indication if the patch is
mergeable, and possibly an indication
of whether the test coverage went up or down, is a huge time saver.
If a review of the patch is satisfying, the build give us the green, we can
just press the merge button, thank the contributor, and move on with our
instead of spending time trying to apply while the code moved, build, go
back and forth
with the committer in a rather inefficient way (and manually run
build/tests every damn time), and so on.
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
Ing. Andrea Aime
Via Poggio alle Viti 1187
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Discuss