Question about used Workflows.

Dear Git developers and contributors,

I was wondering what kind of workflow the Git project itself uses. From
what I gather much of the development takes place using the list, and
patches sent by mail. Do any of the core contributers maintain public
developer repos? And how many developers on average have push privileges
to http://git.kernel.org/?p=git/git.git;a=summary?

thanks

Valentin

On 03/15/2011 02:43 PM, Valentin Haenel wrote:

Dear Git developers and contributors,

I was wondering what kind of workflow the Git project itself uses. From
what I gather much of the development takes place using the list, and
patches sent by mail.

That's correct.

Do any of the core contributers maintain public
developer repos?

Some do, although most contributions are still sent as patches for
public discussion and then taken from there by Junio who has some
nifty routine for that already.

Subpart maintainers, such as the gitk author Paul Mackerras (spelling?)
have repos of their own from which Junio pulls on request. Normally
that's in parts where Junio feels his knowledge lacking and he trusts
the subpart maintainer. From what I've gathered, Tcl isn't Junio's
strong point.

And how many developers on average have push privileges
to http://git.kernel.org/?p=git/git.git;a=summary?

There's no "average" to it. Linus probably still has push access as
he's the founding father and first maintainer. Junio ofcourse has it
as the current maintainer. Shawn Pearce has taken over maintenance
a few times when Junio has been absent for one reason or another. I
doubt push privileges have been revoked in between absences. Oh, and
ofcourse the kernel.org admin team have more or less implicit access
to push, although the git community would certainly frown quite hard
if they ever (ab)used their admin powers to do that.

All that aside; By peer etiquette and for simplicity reasons, only
the current maintainer ever pushes anything to kernel.org. Noone
becomes maintainer (or kernel.org admin) without having invested a
lot of time and shown a lot of devotion to the project.

For some public credit, Junio's doing a great job both maintaining
and choosing interim maintainers. I've rarely seen an opensource
project where the maintainer so rarely (ever?) get annoyed at
anything and keeps everything running smoothly.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.