anurag629 · Oct 31, 2026 · Oct 30, 2026 · Oct 30, 2026 · Oct 31, 2026
diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
diff --git a/.github/workflows/accepted-label.yml b/.github/workflows/accepted-label.yml
@@ -1,7 +1,8 @@
 name: Accepted label
 
-# A merged PR counts on the leaderboard only with the hacktoberfest-accepted
-# label, and only for an issue that was assigned to its author (CONTRIBUTING.md).
+# A merged PR counts on the leaderboard (oss.codercops.com) only with the
+# codercops-accepted label, and only for an issue that was assigned to its
+# author (CONTRIBUTING.md). PRs merged in October also get hacktoberfest-accepted.
 # Maintainers add the label when they merge. This adds it when that was missed,
 # by the same rule as the claim check: every issue the PR closes is assigned to
 # the author. It runs once, at the merge, so removing the label later sticks.
@@ -20,12 +21,13 @@ permissions:
 jobs:
   label:
     name: Label a merged contributor PR
-    # Maintainers and bots don't claim issues, and spam never counts.
+    # Maintainers and bots don't claim issues, and spam never counts. Outside
+    # collaborators (contributors with Triage) are labeled like everyone else.
     if: >-
       github.event.pull_request.merged == true &&
       github.event.pull_request.user.type != 'Bot' &&
-      !contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.pull_request.author_association) &&
-      !contains(github.event.pull_request.labels.*.name, 'hacktoberfest-accepted') &&
+      !contains(fromJSON('["OWNER", "MEMBER"]'), github.event.pull_request.author_association) &&
+      !contains(github.event.pull_request.labels.*.name, 'codercops-accepted') &&
       !contains(github.event.pull_request.labels.*.name, 'spam')
     runs-on: ubuntu-latest
     steps:
@@ -34,6 +36,7 @@ jobs:
           GH_TOKEN: ${{ github.token }}
           REPO: ${{ github.repository }}
           PR: ${{ github.event.pull_request.number }}
+          MERGED_AT: ${{ github.event.pull_request.merged_at }}
         run: |
           set -euo pipefail
 
@@ -70,7 +73,7 @@ jobs:
           fi
 
           if [ "$(jq length <<<"$linked")" -eq 0 ]; then
-            echo "::notice title=Not labeled::This PR isn't linked to an issue, so it doesn't get hacktoberfest-accepted."
+            echo "::notice title=Not labeled::This PR isn't linked to an issue, so it doesn't get codercops-accepted."
             exit 0
           fi
 
@@ -81,9 +84,12 @@ jobs:
             | join(", ")' <<<"$linked")
 
           if [ -n "$missing" ]; then
-            echo "::notice title=Not labeled::$missing isn't assigned to @$author, so this PR doesn't get hacktoberfest-accepted."
+            echo "::notice title=Not labeled::$missing isn't assigned to @$author, so this PR doesn't get codercops-accepted."
             exit 0
           fi
 
-          gh api -X POST "repos/$REPO/issues/$PR/labels" -f "labels[]=hacktoberfest-accepted" --silent
-          echo "Added hacktoberfest-accepted: $(jq -r '[.[].ref] | join(", ")' <<<"$linked") assigned to @$author"
+          labels=(-f "labels[]=codercops-accepted")
+          # Hacktoberfest only counts PRs merged in October (UTC).
+          if [ "${MERGED_AT:5:2}" = "10" ]; then labels+=(-f "labels[]=hacktoberfest-accepted"); fi
+          gh api -X POST "repos/$REPO/issues/$PR/labels" "${labels[@]}" --silent
+          echo "Labeled: $(jq -r '[.[].ref] | join(", ")' <<<"$linked") assigned to @$author"
diff --git a/.github/workflows/claim-check.yml b/.github/workflows/claim-check.yml
@@ -26,7 +26,7 @@ jobs:
     # Maintainers and bots don't claim issues.
     if: >-
       github.event.pull_request.user.type != 'Bot' &&
-      !contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.pull_request.author_association)
+      !contains(fromJSON('["OWNER", "MEMBER"]'), github.event.pull_request.author_association)
     runs-on: ubuntu-latest
     steps:
       - name: Check the linked issue

diff --git a/.well-known/funding-manifest-urls b/.well-known/funding-manifest-urls
@@ -0,0 +1 @@
+https://oss.codercops.com/funding.json
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -2,17 +2,17 @@
 
 Thank you for your interest in contributing! OGCOPS is open source and welcomes contributions of all kinds.
 
-## Hacktoberfest 2026
+## How to contribute
 
-We're taking part in Hacktoberfest this year, and first-time contributors are very welcome.
+First-time contributors are very welcome.
 
