W3C home > Mailing lists > Public > public-webappsec@w3.org > February 2019

Re: WebAppSec Teleconference Timing and Techniques.

From: Mike West <mkwst@google.com>
Date: Mon, 25 Feb 2019 14:58:08 +0100
Message-ID: <CAKXHy=cqnvBAoC=-KRoYrPjbXzD4gnnkB-UBg33ENGyBvFWKDg@mail.gmail.com>
To: "Mike O'Neill" <michael.oneill@baycloud.com>, Dan Veditz <dveditz@mozilla.com>
Cc: Web Application Security Working Group <public-webappsec@w3.org>
If there's enough interest in setting up a timeslot rotation, I suspect we
can find friendly times for US/APAC, and US/EU. Perhaps +Dan Veditz
<dveditz@mozilla.com> can run the former while I'm sleeping.

I'd particularly appreciate feedback here from folks who would _like_ to
join the regular calls, but aren't able to because (for instance) they're
at ~2:00 in Japan. :)

-mike


On Mon, Feb 25, 2019 at 12:25 PM <michael.oneill@baycloud.com> wrote:

> This is  useful tool for planning timeslots.
>
>
>
>
> https://www.timeanddate.com/worldclock/meetingtime.html?iso=20190225&p1=136&p2=224&p3=240&p4=22&p5=179&p6=37&p7=44
>
>
>
> If we can do a late call in Europe  we can get an early slot down under
> and US looks fine.
>
>
>
> We could then alternate with a (very) early CET slot to get the folks in
> India etc. and maybe still manageable for US.
>
>
>
> We should try the TAG tools next call.
>
>
>
> Mike
>
>
>
>
>
> *From:* Mike West <mkwst@google.com>
> *Sent:* 25 February 2019 09:44
> *To:* Web Application Security Working Group <public-webappsec@w3.org>
> *Subject:* WebAppSec Teleconference Timing and Techniques.
>
>
>
> Hey folks,
>
>
>
> As discussed on the last call
> <https://www.w3.org/2019/02/20-webappsec-minutes.html#item03>, I'd like
> for us to think a little bit about how we're using our time on our calls,
> and whether it might be reasonable to make some changes. Three come to mind:
>
>
>
> 1.  I've heard from some folks (including me!) that the current timeslot
> isn't working well. It's early for California, dinnertime in central
> Europe, and the middle of the night across Asia. Perhaps it's reasonable to
> consider a shift, and perhaps even a rotation between time-zones to allow
> access to more folks. As a concrete suggestion to start a conversation: I'd
> generally prefer 11:00 Pacific, 20:00 CET (as my kids will safely be in
> bed). How unworkable would that be for folks who care about the calls?
>
>
>
> 2.  Audio-only conference calls are somewhat awkward. It might be nice to
> try out something that includes video/screen-sharing for somewhat more
> lively conversations (while, of course, retaining audio-only options for
> folks that would prefer for us not to have a camera in their house!). I
> suspect that there's a diversity of preferences in this group: Vidyo,
> Skype, etc. Hangouts are simplest for me personally, but I'm willing to try
> just about anything that works on a Chromebook: the TAG is apparently
> having success with https://appear.in/, for instance?
>
>
>
> 3.  Scribing in IRC is a pain in the butt. While it's nice to be able to
> rely upon the W3C's tooling for autopublication of minutes after a meeting,
> other groups have been successful with more dynamic methods. The TAG, for
> instance, has been using Cryptpad to take collaborative notes during a
> meeting (
> https://cryptpad.w3ctag.org/code/#/2/code/view/PgABV3fUQYNx4vTY8-dCiaaBGUqfwu+jwduYlO6Lzao/),
> and then posting the final result to GitHub (
> https://github.com/w3ctag/meetings/blob/gh-pages/2019/02-tokyo/02-07-minutes.md).
> That's a model that makes sense to me. Perhaps we could try it out?
>
>
>
> WDYT?
>
>
> -mike
>
Received on Monday, 25 February 2019 13:58:43 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 February 2019 13:58:44 UTC