all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: Tom Tromey <tromey@redhat.com>, Ted Zlatanov <tzz@lifelogs.com>,
	emacs-devel@gnu.org
Subject: Re: Emacs and the Status Notification Specification
Date: Thu, 30 Jun 2011 12:07:49 -0400	[thread overview]
Message-ID: <874o37fgkq.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1Qc3xr-0005BF-Ml@fencepost.gnu.org> (Richard Stallman's message of "Wed, 29 Jun 2011 19:14:35 -0400")

Richard Stallman <rms@gnu.org> writes:

>     Please call the GNU ELPA as such, or GELPA, or something besides just
>     "ELPA."  I remember we had this discussion before and I've tried to be
>     consistent, using "GNU ELPA" when I mean "GNU ELPA."
>
> The problem with "GNU ELPA" as a name is that people will tend to
> think that "ELPA" is an abbreviation of it.  To avoid confusion, we
> need a name that is not similar to "ELPA".
>
> How about Remote Emacs Library?

If we abandon ELPA as a term for archives of this type, we need also to
come up with a replacement name for archives of this type.

But "Emacs Lisp Package Archive" is the natural name to use when
referring to archives made using package.el, which internally refers
ubiquitously to "packages" and "archives".  So it would be preferable to
use ELPA as the generic name.

It would help if tromey.com/elpa/ would rebrand itself as "Tom's ELPA"
or something along those lines, instead of "the" ELPA as it currently
(understandably) does.  This will reduce confusion not only with the GNU
ELPA, but also the personal ELPAs that a few users are apparently
starting to set up.

Tom, WDYT?



  parent reply	other threads:[~2011-06-30 16:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 17:31 Emacs and the Status Notification Specification Tom Tromey
2011-06-23 18:28 ` Ted Zlatanov
2011-06-24  8:54   ` Philipp Haselwarter
2011-06-24 11:59     ` Ted Zlatanov
2011-06-24 17:00   ` Tom Tromey
2011-06-26  9:31     ` Michael Albinus
2011-06-26 16:18       ` Richard Stallman
2011-06-27  7:22         ` Stephen J. Turnbull
2011-06-27 16:06     ` Ted Zlatanov
2011-06-27 23:02       ` Richard Stallman
2011-06-28 11:52         ` Ted Zlatanov
2011-06-29 23:14           ` Richard Stallman
2011-06-30 12:38             ` Ted Zlatanov
2011-06-30 13:38               ` Juanma Barranquero
2011-06-30 14:58               ` John Yates
2011-06-30 15:27                 ` Juanma Barranquero
2011-06-30 17:41                   ` John Yates
2011-07-01  0:18               ` Richard Stallman
2011-07-01  1:46                 ` Ted Zlatanov
2011-07-01  1:57                   ` David De La Harpe Golden
2011-07-01  3:07                   ` Stefan Monnier
2011-07-01 11:40                     ` Richard Stallman
2011-07-01 13:11                       ` Ted Zlatanov
2011-07-01 14:16                         ` Stefan Monnier
2011-07-01 14:17                       ` Stefan Monnier
2011-07-02  8:11                         ` Richard Stallman
2011-06-30 16:07             ` Chong Yidong [this message]
2011-06-26  9:25 ` Michael Albinus

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=874o37fgkq.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=tromey@redhat.com \
    --cc=tzz@lifelogs.com \
    /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.