GitLab Hackathon

Joining in

RSVP to our meetup.com event.
The Hackathon is a virtual event open to anyone who is interested in contributing code, 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.

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. RSVP to our meetup.com event.
3. Identify an issue and leave a comment indicating your interest in working on it. 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:
   - 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.
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	Issues
Security	Contributing to GitLab guide	Qualifying issues
Frontend	Frontend Development Guidelines - Design and User Interface Changes guide	- UX-related Issues, UX-related issues quick win - Frontend-related Issues, Frontend-related issues quick win
Backend	Contributing to GitLab guide - GitLab's Architecture	- GitLab Agent for Kubernetes : All Issues, Issues quick win - Stage: Package all issues, Issues quick win - Group: Respond issues, Issues quick win - Group: Optimize all issues, Issues quick win - Group: Source Code all issues, Issues quick win - Group: Editor All Issues, Issues quick win - Group: Import All Issues, Issues quick win - Group: Pipeline execution All Issues, Issues quick win - Group: Release All Issues, Issues quick win - Group: Compliance - Group: Product Intelligence All 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 prizes for this Hackathon.

All qualifying MRs must be submitted between April 23rd 00:00 UTC & April 30th 00:00 UTC and be merged by May 30th at 00:00 UTC.

Categories	Eligibility	Description
Grand Prize	Individual(s) with the most issues closed	A coupon to select swag with a value up to $75 from our Community Store
Second Place	Individual(s) with the second most issues closed	A coupon to select swag with a value up to $50 from our Community Store
Merged MR	Everyone with an MR merged	A coupon to select swag with a value up to $25 from our Community Store

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
April 23rd	TBC	Hackathon Kickoff - Learn all about our new Hackathon format, and get ready to start contributing	Zoom link to Join TBC.	Lee Tickett (@leetickett-gitlab)

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 #hackathon and #contribute channels in Discord. These are channels for hackathon- and contribution-related discussions respectively 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 Discord Community Server!

Hackathon Guidelines

Hackathon organizers and GitLab team members reserve the rights to:

1. not consider a merge request part of the hackathon if it's spam or could be part of a larger merge request, etc. If a GitLab team member decides to reject an MR, they should leave a comment informing the contributing and the thinking behind their decision.

2. to block and ban a user that is not following GitLab's Code of Conduct

3. block and ban a user that is using two or more accounts for participating in the Hackathon

Past events

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