From 14fbced973d8659fbcaa604a0df069974732eac3 Mon Sep 17 00:00:00 2001 From: jamesconwaydev <148910373+jamesconwaydev@users.noreply.github.com> Date: Fri, 6 Nov 2026 13:11:05 -0700 Subject: [PATCH] docs: make the copy match what the bots actually do --- .github/ISSUE_TEMPLATE/report-entry.yml | 2 +- CONTRIBUTING.md | 4 ++-- GOVERNANCE.md | 2 +- README.md | 2 +- site/public/app.js | 5 ++++- site/src/components/Explain.astro | 2 +- site/src/components/Leaderboard.astro | 1 + site/src/pages/how-it-works.astro | 6 +++--- 8 files changed, 14 insertions(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/report-entry.yml b/.github/ISSUE_TEMPLATE/report-entry.yml index 318ca76..524e57e 100644 --- a/.github/ISSUE_TEMPLATE/report-entry.yml +++ b/.github/ISSUE_TEMPLATE/report-entry.yml @@ -6,7 +6,7 @@ body: - type: markdown attributes: value: | - Spotted something on the list that shouldn't be there? Tell us which repo and why. A maintainer reads every report. + Spotted something on the list that shouldn't be there? Tell us which repo and why. A maintainer reads every report, up to 5 a day from any one account. - type: input id: entry attributes: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3988ef3..0c3c18b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -11,7 +11,7 @@ Your account has to be at least 30 days old, with some public activity. You can The repo has to: - be at least 30 days old, with a push in the last 90 days; -- have an OSI-approved license, a real README and a description; +- have an OSI-approved license (Learning & Resources also takes CC0-1.0, CC-BY-4.0 and CC-BY-SA-4.0), a real README and a description; - have at least 2 of these 7 extras: a topic, a CONTRIBUTING guide, a code of conduct, an issue or pull request template, a SECURITY policy, GitHub Actions workflows, or a release. If it passes, the bot opens a PR and the repo lands on its own. If it doesn't, the bot comments on your issue with the reasons. Fix them and submit again whenever you're ready. @@ -44,7 +44,7 @@ We use [Conventional Commits](https://www.conventionalcommits.org/), for example ### Review -Every pull request needs an approving review before it can merge, and the PR checks (`validate`, `test` and `lint`) have to pass. If you're planning something big, open an issue or start a thread in [Ideas](https://github.com/devstreamhq/devstream/discussions/categories/ideas) first, so we can agree on the shape before you write the code. +Every pull request needs an approving review before it can merge, and the PR checks have to pass: `validate`, `test`, `lint`, `site` and the three CodeQL `analyze` jobs. If you're planning something big, open an issue or start a thread in [Ideas](https://github.com/devstreamhq/devstream/discussions/categories/ideas) first, so we can agree on the shape before you write the code. ## Questions diff --git a/GOVERNANCE.md b/GOVERNANCE.md index e756286..95041b1 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -22,7 +22,7 @@ When a case doesn't fit the rules, a human looks at it. Anything a bot can't dec ## Moderation -Anyone can [report an entry](https://github.com/devstreamhq/devstream/issues/new?template=report-entry.yml), and every report about a listed repo goes into the review queue. Some reports also act straight away. When 3 established accounts report the same entry as spam within 30 days, or one established account reports it as malicious, the entry is hidden while I review it. If I un-hide it, only reports filed after that count toward hiding it again. A report that an entry is dead queues a health check. +Anyone can [report an entry](https://github.com/devstreamhq/devstream/issues/new?template=report-entry.yml), and every report about a listed repo goes into the review queue (up to 5 a day from any one account). Some reports also act straight away. When 3 established accounts report the same entry as spam within 30 days, or one established account reports it as malicious, the entry is hidden while I review it. If I un-hide it, only reports filed after that count toward hiding it again. A report that an entry is dead queues a health check. Submissions whose description matches a term in `scripts/blocklist.txt` (SEO, casino, scam and similar spam) are rejected. Everything else is moderated by hand. diff --git a/README.md b/README.md index 1054076..901db27 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ Want what's climbing instead? The site has Trending and New too. ## How it works -1. You submit, and a bot checks. It wants 30 days of history, a push in the last 90, an OSI license, a real README and [a few more things](CONTRIBUTING.md#submit-a-repo). Pass, and a bot PR adds it. Nobody has to wake up and approve it. +1. You submit, and a bot checks. It wants 30 days of history, a push in the last 90, an OSI license (learning resources can use CC0 or CC BY), a real README and [a few more things](CONTRIBUTING.md#submit-a-repo). Pass, and a bot PR adds it. Nobody has to wake up and approve it. 2. You Like what you use. A 👍 on the entry's Discussion counts once per account, and trust filters and burst detection make sock puppets a waste of effort. 3. Dead repos leave. A weekly health check warns the owner first, then archives or removes what's gone quiet. diff --git a/site/public/app.js b/site/public/app.js index b5df066..151f4e6 100644 --- a/site/public/app.js +++ b/site/public/app.js @@ -51,7 +51,10 @@ if (rows) { rows.append(...list, ...all.filter((r) => !list.includes(r))); all.forEach((r) => (r.hidden = !list.slice(0, limit).includes(r))); more.hidden = list.length <= limit; - $("none").hidden = list.length > 0; + // An empty Trending tab with no filters on is quiet, not a failed search. + const quiet = !list.length && tab === "trending" && !t && !lang.value; + $("none").hidden = list.length > 0 || quiet; + $("none-trending").hidden = !quiet; $("count").textContent = `${Math.min(limit, list.length)} of ${list.length} repos`; for (const th of heads) { diff --git a/site/src/components/Explain.astro b/site/src/components/Explain.astro index f2f9cbb..3bb3872 100644 --- a/site/src/components/Explain.astro +++ b/site/src/components/Explain.astro @@ -43,7 +43,7 @@ const submit = "https://github.com/devstreamhq/devstream/issues/new?template=sub

A repo that goes a year without a push, gets archived or says it's unmaintained gets a 30-day warning, then moves to the archive. It comes back by itself if things pick up. Deleted repos, and ones that lose their licence or README, - come off straight away. + get a week's notice, then come off.

diff --git a/site/src/components/Leaderboard.astro b/site/src/components/Leaderboard.astro index 9446788..a331123 100644 --- a/site/src/components/Leaderboard.astro +++ b/site/src/components/Leaderboard.astro @@ -200,6 +200,7 @@ const split = (repo: string) => { ) } +
diff --git a/site/src/pages/how-it-works.astro b/site/src/pages/how-it-works.astro index a253d34..708840e 100644 --- a/site/src/pages/how-it-works.astro +++ b/site/src/pages/how-it-works.astro @@ -18,14 +18,14 @@ const submit = "https://github.com/devstreamhq/devstream/issues/new?template=sub

Counting Likes

Every listed repo gets a Discussion. A thumbs-up there is a Like, as long as it comes from an account that's at least 30 days old with a - public repo or a contribution in the last year. A sudden pile of Likes from brand-new accounts gets the repo flagged and kept out of - Trending until someone checks it. + public repo or a contribution in the last year. Anyone newer doesn't count at all. And if a pile of Likes lands at once from accounts + only a few months old, the repo is flagged and kept out of Trending until someone checks it.

Leaving the list

Repos that stop getting pushes for a year, get archived or call themselves unmaintained get a 30-day warning, then move to the archive. Repos that disappear or drop their licence or README come off straight away. + href="/archived">archive. Repos that disappear or drop their licence or README get a week's notice, then come off.

The full docs