Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!mcvax!unido!infbs!neitzel
From: neitzel@infbs.UUCP (Martin Neitzel)
Newsgroups: gnu.emacs
Subject: gnu.emacs.core ?
Message-ID: <1216@infbs.UUCP>
Date: 17 May 89 20:47:28 GMT
Organization: TU Braunschweig,Informatik,West Germany
Lines: 36


In gnu.emacs, David C Lawrence (tale@pawl.rpi.edu) recently brought up
the topic "integretation of contributed elisp code".  To dig right
into the midst:

dl>	So how do we convince RMS to include some of this stuff in the
dl>	distribution?  Just ask?  (Somewhat novel idea for me; I
dl>	haven't tried it.)  Petition?  I, for one, would like to see
dl>	it be included in the regular distribution.

dl>	So the question remains: how do we get it sanctioned? 

I couldn't agree more.  The handling of ``contributed software'' is
becoming more and more difficult, especially if it concerns
replacements for officially distributed stuff.

Keeping up with the submissions to comp.emacs and gnu.emacs alone,
caring about a simple index file with short descriptions etc. has
become a full time job.

In analogy to the X-consortium, I would like to see some kind of
(visible & addressable) "elisp consortium" established, that cares
about the composition of the emacs "core" distribution.

The "some-kind-of-emacs-consortium" should
- evaluate suggested changes.
- accept those "petitions" and organize votings.
- identify and minimize reduncy in the core.
- act as mediator to the "distributor in charge" (probably RMS & friends)

This work requires much knowledge of and experience with the existing
lisp stuff.

To summarize:  How about a newsgroup gnu.emacs.core?

							Martin