-
Notifications
You must be signed in to change notification settings - Fork 12
Policies
ianbjacobs edited this page Dec 18, 2023
·
61 revisions
Meeting registrants (e.g., TPAC registrants) can propose breakout sessions. It is ok for people who plan to register (but have not yet done so) to propose a session.
Sessions do not require formal approval; W3C breakout planners endeavor to schedule all proposed sessions. See more below on scheduling and room assignments.
- Sessions are intended to be for community discussion of topics, whether existing or new.
- Sessions should not be used for group meetings. For example, a Working Group should not use a breakout session to have another hour for group discussion. Similarly, a Community Group should not use a breakout session for a Community Group meeting.
Each event Web site has pages devoted to breakout session participation policies; please consult that page first.
Note also:
- By default, sessions are open to non-registrants (but all participants must have a W3C account).
- It is preferable but not required that the session chair participate in person (when a session is hybrid).
- There is no requirement that W3C staff participate in a breakout session.
- Code of Ethics and Professional Conduct
- Antitrust and Competition Guidance
- For TPAC, see also the health rules specific to that year's meeting.
W3C breakout planners observe this order of preference when scheduling:
- Any reserved tracks (e.g., governance for TPAC 2023 starting with AC open sessions)
- Meeting sponsor proposals received before the proposal deadline.
- Proposals received before the proposal deadline and indicated timing constraints.
- Proposals received before the proposal deadline without timing constraints.
- Other proposals. These are considered when there are remaining slots, and we will do our best to schedule them based on the remaining slots.
- Avoid too many sessions in parallel; instead create more slots (e.g., 60- and 30-minute slots).
- Seek a "best fit" between sessions and room, given session description attendance estimates and other information.
- Avoid scheduling conflicts between related sessions (e.g., by requesting two very similar sessions to consider merging into a single session).
- Identify and communicate thematically related sessions (e.g., as "tracks") to make it easier for attendees to choose which sessions to join. Endeavor to schedule these in the same meeting space.
- Each session chair is responsible for ensuring that session highlights (at least) are captured in (at least) text.
- Each session chair is responsible for ensuring there are minutes. The W3C breakout planners will work with session chairs to ensure that the session descriptions include a link to the minutes.
- When a meeting record is not available on w3.org, W3C may create a copy on w3.org for persistence.
Some participants cannot participate in sessions that are recorded, or prefer not to. As a result, we have the following policies regarding video or audio recording of sessions:
- Session Chairs may only record presenters, and only with their permission.
- Session Chairs should not record presenters if people at the meeting who wish to participate (either in person or remotely) express concerns.
- Session discussion must not be recorded.
- To make video and audio recordings accessible (see Making Audio and Video Media Accessible), session Chairs should use recording facilities provided by Zoom, which include automatic generation of captions. After the event, W3C breakout planners will publish video and audio recordings on w3.org (essentially "as-is") with captions and a transcript. W3C breakout planners may reach out to Session Chairs to help improve the quality of the captions. If Chairs decide to use another recording mechanism, they must provide the video and audio recordings, with captions, to W3C breakout planners.