All Hands/Austin/electives: Difference between revisions
| Line 28: | Line 28: | ||
===Program Timeline (Revised)* === | ===Program Timeline (Revised)* === | ||
*'''Mon | *'''Mon October 2''' Announcement of Electives, including two-week window for submissions. | ||
*'''Fri | *'''Fri October 13''' Last day for submissions. | ||
*'''Mon October 16 - Fri Oct 20''' Internal Comms matches with capacity, works with session owners to consolidate overlapping/similar submissions as appropriate | |||
*'''Mon | * '''Mon October 23''' Voting begins on full list of submissions (we'll provide a link to descriptions) to gauge attendance | ||
* '''Mon | *'''Friday October 27''' Voting closes | ||
*'''Friday October | *'''Week of October 30''' Internal Comms analyzes voting results, assigns spaces | ||
*''' | *'''Mon November 6''' Final sessions posted on [https://wiki.mozilla.org/All_Hands/Austin/electives wiki somewhere] + on SCHED | ||
*'''Mon | *'''Mon November 13 - All Hands''' Presenters get coaching, prepare and promote their sessions. | ||
*''' | |||
===Submission Guidelines=== | ===Submission Guidelines=== | ||
Revision as of 20:17, 25 September 2017
Electives in Austin
Overview
Electives are blocks of time during our All Hands for programming open to any attendee to lead or attend. Here's when they'll happen in Austin:
Wednesday, December 13
- 1:00pm - 2:30pm
- 2:45pm - 3:45pm
- 4:00pm - 5:00pm
Thursday, December 14
- 3:00pm - 4:00pm
- 4:15pm - 5:30pm
What's the goal?
As a distributed organization it can be tough to get a handle on what’s happening, or know how to help out. Electives provide a unique opportunity for teams and individuals to share projects, best practices and other skills and knowledge beyond their own teams.
In Hawaii (the last time we had electives), 96% of all folks who attended an elective said they'd recommend it to a peer. Some color commentary:
- “It was useful to share information on things that work, things that don't work, and the science to back these assertions up."
- "I learned about resources I wasn't aware of. The panel framed security issues in a way that was really helpful towards figuring out how I should be dealing with passwords, sensitive data, and security practices."
- "Awesome to hear we are doing real experiments. I want to help."
- "I now have a better understanding of Mozilla financials and how we can contribute to increasing revenue and reducing expenses."
- "This kind of tech exchange should be 80% of the work week."
How it works
- Propose your elective idea here by Friday Oct 13.
- Vote for your top submissions Mon Oct 23 - Fri Oct 27 (helps us assign rooms better)
- Schedule which electives you plan to attend after the final list is posted November 6.
Program Timeline (Revised)*
- Mon October 2 Announcement of Electives, including two-week window for submissions.
- Fri October 13 Last day for submissions.
- Mon October 16 - Fri Oct 20 Internal Comms matches with capacity, works with session owners to consolidate overlapping/similar submissions as appropriate
- Mon October 23 Voting begins on full list of submissions (we'll provide a link to descriptions) to gauge attendance
- Friday October 27 Voting closes
- Week of October 30 Internal Comms analyzes voting results, assigns spaces
- Mon November 6 Final sessions posted on wiki somewhere + on SCHED
- Mon November 13 - All Hands Presenters get coaching, prepare and promote their sessions.
Submission Guidelines
Tracks. To help everyone understand how and where your session fits at Mozilla, we ask folks submitting ideas for electives to ensure they fit in one of the following 3 categories (with examples):
- People. e.g. interviewing & hiring best practices, public speaking, community best practices
- Product. e.g. user-facing product and prototype demos and updates, design and UX experiments, approaches to data and experimentation
- Technology. e.g. web-enabling technologies and infrastructure such as Virtual Reality, WebGL, RUST, Servo.
Be complete in your description. People cannot attend all electives, so be sure to convey why yours is worth attending. Here is a recommended outline to help you include enough information in your session description to draw people in:
- What will happen during the session
- What attendees will learn / take away
- Who should attend e.g. ‘ideal participant’ has X skills, interests, knowledge
- What track it supports and why
Presentation Tips
Duration. We encourage you to use one hour as we have limited facility space and hope to accommodate as many electives as possible. If you believe your session absolutely requires two hours, we'll assess whether we can slot it.
Focus. Folks will likely take away 1-2 key points or practices from your session; use the time to go deep vs. wide.
Interactivity. Learning by doing is far more effective than learning by listening. This doc has some tips and practical ways for session owners to create a more engaging experience.