Re: [PING] Friendly reminder - call details and agenda - Thursday 28 February UTC 17

Thats a great idea! Though the barrier of entry to Slack is a little high for outsiders looking for suggestions / advice / early feedback (and I’m not aware of anyway of sharing / making public slack convo). Maybe just a plain-old forum?

> On Feb 28, 2019, at 11:33 AM, Tara Whalen <tjwhalen@gmail.com> wrote:
> 
> Hi Pete (and all),
> 
> Yes, today was a bit of an outlier in terms of agenda completion  -- I really do hope it was useful for the API review (and indeed, this call was scheduled specifically to accommodate them) but that came at the cost of getting through our other items, regretfully. Indeed, this was the second PING meeting in February, which is already a bit more frequent than usual, and we *still* had more to talk about than we managed today! So I agree that we need to take a look at meeting frequency.
> 
> On a related note: the PING chairs and staff have been considering how we might support effective and regular communications apart from, and in between, the scheduled calls, and I'm eager to hear suggestions from folks. We thought it would be helpful to keep a more persistent channel open, which we hope would foster more group discussion and also serve as a place to share things like news articles and research papers about privacy. To that end we're going to set up a Slack channel for PING - expect an announcement soon when we have it up and running. 
> 
> 
> 
> On Thu, Feb 28, 2019 at 1:06 PM Pete Snyder <psnyder@brave.com> wrote:
> Hi all,
> 
> We didn’t even half way though the agenda, but I think the level of discussion we had today was very good.  Since there is no lack of need for privacy discussion in W3C, maybe it’d be worth moving to more frequent standard meetings?
> 
> Thoughts?
> 
> Pete
> 
> > On Feb 26, 2019, at 6:40 AM, Christine Runnegar <runnegar@isoc.org> wrote:
> > 
> > Colleagues,
> > 
> > A friendly reminder about our call on Thursday UTC 17.
> > 
> > Updated agenda
> > 
> > 1. Review substantive changes to the Payment Request API (since it was published as a Candidate Recommendation in July 2018)
> > 
> > Link to the substantive changes (in descriptive format):
> > https://lists.w3.org/Archives/Public/public-payments-wg/2019Feb/0003
> > 
> > For the updated specification, see the Editors' Draft:
> > https://w3c.github.io/payment-request/
> > 
> > 2. Privacy considerations of Inaccessibility of CAPTCHA 
> > 
> > https://www.w3.org/TR/2019/WD-turingtest-20190214/
> > 
> > 3. Verifiable Credentials Data Model 1.0 
> > 
> > Please read: Tip of tree editor's draft:  https://w3c.github.io/vc-data-model/
> > 
> > 4. Brief update regarding revisions to the Self-Review Questionnaire: Security and Privacy
> > 
> > https://github.com/w3cping/security-questionnaire
> > 
> > 5. Brief update and next steps - Private browsing mode (see Pete’s draft and ongoing discussion on the email list)
> > 
> > https://lists.w3.org/Archives/Public/public-privacy/2019JanMar/0021.html
> > 
> > 6. Open discussion (time permitting) - Transparency via a Machine-readable Server Identity and Purpose Descriptor (see Mike’s draft)
> > https://github.com/w3c/web-advertising/blob/master/serverdeclaration.md
> > 
> > Call details
> > 
> > WebEx meeting
> > https://www.w3.org/2018/08/ping-webex.html (W3 login will be needed to access Webex call details)
> > 
> > Please also join us on IRC on the #privacy channel:
> > 
> > Server: irc.w3.org
> > Username: <your name>
> > Port: 6667 or 6665
> > Channel: #privacy
> > 
> > Christine (co-chair)
> 
>

Received on Thursday, 28 February 2019 21:43:40 UTC