WICG / webcomponents

Web Components specifications
Other
4.36k stars 370 forks source link

2020 Spring Virtual F2F #855

Closed hober closed 3 years ago

hober commented 4 years ago

Web Components Spring 2020 Virtual F2F

Where: https://github.com/w3c/webcomponents/wiki/2020-Spring-Virtual-F2F#conference-call-information When: Monday 23 & Tuesday 24, 3 PM - 7 PM UTC Agenda and summary of conclusions: https://docs.google.com/document/d/1lpy6k_ZlI5iVo-Y0vJaDfFAQvYRjpZqUcSlnOex2A0Q/edit#heading=h.9ut5sja3keva Minutes: Day 1, Day 2

rniwa commented 4 years ago

At the start of the meeting, we'll agree on the numerical order in which we want to discuss the topics and how much time we want to allocate. That goes in the live agenda.

We'd probably need to decide the time to discuss each topic prior to the meeting (at least a few days in advance) due to the timezone differences.

JanMiksovsky commented 4 years ago

@rniwa Great point. I've added a Participant Time Zones table at the bottom of that document based on the time zones for declared participants, plus Tokyo and Sydney for people implicated in some of the discussions.

I've tried to highlight regular 9 am–5 pm working hours, plus 3 hours on either side of that if people can make allowances for working somewhat early or late (while staying within the bounds of sanity).

Agree that it would be good to figure out timing of specific discussions by, say, the end of this workweek.

JanMiksovsky commented 4 years ago

Since some people reacted positively to my agenda idea, maybe we can run with that?

If that sounds okay, then the next step would be to have the proposed advocates mentioned for specific discussions add a sentence or two to the draft live agenda summing up where the proposal/issue stands, and how they'd like to focus the discussion during the meeting.

I took a shot at identifying the following people as advocates for proposals/issues: @tabatkins @hayatoito @justinfagnani @rakina @domenic @mfreed7 @diervo @alice @westbrook. (I put myself down for one topic as well.)

It might turn out that some topics are no longer interesting and can be dropped, or won't have enough new information gathered in time to ensure a productive discussion. In that case, feel free to pull something off the agenda.

Alternatively, if you're not going to be able to attend, or you think an issue with your name next to it would be better handled by a different person, you can remove your name and (hopefully) nominate someone else to act as the advocate for it.

domenic commented 4 years ago

I'm no longer working on web components, and would appreciate not being added to any agenda.

JanMiksovsky commented 4 years ago

@domenic Shall I pull off that "Avoiding custom element FOUC" topic then, or did you want to have someone else represent that?

domenic commented 4 years ago

I'm not sure who added it, but it would be best to delete things that weren't volunteered to be presented.

JanMiksovsky commented 4 years ago

I've removed it. I'd started the draft with topics that had been covered in September 2019 and which hadn't been resolved in that meeting, with the assumption that those would still be active topics. Sorry for the confusion.

pmdartus commented 4 years ago

Hi all, the virtual F2F is next week.

I took the opportunity to create the calendar invite and set up the meeting call. As discussed above, let's plan 2 sessions of discussion Monday 23 and Tuesday 24 between 3 PM and 7 PM UTC. We might revisit this schedule depending on the attendance and the agenda on Monday.

Calendar: link

Conference call information:

To join the video meeting, click this link: https://meet.google.com/bbj-kxox-cra To join by phone, look up the best number to use and the PIN on this page: https://meet.google.com/tel/bbj-kxox-cra?hs=5

dandclark commented 4 years ago

There is still an agenda section here: https://github.com/w3c/webcomponents/wiki/2020-Spring-Virtual-F2F#agenda

Separately there is the live agenda page.

Have we settled on using the live agenda? If so, should we replace the Agenda section here with a link to the live one?

mfreed7 commented 4 years ago

...and if the new agenda is the live agenda page, I presume the expectation is that we should be directly editing that doc to reflect what we're interested in discussing? Or would you prefer that change requests be made on this thread?

JanMiksovsky commented 4 years ago

If it's okay with everyone, let's use that live agenda. I think it's going to be much easier for us to follow along in a live doc than a wiki page. I'll update the wiki page to point to that doc.

Everyone should have open edit access to the doc. If anyone, for any reason, would rather not update that doc, or hits technical issues editing it, please just update the wiki page. I'll keep watching that page for changes, and will move any new content over.

On Wed, Mar 18, 2020 at 11:36 AM Mason Freed notifications@github.com wrote:

