Organizers To Do List: Difference between revisions

From Mozilla Internet as a Public Good Event
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
This is the current list of tasks for the IPG organizers.
This is the current list of tasks for the IPG organizers.
=== Travel ===


* <strike>Send travel and accommodations email to participants. Include a note to remind participants that some limited amount of sponsorship is available, if needed.</strike> (Zak)
* <strike>Send travel and accommodations email to participants. Include a note to remind participants that some limited amount of sponsorship is available, if needed.</strike> (Zak)
* <strike>Organize travel and acc. for participants that MoFo is sponsoring</strike> (Zak)
* <strike>Organize travel and acc. for participants that MoFo is sponsoring</strike> (Zak)


* Encourage participants to get an early start on the symposium. Drop them a mail that encourages them to:
* Catch up with those who don't respond to our organization emails
** write up a few brief notes on their interest in the symposium
 
** adopt a session as coordinator
 
** present an edge case
=== Agenda and Activities ===


* Finalize schedule (Zak)
* Finalize schedule (Zak)
** <strike>Send draft to rest of team</strike> (Zak)
** <strike>Send draft to rest of team</strike> (Zak)
* <strike>Solicit edge case presenters (after schedule is finalized)</strike> (Team)


* Draft guidelines for presenting an edge case. Such as:
* Draft guidelines for presenting an edge case. Such as:
** 5 minutes or less (like a lightning talk)
** 5 minutes or less (like a lightning talk)
** ...
** ...
* Solicit edge case presenters (after schedule is finalized) (Team)
=== Orientation ===
* Write participants to encourage them to get an early start on the symposium. Drop them a mail that encourages them to:
** write up a few brief notes on their interest in the symposium
** adopt a session as coordinator
** present an edge case


* Send out an orientation email for participants. Include:
* Send out an orientation email for participants. Include:
Line 26: Line 36:
** a request to blog about the event before they attend
** a request to blog about the event before they attend
** suggestions on how to get the best from the event
** suggestions on how to get the best from the event
** notes which parts of the event are public and which are private private aspects of the event. In other words, let people know to what extent their comments, presentations, etc., will be made public, and to what extent they can engage in more private off-the-record discussions.


* Meaningful outcomes could include:
** blogging about the event
** having participants host or sponsor an IPG in another area
** publishing the discussions or conclusions from the event
** ...


* Misc. Issues:
=== General Logistics ===
** we need to make sure to confirm who can and cannot attend
* Get all participants wiki accounts
** we should also draft a followup message for the event
* Find delivery joints
* Decide if the evening breakouts are at the HBS or at the Charles
 
=== Event Materials ===


* <strike>Create draft badges</strike> (Zak)
* <strike>Create draft badges</strike> (Zak)
* Make final badges
=== Followup ===
* we should draft a followup message for the event

Revision as of 03:08, 10 July 2007

This is the current list of tasks for the IPG organizers.

Travel

  • Send travel and accommodations email to participants. Include a note to remind participants that some limited amount of sponsorship is available, if needed. (Zak)
  • Organize travel and acc. for participants that MoFo is sponsoring (Zak)
  • Catch up with those who don't respond to our organization emails


Agenda and Activities

  • Finalize schedule (Zak)
    • Send draft to rest of team (Zak)
  • Draft guidelines for presenting an edge case. Such as:
    • 5 minutes or less (like a lightning talk)
    • ...
  • Solicit edge case presenters (after schedule is finalized) (Team)


Orientation

  • Write participants to encourage them to get an early start on the symposium. Drop them a mail that encourages them to:
    • write up a few brief notes on their interest in the symposium
    • adopt a session as coordinator
    • present an edge case
  • Send out an orientation email for participants. Include:
    • schedule and a list of activities at the symposium
    • a set of questions to get people thinking about the issues at the symposium
    • maps and travel directions
    • the outcomes we hope to have from the event
    • a request for ideas on what tangible things the event could lead to
    • a request to blog about the event before they attend
    • suggestions on how to get the best from the event
    • notes which parts of the event are public and which are private private aspects of the event. In other words, let people know to what extent their comments, presentations, etc., will be made public, and to what extent they can engage in more private off-the-record discussions.


General Logistics

  • Get all participants wiki accounts
  • Find delivery joints
  • Decide if the evening breakouts are at the HBS or at the Charles

Event Materials

  • Create draft badges (Zak)
  • Make final badges

Followup

  • we should draft a followup message for the event