Join us from April 10 - April 17
Joining in
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.
The Hackathon is scheduled to run for 7 days to be inclusive, accommodating participants who contribute during both their work hours and free time. This week-long duration ensures participants across different time zones and with varying schedules have ample opportunity to contribute. GitLab reviewers typically review MRs from Monday to Friday.
To get started:
Before the Hackathon
- Block the dates on your calendar, or subscribe to the GitLab Developer Evangelism calendar that includes the Hackathon dates and calls.
- RSVP to our meetup.com event.
- Request access to the community forks.
During the Hackathon
- Watch the Hackathon kickoff video to find out more about the Hackathon.
- In case you don't want to work on the issues described in the contribute area below:
- Choose or create an issue, based on the project you are interested in contributing to.
- You can also check out#contribution-opportunitieschannel in Discord for curated issues. - Leave a comment on the issue(s) you are working on.
- Create your MRs during the Hackathon dates - all MRs created during the Hackathon dates are eligible to score points. Include a link to the issue in your MR, if applicable.
- Check out the live Hackathon leaderboard!
After the Hackathon
- You'll have one month from the Hackathon end date to finish going through the feedback, review, and merge process for your MRs.
- At the end of the month, the team will review the contributions and results will be made public within a week.
- Participants and winners will be contacted to claim their prizes.
Issues to contribute to
When you create a merge request during the Hackathon, @gitlab-bot will automatically identify, label, and let you know it is eligible.
Contributions to all projects under the gitlab-org, gitlab-com, and components groups qualify for the Hackathon.
We recommend starting with our GitLab contribution guide which covers the process of finding an issue to work on, setting up a development environment, and raising a merge request.
We have several reproducible issues which are great for first time contributors. Please only pickup a single fix from these issues to allow other contributors to participate.
You can contribute to any page in the GitLab Handbook by clicking "Edit this page" located in the footer of the page. There is no specific list of issues, we encourage you to explore the handbook for typos, broken links and outdated information.
Hackathon scoring and prizes
We award 5 points for every merged MR closing an issue, and 1 point for every merged MR which does not close an issue. We are excited to offer the following prizes for this Hackathon.
All qualifying MRs must be submitted between April 10 00:00 UTC & April 17 00:00 UTC and be merged by May 18 at 00:00 UTC.
| Categories | Eligibility | Description |
|---|---|---|
| First Place | Individual(s) with the most points | 200 credits to redeem in our Contributor Success store |
| Second Place | Individual(s) with the second most points | 150 credits to redeem in our Contributor Success store |
| Third Place | Individual(s) with the third most points | 100 credits to redeem in our Contributor Success store |
| Merged MR | Everyone with a merged MR | 50 credits to redeem in our Contributor Success store |
Don't need swag? You can also use store credits to plant trees in the GitLab Forest!
A preview of the prizes can be found in our Contributor Success store.
Hackathon kickoff and community pairing sessions
| Date |
Time in
UTC
(click for local time) |
Topic | Session | Speakers |
|---|---|---|---|---|
| April 10 | Hackathon Kickoff - Learn all about our Hackathon format and get ready to start contributing! | Recording | Arianna Haradon (@aharadon) | |
| Tuesdays | 11:15 am | Community pairing - Ask questions, get help on your merge requests, and meet other contributors! | Meetup | Lee Tickett (@leetickett-gitlab) |
| Thursdays | 8:00 pm | Community pairing - Ask questions, get help on your merge requests, and meet other contributors! | Meetup | Arianna Haradon (@aharadon) |
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 #contribute channel in Discord.
This channel is for contribution-related discussions and for community members to help each other 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, the guidance for the team member is to leave a comment informing the contributor and their thinking behind their decision.
2. 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
Disclaimer: Due to applicable trade control law and the policies of our shipping partners, prizes cannot be shipped to the following countries: Cuba, Iran, North Korea, Syria, Ukraine, Russia, and Belarus. This list is subject to change without notice.
Past events
To learn more about previous Hackathon events, visit the past GitLab Hackathons page.