Re: [webpayments] Please enable issues to be reflected on the mailing list (#9)

Hi Manu,

To clarify what has been setup.


- There is now a bot Github user (https://github.com/webpayments/) with
the email address github-w3c-webpayments-wg@w3.org
- That email account is subscribed to the WG mailing list and is also
subscribed to all Github issue notifications on the repo:
https://github.com/w3c/webpayments
- When that account receives mails from Github it forwards them to the
mailing list.
- When the account receives replies from the mailing list it forwards
them to Github.

The result (once all moderation issues have been resolved) will be that:

- If a new issue is logged or a comment is added to an existing issue
then a mail will be sent to the mailing list
- Anyone replying to mails on the mailing list related to issues will
see their replies posted against the Github issue.

We still recommend that members of the WG post their comments and issues
directly on Github if possible as this has the least chance of creating
SPAM, messing with formatting or sending out duplicate messages.

Are there any outstanding security concerns:

1. Is it possible to compromise the Github account of the bot?
2. Is it possible to post to Github "anonymously"?
3. Are we certain that non email sent to the members-only mailing list
will end up on Github?

Thanks for making this work. If it's as seamless as it appears it should be
then I think it will be a great way to use Guthub and still accommodate
those that like to (or have to) use the mailing list.

Adrian


On 15 November 2015 at 21:32, webpayments <notifications@github.com> wrote:

> Hi Manu,
>
> Not sure what list is intended but I”m getting a moderator action…
>
> Ian
>
> > On Nov 14, 2015, at 3:05 PM, Manu Sporny <notifications@github.com>
> wrote:
> >
> > Hi all,
> >
> > Mailing list traffic for the Web Payments Working Group is going to
> start increasing in the next day or two. This is due to hooking up Github
> issue notifications to the public-payments-wg@w3.org mailing list. Here's
> how it works:
> >
> > • All issue discussion related to Github repositories that we're
> watching will be reflected on the mailing list.
> > • If you want to respond to the issue, the best way to do so is to click
> on the link at the end of the message and respond via Github's issue
> tracker.
> > • If you do not have access to Github, just "Reply" to the email. Please
> don't "Reply All" as it'll result in two emails being sent out.
> > This approach enables those that want to work in Github to do so while
> ensuring that those that can't work via Github can still participate in the
> discussion. I will send a separate email outlining how the Chairs and W3C
> Staff Contacts should manage messages.
> >
> > —
> > Reply to this email directly or view it on GitHub.
> >
>
> --
> Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs
> Tel: +1 718 260 9447
>
>
>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/webpayments/issues/9#issuecomment-156845681>.
>
—
Reply to this email directly or view it on GitHub <https://github.com/w3c/webpayments/issues/9#issuecomment-156973244>.