all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>,
	David Gonzalez Gandara <dggandara@member.fsf.org>
Cc: emacs-elpa-diffs@gnu.org
Subject: announcing GNU ELPA updates    [was: [elpa] master 9a3a508: Package transcribe added]
Date: Sun, 29 Nov 2015 16:19:31 -0800 (PST)	[thread overview]
Message-ID: <8c1b4ee0-7c41-456a-bdad-ce1a941be748@default> (raw)
In-Reply-To: <CAAdUY-LCYa3f4Qd6uKpmgG6hDJi2RjJhcOR2+ZZEboHuG_8qQQ@mail.gmail.com>

> we now announce on emacs-devel before adding new packages to Elpa.
> There's more information on the readme. 
> It's just a way of keeping everybody informed about new additions.

1. Why do we do this?  It already gets "announced" on gnu-emacs-sources@gnu.org.

Also, I guess that the many messages I get on that list, and
which are so succinct, are automated (?).  For example:

 Version 20151123 of GNU ELPA package org has just been released.
 You can now find it in M-x package-list RET.

 More at http://elpa.gnu.org/packages/org.html

It would be more helpful if a one-line description of what
the package is/does were included.  And that would probably
also suffice as the initial "announcement" of a package, no?


2. A year ago, such automated announcements were being sent
to info-gnu-emacs@gnu.org.  Why the change?  Now they drown
out the source-code announcement messages submitted manually
by actual users.  IOW, gnu-emacs-sources@gnu.org has more or
less been hijacked.

I agree that GNU ELPA should announce its updates, but
somewhere else might be better, no?  What was wrong with
info-gnu-emacs@gnu.org?  I suppose that it was thought that
the ELPA update msgs were drowning out other, more important
messages about GNU Emacs.  That's understandable.

Maybe GNU ELPA updates need their own list, so they don't
drown out anything?



  reply	other threads:[~2015-11-30  0:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151129123851.5369.35231@vcs.savannah.gnu.org>
     [not found] ` <E1a31Fj-0001PD-Bq@vcs.savannah.gnu.org>
2015-11-29 22:41   ` [elpa] master 9a3a508: Package transcribe added Stefan Monnier
2015-11-29 23:37     ` Artur Malabarba
     [not found]   ` <E1a31Fj-0001PD-Bq-7jckXlaVFY8RVz71yTsr42D2FQJk+8+b@public.gmane.org>
2015-11-29 23:35     ` Artur Malabarba
2015-11-30  0:19       ` Drew Adams [this message]
2015-11-30 10:57         ` announcing GNU ELPA updates [was: [elpa] master 9a3a508: Package transcribe added] Rolf Ade
     [not found]       ` <CAAdUY-LCYa3f4Qd6uKpmgG6hDJi2RjJhcOR2+ZZEboHuG_8qQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-30 10:19         ` [elpa] master 9a3a508: Package transcribe added Artur Malabarba
2015-11-30 17:11           ` David González Gándara

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=8c1b4ee0-7c41-456a-bdad-ce1a941be748@default \
    --to=drew.adams@oracle.com \
    --cc=bruce.connor.am@gmail.com \
    --cc=dggandara@member.fsf.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-elpa-diffs@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.