unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Maintainer overview
Date: Thu, 28 Jul 2011 09:35:46 +0200	[thread overview]
Message-ID: <m3y5zivovh.fsf@stories.gnus.org> (raw)
In-Reply-To: <83oc0fdsgg.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul 2011 05:55:43 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> I think it would be very nice if we had such a list of
>> packages/maintainers -- that was up-to-date.
>
> We have something in admin/MAINTAINERS.

It's a starting point.

>> 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.
>
> What about source files that are not packages, like code written in C,
> or issues that are not confined to a single file/package?

Perhaps "area" is a better concept than "package".  I mean, Ted and
Juanma would probably appreciate being notified on gnutls issues, and
you would like (or "like" :-)) to get bidi notifications.

However, areas that are mostly covered by people who are participating
actively on emacs-devel already don't really need to get these
notifications, since we all read emacs-bugs already, don't we?  :-)

So, while nice, it's probably more useful for packages maintained by
people who don't read these lists regularly.

So, yes, "area".  And I'd suggest a file format like

bidi: Eli Zaretskii <eliz@gnu.org>

gnutls: Ted Zlatanov <tzz@lifelogs.com>
 Juanma Barranquero <lekktu@gmail.com>

gnus,message: Lars Magne Ingebrigtsen <larsi@gnus.org>
 
Easy to parse and edit.
 
-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2011-07-28  7:35 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 [this message]
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
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=m3y5zivovh.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --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).