Skip to content

FY24 Q2 Hackathon

https://about.gitlab.com/community/hackathon/

https://www.meetup.com/gitlab-virtual-meetups/events/292094064/

Let's simplify:

  • All projects under gitlab-org and gitlab-com groups will be included
  • All contribution areas will be included
  • RSVP will not be mandatory
  • Prizes will be $75, $50 and $25 coupons for the special community shop
  • Points calculation will be taken care of by google sheets

This will make the process more efficient.

Prior to the Hackathon

Hackathon minus 4 weeks

  1. Create the Meetup.com event: https://www.meetup.com/gitlab-virtual-meetups/events/293317560/
  2. Open an issue for tracking community contributions during the Hackathon: https://gitlab.com/gitlab-org/community-relations/contributor-success/team-task/-/issues/237
  3. Add the event in the Developer Evangelism (public) calendar: https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MDZiNnMwMnV0MmVnYWhoNzVodWV1YnZraHUgY183OTMwZmNiMGM5ZTQ3ODNiZGQzZDIzODU4YWU5YWY0MzA2ZjI4ZDk3NmE0MGM4MzNmNTA3MTBjN2NiODZiYTgyQGc&tmsrc=c_7930fcb0c9e4783bdd3d23858ae9af4306f28d976a40c833f50710c7cb86ba82%40group.calendar.google.com
  4. Update the Hackathon page(s) with all the necessary information: gitlab-com/www-gitlab-com!124047 (merged)
    1. Update the dates
    2. Update the meetup links
    3. Update the counter
    4. Update the schedule
  5. Add the new Hackathon to the GitLab events page: gitlab-com/marketing/digital-experience/buyer-experience!2165 (merged).
  6. Move the previous Hackathon content to the Past Events page: gitlab-com/www-gitlab-com!124252 (merged)
  7. Open an issue in Corporate Marketing to request a social promotion on Facebook, LinkedIn, and Twitter: https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/7978
  8. Make an announcement on following channels:
    1. Forum. Consider making the topic a banner on the forum for the period leading into the event.
    2. Discord
    3. Reddit
  9. Open an issue for including the Hackathon in the upcoming montlhy newsletter.
  10. Submit a request for the GitLab bot to auto-add the Hackathon label to any community MRs during the Hackathon period
  11. Open an issue to gather input from various teams in regard to important issues for people to contribute to.
    1. Post at #what-happening-at-gitlab inviting people to add issues
    2. #tw-team
    3. #community-relations
    4. #engineering-fyi
    5. #mr-coaching
  12. Update TAMs bi-weekly call agenda with the new Hackathon details and how customers can participate (agenda doc)
  13. Start working with merchandise vendors (e.g. Boundless) to select and order Hackathon prizes?

Hackathon minus 2-3 weeks

  1. Line-up topics and speakers for tutorial sessions.
  2. Post reminders on Forum/Discord/Reddit.
  3. Create calendar events with Zoom details for each scheduled session
  4. Update the Hackathon website with the session details
  5. Update the GitLab Public Calendar with event details

Hackathon minus 1 week

  1. Post reminders on:
  2. Forum
  3. Discord
  4. Reddit
  5. Slack

During the Hackathon

  1. Announce the event kickoff on Forum/Discord/Reddit.
  2. Post recorded tutorial sessions after each session
  3. MR's
    1. Add the submitted MR's to the issue create above to track MR's.
    2. Ensure that the MR counter on the landing page is working, once the first MR has been submitted.
    3. Triage the MR's by applying labels and mentioning appropriate product managers/groups for the MR.
  4. 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).
  5. At the end of Day 1, post a wrap-up tweet with accomplishments highlighted.
  6. At the end of the event, post an event wrap-up tweet and thank the community.

After the Hackathon

  1. Post an event wrap-up on Forum/Discord/Reddit channels.
  2. Post a thank you message on #thanks Slack channel.
  3. 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.
  4. Update the Hackathon banner with the next Hackathon date on the Contribute page.
  5. 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.
  6. Post a wrap-up post on the forum.
  7. Update the GitLab Hackathon page with links to prize winners and the wrap-up blog post.
Edited by Lee Tickett