comp615
commented
6 years ago As mentioned in #3, I think getting the browser's perspectives on how a long-term dev-browser relationship might look could inform this. For instance, Chrome may have PR constraints and not be able to share their plans before Chrome Dev Summit. If so, then we could not productively have an honest conversation about future roadmaps; maybe it should occurs after that? Or maybe they'd be open to sharing before in a small group setting. Worth checking. (Maybe you can tag them on #3)
To location, I think SF is a strong choice as most of the vendors are on the west-coast US and if we want to rally around them, making it easy might be helpful...again just depends on the focus of the event.
webmaxru
poshaughnessy
gavmck
docluv
Sneiwert
christianliebel
I propose (please, comment on all the points):
Form One-day, single track event finishing by the round table with the reps from all browser vendors. The possible alternative (if we have too much really useful content to share) is two tracks event:
Date October 25 The possible alternatives: October 17, 18, 19, 24, 26 October is traditionally full-packed by the web dev events, so we'll never find 100% free date. Let's choose the best trade-off.
Reasoning Autumn 2018 is the perfect moment for the gathering:
Location London
Reasoning Many folks from browsers devrel teams are located there. At least from Google, Mozilla, Samsung Internet. This will be easier to organize the logistics.
Organizing team We need a team of core organizers and contributors. I propose to have the team as volunteers (and I nominate myself for being a part of the team) and hire some event agency to help us with the basic tasks. Of course, we'll need some sponsors and an organization (registered as not-for-profit) to operate on behalf of.
We could hold all the public discussions at this repo and all the private ones on PWA slack in the #pwaconf private group (it's there for a long time).