canmove, Confirmed users
1,953
edits
MDN/Get involved/Event Guidelines: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 99: | Line 99: | ||
* Prizes for best contribution | * Prizes for best contribution | ||
* Dashboard to show progress (see, for example, http://hackdash.org/ , Trello) | * Dashboard to show progress (see, for example, http://hackdash.org/ , Trello) | ||
== Best practices == | |||
The ideas below are not requirements for holding an event, but have been helpful for other event organizers in the past. | |||
* Advertise your event: | |||
** At least a month in advance with regular reminders | |||
** Through social media as well as offline means | |||
** Be active and relentless, the more the better | |||
* The day of the event, make it visible and make sure attendees will have no difficulty to find the place and join the party. | |||
* Provide a way to contact the organizers. | |||
* Possibly schedule the event in connection to a bigger event, such as a conference, especially if the conference has hack days or workshop days. Publicize in advance so that people traveling to the conference know to allow extra days. | |||
* If you have shortage of swags, give it only to people who end up contributing. Give out swag at the END of the event. | |||
* If the event is not at an organization that can provide space (e.g., college or university), look for meeting space at: libraries, co-working spaces, friendly tech companies, schools, churches, bars; wherever you have contacts. Be sure that infrastructure requirements can be met. | |||
* Define skill requirements for participants. People won't always meet them, but at least you will set expectations. | |||
** [Awareness] None | |||
** [doc sprint] Fluency in English; some familarity with Web development | |||
** [code sprint] Familiarity with HTML/CSS/JavaScript/Python development | |||
** [localization] some familarity with Web development. Good grasp of local language. | |||
* Good durations for event formats: | |||
** Code sprint: ~3 to 24 hours (preferably overnight); possibly have a shorter session for environment installs, the evening before the main sprint. | |||
** Doc sprint: ~2 to 6 hours (x multiple days) | |||
** Localization sprint: same as Doc sprint | |||
** Introduction/Awareness: ~15 minutes to ~2 hours. | |||
* Add a hard stop for people joining the event. If someone shows up late, they can't join. It's too much of a distraction for everybody else. | |||
* Plan potential tasks for people to work on, in case they don't have ideas of their own. | |||
** [doc sprints] editorial reviews, tagging, clean-up | |||
** [localization] prioritized list of pages to translate | |||
** [code sprints] prioritized list of bugs or features | |||