Q2'2019 GitLab Hackathon
(Enter dates for the Hackathon plus any relevant notes for the event such as new themes, prizes, etc.)
Prior to the Hackathon
Hackathon minus 4 weeks
- Promote the event & the blog post on social channels.
- Add the new event to the GitLab Hackathon page: relevant merchandise issue
- Add the new Hackathon to the GitLab events page as a "featured" event.
- Add/update the Hackathon banner on the Contribute page.
- Contact the content team to add the Hackathon to the next bi-weekly newsletter: gitlab-com/marketing/digital-marketing-programs#557 (comment 166938228)
Hackathon minus 2-3 weeks
- Line-up topics and speakers for tutorial sessions.
- Update the GitLab Hackathon page with event details such as tutorial sessions.
- Post reminders on social channels.
Hackathon minus 1 week
- Post reminders on Slack channels (e.g. #core, #mr-coaching).
- Create an issue to track MR's during the event. An example from Q4'18
- Update social channels highlighting event logistics including schedule, logistics, etc.
During the Hackathon
- Announce the event kickoff on social channels.
- Post recorded tutorial sessions on YouTube.
- Add the submitted MR's to the issue create above to track MR's.
- Triage the MR's by applying labels and mentioning appropriate product managers/groups for the MR.
- Throughout the event, monitor Gitter and other channels for questions/discussions. If necessary escalate any questions to other GitLab team members (e.g. #mr-coaching on Slack).
- At the end of Day 1, post a wrap-up tweet with accomplishments highlighted.
- At the end of the event, post an event wrap-up tweet and thank the community.
After the Hackathon
- Post an event wrap-up on social channels.
- Post a thank you message on #thanks Slack channel.
- Remove the event as a "featured" event in the events page
- Delete/update the Hackathon banner on the Contribute page.
- Give a remider to the community on the deadline for merged MR's and who they can contact if they need any assistance with MR's.
- Open an issue to annouce the prize winners and list their GitLab ID's only (no email addresses due to privacy concerns). If any of the winners want to provide a different email address (vs. what is in the commit), they can open a Service Desk issue so they can provide their emails confidentially. An example from Q3'18
- Post a wrap-up blog post (incl. prize winners).
- Update the GitLab Hackathon page with links to prize winners and the wrap-up blog post.
Suggested issues list
- First-time contributors
- Experienced contributors
- General: https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&weight=2&label_name=Accepting%20merge%20requests&milestone_title=Backlog