From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb@sourceware.org, cagney@gnu.org, jtc@acorntoolworks.com,
fnf@ninemoons.com, Peter.Schauer@regent.e-technik.tu-muenchen.de,
ezannoni@redhat.com
Subject: Re: Maintainer policy for GDB
Date: Fri, 18 Nov 2005 12:14:00 -0000 [thread overview]
Message-ID: <ud5ky5f4q.fsf@gnu.org> (raw)
In-Reply-To: <8f2776cb0511171310m556a37c5r723cef451735a96a@mail.gmail.com> (message from Jim Blandy on Thu, 17 Nov 2005 13:10:21 -0800)
> Date: Thu, 17 Nov 2005 13:10:21 -0800
> From: Jim Blandy <jimb@red-bean.com>
> Cc: gdb@sourceware.org, Andrew Cagney <cagney@gnu.org>,
> "J.T. Conklin" <jtc@acorntoolworks.com>,
> Fred Fish <fnf@ninemoons.com>,
> Peter Schauer <Peter.Schauer@regent.e-technik.tu-muenchen.de>,
> Elena Zannoni <ezannoni@redhat.com>
>
> > The problem is, trust is built by following rules which are initially
> > intentionally restrictive. As the trust grows, the restrictions can
> > be gradually lifted.
>
> That's not the pattern I'm familiar with. An organization can have
> strict rules, and as trust is built up, people will tolerate those
> rules being bent or set aside in specific cases. But I've never seen
> the restrictions be explicitly lifted as a result of that.
I don't see any significant difference between these two patterns. If
and when people tolerate rule-bending, we might as well codify that.
> We have restrictions in place that many of GDB's contributors don't
> like, and which are definitely hampering progress.
You are generalizing what I said in a way that wasn't in my intent. I
wasn't arguing for more restrictions, I was arguing for codified
self-restraint where we were burnt in the past.
> > By contrast, you suggest to begin with unconditional trust. We
> > already tried that in the past, and we saw what happened. Why try
> > that again? why assume that what happened once, cannot happen again?
>
> You need to be more specific. I agree with your characterization that
> we trusted too much in 1999 that everything would just work out, but I
> don't see that this proposal makes the same mistake. What particular
> passages concern you?
The comment by Daniel that his suggestions, and specifically the power
to commit without an RFA, implicitly assume trust.
> What are their consequences?
Bad blood and, eventually, deep mistrust. We've been there, I'm sure
you remember that.
Daniel says that if we don't trust each other, we should ``work on
trust''. But how do we ``work on trust''? do we all go to a shrink
together once a week? The only way I know of to work on trust is by
building it as we cooperate in the development and maintenance of GDB.
And while trust is in construction, it might be a good idea to take
some voluntary restraint upon ourselves.
next prev parent reply other threads:[~2005-11-18 12:14 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
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 [this message]
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=ud5ky5f4q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
--cc=cagney@gnu.org \
--cc=ezannoni@redhat.com \
--cc=fnf@ninemoons.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.com \
--cc=jtc@acorntoolworks.com \
/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