- From: Anton Vayvod <avayvod@google.com>
- Date: Mon, 2 Feb 2015 15:06:34 +0000
- To: "mark a. foltz" <mfoltz@google.com>
- Cc: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "public-secondscreen@w3.org" <public-secondscreen@w3.org>
- Message-ID: <CAOjek6p8W7aV_OS=i5U206OFZKCKxwk6cH5G4_2jaWLMW4Ea0g@mail.gmail.com>
+1 On Fri, Jan 30, 2015 at 4:32 PM, mark a. foltz <mfoltz@google.com> wrote: > Sounds good to me. > > > On Fri, Jan 30, 2015 at 2:26 AM, Kostiainen, Anssi < > anssi.kostiainen@intel.com> wrote: > >> Hi All, >> >> I'm wondering whether we should try Dom's github-notify-ml [1] in this >> group. It automatically notifies the mailing list of the following activity >> in the GitHub re the Presentation-API: >> >> * issues are opened, commented on, closed >> * pull requests are opened >> * commits are pushed >> >> This would simplify the workflow, since no need to send a separate mail >> to this mailing list and cross-link the mailing list discussions with the >> GitHub activity (as that'd be done automatically). This would allow us to >> have discussions in the GH issues. >> > Should discussions move to the GH issues by default then? > >> Of course, there are some tradeoffs (duplicates if you watch the repo >> too, replies to the automatic notifications are not reflected back to GH). >> > Just to clarify: one won't be able to join the discussion of a GH issue on the mailing list since the replies won't be posted back to the issue? (e.g. code.google.com as many other bug tracking sites I've been using allow to reply to the email notification to leave a comment). > >> Nevertheless, I'd suggest we give it a spin, since this mailing list is >> relatively low volume. >> >> If it seems not to work, we could just disable it. All this assuming we >> get help from Francois and/or Dom to enable this for our group :-) >> >> See Dom's mail [2] for more. >> >> WDYT? >> >> Thanks, >> >> -Anssi (WG chair) >> >> [1] https://github.com/dontcallmedom/github-notify-ml >> [2] >> https://lists.w3.org/Archives/Public/public-media-capture/2014Dec/0009.html >> > >
Received on Monday, 2 February 2015 15:07:25 UTC