Joining in

The Hackathon is a virtual event open to anyone who is interested in contributing code, documentation, translations, UX designs and more to GitLab. By participating in GitLab's Hackathon, you have the opportunity to work on issues that matter to you and advance your skills/experience while joining a global, diverse and inclusive team of contributors and GitLab team members.
For this Hackathon, we are introducing the following contribution areas: Website, Security, Front-end, Back-end, Documentation. Prizes are awarded to participants for having Merge Requests (MRs) merged that contribute to the issues/epics linked below on each contribution area.

To get started:

Prior the Hackathon

  1. Block the dates on your calendar, or subscribe to the GitLab Developer Evangelism calendar that includes the Hackathon dates and calls.
  2. Identify an issue (or more) and leave a comment indicating your interest in working on this/these. That way it's less likely for multiple people to be working on the same issue.

During the Hackathon

  1. Join the sessions to find more about the hackathon or watch the recording that will be posted afterwards.
  2. In case you don't want to work on the issues described in the contribute area below:
    - An easy way to get started for first timers is contributing to documentation. Check out the curated documentation issues which are welcoming contributions. Don't pick more than three documentation issues at once to allow other members of the community to contribute as well.
    - To get started with code, check out the curated list of issues to contribute to, based on the project you are interested in contributing to.
    - Check out the Contribute page for additional ways of contributing.
  3. Leave a comment on the issue(s) you are working on. For help, you can ask directly in the issue or at the contributors channel.

Issues/Epics to contribute to

Contribution Area Guides Qualifying (for 5 points) Issues
Security Contributing to GitLab guide Qualifying issues
Front-end Frontend Development Guidelines
- Design and User Interface Changes guide
- UX-related Issues
- Frontend-related Issues
Back-end Contributing to GitLab guide
- GitLab's Architecture
- GitLab Agent for Kubernetes
- Stage: Package
- Group: Respond
- Group: Optimize
- Group: Source Code
- Group: Editor
- Group: Import
- Group: Pipeline execution
- Group: Release
Technical Writing Contributing to documentation Documentation issues
Website, Handbook You can contribute to any page, by clicking "Edit in Web IDE" located in the footer of the page. Although there is not a specific list of issues to contribute to, we encourage Hackathon participants to explore the website for typos, broken links and outdated information.

Hackathon Prizes

We are excited to offer the following categories of prizes for this Hackathon per each contribution area.

All qualifying MRs must be submitted between August 2nd 12:00 UTC & August 9th 12:00 UTC and be merged by September 15th at 23:00 UTC.

Categories Eligibility Prizes Description
Grand Prize Individual(s) with the most points gathered (awarded on each contribution area) Grand prize A $100 giftcard for our swag shop
Second Place Individual(s) with the second most points gathered (awarded on each contribution area) Second prize Second Place prize will be replaced with equal value items due to our branding update.
Merged MR Everyone with an MR merged Merged MRs Participation prize will be replaced with equal value items due to our branding update.

Hackathon Tutorials & office hour sessions

Tutorial sessions during the Hackathon help you get kickstarted with contributing and to learn more about GitLab development. More sessions/speakers may be added as they are confirmed.

Date Time in UTC
(click for local time)
Topic Session Speakers
August 2nd 14:30 - 15:00, Add it to your calendar Hackathon Kickoff - Learn all about our new Hackathon format, and get ready to start contributing Zoom link to Join. Christos Bacharakis (@cbacharakis)
August 4th 14:30 - 15:00, Add it to your calendar Office hour call - Discuss anything related to the Hackathon or GitLab in general Zoom link to Join. Christos Bacharakis (@cbacharakis)
August 9th 14:30 - 15:00, Add it to your calendar Hackathon Wrap-up call - The Hackathon is over, what's next?! Zoom link to Join. Christos Bacharakis (@cbacharakis)

If you miss any of the sessions, you will find the recordings in the Hackathon Playlist.

Getting help

For communications during the Hackathon, we will use the GitLab Contributors room in Gitter. This is a channel for community-related discussions and for community members to help each other as people have questions when contributing to GitLab.

It's open to everyone, so please join us at the Contributors Gitter room!

Past events

To learn more about previous Hackathon events, visit the past GitLab Hackathons page.

Frequently Asked Questions

  1. Which GitLab projects qualify for the Hackathon?

    While we generally encourage contribution to the GitLab project, MRs for any project under the gitlab-org group, Meltano, and www-gitlab-com qualify for the Hackathon. If you are in doubt about a project which is not on this list, please do ask us on the Contributors Gitter channel.

  1. How are the points being calculated?

    In a previous Hackathon (Q2 2021), we introduced a point system upon which the winners were decided. This worked well, so we're keen to continue with its adoption. However, for this Hackathon, points will be calculated per contribution area. As a result, we will have five leaderboards on each contribution area: Website, Security, Front-end, Back-end, Documentation.
    Specifically:
    - 1 point for any MR merged that is not associated with an open/existing issue
    - 2 points, for each MR merged that is associated/closing an open/existing issue
    - 5 points, for each MR merged that is associated/closing one of the issues linked to in the Hackathon's main page

  1. My Merge Request has been merged. What's next?

    After the 15th of September, the team will review all the qualifying MRs merged and reach out to contributors. Please expect an email by the 26th of September.