Confirmed users
660
edits
Summit2013WorkingGroup: Difference between revisions
Jump to navigation
Jump to search
→Experience pods
| (4 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
The SWGs and their pods will help the rest of the organization know and understand the Summit 2013 plan, process, and timeline. This group will be offered to the organization as Summit points of contact available to answer or direct questions, share progress, manage feedback and input from Mozillians and act as a reference point for those wanting to help. | The SWGs and their pods will help the rest of the organization know and understand the Summit 2013 plan, process, and timeline. This group will be offered to the organization as Summit points of contact available to answer or direct questions, share progress, manage feedback and input from Mozillians and act as a reference point for those wanting to help. | ||
==Process== | |||
We have made some initial nominations for lead positions on the working groups below. The Steering Committee is reviewing these currently and we should have final approval on them by April 3rd. From there, we'll invite our nominees to the groups. This process should be complete and names posted by April 30th (hopefully sooner). | |||
Once we have leads determined, those folks will become points of intake for anyone who's excited to participate and join a pod. | |||
==Time Commitment== | ==Time Commitment== | ||
| Line 26: | Line 32: | ||
*'''Memories''': Works as a consultant to our event vendor to help with the application of our branding and other experiences (helps to make sure it all feels “Mozilla”). | *'''Memories''': Works as a consultant to our event vendor to help with the application of our branding and other experiences (helps to make sure it all feels “Mozilla”). | ||
*'''Attendance''': Determines our approach and process for volunteer invitations (how we decide who goes where). Consults with tools lead, Webdev + event vendor to implement the registration process. | *'''Attendance''' [Pierros + William Q]: Determines our approach and process for volunteer invitations (how we decide who goes where). Consults with tools lead, Webdev + event vendor to implement the registration process. | ||
*'''Executives + BOD''': In partnership with the whole EA group, oversees the care and feeding of Mozilla executives and participating BOD Members. Coordinates attendance (who goes where) and travel plans provides ad hoc support for this group. Works with event planner + contractor to create and distribute Executive Guides to the Summit. | *'''Executives + BOD''': In partnership with the whole EA group, oversees the care and feeding of Mozilla executives and participating BOD Members. Coordinates attendance (who goes where) and travel plans provides ad hoc support for this group. Works with event planner + contractor to create and distribute Executive Guides to the Summit. | ||