Hi Christopher, Brian,
On 2015-02-10 10:41, Dearlove, Christopher (UK) wrote:
Fred Baker
I use the draft-*.all mailing lists to do what their description
says they do - copy the authors, working group chairs, and relevant
ADs on something specific to the draft.
The document shepherd should also be on that list. I've seen a case
where he missed something he should have seen due to a similar list
being used.
The shepherd is on the .all list, and this has been the case since the
.shepherd alias was introduced, which was about a year or year and a half
ago. The aliases that are created currently are as follows (except that
aliases that have empty expansions are not created):
<draftname> Authors
<draftname>.authors Authors
<draftname>.chairs WG Chairs (for WG drafts)
<draftname>.ad AD/ADs (if any)
<draftname>.shepherd Shepherd (if any)
<draftname>.notify As set in the document's notify field in the DB
and finally
<draftname>.all All of the above
Setting the notify field to contain .all or all of the components of .all,
which is the default now, essentially makes the notify field and the .all
aliases have the same semantics. I think that's a mistake.
A better solution would be to tease apart which kind of notifications
should be sent to all, and which need go only to people more closely
involved in the day-to-day handling of a draft, and have the datatracker
send notifications either to .notify or .all, depending on the kind of
notification.
Possibly an additional alias <draftname>.group would turn out to be
useful in order to populate .all with the WG list, if that is deemed
desirable.
Best regards,
Henrik