Re: github notifications setup for w3c/webauthn?

Sure, we can give it a try. We may be getting our gh notifications
through two different streams, and so if we see duplicates, I'll try to
weed them out.

--Wendy

On 05/26/2016 11:16 AM, Hodges, Jeff wrote:
> HI Wendy,
> 
> might we update the webauthn entry in https://github.com/w3c/github-notify-ml-config/blob/master/mls.json to include..
> 
> "pull_request.opened",  "pull_request.closed", "push"
> 
> ..?   If for some reason it doesnt add value we can always change it back, yes?
> 
> thx,
> 
> =JeffH
> 
> On 4/21/16, 10:12 AM, "Alexei Czeskis" <aczeskis@google.com<mailto:aczeskis@google.com>> wrote:
> 
> pull request opened/closed seems nice.  So does "push".
> 
> 
> On Thu, Apr 21, 2016 at 9:58 AM, Hodges, Jeff <jeff.hodges@paypal.com<mailto:jeff.hodges@paypal.com>> wrote:
> So our github notifications setup for https://github.com/w3c/webauthn is..
> 
> "public-webauthn@w3.org<mailto:public-webauthn@w3.org>": {
>         "w3c/webauthn": {
> 
> "events": ["issues.opened", "issues.labeled", "issues.closed", "issue_comment.created"]
> }
> }
> 
> ...( as found at end of this file: https://github.com/w3c/github-notify-ml-config/blob/master/mls.json )
> 
> I note that we could also have notifications for "pull_request.opened", "pull_request.labeled", "pull_request.closed", "push", and "tr.published" (see set of templates here: https://github.com/dontcallmedom/github-notify-ml/tree/master/templates/generic )
> 
> examining mls.json (linked above) shows other working groups are all over the map regarding which events they get notified for, so it seems tough to glean guidance from their examples without querying for rationale.
> 
> but anyway, i just wanted to raise consciousness -- i'm wondering if we might want to add notifications for pull_request.* and see if it's useful...
> 
> =JeffH
> 
> 
> 
> 


-- 
Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
Policy Counsel and Domain Lead, World Wide Web Consortium (W3C)
https://wendy.seltzer.org/        +1.617.863.0613 (mobile)

Received on Thursday, 26 May 2016 15:27:27 UTC