December 2023 GitLab Hackathon
https://about.gitlab.com/community/hackathon/
https://www.meetup.com/gitlab-virtual-meetups/events/296831460/
Let's simplify:
- All projects under
gitlab-org
andgitlab-com
groups will be included - All contribution areas will be included
- RSVP will not be mandatory
- Prizes will be tier 1, tier 2 and tier 3 coupons for the special community shop
- Points calculation will be taken care of by the merge request leaderboard: https://gitlab-community.gitlab.io/community-projects/merge-request-leaderboard/?&createdAfter=2023-12-11&createdBefore=2023-12-18&mergedBefore=2024-01-18&label=Hackathon
This will make the process more efficient.
Prior to the Hackathon
Hackathon minus 4 weeks
-
Create the Meetup.com event: https://www.meetup.com/gitlab-virtual-meetups/events/296831460/ -
Open an issue for tracking community contributions during the Hackathon: #353 (closed) -
Add the event in the Developer Evangelism (public) calendar: https://calendar.google.com/calendar/u/0/r/eventedit/MWRhc2o4dmh1a21rc3ZvNDAyY3Q4NjV0MmYgY183OTMwZmNiMGM5ZTQ3ODNiZGQzZDIzODU4YWU5YWY0MzA2ZjI4ZDk3NmE0MGM4MzNmNTA3MTBjN2NiODZiYTgyQGc -
Update the Hackathon page(s) with all the necessary information: gitlab-com/www-gitlab-com!130520 (merged) -
Move the previous Hackathon content to the Past Events page
-
-
Add the new Hackathon to the GitLab events page: gitlab-com/marketing/digital-experience/buyer-experience!3110 (merged) -
Open an issue in Corporate Marketing using the social-general-request issue template on Facebook, LinkedIn, and Twitter: https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/8480 -
Make an announcement on following channels: -
Forum. Consider making the topic a banner on the forum for the period leading into the event. https://forum.gitlab.com/t/announcement-gitlab-december-2023-hackathon/95055 -
Discord -
Reddit https://www.reddit.com/r/gitlab/comments/17qaf9d/announcement_gitlab_december_2023_hackathon/
-
-
Open an issue for including the Hackathon in the upcoming montlhy newsletter. -
Request inclusion in the community newsletter issue -
Update triage-ops / the @gitLab-bot
to auto-add the Hackathon label to any community MRs during the Hackathon period: gitlab-org/quality/triage-ops!2485 (merged) -
Open an issue to gather input from various teams in regard to important issues for people to contribute to. -
Post at #what-happening-at-gitlab inviting people to add issues -
#tw-team -
#developer-relations -
#engineering-fyi -
#mr-coaching
-
-
Update TAMs bi-weekly call agenda with the new Hackathon details and how customers can participate (agenda doc)
Hackathon minus 2-3 weeks
-
Line-up topics and speakers for tutorial sessions. -
Post reminders on Forum/Discord/Reddit. -
Create calendar events with Zoom details for each scheduled session -
Update the Hackathon website with the session details -
Update the GitLab Public Calendar with event details
Hackathon minus 1 week
During the Hackathon
-
Announce the event kickoff on Forum/Discord/Reddit -
Post recorded tutorial sessions after each session -
MR's -
Add the submitted MR's to the issue create above to track MR's. -
Ensure that the MR counter on the landing page is working, once the first MR has been submitted. -
Triage the MR's by applying labels and mentioning appropriate product managers/groups for the MR.
-
-
Throughout the event, monitor Discord 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 Forum/Discord/Reddit channels. -
Post a thank you message on #thanks Slack channel. -
Post a thank you message reminding of the cut-off date on the tracking issue (and CC all participants using the copy usernames button from the merge request leaderboard). -
Post a follow-up message a few weeks later (and CC all participants with un-merged MRs).
-
-
Select the next Hackathon dates and update the dates and countdown clock on the GitLab Hackathon page. The new hackthon dates should be set in the code.
NOTE: Try to avoid December as team members are busy trying to wrap up before the holiday period. -
Give a reminder to the community on the deadline for merged MR's and who they can contact if they need any assistance with MR's. -
Update the GitLab Hackathon page with links to prize winners and the wrap-up blog post. -
Generate "swag issues" for participants. -
Award GitLab achievements: https://gitlab.com/-/graphql-explorer mutation m { achievementsAward(input: { userId: "gid://gitlab/User/XXX" achievementId: "gid://gitlab/Achievements::Achievement/54" }) { errors } }
Edited by Lee Tickett