Skip to content

October 2024 Hackathon

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

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

Let's simplify:

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/303525623
    1. Publish straight away if happy or ask someone to VET it?
    2. Announce once hackathon page is updated etc?
  2. Open an issue for tracking community contributions during the Hackathon: #624 (closed)
  3. Add the event in the Developer Advocacy (public) calendar: https://calendar.google.com/calendar/u/0/r/eventedit/NG1ma242ZzJvMW52ZjR0NzVwN2NwcmNnZTUgY183OTMwZmNiMGM5ZTQ3ODNiZGQzZDIzODU4YWU5YWY0MzA2ZjI4ZDk3NmE0MGM4MzNmNTA3MTBjN2NiODZiYTgyQGc
  4. Update the Hackathon page(s) with all the necessary information: gitlab-com/www-gitlab-com!136298 (merged)
    1. Confirm countdown correct, meetup link correct, and qualifying merge requests links to the correct issue
  5. Move the previous Hackathon content to the Past Events page
  6. Create an event in Discord: https://discord.gg/gitlab?event=1286335284161679382
  7. Update the Hackathon event date on the GitLab events page: https://app.contentful.com/spaces/xz1dnu24egyd/entries/1QSwerZqw5vMbxJEHrSdT1?focusedField=internalName
    1. Check the event is listed/published
  8. 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/8875
    1. Check in whether the issue has been actioned
  9. Make an announcement on following channels:
    1. Forum. Consider making the topic a banner on the forum for the period leading into the event. @sugaroverflow https://forum.gitlab.com/t/our-next-gitlab-hackathon-x-hacktoberfest-starts-on-october-21/115365
    2. Discord
    3. Reddit @sugaroverflow https://www.reddit.com/r/gitlab/comments/1g4nr6x/our_next_gitlab_hackathon_x_hacktoberfest_starts
  10. Open an issue for including the Hackathon in the upcoming monthly newsletter: https://gitlab.com/gitlab-com/internal-communications/newsletter/-/issues/71#note_2122194313 @sugaroverflow
  11. Request inclusion in the community newsletter issue
  12. 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!3034 (merged)
  13. 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. #developer-relations
    4. #engineering-fyi
    5. #mr-coaching
  14. Update TAMs bi-weekly call agenda with the new Hackathon details and how customers can participate (agenda doc)

New for next time:

  1. Contact @janasenap to arrange e-mail outreach to all community program members
  2. Connect with @vkarnes to tie up with product design: image

Hackathon minus 2-3 weeks

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

Hackathon minus 1 week

  1. Post reminders on:
    1. Forum @sugaroverflow - made topic global banner
    2. Discord
    3. Reddit @sugaroverflow - made topic sticky on subreddit
    4. Slack

During the Hackathon

  1. Announce the event kickoff on Slack/Discord.
  2. Announce the event kickoff on Reddit/Forum.@sugaroverflow
  3. Post recorded tutorial sessions after each session
  4. 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.
  5. 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).
  6. At the end of Day 1, post a wrap-up tweet with accomplishments highlighted.
  7. 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/Reddit channels. @sugaroverflow can you take care of this? I'll share the wrap up message as soon as I write it

  2. Post an event wrap-up on Discord.

  3. Post a thank you message on #thanks Slack channel.

  4. 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).

    1. Post a follow-up message a few weeks later (and CC all participants with un-merged MRs).

  5. 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.

  6. /clone this issue to create the next one...

    1. Update the title
    2. Uncheck all the boxes

  7. 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.

  8. Update the GitLab Hackathon page with links to prize winners and the wrap-up blog post.

  9. Generate "swag issues" for participants.

  10. 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 Arianna Haradon