search

w3c / secondscreen-wg

Home page of the Second Screen Working Group
https://www.w3.org/2014/secondscreen/
8 stars 5 forks source link

Second Screen WG/CG - 2021 Q1 virtual meeting #2

Open anssiko opened 3 years ago

anssiko commented 3 years ago

☝ī¸ This issue is to work out an agenda for the Second Screen WG/CG 2021 Q1 virtual meeting.

Registration

All Second Screen WG and CG participants are welcome to attend this virtual meeting without registration.

Some confirmed Participants listed below 👇

Logistics

The meeting takes place over two days, 2 hours per day.

Zoom and meeting invite links restricted to Second Screen CG participants and W3C Members, non-Members ping @tidoust in comments or send him an email.

Agenda

06:00 UTC 23 Feb 2021

:warning: Feedback and suggestion on specific agenda items welcome via comments. 👇

⏰ UTC time 23 Feb 2021
06:00 UTC Welcome, agenda bashing
06:05 UTC Open Screen Protocol (Mark Foltz @mfoltzgoogle)
ℹī¸ https://github.com/w3c/openscreenprotocol/issues/249
06:30 UTC Presentation API (Mark Foltz @mfoltzgoogle)
06:45 UTC Remote Playback API (Mark Foltz @mfoltzgoogle, Mounir Lamouri @mounirlamouri?)
07:00 UTC :coffee: :tea: Break
07:10 UTC "Deskreen intro" (Pavlo Buidenkov @pavlobu Slides)
07:25 UTC "Second screen use cases in webOS" (Hyojin Song @anawhj Slides)
07:40 UTC "Local Devices Protocol - Building Blocks for the Local Web" (Michiel De Backker @backkem Slides)

06:00 UTC 24 Feb 2021

⏰ UTC time 24 Feb 2021
06:00 UTC Screen Fold API (Kenneth Christiansen @kenchris, Alexis Menard @darktears)
ℹī¸ https://github.com/w3ctag/design-reviews/issues/575#issuecomment-766925899
ℹī¸ https://github.com/w3c/screen-fold/issues/54
06:40 UTC Multi-Screen Window Placement (Mike Wasserman @michaelwasserman)
ℹī¸ Discuss explainer updates
07:00 UTC :coffee: :tea: Break
07:10 UTC Window Segments (Daniel Libby @dlibby-)
ℹī¸ https://github.com/webscreens/window-segments/issues/12
ℹī¸ Interop with declarative https://github.com/w3c/csswg-drafts/issues/5621 and https://github.com/w3c/csswg-drafts/issues/5622
ℹī¸ Interop with visualViewport API
07:30 UTC Form Factors explained
ℹī¸ Discuss and identify next high priority work items
07:50 UTC Other related work:
ℹī¸ Same-screen presentation w3c/presentation-api#476 and w3c/presentation-api#479 (Daniel Libby @dlibby-)

Minutes

Participants

Some participants with timezone breakdown. Checked box indicates confirmed availability for the proposed meeting dates/times.

Please do not hesitate to drop a comment to be added to the list of participants here.

EU

US West Coast

US East Coast

APAC

louaybassbouss commented 3 years ago

Thanks @anssiko regarding registration I also propose to keep it simple by adding a comment in this issue and we keep the list of participants up-to-date.

anssiko commented 3 years ago

@louaybassbouss, sounds good! I adjusted the reg instructions accordingly and added some checkboxes next to the names awaiting signals on folks' availability. We can do a doodle poll if we find the first proposed dates/times problematic.

chrisn commented 3 years ago

Dates and times are OK for me (I had booked leave that week, but I'm flexible).

darktears commented 3 years ago

I'm East Coast now and it's going to be hard for me :) but I'll make it.

anssiko commented 3 years ago

@chrisn thank you, checked the participants box for you.

@darktears, I forgot that, sorry! I need to send you some good :coffee: to keep you awake if this time is really doable. We can try schedule your most important thing(s) as the first topic, let us know?

Anyone else on the East Coast? The challenge remains the wide geo distribution as long as we don't go back to the flat Earth :smile:

markafoltz commented 3 years ago

Overall availability is fine - as long as the agenda is < 2 hours per day, I shouldn't have any time constraints

michaelwasserman commented 3 years ago

I will plan to join, thanks. (looks like Tue is actually the 23rd, and Wed is the 24th?)

louaybassbouss commented 3 years ago

I will plan to join, thanks. (looks like Tue is actually the 23rd, and Wed is the 24th?)

Thanks @michaelwasserman I will correct the dates 👍

louaybassbouss commented 3 years ago

Overall availability is fine - as long as the agenda is < 2 hours per day, I shouldn't have any time constraints

Thanks @mfoltzgoogle for confirming the time slots yes we we will not exceed 2 hours per day. Do you think 30 minutes is reasonable for an OSP session? Feel free to propose Agenda items for this session.

anssiko commented 3 years ago

The dates should be fixed now. We'll look into ical invites so you get this in your calendars properly.

Please note the meeting takes place either Mon/Tue if you're on the US West Coast or Tue/Wed if you're in the EU, APAC or in Florida... sorry @darktears.

anssiko commented 3 years ago

Gently pinging @dlibby- from Microsoft for availability.

dlibby- commented 3 years ago

Yes I can attend the Tue/Wed time slot.

louaybassbouss commented 3 years ago

Thanks Hyojin (@anawhj) for confirming the lightning talk "second screen use cases in webOS" 👍

louaybassbouss commented 3 years ago

welcome Michiel (@backkem) and looking forward to your lightning talk "Local Devices - Building Blocks for the Local Web".

kenchris commented 3 years ago

We should discuss https://github.com/w3c/screen-fold/issues/54

anssiko commented 3 years ago

The agenda has been updated with some additional details to the Window Segments related discussion (thanks @dlibby-!).

All - please note we propose to flip the Screen Fold API and Form Factors discussion slots around on Day 2. This should make it easier for our US East Coast participant @darktears to attend the Screen Fold API discussion.

markafoltz commented 3 years ago

For the Presentation API, it may be useful to cover the following two issues briefly

For the Remote Playback API, we had a followup action from TPAC 2020 on this issue, if there are any updates to share on it.

markafoltz commented 3 years ago

For the Open Screen Protocol, the main agenda item I would like to discuss is publication of the FPWD. I would like to ask Francois any preparation we would need to make before doing so, and as a group list any issues we wanted to close out before publishing.

I propose we include the following "editorial" issues I see listed in the tracker:

These issues either have resolutions from previous meetings that need to be incorporated into the spec, or are improvements to the spec document (but not changes to the spec itself).

We could also decide to address Update SPAKE2 section according to current IETF draft (w3c/openscreenprotocol#235) before FPWD, however, we may end up choosing an alternative PAKE in the end (w3c/openscreenprotocol#242).

There are also two open PRs, which I believe are nearly ready to be merged:

The second one is awaiting feedback, if we have time in the agenda happy to go through it.

Anyway, once the group is happy with the FPWD task list, we can update the FPWD meta-issue to track closing these out, and I will start preparing/updating PRs.