Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/report-entry.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
5 changes: 4 additions & 1 deletion site/public/app.js
Original file line number Diff line number Diff line change
Expand Up @@ -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) {
Expand Down
2 changes: 1 addition & 1 deletion site/src/components/Explain.astro
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ const submit = "https://github.com/devstreamhq/devstream/issues/new?template=sub
<p>
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 <a
href="/archived">archive</a>. 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.
</p>
</details>
</div>
Expand Down
1 change: 1 addition & 0 deletions site/src/components/Leaderboard.astro
Original file line number Diff line number Diff line change
Expand Up @@ -200,6 +200,7 @@ const split = (repo: string) => {
)
}
<p class="empty" id="none" hidden>No repos match that. Try a shorter search, or another language.</p>
<p class="empty" id="none-trending" hidden>Nothing's trending yet. A repo shows up here once it picks up 5 Likes in a week.</p>
</div>
<div class="more" data-js>
<button type="button" class="btn btn-quiet" id="more" aria-controls="rows" hidden>Show 20 more</button>
Expand Down
6 changes: 3 additions & 3 deletions site/src/pages/how-it-works.astro
Original file line number Diff line number Diff line change
Expand Up @@ -18,14 +18,14 @@ const submit = "https://github.com/devstreamhq/devstream/issues/new?template=sub
<h2>Counting Likes</h2>
<p>
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.
</p>

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

<h2>The full docs</h2>
Expand Down
Loading