H <\> K

Hacker Guide

No matter your experience in quantum tech or open source communities, you can help make quantum open source better (and get PAID!). This guide will help you understand more about the event and how you can make the most of it!

There's no TL:DR - please read this page, the Rules page, and the AI Policy thoroughly before you get started.

⌚ Phase 1: Preparation

If you're new to open source or quantum computing, spend some time with these resources before the hack begins:

Master the Tools

Brush Up on Quantum

🔨 Phase 2: During the Hack

  1. Join the Discord
    The Unitary Foundation Discord is your primary hub. Use it to find collaborators, ask maintainers technical questions, or clarify rules with the UF team.
  2. Find Your Issue
    Browse the Bounties Page or look for the unitaryHACK26 label on GitHub.
    • The "Squatting" Rule: We ask that you do not comment on more than 3–4 projects per day. And please do not “claim” issues by saying “I’m working on it” or something similar. You can just work on your PR and submit it without discouraging others from trying to support the maintainers as well.
    • Teaming Up: If you want to collaborate, comment on the unitaryHACK Discord channel to find partners. Note that most bounties are awarded to a single PR; one person must be designated to receive the payout.
  3. Submit Your PR
    When your solution is ready and passes all local tests:
    • Link the Issue: Your PR description must link to the issue (e.g., Closes #123).
    • PR Limit: You may have no more than 4 open Pull Requests at one time. This ensures you are focusing on quality and gives other hackers a fair chance to contribute. To keep everyone honest, we ask that hackers' Github contribution activity is set to public during the HACK. Maintainers have the right to disregard your contribution if your activity is set to private.
    • Get Assigned: To help our bots track your work, ask a maintainer to "assign" the issue to you once you have a viable PR started.
  4. The Ethical AI Standard
    We have a strict No AI Slop policy. AI should be your co-pilot, not your author.
    Read the Hacker’s Guide to Ethical AI Unverified, "copy-paste" AI submissions are disrespectful to maintainers and will lead to immediate disqualification.

🎉 Phase 3: After the Hack

If your PR is accepted and merged:

🗓️ Hacker timeline