all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Looking for a new Emacs maintainer or team
Date: Mon, 31 Dec 2007 15:22:53 -0800	[thread overview]
Message-ID: <200712312322.lBVNMsBg021808@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <E1J9T9Y-0003Xf-Ep@fencepost.gnu.org> (Richard Stallman's message of "Mon, 31 Dec 2007 17:30:36 -0500")

Richard Stallman <rms@gnu.org> writes:

  >       > Once Emacs 22 is released, I would like to hand over Emacs maintenance
  >       > to one person or a small team.  The new maintainer or maintainers
  >       > would take responsibility for making sure new releases are made and
  >       > that they are reliable, and for focusing attention on priority
  >       > projects for improvement.
  > 
  >     Is this still the plan?  Last time this was discussed on the list many
  >     very capable volunteers were found.
  > 
  > A few people volunteered, and they could be useful members of a team,
  > but (as I recall) they didn't include the most knowledgeable people.

OK, if this is the cause of the blockage, then let's work on what your
criteria would be for choosing the maintainer(s).


One proposal was to have a committee with 3 people:

- a "technical lead" which is responsible for the "quality" of the
  major modifications to the software (i.e. C and Lisp code).

- a "release manager" which is responsible for the release, including
  documentation, copyright stuff, packaging, etc  (basically anything
  else)

- a "chairman" (the third person) who has the "final word" on any
  disputes in the committee, based on an overall understanding of
  Emacs "policies, history and visions" (whatever they are)...

And there were volunteers for these positions: Kenichi Handa, Chong
Yidong and Stefan Monnier.

If you'd like more people on the committee, why not just nominate them
and maybe they will accept?

  reply	other threads:[~2007-12-31 23:22 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 17:34 Looking for a new Emacs maintainer or team Richard Stallman
2007-12-31 17:14 ` Dan Nicolaescu
2007-12-31 22:30   ` Richard Stallman
2007-12-31 23:22     ` Dan Nicolaescu [this message]
2008-01-01  0:14       ` Mike Mattie
2008-01-01  0:14     ` Miles Bader
2008-01-01 21:24       ` Richard Stallman
2008-02-22  5:27         ` Dan Nicolaescu
2008-02-22 22:57           ` Richard Stallman
2008-02-22 23:08             ` Dan Nicolaescu
2008-02-22 23:26               ` Mike Mattie
2008-02-23  9:03                 ` David Kastrup
2008-02-23 19:29                 ` Richard Stallman
2008-02-23  9:17             ` Paul Michael Reilly
2008-02-23 13:26               ` Juanma Barranquero
2008-02-23 14:33                 ` David Kastrup
2008-02-23 14:57                   ` Juanma Barranquero
2008-02-24  0:54                   ` Richard Stallman
2008-02-23 19:40               ` T. V. Raman
2008-02-24  0:53               ` Richard Stallman
2008-02-24  1:15                 ` Miles Bader
2008-02-24  4:10                   ` Chong Yidong
2008-02-24  9:04                 ` Paul Michael Reilly
     [not found]                   ` <fb5c9a920802241406w31e3e8e2ve538d311ec3a9375@mail.gmail.com>
2008-02-24 22:08                     ` Claus
2008-02-25 10:57                       ` Richard Stallman
2008-02-26  2:00                 ` Xavier Maillard
2008-02-23 10:35             ` Bastien
2008-02-23 16:43               ` Jay Belanger
2008-02-24  2:00             ` Xavier Maillard
2008-02-24 22:30               ` Richard Stallman
2008-02-26  2:00                 ` Xavier Maillard
  -- strict thread matches above, loose matches on Subject: below --
2008-02-23 17:26 Vijay Rao
2008-02-24  0:54 ` Richard Stallman
2008-02-24 16:12   ` Vijay Rao
2008-02-24 23:04     ` Richard Stallman
2008-02-25  3:59       ` Vijay Rao

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200712312322.lBVNMsBg021808@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.