From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 20389@debbugs.gnu.org
Subject: bug#20389: A way to communicate announcements to developers
Date: Wed, 22 Apr 2015 13:18:41 -0400 [thread overview]
Message-ID: <iq4mo8rsi6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvegnes2hh.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 20 Apr 2015 21:20:01 -0400")
Stefan Monnier wrote:
>> 3. Add topic name "emacs-announce"; regexp "emacs-announce"; description
>> "announcements all Emacs developers should read".
>> (Using just "announce" may lead to false positives?)
>
> I could live with that. But I wonder if using gnu.emacs.announce would
> be worse or better. I mean, there might some benefit to "announce
> feature freeze to the world" rather than only to the developers.
But there's other stuff than the (relatively) interesting feature freeze
example. There's "hey, we don't use ChangeLogs any more";
"hey, start using 'foo' quotes rather than `blah' quotes";
"hey, remember to do your commit messages like this not like that";
etc. I think almost all announcements will not relevant be for info-gnu-emacs.
emacs-devel seems the natural home for such things to me.
info-gnu-emacs has 835 subscribers versus 200 committers;
don't know what the overlap is.
But the main point of this report was to get SOME kind of system.
If you want to make and advertise a different system, please do.
Eg https://pumprock.net/fsfstatus, s/fsf/emacs ;)
next prev parent reply other threads:[~2015-04-22 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 21:56 bug#20389: A way to communicate announcements to developers Glenn Morris
2015-04-21 1:20 ` Stefan Monnier
2015-04-22 17:18 ` Glenn Morris [this message]
2015-04-22 20:53 ` Stefan Monnier
2015-04-21 16:32 ` Eli Zaretskii
2015-04-21 17:22 ` Andreas Schwab
2015-04-21 18:37 ` Eli Zaretskii
2015-04-22 17:21 ` Glenn Morris
2015-04-22 17:50 ` Eli Zaretskii
2015-04-24 18:29 ` Glenn Morris
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=iq4mo8rsi6.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=20389@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.