unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: Maintainer overview
Date: Fri, 29 Jul 2011 11:11:28 +0900	[thread overview]
Message-ID: <87y5zhq1in.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E1QmLTB-0001Qq-52@fencepost.gnu.org>

Eli Zaretskii writes:

 > Maybe we should take a step back and talk about the goals of this
 > feature.  Is this just to be nice to those who don't read
 > bug-gnu-emacs and send them a notification?

The situation of Emacs (whose goal is to incorporate all the elisp
that's fit to execute[1]) is somewhat different -- always using
bug-gnu-emacs makes quite a bit of sense -- but XEmacs packages have
had their own bug addresses for over a decade.  The following use
cases are seen, from more common to less (in my recollection, I could
check if anybody cares):

1) Redirect to xemacs-beta (the closest we have to bug-gnu-emacs).
2) Redirect to an @xemacs.org alias of the package maintainer.  These
   are practically public as they are easy to guess.
3) Redirect to a public email address of the package maintainer.
4) Redirect to a mailing list dedicated to the package.
5) Redirect to a private email address of the package maintainer.

(Here "public" means an address the user is willing to have exposed in
ML archives and the like.  "Private" means the user expects the
address to be known only to specified correspondents and their MTAs.)

The maintenance burden is small (for us; we own the alias file for
xemacs.org, I don't know if that would be the same in GNU or if you'd
have to ask for service from Savannah); about an hour to set up and
test example aliases, another two hours to create the original list of
about 200 aliases for 50 or so packages (we actually have 4 aliases
per package, but that's probably overkill), including gathering
information from about 25 package maintainers about their preferences
(some do prefer to read about their packages on xemacs-beta); and
about 1 minute per new package or change of package maintainer, of
which there have probably been about 50 over the decade.

We do occasionally get complaints about stale aliases, but the former
maintainers are usually pretty sympathetic and relieved that the
change is done immediately.  Mostly stale aliases just revert to
"xemacs-beta", it's not difficult.

AFAIK most never got used very much, but a few were quite active
(mostly those that had courtesy @xemacs.org addresses before we
systematized the package addresses).  Given the low maintenance
burden, I think it is well worth it.  YMMV of course.

Footnotes: 
[1]  Don't take that too seriously, Eli, it's a play on The New York
Times's motto.




  parent reply	other threads:[~2011-07-29  2:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 22:48 Maintainer overview Lars Magne Ingebrigtsen
2011-07-28  2:55 ` Eli Zaretskii
2011-07-28  7:35   ` Lars Magne Ingebrigtsen
2011-07-28  7:57     ` Eli Zaretskii
2011-07-28  8:09       ` Lars Magne Ingebrigtsen
2011-07-28  9:05         ` Eli Zaretskii
2011-07-28  9:08           ` Lars Magne Ingebrigtsen
2011-07-29  2:11       ` Stephen J. Turnbull [this message]
2011-07-28  8:48     ` Detlev Zundel
2011-07-28 11:23     ` Juanma Barranquero
2011-07-28  4:47 ` Jambunathan K
2011-07-28  6:14 ` Tim Cross
2011-07-28  7:11   ` Jambunathan K
2011-07-28  7:37   ` Lars Magne Ingebrigtsen
2011-07-28  8:23     ` Tim Cross
2011-07-28  9:04       ` Eli Zaretskii
2011-07-28  8:07 ` Bastien
2011-07-28 16:49 ` Chong Yidong
2011-07-29 11:22   ` Lars Magne Ingebrigtsen
2011-08-02 15:13 ` Stefan Monnier

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=87y5zhq1in.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    /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).