Skip to content

MRWK bounty: 150 MRWK - focused small fixes from confirmed project needs #647

@ramimbo

Description

@ramimbo

Status: proposed treasury bounty. This issue is not claimable yet.

Reward: 150 MRWK per accepted award
Max awards: 10

Work Needed

Implement focused small fixes that address confirmed MergeWork project needs without waiting for a separate full-size bounty each time.

A valid item must be anchored to one of these sources:

  • an open GitHub issue where maintainers explicitly say the work fits this round,
  • a proposed-work issue that maintainers explicitly route to this round,
  • a maintainer queue comment identifying the bug or small improvement,
  • or a clear current-queue blocker that maintainers confirm before acceptance.

Acceptance Criteria

Each accepted award should be one focused PR that:

  • fixes a concrete bug, small UX/API/docs behavior gap, validation edge case, test gap, or queue blocker;
  • includes regression tests or clear verification evidence appropriate to the change;
  • stays small enough to review independently;
  • does not duplicate an already-open useful PR;
  • does not stretch a closed, exhausted, pending, or non-live bounty reference.

How To Submit

After this proposal executes and the issue is made claimable, open a focused PR with Bounty #<this issue number> in the PR body and link the confirmed source issue/comment.

Evidence or Tests Required

Run the focused tests for the touched behavior. For app behavior changes, include relevant pytest coverage. For docs/template changes, run ./.venv/bin/python scripts/docs_smoke.py.

Out of Scope

  • Broad rewrites, speculative features, unrelated generated files, or drive-by style churn.
  • Security exploit details or private vulnerability disclosure.
  • PRs based only on a contributor's own unapproved idea without maintainer confirmation.
  • Any price, investment, exchange, liquidity, bridge, cash-out, fabricated payout, private security detail, or unrelated claim.

Duplicate and Stale Work Rules

Duplicate, vague, generated, stale-head, no-test, no-source, or no-value submissions do not qualify. If multiple PRs address the same small fix, maintainers may accept the earliest complete, correct, and reviewed one.

Do not submit /claim work for MRWK from this issue until the treasury proposal executes and maintainers post the claims-open reservation comment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    mrwk:bountyMRWK bounty is postedmrwk:paidLedger payment recorded

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions