MDN/Get involved/Events/HackOnMDN: Difference between revisions
mNo edit summary |
|||
| Line 16: | Line 16: | ||
Give us an idea of what you would want to work on over the weekend. | Give us an idea of what you would want to work on over the weekend. | ||
=How | =How the Hack on MDN Weekend will work= | ||
Friday morning, anyone with an idea they want to work on with the team will make a 5-minute "pitch" about that idea. The idea can be a new feature, improvements to current features, new content, improvements to content, new wiki code, or pretty much anything else. | Friday morning, anyone with an idea they want to work on with the team will make a 5-minute "pitch" about that idea. The idea can be a new feature, improvements to current features, new content, improvements to content, new wiki code, or pretty much anything else. | ||
| Line 26: | Line 26: | ||
* the pitch will be recorded in an etherpad & on a card for the "idea board" | * the pitch will be recorded in an etherpad & on a card for the "idea board" | ||
After all pitches have been made (you don't need to be present to pitch an idea), teams will form to work on the ideas. You can work on 1 idea at a time. Work on ideas may finish before the end of the three days - in that case, the team will pick a new idea (with the same or different members) and work on that. | After all pitches have been made (you don't need to be present to pitch an idea), teams will form to work on the ideas. You can work on 1 idea at a time. Work on ideas may finish before the end of the three days - in that case, the team will pick a new idea (with the same or different members) and work on that. | ||
=Schedule= | =Schedule= | ||
Revision as of 19:12, 14 January 2015
Goal
To do actual, tangible work: written idea proposals, designs/mockups, new docs, code, and/or new tools or processes. The goal is to produce something tangible at the end of the three days. We want anyone and everyone to be able to participate, share their idea/feature/product, and work on it with others.
How to Attend
We welcome all contributors to MDN - both volunteer and paid staff, old timers and new! However, to keep the sessions as productive as possible, we are limiting the number of attendees. Both contributors and paid staff must apply to attend. The application form is available on Google Docs
For the March 2015 Hack on MDN Weekend, the application period will be from January 14 to January 20th. We will notify chosen attendees on January 22nd at the latest.
We’ll make sure to have virtual participation as an option as well. Details will be available here soon.
For volunteers: Mozilla will cover your travel costs to attend the event. Paid staff, if possible, we prefer your department/organization to cover the cost of travel, but we should be able to cover from the MDN budget if necessary.
What do you need to do to attend? You need an MDN profile (this shows your activity on MDN) Give us an idea of what you would want to work on over the weekend.
How the Hack on MDN Weekend will work
Friday morning, anyone with an idea they want to work on with the team will make a 5-minute "pitch" about that idea. The idea can be a new feature, improvements to current features, new content, improvements to content, new wiki code, or pretty much anything else.
a pitch must include:
- the idea
- what will be produced when you are finished (articles, code, requirements doc, etc.)
- what kind of help you need (User experience design, coding, writing, etc)
- the pitch will be recorded in an etherpad & on a card for the "idea board"
After all pitches have been made (you don't need to be present to pitch an idea), teams will form to work on the ideas. You can work on 1 idea at a time. Work on ideas may finish before the end of the three days - in that case, the team will pick a new idea (with the same or different members) and work on that.
Schedule
- Thursday:
- Travel (everyone should plan to arrive this day/evening)
- 18:30 (6:30 pm): happy hour/dinner
- Friday:
- 9:15: Arrive at the office/venue
- 9:30: Welcome & Introductions - START VIDYO SESSION
- 10:00: Design our Alliance
- 10:30: Review goals
- 11:00: Pitch ideas, form teams (minimum of 2 people), determine vidyo for remote participants. END MORNING VIDYO SESSION
- 12:30: lunch
- 13:00: Teams meet, set team goals & working agreements
- 14:00 - 18:00 - make stuff
- small group dinner
- Saturday, March 8
- 9:00: Lightning check in (5 min per project)
- 9:30: Make stuff
- 12:30: Lunch
- 13:15: Lightning check in (5 min per project)
- 13:30 - 18:00: make stuff
- Hacking/pizza/beer
- Sunday, March 9
- 9:00: Lightning check in (5 min per project)
- 9:30: Make stuff
- 12:30: Lunch
- 16:00: Present results VIDYO SESSION
- After party & dinner
- Monday
- Travel home, hopefully exhausted