Skip to content

FY23 - Verify Hackathon - Pitches

As part of the Verify Team Week, we'll be having a Hackathon amongst folks who work in the stage! 🎉

UPDATE: Sign-up!

Thank you all for contributing these ideas! Please sign up in this spreadsheet. Also see this internal Slack announcement about next steps. LOOKING FORWARD TO NEXT WEEK! 💪

Pitching an idea? 🔮

📝 Add a comment as a new thread, detailing:

  • What is the problem to solve and why it's important ❓
  • What expertise/skillset is needed (e.g. As specific as 1 UX, 1 BE, 1 FE or as general as anyone who wants to reorganize our docs in this area!) 💻 🎨 🗞
  • Effort expected (or how you intend to timebox the effort to 1 week) ⏲

Upon completion of the hackathon, link to the artifact(s) to showcase your work (ideally a recorded demo would be great so that we can share them asynchronously!) 📹

📋 Sample template, you are welcome to copy/paste:

**Problem to Solve**

There's a number of CI templates that have gone untested, and we end up fixing them ad-hoc as users request it.
I'd like to collaborate with a few other interested individuals to:
1. Validate that they still run on a test project
2. Create an MR to fix the ones that do not work (e.g. pointing to an out of date image)

**Why this is important?**

We want to drive adoption of CI, much of which starts with a new user trying out a template.
This can become cumbersome for each of our users to stumble upon errors, then have to create a bug 
only when they get a failed pipeline. 

**Requested expertise**

Anyone who enjoys debugging and fixing broken builds built from syntax in our CI templates! :) 

**Effort expected**

Likely 2-3 days of dedicated effort, depending on the number of individual interested in joining this effort

**Artifacts to be produced**

Record a short walkthrough of the changes made, with links to MRs.
Edited by Cheryl Li