Name: Port Mortem 2026 | Code Resurrection Hackathon
Start: 2026-07-31T00:00:00.000Z
End: 2026-08-03T00:00:00.000Z

Question 1

What's the team size limit?

Accepted Answer

1–4 people. Solo welcome. We recommend 2–3 for the 72-hour window — bigger teams hit coordination overhead fast on a port project.

Question 2

Can I use AI code generation?

Accepted Answer

Yes, and you should. Cursor, Aider, Copilot, Continue, local Ollama agents — anything from free OSS tools to paid SaaS is expected. We don't gatekeep AI use; we gatekeep the artifact. DECISIONS.md, the differential fuzz log, and the original test suite are the receipts. If the port can't be defended in writing, it scores accordingly.

Question 3

Can I pick any GitHub repo?

Accepted Answer

For tracks A–G: pick from our pre-vetted pool (~30 repos), or get judge approval for an off-pool choice within hour 4 of kickoff. For Track H (Open Pair): any defensible public repo, justified in your README.

Question 4

Can I work on my port before July 31?

Accepted Answer

No code. Planning, candidate-repo scouting, agent prompt tuning, reading the source — all fine. Any port code committed before kickoff disqualifies the project.

Question 5

What if my port discovers a bug in the original?

Accepted Answer

File the upstream issue during the hackathon. Document it in your submission. That's the Bug Catcher bonus. The whole point of differential testing is that the rewriter often sees what the original maintainers missed.

Port Mortem 2026 | Code Resurrection Hackathon

About this event

Frequently asked questions