W3C home > Mailing lists > Public > public-w3process@w3.org > July 2015

Re: [closed] Re: Announcing FPWD pubs on p-review-announce [Was: Re: Comments on: W3C Process2015]

From: timeless <timeless@gmail.com>
Date: Thu, 2 Jul 2015 15:41:08 -0400
Message-ID: <CACsW8eFkEYavui93PRh5Los9b+umRCns53o_BP_GOg5fMC5jiA@mail.gmail.com>
To: Coralie Mercier <coralie@w3.org>, Philippe Le Hégaret <plh@w3.org>
Cc: public-w3process <public-w3process@w3.org>
On Wed, May 20, 2015 at 8:23 AM, Coralie Mercier <coralie@w3.org> wrote:
> Belatedly closing the loop on that thread.
> Philippe Le Hégaret and the Systems team worked to implement automatic
> notification to public-review-announce@w3.org.

> ------- Forwarded message -------
> From: "Philippe Le Hegaret" <plh@w3.org>
> Subject: Re: Fwd: Announcing FPWD pubs on p-review-announce [Was: Re:
> Comments on: W3C Process2015]
> Date: Thu, 14 May 2015 23:29:16 +0200
>
> The transition notifier is now activated. See the notifications generated
> in
>    https://lists.w3.org/Archives/Public/public-review-announce/2015May/
>
> It notifies FPWD, LCWD, CR, and WD mentioning "wide review" in their
> status.

First, thanks to everyone for working on this.
I've been slowly working through the list and am quite thankful for
its existence.
(I've also been filing bugs directly to plh on minor items involved in
how the notifier formats emails.)

The only other request I have is some way that would be Gmail
compatible to recognize when a review request has been obsoleted. That
way when I have a message which is planned, I can know if I need to
change its priority (either plus or minus). This is actually fairly
easy to do in theory:

1. Keep track of the last review request email (subject, messageid,
archiveurl) for a given document.
2. After sending a new review request for the same document, "reply"
to the previous email w/ a pointer to the newer request (include the
new subject in the body along w/ the lists.w3.org url and the
messageid as a followup record??).

I can imagine that such emails could annoy people, so, there are a few
things that could help:
1. they shouldn't be sent from the same sender as the normal notifier
(so people could filter them out -- obsolete-notifier@).
2. it could probably be sent to a second mailing list, so people would
subscribe to public-review-obsoleted@ or something. As long as the
obsolete-notifier@ is replying to the right email w/ the proper
subject, Gmail should tolerate the crossing of lists behavior (and I'd
imagine most other mail software would too).
Received on Thursday, 2 July 2015 19:41:36 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 2 July 2015 19:41:36 UTC