From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mike Mattie Newsgroups: gmane.emacs.devel Subject: Re: Looking for a new Emacs maintainer or team Date: Mon, 31 Dec 2007 16:14:03 -0800 Message-ID: <20071231161403.1f786e57@reforged> References: <200712311714.lBVHEdvC029794@oogie-boogie.ics.uci.edu> <200712312322.lBVNMsBg021808@oogie-boogie.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1343260382==" X-Trace: ger.gmane.org 1199146515 11422 80.91.229.12 (1 Jan 2008 00:15:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Jan 2008 00:15:15 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 01 01:15:30 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1J9Un3-0004OC-IV for ged-emacs-devel@m.gmane.org; Tue, 01 Jan 2008 01:15:29 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J9Umh-0004Gw-NZ for ged-emacs-devel@m.gmane.org; Mon, 31 Dec 2007 19:15:07 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J9Umc-0004DC-08 for emacs-devel@gnu.org; Mon, 31 Dec 2007 19:15:02 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J9Uma-0004Bu-Li for emacs-devel@gnu.org; Mon, 31 Dec 2007 19:15:00 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J9UmZ-0004Bc-O3 for emacs-devel@gnu.org; Mon, 31 Dec 2007 19:14:59 -0500 Original-Received: from wa-out-1112.google.com ([209.85.146.177]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J9UmZ-000675-C6 for emacs-devel@gnu.org; Mon, 31 Dec 2007 19:14:59 -0500 Original-Received: by wa-out-1112.google.com with SMTP id k34so7929171wah.10 for ; Mon, 31 Dec 2007 16:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; bh=eoSgvjhRiEPwdw7uzxw4xGHvwxQITaiJm/2ME/WaPlk=; b=RGnZfh5RzSVkczLbvPOiXz25r6iyHq/yH/ssvUM0cduH+kF5CvdTAz+WuhKq9chLugYNENJIhbqs1qVyY9H4RcCXl4usiUpt7unYoYUSD868SvNKsZAbkOjws+aXLrI2G/sUmQheW+rGTvQrhDJjiJhRGx6e66JOTEtzU3fxZV4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=AYkflm8UVZPFhUQKvcGmgzPLJBFhGJMCtpRIpSg/ZeTfTIR7QpjuY1sRzYvcDiWHZdGk45Ek+5i/4yWonpuuofPq+ObnLN2JDK7sSV7qmRsnd2pGNI1YDaVIqHXed4wnb2ii+VG7VXV0nKqgcmtj7w40c65hpCsLvrQGs2LQ8tg= Original-Received: by 10.114.177.1 with SMTP id z1mr13414378wae.7.1199146497976; Mon, 31 Dec 2007 16:14:57 -0800 (PST) Original-Received: from reforged ( [71.217.198.62]) by mx.google.com with ESMTPS id j6sm17237374wah.6.2007.12.31.16.14.53 (version=SSLv3 cipher=OTHER); Mon, 31 Dec 2007 16:14:56 -0800 (PST) In-Reply-To: <200712312322.lBVNMsBg021808@oogie-boogie.ics.uci.edu> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i686-pc-linux-gnu) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:85783 Archived-At: --===============1343260382== Content-Type: multipart/signed; boundary="Sig_/Pm6LzHcvy7DrZqqZR.kDi8Q"; protocol="application/pgp-signature"; micalg=PGP-SHA1 --Sig_/Pm6LzHcvy7DrZqqZR.kDi8Q Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 31 Dec 2007 15:22:53 -0800 Dan Nicolaescu wrote: > Richard Stallman writes: >=20 > > > 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. > >=20 > > Is this still the plan? Last time this was discussed on the > > list many very capable volunteers were found. > >=20 > > 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. >=20 > OK, if this is the cause of the blockage, then let's work on what your > criteria would be for choosing the maintainer(s). >=20 >=20 > One proposal was to have a committee with 3 people: >=20 > - a "technical lead" which is responsible for the "quality" of the > major modifications to the software (i.e. C and Lisp code). >=20 > - a "release manager" which is responsible for the release, including > documentation, copyright stuff, packaging, etc (basically anything > else) >=20 > - 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)... I don't think that is a very good description of a chairman. A chairman arbitrates procedure and typically does not vote. With your triad you cannot even reach a quorum without the chairman. Creating a political structure is non-trivial with many subtle pitfalls. Programmers are not automatically skilled at this simply because they work with complex systems. Most of the politically structured projects I have read, or participated in functioned more like an Asperger's convention than a decision making process. I think a benevolent dictator who can interact with people according to social norms is key for a project, especially when the profession is considered a haven for High Functioning Autism and a variety of other handicaps. A leader should be able to understand the people he leads, where their strengths can be used, and how to avoid the certain pitfalls inherent in every personality. If a committee helps then it's a good thing.=20 The one certainty of this thread is that it will grow like cancer until the constitutionalists form a separate mailing list. Just stating the obvious from the back row. > And there were volunteers for these positions: Kenichi Handa, Chong > Yidong and Stefan Monnier. >=20 > If you'd like more people on the committee, why not just nominate them > and maybe they will accept? >=20 >=20 > _______________________________________________ > Emacs-devel mailing list > Emacs-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-devel --Sig_/Pm6LzHcvy7DrZqqZR.kDi8Q Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHeYXLdfRchrkBInkRAhI6AJ9KkRJfhAt3oqTUwsOL1DLxyGCBZACgyMmv h0kgJ68oJN1mXSIYjute+70= =idjP -----END PGP SIGNATURE----- --Sig_/Pm6LzHcvy7DrZqqZR.kDi8Q-- --===============1343260382== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --===============1343260382==--