canmove, Confirmed users
1,953
edits
MDN/Hack on MDN/How to guide: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 61: | Line 61: | ||
===Planning the work=== | ===Planning the work=== | ||
Ahead of the event, once you know the topical focus, you can collect tasks that can attendees can work on during the sprint. There may be generated lists that can be helpful, such as lists of pages with a particular [https://developer.mozilla.org/en-US/docs/tag/Web tag] or [https://developer.mozilla.org/en-US/docs/needs-review/editorial flag], or bug reports, etc. Or you might collect items that need to be worked on into a spreadsheet for tracking purposes. | Ahead of the event, once you know the topical focus, you can collect tasks that can attendees can work on during the sprint. There may be generated lists that can be helpful, such as lists of pages with a particular [https://developer.mozilla.org/en-US/docs/tag/Web tag] or [https://developer.mozilla.org/en-US/docs/needs-review/editorial flag], or bug reports, etc. Or you might collect items that need to be worked on into a spreadsheet for tracking purposes. | ||
===At the start=== | |||
Be sure to make an introduction at the start of the event. This need not be formal, but be sure to introduce leaders of the event, point out logistics like bathrooms and emergency exits, and mention the Code of Conduct for the event. (Mozilla-associated events are governed by Mozilla's [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]; the shortlink is https://mzl.la/cpg ). Have attendees briefly introduce themselves and state what they're interested in working on, so you can help them find others to collaborate with. | |||
===Tracking tasks=== | ===Tracking tasks=== | ||