From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Maintainer overview
Date: Thu, 28 Jul 2011 16:14:55 +1000 [thread overview]
Message-ID: <CAC=50j_h2aUuwXHZkVK3d411q-g4-ESwyE4GbxHOeLXxqaWbuw@mail.gmail.com> (raw)
In-Reply-To: <m3fwlrz6fj.fsf@stories.gnus.org>
On Thu, Jul 28, 2011 at 8:48 AM, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> Emacs has more than a few bits and pieces that some specific people feel
> ownership to. However, we don't really seem to have a mechanism for
> notifying these people when bugs that affect their packages show up in
> the Emacs bug tracker.
>
> I think it would be very nice if we had such a list of
> packages/maintainers -- that was up-to-date.
>
> Now, some of the .el files themselves do have Maintainer: lines, but you
> really have to root around, and know that you're supposed to root
> around, to find them.
>
> What I'd ideally like to see is to be able to say `C package TAB' (in
> debbugs-gnu mode, of course) and see what packages a bug report can be
> assigned to, and have the maintainer(s) Cc'd on the existence of the bug
> report.
>
> I think the most pleasant way to do this would be to add a slightly more
> formal Maintainer: syntax. Grepping though the sources, we find stuff
> like:
>
> vt-control.el:6:;; Maintainer: Rob Riepel <riepel@networking.stanford.edu>
> whitespace.el:6:;; Maintainer: Vinicius Jose Latorre <viniciusjl@ig.com.br>
> wid-edit.el:6:;; Maintainer: FSF
> window.el:6:;; Maintainer: FSF
> woman.el:6:;; Maintainer: FSF
> x-dnd.el:6:;; Maintainer: FSF
> xml.el:6:;; Maintainer: Mark A. Hershberger <mah@everybody.org>
> calc/calc-aent.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calcalg2.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calcalg3.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calc-alg.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calc-arith.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calc-bin.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
>
> My suggestion would be to change this to
>
> ;; Package-maintainer: calc:Jay Belanger <jay.p.belanger@gmail.com>
>
> The `C package' command could then go through all the .el files, gather
> the package names, and allow TAB-ing over them.
>
> Alternatively, we could just put a new file into etc that lists all the
> packages and their maintainers, which would, of course, be a lot more
> efficient.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog http://lars.ingebrigtsen.no/
>
>
>
That sounds like useful improvements. However, can I suggest
abstracting the contact details another layer. Some maintainers may
not like their email being distributed inside emacs source files and
when that maintainer leaves or someone else takes over maintenance,
the information becomes outdated.
Perhaps we could use a emacs-package@gnu.org address which is
redirected to the real address of the person currently maintaining the
package or something similar. This would allow the user to control
distribution of their email address and ensure the most current or
best address is used
Tim
next prev parent reply other threads:[~2011-07-28 6:14 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
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 [this message]
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='CAC=50j_h2aUuwXHZkVK3d411q-g4-ESwyE4GbxHOeLXxqaWbuw@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-devel@gnu.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).