This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: Status
> Personally, I think for GDB the benefits of having a single chief
> maintainer outweigh the problems.
Well, if someone is dumb enough to make themselves a target like that,
I suppose I might go for it :-).
But I guess the GCC system makes sense to me. If something is enough
of an issue to be a "technical controversy" in the sense of something
people would escalate to the chief technical maintainer/team, you kind
of want to get people on board as much as possible. Because if you
proceed without _some_ level of consensus (not among the whole world,
but at least among a small group of people most involved), then it
creates various kinds of pain.
I mean, there is almost always a way out (e.g. make it an option or
something, if there really a demand for both solutions).
One thing I don't want to be single-string is the process of making
checkins which are believed to be relatively uncontroversial. Right
now there is a big problem when the person listed in MAINTAINERS for a
particular file gets busy or is on vacation or whatever. Or to put it
another way, being a maintainer should grant you the right to overrule
other people but it shouldn't grant you the right to stop things in
their tracks. Or something like that.