Notify Chairs and Comm of new transition requests

[vivienlacourba]

In order to continue to notify by emails Chairs and Comm of incoming transition requests you could use
github-notify-ml (using the proper combination of events and filters).
Note that this only sends email in digest mode (ie at max once a day).

(I discussed this with @deniak, that would answer @koalie recent comment)

[svgeesus]

That would be good. I have seen a couple of instances where this repo was updated but chairs was not copied, thus delaying the start of the one-week timeout.

[plehegar]

This should be addressed for the requirements in #71

[plehegar]

fyi, the code is at https://github.com/w3c/transition-issues-bot
as soon as I have a labs.w3.org, I'll start live testing the email and setting labels.

[svgeesus]

I was wondering whether, in the interests of supporting modern tooling and workflow, we could get rid of the need to mail chairs and comm? Now that this repo is no longer a CSSWG-guinea-pig but is in widespread use, it is the go-to place to look for u to date info about any transition. And everything for one transition is in a single issue instead of spread among multiple lists.

I posted the last two CSSWG transition announcements to chairs, I also added a request that further discussion be on this repo. But of course that ca't be enforced so if any chair starts a discussion it needs to be tracked on that (W3C Member-only) list.

I propose that a proposal be circulated to chairs and to comm suggesting this change. Unless there is objection, we would then remove the mail requirement. The 7-day timout starts when the issue is posted to this repo.

An additional benefit is that this repo is public, which the chairs list is Member-only (and for no good reason that I can see).

[koalie]

I wouldn't object. I abstain, in fact.

[plehegar]

New notification is deployed.