internal

Bounty board

Ongoing projects for Open Reality (also a tool for open work coordination). Each bounty comes with a goal, spec, fixtures, and (potentially) acceptance criteria. Some may come in the form of an independent github repository while others involve direct contribution to the existing codebase.

Join the Open Reality Discord- questions, claims, and whoever else is working on your bounty

49
Open bounties
4
Zero-access (Ring 0)
~348d
Scoped work on the board

Access rings

Every bounty is labeled with the access it actually requires. You start at the ring your bounty needs. Access rings are a way to track the complexity of the work.

RING 0 No access

Public-web research and public datasets only. Deliverables are documents. Nothing to clone.

RING 1 Specs + artifacts

A private bounty repo holding format specs, frozen result files, and fixture data. No product code.

RING 2 Extracted module

A bounty repo seeded with one module or package plus its tests and fixtures - still not a clone of any product repo.

RING 3 Component read

Read + branch access to a single component repo. Earned after two accepted bounties. Integration still lands through us.

How a bounty runs

  1. Claim. Claim the bounty on this page with your Open Reality account. I will ask you for your github username. Multiple people can work on the same bounty*. *when this happens, remind me to setup a slack / discord channel for Open Reality.
  2. Kit. Within a day you will get either a github repository or a direct link to the codebase.
  3. Build. Open a draft PR early; ask questions on the PR and in DMs.
  4. Review. Acceptance criteria are mentioned, but we will discuss the work and the results together.
  5. Integration. We port accepted work into the product repos and you pick your next bounty.
  6. Credit. You will be credited for your work in the product repos. Payments (I have not fully come up with this yet) should be attached to each bounty.

Ground rules

  • Bounty materials stay private. Don't redistribute repos, specs, or fixtures. We will make a lot of work public in due time.
  • Numbers. Let's try to keep numbers as objective as possible.
  • Post your own bounties. If you have a project you want to work on, post it here.