w3c/webappswg

Planning for a virtual TPAC meeting

Closed this issue · 15 comments

marcoscaceres commented
  • We should find out who wants to meet for a virtual meeting?
    • Smaller chunks of meetings.
    • Status updates - on GitHub write up like last year. See if progress has been made.
    • Could we change it do dial in over?
    • Maybe over 2 weeks? Or restart the calls...
    • Maybe call them working sessions...
    • How do we deal with cross group pollination of ideas...

Editing task force already meets monthly?

inexorabletash commented

+1 to status updates on github - that seemed to work well. Also encourage as much async discussion and decision making as possible.

Re: Working sessions: I found the "breakouts" that emerged in Fukuoka to be very productive (one on general Storage, one on Indexed DB specifically). I'd like to capture that again, while being more inclusive: i.e. having them announced/scheduled ahead of time, and not competing for space/time/attention. So: gather a list, schedule them non-overlapping to take advantage of not having a tight F2F schedule, which addresses cross-pollination - apart from time zones, there won't be scheduling conflicts. (Other than cross-WG...)

  • 👍2
garykac commented

[...] i.e. having them announced/scheduled ahead of time, and not competing for space/time/attention. So: gather a list, schedule them non-overlapping to take advantage of not having a tight F2F schedule

+1 +1 +1 +1 +1 I wanted to participate or listen in on more than one of the overlapping breakout sessions. The discussions also felt a bit siloed – I don't think any of the breakouts had remote participants and I don't recall a lot of scribing.

Is there anything preventing us from recording the video/audio for these sessions?

Also, I've always feel bad for the people dialing in remotely because it's often hard to follow the discussion (and side-discussions) happening in the room. It would be nice to use this opportunity to experiment with ways to improve remote participation that we could carry on once we start meeting in person again.

marcoscaceres commented

We discussed doing the following on the chair's call:

  • Announce that TPAC will be virtual this year - dates forthcoming.
  • Will your community want to meet (what time? for how long?).... somehow centralize the schedule (probably just a shared online Calendar).
  • Provide a status report - with a deadline.
  • Provide a cross-group "office hours" for general chat... maybe something like a big zoom meeting and get more people on the Slack channel... or people create their own Slacks channels.
marcoscaceres commented

Fixed some typos above...

LJWatson commented

I've posted issues on the following repos:

  • ARIA in HTML
  • File API
  • Clipboard API & Events
  • Gamepad API
  • IndexedDB
  • Input Events Levels 1 and 2
  • Image Resource
  • Intersection Observer
  • Pointer Lock
  • Push API
  • Selection API
  • Screen Orientation API
  • UI Events
  • UI Events Key Values
  • UI Events Code Values
  • Web Share
  • Webapp Manifest
  • ❤️1
marcoscaceres commented

Excellent, thanks @LJWatson!

inexorabletash commented

Do we want a session (or multiple sessions) on specs in incubation (e.g. in WICG) that are on track to graduating to the WebAppsWG soonish?

A non-comprehensive list of ones that I'm somewhat involved in, at different stages.

I'm certain there are many more.

FWIW, I've never been entirely clear on whether the WICG sessions at TPAC are intended to be a catch-all for anything in WICG, or a meta-discussion of the CG process itself, or both. We should avoid overlap, though! But the relevant part is at least any specs that are graduating from incubation and fit into the charter or would require rechartering.

marcoscaceres commented

Do we want a session (or multiple sessions) on specs in incubation (e.g. in WICG) that are on track to graduating to the WebAppsWG soonish?
... snip...
FWIW, I've never been entirely clear on whether the WICG sessions at TPAC are intended to be a catch-all for anything in WICG, or a meta-discussion of the CG process itself, or both.

Can be both...

We should avoid overlap, though! But the relevant part is at least any specs that are graduating from incubation and fit into the charter or would require rechartering.

You are on point about requiring rechartering. It would be appropriate to have a "pitching" session to pitch new deliverables to working group members/implementers, as the working group needs to recharter to adopt those. Right now, only "Cookie Store" is in scope for the working group.

To adopt the new items, we would need interest from other browser vendors - and accompanying "intent to migrate".

However, it wouldn't be appropriate to have "working sessions" for WICG things as part of the WebAppsWG meeting... as actual technical work on the specs you listed should happen at the WICG until we adopt them. cc @wicg/chairs.

For sessions specifically for WICG items, they are best organized in: WICG/admin#122

marcoscaceres commented

Rules to have a meeting:

  • must take minutes: however, we don't mind where the minutes are taken, as long as they end up somewhere where we can collate them (e.g., google docs).

  • We need an example of how to take good minutes.

    • Who is scribing the minutes
    • who is present is present
    • who sent regrets
    • Clearly labelling Topics discussed
    • Actions (these can just be links to GitHub Issues)
    • Any "resolutions", although asynchronous resolutions are preferred through consensus.

  • Provide an agenda ahead of time.

We can reuse much of https://www.w3.org/2002/ws/addr/minutes.html except to for the zakim bits... people can even use IRC if they want Zakim support.

People can appoint themselves as meeting chairs, if they would like... The WG Chairs and Team can drop into meeting as time allows, but please organize your own scribe.

siusin commented

TPAC 2020 Group Meetings:

  • Joint Group meetings - week of 12-16 October
  • WG/IG/BG Group Meetings - week of 19-23 October
  • the TPAC breakout sessions - week of 26 to 30 October

I added a 2-hr event on 19 Oct (20 Oct those in AEDT and CST) to the WebApps WG TPAC calendar.

rniwa commented

I'm a bit confused here. When exactly is the meeting? Is it 2020-10-26T21:00:00Z?

siusin commented

@rniwa no, WebApps WG meeting will be on 2020-10-19
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=10&day=19&hour=21&min=0&sec=0&p1=152&p2=137&p3=179&p4=136&p5=33

WG meetings will be in the week of 19-23 October to avoid conflict with the breakout sessions (week of 26 to 30 October).

  • 👍1