unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jay.p.belanger@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: Another others for maintainer?
Date: Tue, 20 Oct 2015 20:10:01 +0300	[thread overview]
Message-ID: <837fmhfouu.fsf@gnu.org> (raw)
In-Reply-To: <87a8rd7bu1.fsf@gmail.com>

> From: Jay Belanger <jay.p.belanger@gmail.com>
> Date: Tue, 20 Oct 2015 11:18:30 -0500
> Cc: jay.p.belanger@gmail.com
> 
> Yes; Eli has always done a great job with Emacs.

Thanks.

> Has he weighed in on his willingness to be a (co)maintainer?

No, he hasn't.  Primarily because I don't know what is expected of a
(co)maintainer that I don't already do.  If the answer is NOTHING,
then you already have me, albeit unannounced.  In that case, I can
give up the title.

I also have serious doubts it's a good idea to upgrade my status in
any serious ways.  "A man's got to know his limitations"; here are
some of mine:

  . I know too little about some very important core parts of Emacs,
    so little that I will be unable to make decisions about changes
    there.

  . I have very little time to work on Emacs.  E.g., I will probably
    be unable to track the commits the way Stefan did (see also
    previous item), and can only review maybe one or 2 patches per
    day, sometimes none.  That's no way of keeping the QA standards
    high enough.  I'm not even sure my Lisp instincts are good enough
    for serious reviews of large non-trivial packages.

  . I tend to annoy some people, for reasons that I honestly don't
    understand (the latest episode is still unwinding here -- and also
    on IRC, I'm told).  My ideas are frequently rejected.  That's not
    a good starting point for leadership.

'Nough said.



  reply	other threads:[~2015-10-20 17:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  7:59 Another others for maintainer? John Wiegley
2015-10-20  8:27 ` David Kastrup
2015-10-20  8:48 ` Nicolas Petton
2015-10-20 15:25   ` John Wiegley
2015-10-20 16:03     ` Dmitry Gutov
2015-10-20 16:07     ` Nicolas Petton
2015-10-20 16:18       ` Jay Belanger
2015-10-20 17:10         ` Eli Zaretskii [this message]
2015-10-20 21:34           ` Rasmus
2015-10-20 23:44           ` John Wiegley
2015-10-22 15:32             ` Eli Zaretskii
2015-10-22 16:49               ` Przemysław Wojnowski
2015-10-22 17:11                 ` Eli Zaretskii
2015-10-22 17:51               ` John Wiegley
2015-10-22 22:06               ` Rasmus
2015-10-23  6:49                 ` Eli Zaretskii
2015-10-25 19:23                   ` John Wiegley
2015-10-24  9:35               ` Bastien
2015-10-24 10:29                 ` Eli Zaretskii
2015-10-25 19:29                 ` John Wiegley
2015-10-26 13:32                   ` Stephen Leake

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=837fmhfouu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jay.p.belanger@gmail.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.
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).