From: Andreas Ericsson <ae@op5.se>
To: Valentin Haenel <valentin@fsfe.org>
Cc: Git-List <git@vger.kernel.org>
Subject: Re: Question about used Workflows.
Date: Tue, 15 Mar 2011 15:15:01 +0100 [thread overview]
Message-ID: <4D7F7465.8000307@op5.se> (raw)
In-Reply-To: <20110315134331.GA5165@kudu.in-berlin.de>
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.
next prev parent reply other threads:[~2011-03-15 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 13:43 Question about used Workflows Valentin Haenel
2011-03-15 14:15 ` Andreas Ericsson [this message]
2011-03-15 17:57 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7F7465.8000307@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=valentin@fsfe.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).