Re: Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration.

On Tue, May 23, 2023 at 08:12:10PM +0000, Joseph Myers wrote:
> On Tue, 23 May 2023, Konstantin Ryabitsev wrote:
> 
> > Okay, perhaps I'm not fully grokking the picture. How many people are able to
> > push to master/release branches? I was expecting it to be 1-2, maybe a handful
> > of people, but perhaps it's a much wider set of developers?
> 
> There are 612 users in the gcc group.  There are 121 users in the glibc 
> group.  There are 461 users in the src group (which can commit to the 
> binutils-gdb repository).

Okay, clearly a totally different approach to the kernel world where only a
single person (or perhaps 2-3 people) can write to a repository like
torvalds/linux.git or stable/linux.git. Hence my misunderstanding of what is
happening.

Can you please describe the lifecycle of a patch and how it gets from "user
sends a change to the mailing list" to "that patch becomes a commit in the
official project repository where it lives forever."

E.g. for the kernel, it is:

- the patch receives initial review by the subsystem maintainer
- after a few iterations, the patch is committed to that maintainer's
  separate repository (either on kernel.org or elsewhere)
- during the merge window, the maintainer sends a pull request to the mainline
  maintainer (Linus) who does a final review and either rejects it or merges
  it into the mainline

I need to more clearly understand the kind of access 612 users of the gcc
group have to the git repository.

-K