-1. Pick an open issue labeled [`hacktoberfest`](https://github.com/codercops/ogcops/issues?q=is%3Aissue+is%3Aopen+label%3Ahacktoberfest+no%3Aassignee) or [`good first issue`](https://github.com/codercops/ogcops/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+no%3Aassignee) that nobody is assigned to. New template ideas are listed in [#5](https://github.com/codercops/ogcops/issues/5).
+1. Pick an open issue labeled [`good first issue`](https://github.com/codercops/ogcops/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+no%3Aassignee) that nobody is assigned to. New template ideas are listed in [#5](https://github.com/codercops/ogcops/issues/5).
 2. Comment on it to ask for it. I'll assign it to you, usually within a day. Please don't start on an issue that's assigned to someone else.
 3. Take one issue at a time. Once your PR is merged, grab the next one. After 3 merged PRs with us you can hold two issues at once.
 4. If you're assigned and there's no PR or update for 5 days, I'll free the issue up for someone else. Just comment if you need more time.
 5. Open your PR against `dev` here in codercops/ogcops and put `Closes #<issue number>` in the description. A PR merged inside your own fork never reaches us, so it doesn't count. A check on the PR ("Claim check") fails if that issue isn't assigned to you. Another one ("Description check") fails while the "How I tested this" or "AI assistance" section of the description is missing or empty.
 
-PRs count for Hacktoberfest once they're merged or labeled `hacktoberfest-accepted`. PRs that aren't linked to an issue, only reformat code, or change things nobody asked for will be closed, and spammy ones get the `spam` label. If you have an idea that isn't an issue yet, open an issue first so we can agree on it before you write code. The full rules are under [Ground Rules](#ground-rules) below.
+A merged PR counts on the monthly leaderboard once it's labeled `codercops-accepted`. A workflow adds that label when the PR is merged, as long as every issue it closes is assigned to you. PRs that aren't linked to an issue, only reformat code, or change things nobody asked for will be closed, and spammy ones get the `spam` label. If you have an idea that isn't an issue yet, open an issue first so we can agree on it before you write code. The full rules are under [Ground Rules](#ground-rules) below.
 
 Stuck? Ask on the issue, or in `#oss-help` on our [Discord](https://discord.gg/mpGdJyjaRQ). Questions are welcome. Claims still happen on the issue, so the assignment stays visible to everyone.
 
@@ -38,7 +38,7 @@ These get closed and labeled `spam`:
 - claiming a pile of issues at once, or bulk and automated submissions
 - untested generated code
 
-Two spam PRs and you won't be assigned more issues this month, and you're out of the CODERCOPS goodies.
+Two spam PRs and you won't be assigned more issues this month, and your PRs stop counting on the leaderboard.
 
 ### Reviews
 
@@ -48,15 +48,15 @@ For a bug fix, check that your new test fails without the fix: undo the change i
 
 I review most PRs within a few days. Please don't ping repeatedly or DM maintainers about a review. If three days pass with no reply, one follow-up comment on the PR is fine.
 
-### Goodies
+### Monthly leaderboard
 
-The top 5 contributors this October get a CODERCOPS T-shirt and stickers. You need at least 5 merged PRs labeled `hacktoberfest-accepted` across chatcops, ogcops, toolbelt and discord-bot, merged between Oct 1 and Oct 31 (UTC), and ties go to whoever got there first. To keep it fair:
+Every month has its own leaderboard at [oss.codercops.com/leaderboard](https://oss.codercops.com/leaderboard). It counts PRs labeled `codercops-accepted` across chatcops, ogcops, toolbelt and discord-bot that were merged in that month (UTC). You're ranked from 3 merged PRs, and the top 5 get a shout-out on our X and LinkedIn pages. To keep it fair:
 
 - only PRs for issues that were assigned to you count
 - a fix split into several PRs counts once
 - what counts is the maintainers' call, and that call is final
 
-These goodies come from CODERCOPS through our own open source program. They're separate from Hacktoberfest, so anything Hacktoberfest itself gives out is a different thing with its own rules.
+People who keep contributing can be invited as maintainers with Triage access. [GOVERNANCE.md](https://github.com/codercops/.github/blob/main/GOVERNANCE.md) explains how that works and who maintains what.
 
 ## Ways to Contribute
 

diff --git a/README.md b/README.md
@@ -129,6 +129,10 @@ git checkout -b your-feature-branch
 - [Join the Discord](https://discord.gg/mpGdJyjaRQ) to chat with other contributors
 - [Start a discussion](https://github.com/codercops/ogcops/discussions) — questions, ideas, show & tell
 
+## Maintainers and funding
+
+OGCOPS is maintained by CODERCOPS together with contributors who have Triage access. [GOVERNANCE.md](https://github.com/codercops/.github/blob/main/GOVERNANCE.md) lists who they are and how to become one. The project is free and MIT licensed, and CODERCOPS doesn't sell it or a hosted version of it. If it's useful to you, you can [sponsor the maintainers](https://github.com/sponsors/anurag629). The money pays for review time and hosting.
+
 ## License
 
 [MIT](LICENSE)