unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Maintainership
Date: Sat, 11 Jan 2014 23:09:40 -0500	[thread overview]
Message-ID: <20140112040940.GC32704@thyrsus.com> (raw)
In-Reply-To: <jwvvbxpx52o.fsf-monnier+emacs@gnu.org>

Stefan Monnier <monnier@iro.umontreal.ca>:
> It's nice to be a dictator, but it takes too much time, so in order to
> try and reduce this load, I'd like to dilute my dictatorship a bit.
> 
> To a large extent, this has already been the case, but I think it's
> worth stating it more formally: if Glenn, Eli, Richard, Yidong, Handa, or
> Jan agrees with a change, then you don't need my agreement.
> IOW you only need my opinion if none of them has an opinion or if
> there's a disagreement.

OK.  The following question is *not* an attempt to be contentious; I'm
trying to figure out how this is supposed to work, and help everyone
else figure out too.

You have expressed "100% agreement" with a post objecting to me doing /etc
cleanup during feature freeze.

On the other hand, Richard has approved the idea and actively assisted.

If I understand your intention correctly, that makes the completion of
the /etc cleanup changes an approved project.  The alternative
interpretation is that Richard should take "100% agreement" as 
direction to stop helping me with it.

I can cheerfully live with either theory - I've certainly got enough
on my task list to occupy me for a while.  So I'm not pushing for either
outcome in particular, I just want to know how the decision procedure
works.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>



  reply	other threads:[~2014-01-12  4:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12  3:23 Maintainership Stefan Monnier
2014-01-12  4:09 ` Eric S. Raymond [this message]
2014-01-12  9:37   ` Maintainership David Kastrup
2014-01-12 15:51   ` Maintainership Eli Zaretskii
2014-01-12  9:12 ` Maintainership Jarek Czekalski

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140112040940.GC32704@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).