This is the mail archive of the
mailing list for the GDB project.
Re: GDB's roles
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gdb at sources dot redhat dot com
- Date: Fri, 21 Feb 2003 13:51:23 -0500
- Subject: Re: GDB's roles
- References: <3E567466.email@example.com>
On Fri, Feb 21, 2003 at 01:48:06PM -0500, Andrew Cagney wrote:
> Core Maintainers:
> These are the people on which everyone else depends. They put
> themselves to the grindstone ensuring that the GDB wheel keeps turning.
> These are the people that do the hard work of reviewing / approving
> patches. These people need to be relatively reliable. These people
> need to be willing to do the dirty work (such as restructuring) that
> can't reasonably be expected of a contributor.
> While a core maintainer might also be responsible for certain specific
> areas (symtab, threads, remote), they won't cherry pick the patch list
> and definitly won't fall asleep at the wheel.
> Specific Maintainers:
> These are responsible for specific areas. Native, target, host and
> language maintainers come to mind. Their responsabilities are pretty
> clear, while needing to be responsive, they are not on the critical path
> like core maintainers. The thing I really like about the target
> maintainers is how they, every so often, pop up to do some maintenance
> (eliminate something deprecated), and then pop back down again.
One of my concerns from my previous thread about this, which seems to
have died, is that the above doesn't completely describe current
structure. The set of core maintainers breaks down into specific
maintainers for core components.
MontaVista Software Debian GNU/Linux Developer