Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
planning:hosting [2015/02/09 17:05] – Add line about veg tabatkinsplanning:hosting [2024/02/13 09:17] (current) – removing telephone requirement, we have not used that for a while astearns
Line 4: Line 4:
  
 To host a CSS meeting, you MUST provide: To host a CSS meeting, you MUST provide:
-  * A meeting room where the group can meet, without needing to sign any NDA or other agreement. +  * A meeting room where the group can meet, without needing to sign any NDA or other agreement. Meetings are typically 3 days (4 days if co-hosting a [[https://wiki.css-houdini.org/ | Houdini]] meeting), and a room is needed the entire time. It SHOULD be the same room every day
-  * Chairs for people to sit in and tables for them to put their laptops at (which SHOULD be arranged in a U shape) such that the participants can easily hear each other speak+  * Chairs for people to sit in and tables for them to put their laptops at (which SHOULD be arranged in a U shape) such that the participants can easily hear each other speak. Attendance may vary, but is typically around 30 people.
   * electricity for everybody's laptops (probably assume greater than 1 device per person average)   * electricity for everybody's laptops (probably assume greater than 1 device per person average)
   * network connectivity that allows at least access to Web, IRC, and email, and preferably also skype/VoIP   * network connectivity that allows at least access to Web, IRC, and email, and preferably also skype/VoIP
   * A projection screen easily visible from all the chairs, and preferably to which anyone in any of the chairs can project from their seats   * A projection screen easily visible from all the chairs, and preferably to which anyone in any of the chairs can project from their seats
   * Either a whiteboard or flipchart that people can draw on, also visible from all the seats.   * Either a whiteboard or flipchart that people can draw on, also visible from all the seats.
-  * Telephone access, preferably a multi-microphone conference phone, tested in advance to make sure audio works in both directions (is this a MUST or a SHOULD?) +  * All of the above MUST be ready to go by 9am on each meeting day, and must remain available until the end of the meeting at 6pm. 
- +  * The meeting room SHOULD be available half an hour before the meeting start so that people can arrive, and SHOULD remain available for at least 30 minutes to an hour after the likely end of the meeting, both so that the meeting can continue a few minutes longer if needed, and so that participants can linger to finish ongoing conversations, make dinner plans, etc. 
-All of the above should be ready to go by 9am on each meeting day.+  * instructions for how to get to the meeting location
  
 You also SHOULD provide: You also SHOULD provide:
Line 18: Line 18:
   * natural light in the meeting room (which helps people who are jetlagged)   * natural light in the meeting room (which helps people who are jetlagged)
   * a meeting space that does not permit smoking indoors   * a meeting space that does not permit smoking indoors
 +  * A secondary meeting room, to enable the group to temporarily split and discuss in parallel topics which only interest a subset of the members.
 +  * On-premise or nearby child care during meeting hours
 +
 +You MAY also:
 +  * Invite everybody for dinner once during the F2F. This is often done and appreciated, but is not a requirement and members do understand that you may have budget constraints.
 +  * Organize a side event to meet with local web developers. If you do so, you SHOULD inform the CSSWG members well in advance, as they may otherwise have conflicting travel plans.
 +
 
planning/hosting.1423530326.txt.gz · Last modified: 2015/02/09 17:05 by tabatkins
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki