From: John Wiegley <johnw@newartisans.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jay.p.belanger@gmail.com, emacs-devel@gnu.org
Subject: Re: Another others for maintainer?
Date: Thu, 22 Oct 2015 10:51:12 -0700 [thread overview]
Message-ID: <m237x2pzan.fsf@newartisans.com> (raw)
In-Reply-To: <837fmeudev.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Oct 2015 18:32:40 +0300")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> Thanks, but you make this sound like if tomorrow I'm overrun by a bus, Emacs
> will die, or at least stagnate. Which of course is not true. There are quite
> a few people here without whom Emacs development would not have been what it
> is, let alone what it (hopefully) will be.
A good point. I was referring more to your combination of consistency and
energy, with long experience in the project. That's more valuable than maybe
you give yourself credit for.
> If you don't have enough time to actively engage in technical issues, like
> discussing development and design/implementation decisions, reviewing
> patches, fixing bugs, etc. -- then the above scenario is not viable. There's
> no chance in the world I alone will be able to deal with that workload: I
> have neither the time nor knowledge (nor talent, to be honest) to do that.
> So we will need at least some of the team you describe here:
It's true, I don't have the time it would take to do what you do now, Eli.
We'll need to make building up our "development team" a first and crucial
task, as you say.
> P.S. I think many people don't realize how many simple, mundane tasks are
> part of what we call "Emacs maintenance". Stuff like fixing spelling errors,
> committing auto-generated files, fixing unsafe or sub-optimal code revealed
> by compiler warnings, closing bugs that were resolved but left open, merging
> bug reports for the same bug, fixing typos in generated log messages,
> managing our mailing lists and the Web site -- all this is part of the job.
> That we currently have a few kind people like Glenn, Paul, Juanma, and
> others silently doing this behind the scenes (look at "git log" to see what
> I mean) is sheer luck. People who want to help could start with these small
> but important tasks. With time and experience, they will gain confidence in
> their talents and abilities, and -- no less important -- upgrade their
> status within the community, and that will help them decide which larger
> tasks they could take upon themselves.
This paragraph is perfect. I'll draft up a call for volunteers as soon as I
can find some time this weekend, starting from what you've written here.
John
next prev parent reply other threads:[~2015-10-22 17:51 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
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 [this message]
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=m237x2pzan.fsf@newartisans.com \
--to=johnw@newartisans.com \
--cc=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).