...and if the new agenda is the live agenda page https://docs.google.com/document/d/1lpy6k_ZlI5iVo-Y0vJaDfFAQvYRjpZqUcSlnOex2A0Q/edit#, I presume the expectation is that we should be directly editing that doc to reflect what we're interested in discussing? Or would you prefer that change requests be made on this thread?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/w3c/webcomponents/issues/855#issuecomment-600795644, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAVA62ZCQMSJBFRSUTWKJDRIEID7ANCNFSM4JQGAGXQ .

justinfagnani commented 4 years ago

Since on a virtual meeting we're not going to have a chance for serendipitous hallway conversations, should we schedule something to take that place? I'm not sure what, but maybe open-discussion, or un-conference-like breakouts?

JanMiksovsky commented 4 years ago

Good idea. Maybe this could be an optional block that follows the 4 hour official session that ends at 7:00 pm UTC.

Looking at the participant time zone map at the bottom of the agenda, it looks like the end of the official session falls roughly at dinnertime for CET, lunchtime for PDT, and, um, snack time for EDT. So maybe we could do this as a virtual shared meal: people gather in breakouts to eat and talk together?

rniwa commented 4 years ago

Looking at the participant time zone map at the bottom of the agenda, it looks like the end of the official session falls roughly at dinnertime for CET, lunchtime for PDT, and, um, snack time for EDT. So maybe we could do this as a virtual shared meal: people gather in breakouts to eat and talk together?

Well, that's a bit problematic because I do need to get food somewhere in order to have my meal.

Westbrook commented 4 years ago

@pmdartus I couldn't open those calendar events, are their permissions open?

We're committed to meeting next week? There was some talk about wanting a different timeline to prepare for presenting digitally and wanted to confirm.

rniwa commented 4 years ago

@pmdartus I couldn't open those calendar events, are their permissions open?

We're committed to meeting next week? There was some talk about wanting a different timeline to prepare for presenting digitally and wanted to confirm.

It's happening Monday 23 & Tuesday 24, 3 PM - 7 PM UTC.

pmdartus commented 4 years ago

@Westbrook Here is the new calendar. I made the calendar public, so you should have access to it.

annevk commented 4 years ago

I added a couple of comments to the live agenda. I think it would be useful if each topic had an advocate that's intimately familiar with the topic and can give a brief introduction as well as the required next steps. (Not needed for triage of course.) I'm not sure how much chairing we'll need but I'm happy to volunteer.

Using Zakim and #components on W3C IRC seems reasonable. Automated transcription sounds great. If that's guaranteed let's use the IRC channel as a backchannel and a way to exchange links and such.

Anything else?

tabatkins commented 4 years ago

On Wed, Mar 18, 2020 at 2:36 AM Pierre-Marie Dartus notifications@github.com wrote: Conference call information:

To join the video meeting, click this link: https://meet.google.com/bbj-kxox-cra Otherwise, to join by phone, dial XXXXXXXXXXXXX and enter this PIN: 969 359# To view more phone numbers, click this link: https://tel.meet/bbj-kxox-cra?hs=5

So hey pro tip, please don't include a French number in the instructions and hide other numbers behind a link. I, uh, may have just gotten a text from T-Mobile that I incurred $600 of international calling fees from today's meeting.

It would have been much friendlier, and less likely to catch people, to just not have a phone number listed, and direct everyone to the link.

~TJ

hober commented 4 years ago

I've updated the wiki page and this page to drop references to that phone number. So sorry that happened, @pmdartus.

tabatkins commented 4 years ago

It was me, actually; I forgot that Markdown blockquotes pick up the following paragraphs unless you double-space, so it parsed weird here in the comment (I replied in an email and didn't see the misparse).

It's fine, if I can't get it removed I'll expense it, but thank you for fixing it for others. ^_^

pmdartus commented 4 years ago

Sorry for the inconvenience @tabatkins, I didn't catch this when preparing the meeting invite.

rniwa commented 4 years ago

This virtual F2F went pretty well! I'm now suggesting that maybe we can have another one focused on accessibility. Please let us know of your interests :)

sideshowbarker commented 4 years ago

From the people here who participated in this meeting, it would be nice to record some detailed feedback somewhere about how the logistics went: What worked well, what didn’t, etc.

For other groups who’ll be doing similar “virtual f2f” meetings over the coming months, having some such “here’s what worked well, here’s what didn’t; based on our experiencer, here are some tips on how to make it better” info could be really helpful.

For now https://github.com/w3c/webcomponents/wiki/2020-Spring-Virtual-F2F would be a good place to add such info. We can copy/move it to another more-general location later.

JanMiksovsky commented 3 years ago

Seems like we can close this issue...

sideshowbarker commented 3 years ago

Seems like we can close this issue...

Yup, made it so