Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Maintainer policy for GDB - take N
Date: Fri, 06 Jan 2006 23:15:00 -0000	[thread overview]
Message-ID: <uace9gd7d.fsf@gnu.org> (raw)
In-Reply-To: <20060106194007.GA9104@nevyn.them.org> (message from Daniel 	Jacobowitz on Fri, 6 Jan 2006 14:40:07 -0500)

> Date: Fri, 6 Jan 2006 14:40:07 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> Below I have a complete copy of the MAINTAINERS file, adjusted for all
> the changes I've proposed and for all the feedback I received when I
> posted them in November.  Sorry about the delay; the end of the year
> was unexpectedly hectic.
> 
> I'm going to be traveling much of next week.  I'll have access to
> email, but limited time to respond, so I may be out of touch from
> Sunday to Friday.  I'm eager to hear any feedback on this revision,
> especially from Eli, Chris, and Mark.

The structure of the maintainership, with all the different kinds of
maintainers, sounds too complicated.  (Yes, I know that you wrote it's
simpler than it sounds, but I'm trying to read this through the eyes
of a casual contributor.)  Can we simplify that?  For example, Patch
Champions and Past Maintainers have no responsibilities under this
scheme, so perhaps we should exclude them from the system description.

Or maybe we should have a separate description of the system,
explaining its checks and balances, and referring to the lists of
maintainers further down the document (the point being that the lists
are sometimes quite long, and reading through them distracts from
getting the coherent picture of the system of responsibilities and
authorities).

Other than that, I have no open issues with this suggestion.

Thank you for all the hard work of getting this suggested, discussed,
rewritten, refined, redone, etc. etc...


  reply	other threads:[~2006-01-06 23:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 19:40 Daniel Jacobowitz
2006-01-06 23:15 ` Eli Zaretskii [this message]
2006-01-08 17:52 ` Mark Kettenis
2006-01-09  5:53   ` Jim Blandy
2006-01-09 18:00 ` Christopher Faylor
2006-01-17 22:09 ` Daniel Jacobowitz
2006-01-17 23:28   ` Mark Kettenis
2006-01-18 11:17   ` Christopher Faylor

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=uace9gd7d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.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