* bug#20389: A way to communicate announcements to developers
@ 2015-04-20 21:56 Glenn Morris
2015-04-21 1:20 ` Stefan Monnier
2015-04-21 16:32 ` Eli Zaretskii
0 siblings, 2 replies; 10+ messages in thread
From: Glenn Morris @ 2015-04-20 21:56 UTC (permalink / raw
To: 20389
Package: emacs
Severity: wishlist
Version: 24.5
(Bug report to remind about
http://lists.gnu.org/archive/html/emacs-devel/2014-12/msg00851.html)
Please create a mechanism to communicate important announcements
(feature freezes, etc) to emacs developers.
No-one should have to read (all of) emacs-devel, it's too noisy.
And the info-gnu-emacs list is not appropriate for this IMO.
FWIW, here's what I would do. It'd only take a few mins to set up:
1. Go to https://lists.gnu.org/mailman/admin/emacs-devel/topics
2. Enable topic filter.
3. Add topic name "emacs-announce"; regexp "emacs-announce"; description
"announcements all Emacs developers should read".
(Using just "announce" may lead to false positives?)
4. Document that developers should subscribe to emacs-devel and at
least subscribe to the "emacs-announce" topic. Whether or not they also
choose to "receive messages that do not match any topic filter" is up
to the individual.
5. Use "Keywords: emacs-announce" in the header of relevant mails.
Better (?) to use keywords: than the subject: header, to avoid all the
replies to said subject being sent out as announcements too. If you
forget to add it to a message, you or anyone else can just resend it.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
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
2015-04-21 16:32 ` Eli Zaretskii
1 sibling, 1 reply; 10+ messages in thread
From: Stefan Monnier @ 2015-04-21 1:20 UTC (permalink / raw
To: Glenn Morris; +Cc: 20389
> 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.
Stefan
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
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-21 16:32 ` Eli Zaretskii
2015-04-21 17:22 ` Andreas Schwab
1 sibling, 1 reply; 10+ messages in thread
From: Eli Zaretskii @ 2015-04-21 16:32 UTC (permalink / raw
To: Glenn Morris; +Cc: 20389
> From: Glenn Morris <rgm@gnu.org>
> Date: Mon, 20 Apr 2015 17:56:23 -0400
>
> 1. Go to https://lists.gnu.org/mailman/admin/emacs-devel/topics
>
> 2. Enable topic filter.
>
> 3. Add topic name "emacs-announce"; regexp "emacs-announce"; description
> "announcements all Emacs developers should read".
> (Using just "announce" may lead to false positives?)
>
> 4. Document that developers should subscribe to emacs-devel and at
> least subscribe to the "emacs-announce" topic. Whether or not they also
> choose to "receive messages that do not match any topic filter" is up
> to the individual.
Doesn't enabling the topic filter mean that every subscriber must
update their subscription, to choose the topics to which they want to
subscribe?
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
2015-04-21 16:32 ` Eli Zaretskii
@ 2015-04-21 17:22 ` Andreas Schwab
2015-04-21 18:37 ` Eli Zaretskii
0 siblings, 1 reply; 10+ messages in thread
From: Andreas Schwab @ 2015-04-21 17:22 UTC (permalink / raw
To: Eli Zaretskii; +Cc: 20389
Eli Zaretskii <eliz@gnu.org> writes:
> Doesn't enabling the topic filter mean that every subscriber must
> update their subscription, to choose the topics to which they want to
> subscribe?
"If you do not select any topics of interest, you will get all the
messages sent to the mailing list."
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
2015-04-21 17:22 ` Andreas Schwab
@ 2015-04-21 18:37 ` Eli Zaretskii
2015-04-22 17:21 ` Glenn Morris
0 siblings, 1 reply; 10+ messages in thread
From: Eli Zaretskii @ 2015-04-21 18:37 UTC (permalink / raw
To: Andreas Schwab; +Cc: 20389-done
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Glenn Morris <rgm@gnu.org>, 20389@debbugs.gnu.org
> Date: Tue, 21 Apr 2015 19:22:33 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Doesn't enabling the topic filter mean that every subscriber must
> > update their subscription, to choose the topics to which they want to
> > subscribe?
>
> "If you do not select any topics of interest, you will get all the
> messages sent to the mailing list."
Thanks.
I did what Glenn suggested for the mailing list changes. One concern:
my reading of the "Topics" page is that the topic matcher scans the
_body_ of the message, so the suggestion to use "Keywords:
emacs-announce" in the _headers_ of the mail will probably not work.
Or maybe I misunderstood what Glenn meant by that.
I did nothing about item 4 in Glenn's message.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
2015-04-21 1:20 ` Stefan Monnier
@ 2015-04-22 17:18 ` Glenn Morris
2015-04-22 20:53 ` Stefan Monnier
0 siblings, 1 reply; 10+ messages in thread
From: Glenn Morris @ 2015-04-22 17:18 UTC (permalink / raw
To: Stefan Monnier; +Cc: 20389
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 ;)
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
2015-04-21 18:37 ` Eli Zaretskii
@ 2015-04-22 17:21 ` Glenn Morris
2015-04-22 17:50 ` Eli Zaretskii
0 siblings, 1 reply; 10+ messages in thread
From: Glenn Morris @ 2015-04-22 17:21 UTC (permalink / raw
To: Eli Zaretskii; +Cc: Andreas Schwab, 20389
Eli Zaretskii wrote:
> I did what Glenn suggested for the mailing list changes. One concern:
> my reading of the "Topics" page is that the topic matcher scans the
> _body_ of the message, so the suggestion to use "Keywords:
> emacs-announce" in the _headers_ of the mail will probably not work.
Thanks for setting that up.
I can assure you that it works on real headers as well as "pseudo"
headers in the body. See eg help text at
https://lists.gnu.org/mailman/admin/emacs-devel/?VARHELP=topics/topics_bodylines_limit
Before this report is closed, the other aspects of it were:
1) Is that a system people are ok with using? It was just my suggestion.
2) If so, get it documented/advertised/used.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
2015-04-22 17:21 ` Glenn Morris
@ 2015-04-22 17:50 ` Eli Zaretskii
2015-04-24 18:29 ` Glenn Morris
0 siblings, 1 reply; 10+ messages in thread
From: Eli Zaretskii @ 2015-04-22 17:50 UTC (permalink / raw
To: Glenn Morris; +Cc: schwab, 20389
> From: Glenn Morris <rgm@gnu.org>
> Cc: Andreas Schwab <schwab@linux-m68k.org>, 20389@debbugs.gnu.org
> Date: Wed, 22 Apr 2015 13:21:37 -0400
>
> 1) Is that a system people are ok with using? It was just my suggestion.
I guess we will see.
> 2) If so, get it documented/advertised/used.
It already is, see CONTRIBUTE.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
2015-04-22 17:18 ` Glenn Morris
@ 2015-04-22 20:53 ` Stefan Monnier
0 siblings, 0 replies; 10+ messages in thread
From: Stefan Monnier @ 2015-04-22 20:53 UTC (permalink / raw
To: Glenn Morris; +Cc: 20389
> 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.
Right, makes sense, thanks,
Stefan
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#20389: A way to communicate announcements to developers
2015-04-22 17:50 ` Eli Zaretskii
@ 2015-04-24 18:29 ` Glenn Morris
0 siblings, 0 replies; 10+ messages in thread
From: Glenn Morris @ 2015-04-24 18:29 UTC (permalink / raw
To: Eli Zaretskii; +Cc: schwab, 20389
Eli Zaretskii wrote:
>> 2) If so, get it documented/advertised/used.
>
> It already is, see CONTRIBUTE.
Oh thanks, I missed that.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2015-04-24 18:29 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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.