From: Eli Zaretskii <eliz@gnu.org>
To: David Carlton <david.carlton@sun.com>
Cc: gdb@sourceware.org
Subject: Re: Maintainer policy for GDB
Date: Sat, 19 Nov 2005 10:38:00 -0000 [thread overview]
Message-ID: <uk6f4hqil.fsf@gnu.org> (raw)
In-Reply-To: <yf21x1dshey.fsf@kealia.sfbay.sun.com> (message from David Carlton on Fri, 18 Nov 2005 14:46:45 -0800)
> From: David Carlton <david.carlton@sun.com>
> Date: Fri, 18 Nov 2005 14:46:45 -0800
>
> > In other words, if responsibility doesn't come with some unique
> > authority, who will want such a responsibility?
>
> One possible way to treat this question is as an empirical one. To
> that end, one could ask people currently listed in MAINTAINERS as
> maintaining a given domain whether they would prefer to remain
> responsible for maintaining, or merely authorized, and why. For
> example, would you be interested in being responsible for djgpp and/or
> documentation under the proposed new rules? If so, why?
Thanks, that was a useful thought experiment.
After thinking about this for a while, I concluded that my main
reasons for being interested in becoming a responsible maintainer is
that I'd like to influence the development and maintenance of those
specific areas according to ideas I have. For example, I might wish
to make sure the manual is well indexed: each important concept has a
@cindex entry, each command has a @kindex entry, the index entries are
well thought and easy to guess, and allow the reader to use the manual
as a reference, etc.
Now, under the suggested rules, somebody who is authorized to approve
patches to the documentation could commit changes that don't fit my
plan about indexing, without asking me, right? How can I shape the
documentation according to my ideas if I don't have the final say?
The only way would be to revert changes and/or redo them myself.
Under the current scheme, I can refuse the approval unless and until
the contributor reworks the changes according to my standards. With
that authority gone, I'm left dead in the water; doing everything
myself is not an option for me, given my chronic lack of free time,
and starting a revert war or going to the SC over disputes about
@cindex is either time-consuming or childishly silly or both.
next prev parent reply other threads:[~2005-11-19 10:38 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 4:48 Daniel Jacobowitz
[not found] ` <8f2776cb0511162240q6f550008udda9803b5253fd88@mail.gmail.com>
2005-11-17 6:44 ` Fwd: " Jim Blandy
2005-11-17 14:04 ` Daniel Jacobowitz
2005-11-17 17:07 ` Jim Blandy
2005-11-17 20:38 ` Jim Blandy
2005-11-17 20:15 ` Eli Zaretskii
2005-11-17 20:16 ` Eli Zaretskii
2005-11-17 20:14 ` Eli Zaretskii
2005-11-17 21:10 ` Jim Blandy
2005-11-18 3:07 ` Daniel Jacobowitz
2005-11-18 3:26 ` Joel Brobecker
2005-11-18 3:30 ` Daniel Jacobowitz
2005-11-18 3:33 ` Joel Brobecker
2005-11-18 3:46 ` Wu Zhou
2005-11-18 11:09 ` Andrew STUBBS
2005-11-18 11:46 ` Eli Zaretskii
2005-11-18 11:59 ` Andrew STUBBS
2005-11-18 13:15 ` Eli Zaretskii
2005-11-18 15:26 ` Daniel Jacobowitz
2005-11-18 18:24 ` Eli Zaretskii
2005-11-18 18:44 ` Ian Lance Taylor
2005-11-18 18:51 ` Daniel Jacobowitz
2005-11-18 21:40 ` Eli Zaretskii
2005-11-18 21:46 ` Daniel Jacobowitz
2005-11-18 22:33 ` Eli Zaretskii
2005-11-18 22:41 ` Daniel Jacobowitz
2005-11-19 9:34 ` Eli Zaretskii
2005-11-18 21:51 ` Jim Blandy
2005-11-18 22:29 ` Eli Zaretskii
2005-11-19 0:34 ` Jim Blandy
2005-11-19 10:54 ` Eli Zaretskii
2005-11-21 7:52 ` Jim Blandy
2005-11-21 22:35 ` Eli Zaretskii
2005-11-18 22:46 ` David Carlton
2005-11-19 10:38 ` Eli Zaretskii [this message]
2005-11-23 1:28 ` David Carlton
2005-11-23 19:56 ` Eli Zaretskii
2005-11-23 20:13 ` Joel Brobecker
2005-11-24 4:51 ` Eli Zaretskii
2005-11-24 20:36 ` Joel Brobecker
2005-11-24 20:47 ` Eli Zaretskii
2005-11-24 21:20 ` Joel Brobecker
2005-11-25 3:07 ` Daniel Jacobowitz
2005-11-25 8:36 ` Christopher Faylor
2005-11-25 8:37 ` Eli Zaretskii
2005-11-25 17:07 ` Daniel Jacobowitz
2005-11-25 19:53 ` Joel Brobecker
2005-11-25 20:43 ` Eli Zaretskii
2005-11-25 20:10 ` Eli Zaretskii
2005-11-25 21:03 ` Daniel Jacobowitz
2005-11-25 21:38 ` Eli Zaretskii
2005-11-25 23:04 ` Daniel Jacobowitz
2005-11-25 23:42 ` Mark Kettenis
2005-11-26 0:03 ` Daniel Jacobowitz
2005-11-26 9:38 ` Eli Zaretskii
2005-11-26 9:31 ` Eli Zaretskii
2005-11-27 15:07 ` Daniel Jacobowitz
2005-11-28 8:51 ` Eli Zaretskii
2005-11-25 9:23 ` Eli Zaretskii
2005-11-25 16:04 ` Daniel Jacobowitz
2005-11-25 20:08 ` Eli Zaretskii
2005-11-26 7:28 ` Christopher Faylor
2005-11-26 15:18 ` Eli Zaretskii
2005-11-26 16:38 ` Daniel Jacobowitz
2005-11-23 20:41 ` Christopher Faylor
2005-11-24 4:56 ` Eli Zaretskii
2005-11-24 2:05 ` David Carlton
2005-11-24 6:17 ` Eli Zaretskii
2005-11-18 21:09 ` Eli Zaretskii
2005-11-18 21:32 ` Daniel Jacobowitz
2005-11-18 12:14 ` Eli Zaretskii
2005-11-17 23:10 ` Joel Brobecker
2005-11-18 12:42 ` Eli Zaretskii
2005-11-18 15:05 ` Daniel Jacobowitz
2005-11-18 18:11 ` Eli Zaretskii
2005-11-18 17:53 ` Paul Gilliam
2005-11-18 18:36 ` Eli Zaretskii
2005-11-18 19:25 ` Joel Brobecker
2005-11-18 21:02 ` Paul Gilliam
2005-11-19 2:44 ` Christopher Faylor
2005-11-19 10:56 ` Eli Zaretskii
2005-11-19 17:05 ` Christopher Faylor
2005-11-19 19:39 ` Eli Zaretskii
2005-11-19 22:21 ` Christopher Faylor
2005-11-19 22:23 ` Christopher Faylor
2005-11-19 22:25 ` Christopher Faylor
2005-11-19 22:54 ` Eli Zaretskii
2005-11-19 22:55 ` Eli Zaretskii
2005-11-20 5:28 ` Joel Brobecker
2005-11-20 19:22 ` Eli Zaretskii
2005-11-20 21:55 ` Christopher Faylor
2005-11-20 22:01 ` Daniel Jacobowitz
2005-11-18 19:50 ` Joel Brobecker
2005-11-18 21:41 ` Eli Zaretskii
2005-11-17 23:52 ` Mark Kettenis
2005-11-18 21:51 ` David Carlton
2005-11-27 4:50 Michael Snyder
2005-11-27 4:59 ` Eli Zaretskii
2005-11-27 5:00 ` Ian Lance Taylor
2005-11-27 19:22 ` Eli Zaretskii
2005-11-27 19:18 ` 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=uk6f4hqil.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=david.carlton@sun.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).