MeetingsAndWorkshops
Meetings and Workshops
Extensible Web Summit wasn't a W3C event
Publicly announced with 2 weeks' notice, not under the guise of a Workshop, not directly affiliated with the TAG.
Goal: a constructive, rough-consensus-driven environment
Agile vs. Inclusive is difficult balance.
- How do we make the process agile?
- Reality: implementers are more equal than others.
- Reality: more people in the room means lower velocity.
- But we want to be inclusive. (See goal.)
- Remote participation is critical.
Meetings - CG, WG, AB, TAG - and Workshops - Proposal
- Announcements of primarily face-to-face events should give 8 weeks notice for people to arrange attending, in the absence of a pressing reason for shorter notice.
- This is particularly important for meetings aiming to make decisions, such as future directions for work, or resolving issues with a spec. For events which are e.g. just generating tests, or explaining work that is happening, it is still very helpful.
- Should the default mode for meetings be "distributed"? This can ensure that people can effectively participate without needing to arrange travel, visas, etc., but it doesn't resolve the issue that people in different timezones are likely to have a poorer experience of participation?
- For less than 8-week notice, the following is important
- remote participation is enabled - "is topic x worth traveling half-way around the world"
- minutes are taken (and live on IRC)
- it is understood that binding decisions cannot be made in realtime without a full, announced WG meeting.
You still need
- Hosting group to approve use of attribution, and publicize the event appropriately
- Announcement on appropriate forum (WG list for WG meetings, add to W3C calendar for broader-focused events)
- Host to supply logistics (space, food, whatever)
- Minuting
- Remote participation - from 1-way telephone to livestreaming/WebRTC participation.