Search

Find public work and evidence.

    Documentation

    Acceptance, revision and appeal

    After you submit, the assigned reviewer can accept the work, accept part of it, ask for changes or reject it. Each decision must explain how your evidence meets the task requirements.

    What the reviewer checks

    The reviewer uses the contract version recorded when you claimed the task. Goals, non-goals, materials, criterion IDs, review policy and declared rewards remain tied to that version. The decision records reasons, checked evidence and the required relationship declaration. A new requirement should be clarified as a scope change rather than silently added to the old criteria.

    Know who will review the work

    Ordinary tasks use a reviewer independent of the publisher and contributor. Official HeartBoat tasks marked “Maintainer review” are reviewed by their publisher for 0 HC. That maintainer must disclose this role and remain independent of the contributor; the maintainer and its delegated accounts cannot claim the task. Neither policy permits approving work you produced or controlled yourself.

    The four review outcomes

    Accepted: all criteria are met, and their declared HC are awarded. Partial acceptance: only the predeclared completed criteria are awarded. The reviewer records which criteria were accepted.

    Revision: the full reservation is kept, no review fee is settled yet, and you can submit a revised version. Rejected: the decision explains why the criteria were not met; no contributor award is made, and unused reserved funds return to the publisher. Independent review may settle a documented fee within its reserved budget; maintainer review always pays 0 HC.

    Use evidence and the agreed standards

    GitHub does not allow pull request authors to approve their own contributions. Google’s review guidance favors technical evidence and useful improvements over demands for perfection. HeartBoat draws on these practices: record the checks actually performed, connect required changes to the accepted criteria and distinguish optional suggestions from conditions of acceptance.

    Responding to requested changes

    When someone requests changes, be responsive. They have taken the time to review your contribution. Address each point, explain your changes and attach the new evidence. If you do not know how to make a change, research the problem and ask for help. Keep your earlier evidence available so the reviewer can see what changed.

    Opening an appeal

    If you are not sure why a contribution was not accepted, it is reasonable to ask for feedback and clarification. Link the accepted version and criterion, identify the evidence you believe was missed, and state the correction you seek.

    A contributor or publisher can open a dispute from the private submission page. The task pauses and the contributor and reviewer HC accounts freeze while it is open. Resolution needs an administrator independent of the parties. If none is available, the case stays open; there is no guaranteed resolution date. Reversing a spent award cannot create a negative participant balance.

    If you have not received a review

    After a week without feedback, send a reminder with the submission ID. Use a private community ticket if you cannot reach the reviewer. Reviews waiting over seven days are flagged for the operator, but the system does not approve them automatically. There is no guaranteed review date; check reviewer availability before taking on substantial work.

    Sources and adaptation

    Adapted from Open Source Guides, © Open Source Guides authors, under CC BY 4.0. Examples, account access, evidence, review and HC instructions have been changed to describe HeartBoat. These adapted guide paragraphs are available under the same license.