FY25-Q1 Support Hackathon

What?!

The idea is to set aside some time (2-3 hours) to have a hackathon where Support team members can work on code contributions.

This can include contributions to GitLab "as usual", internal tooling, or anything else that would improve Support/GitLab, think gitlab-com/support and gitlab-org.

How?!

There's sync sessions that work as blockers for anyone who wants to participate – find them on the Support Team Calendar ("Support Hackathon").

• 2024-03-01 00-02 UTC ("AMER/APAC friendly")
• 2024-03-01 08-10 UTC ("APAC/EMEA friendly")
• 2024-03-01 14-16 UTC ("EMEA/AMER friendly")

1. It is recommended to post in #spt_pod_code-contributions ahead of time to find a "buddy" if you'd like one.
2. You can still drop by the sync sessions to see if there is someone who wants to work on the same thing, to get more ideas, or pointers. Your hosts will be available to help you along.

Ideas

Specific ideas/projects:

1. Handle encoding issues in gitlab.rb file (gitlab-com/support/toolbox/gitlabrb_sanitizer!20) or anything else in the gitlabrb_sanitizer project
2. Plenty of improvements to continue working on in the team-tracking project
3. Get the ci-reproducionizer into a more usable state
4. GitLabSAR - a fast log search tool for SM customers. If you are interested in this, feel free to reach out to @a.conrad!
5. ...
6. add more!

GitLab issues:

1. Add "Download" button to job log (gitlab-org/gitlab#29826)
2. Audit events epic
3. …
4. add more!
5. Any Support Priority/Efficiency issues