unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@newartisans.com>
To: Bastien <bzg@gnu.org>
Cc: jay.p.belanger@gmail.com, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Another others for maintainer?
Date: Sun, 25 Oct 2015 12:29:25 -0700	[thread overview]
Message-ID: <m2pp02iw6i.fsf@newartisans.com> (raw)
In-Reply-To: <87h9lg4nio.fsf@gnu.org> (Bastien's message of "Sat, 24 Oct 2015 11:35:43 +0200")

>>>>> Bastien  <bzg@gnu.org> writes:

> I volunteer to continue being Org-mode's maintainer, definitely with more
> time next year. (I've been relying on the Org-mode team for most of 2015,
> which worked okay, but the project needs to move forward.)

Fantastic!

> I also volunteer to try sorting out more mundane issues from the bug
> tracking system. As Eli pointed out, there is a lot already done in this
> area, but a lot left to be done too. I personally enjoy the thrill of doing
> trivial tasks like fixing typos, closing dead bugs, etc. So you can count on
> me for this!

This is amazing, Bastien; we could really use some good "bug shepherds". The
most often cited reason for disappointment with Emacs development I hear is
that bugs and patches "die on the vine", for want of time on the maintainer's
part to attend to them all.

So what I'd love to see happen first is to go through the bug tracker and find
every issue with a waiting patch. Confirm with the submitter that they believe
their patch is in final ready status, and that it works with current Git HEAD.
Then let's start moving these patches in and closing their associated bugs.

Let's harvest our low-hanging fruit!

John



  parent reply	other threads:[~2015-10-25 19:29 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
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 [this message]
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=m2pp02iw6i.fsf@newartisans.com \
    --to=johnw@newartisans.com \
    --cc=bzg@gnu.org \
    --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).