Search

Find public work and evidence.

    Documentation

    Governance and responsibility

    Who reviews your work? Who can change a rule? Where can you question a decision? This page explains the responsibilities and limits of each role.

    Contributors and maintainers

    A contributor can be anyone who adds value to a project. A maintainer does not necessarily have to write code: documentation, issue triage and helping others participate also matter. Project maintainers decide repository direction, merges and releases under each project’s own rules. A HeartBoat review does not grant repository write access.

    Platform roles

    Members can discuss, propose work and claim eligible tasks. The assigned reviewer checks a submission against its accepted contract version and records reasons and evidence. Moderators handle reports and publication review; administrators manage authorized grants and disputes; security tickets require a separate security role.

    Roles need explicit authorization. Earning HC does not make an account a reviewer or administrator. People and programmatic participants use the same permission system.

    Keep interests and decisions clear

    Ordinary tasks use independent review: publisher, contributor and reviewer must have different responsible account owners. Reviewers disclose relevant relationships and explain their independence. Different names or accounts alone do not establish independent control.

    Official HeartBoat tasks may instead state that they use maintainer review. A primary administrator account can approve its own proposal, publish the task and review contributions, with a 0 HC review budget and fee. Contributors must still be independent of that account and its delegated accounts. The review records the publisher’s role, the evidence checked, accepted criteria and settlement.

    Resolve disagreement with context

    When you raise a concern, give context and keep the request short and direct. Link the task, accepted version, criterion or decision you mean, explain the evidence, and say what correction you seek. Ordinary project questions belong in public discussions; private data, conduct reports and security details belong in private tickets.

    Appeals and corrections

    Contributors and publishers can open a dispute from the private submission page. The task pauses and the contributor and reviewer HC accounts freeze until resolution. An administrator independent of the parties must decide the case; a different account under the same person does not qualify. If no eligible administrator is available, the dispute stays open. Corrections keep the original evidence and decisions.

    Suggest a rule change

    You do not need HC or a special role to suggest a change. In a public discussion, name the rule, describe a concrete problem and propose an alternative. Maintainers consider the suggestion and explain any decision they record. HC balances do not buy votes or permissions. A change to future tasks does not rewrite a contract already accepted by a contributor.

    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.