From 289de097fa5f2f88ac5ff362c821319ba2cf8b02 Mon Sep 17 00:00:00 2001
From: woodser <woodser@protonmail.com>
Date: Sat, 24 Feb 2024 12:14:38 -0500
Subject: [PATCH] add bounty system

---
 .github/workflows/label.yml | 25 +++++++++++++++++++++++++
 docs/bounties.md            | 17 +++++++++++++++++
 2 files changed, 42 insertions(+)
 create mode 100644 .github/workflows/label.yml
 create mode 100644 docs/bounties.md

diff --git a/.github/workflows/label.yml b/.github/workflows/label.yml
new file mode 100644
index 00000000..2aa11c02
--- /dev/null
+++ b/.github/workflows/label.yml
@@ -0,0 +1,25 @@
+name: Comment to label
+
+on:
+  issues:
+    types: [labeled]
+  workflow_call:
+
+jobs:
+  issueLabeled:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Bounty explanation
+        uses: peter-evans/create-or-update-comment@v2
+        if: github.event.label.name == '💰bounty'
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: >
+            There is a bounty on this issue. The amount is in the title. The reward will be awarded to the first person or group of people who resolve this issue.
+
+
+            If you are starting to work on this bounty, please write a comment so that we can assign the issue to you. We expect contributors to provide a PR in a reasonable timeframe or, in case of an extensive work, updates on their progress. We will unassign the issue if we feel the assignee is not responsive or has abandoned the task.
+
+
+            Read the [full conditions and details](https://github.com/woodser/monero-cpp/blob/master/docs/bounties.md) of the bounty system.
diff --git a/docs/bounties.md b/docs/bounties.md
new file mode 100644
index 00000000..43067162
--- /dev/null
+++ b/docs/bounties.md
@@ -0,0 +1,17 @@
+## Bounties
+
+Bounties are used to incentivize development and reward contributors.
+
+To receive a bounty, you agree to these conditions:
+
+- Your changes must follow the existing coding conventions.
+- Bounties will be set and awarded in XMR.
+- The issues eligible for a bounty are labelled '💰bounty' and have the amount of the bounty specified in the title in this form: `[$200]` if in dollars or `[1 XMR]` if in Monero.
+- An issue is considered resolved when the patch(es) proposed by the contributor is/are merged in the appropriate repository according to terms of the issue. Pull requests to monero-project must be merged into the release branch to be considered final.
+- The first person who resolves an issue in its entirety will receive the entire amount of the bounty.
+- If the issue is resolved collaboratively by more than one person, the reward will be distributed among the contributors at our discretion.
+- Let the Maintainers know if you intend to work on a bounty, so that the issue can be assigned to you. Being assigned to an issue doesn't make that issue resolvable only by the assignee. It's meant to avoid duplication of efforts and not to discourage collective works.
+- After the issue is resolved, contact the maintainers and claim your bounty (remember to provide them with a Monero address).
+- If the bounty is in dollars, the contributor will receive the amount in Monero according to the value of XMR at the moment the issue was practically resolved, so in the moment the maintainers accept the last patch resolving the issue.
+
+We want to keep the system simple and flexible, but we will add new rules or edit existing ones if necessary.