What is the "deal-flow yield" of a community?

Yield is a three-tier rating, primary, secondary, ambient, describing how often a community has been the first public surface where a repo or founder we now surface inside the product appeared. Primary means multiple deals trace back to the room; ambient means the room is read for framing, not sourcing.

Why is open-source maintainer spaces indexed by type instead of by platform?

The platform map at /voices already covers per-platform rosters (Reddit-100, HN-100, X-100). Indexing by type cuts the same audience differently, a Cursor user in a Cursor Discord is a different deal-flow signal than the same user in a CNCF channel, even though both are on Discord.

Do we engage in every community on this page?

No. Each community is tagged with an engagement status (engage / watch / hold / read / blocked). The default for most rooms is "watch" or "read", we listen but do not post. The "engage" tag is reserved for a small number of rooms where comment-only engagement on technical Q&A is allowed by both the room rules and our anonymity rule.

Are the individuals inside these communities listed anywhere?

No. The anonymity rule that governs the entire site applies here: we name communities, not individuals. The specific founders, maintainers, and contributors we surface live inside the paid product, that is the buyer's edge.

Maintainers, foundation-grade infra contributors · 12 rooms · ranked by yield

Open-source maintainer spaces. Ranked by deal-flow yield.

GitHub Discussions, CNCF Slack, Sustain OSS, where 'we're going commercial' leaks earliest.

Maintainer-side rooms. The high-yield pattern here is the maintainer-to-company transition, a project's GitHub Discussions or a foundation's Slack often carry the earliest public signal that a repo is leaving the foundation orbit for a company.

Yield story

Primary surfaces are GitHub Discussions (per-repo), CNCF Slack, LF AI & Data Slack, and Sustain OSS Discourse, four surfaces where the OSS-to-company flip telegraphs ~3-6 weeks before a press announcement.

Cadence

Weekly read on the four primary surfaces; ambient consumption of the rest via aggregator.

Caveat

Foundation-grade rooms are governance-sensitive, we read, we do not engage on roadmap or sustainability threads.

Yield breakdown · 12 rooms

4
Primary
Direct deal-flow surface. Multiple repos we surface first showed up here.
5
Secondary
Adjacent. Signals overlap, but rarely the first-mention surface.
3
Ambient
Culture / reading list. Useful for framing, not for sourcing.

Engagement status

0
Engage
7
Watch
0
Hold
5
Read
0
Blocked

The ranked roster

12 rooms, sorted by yield tier, numbered, linked.

Primary first, then secondary, then ambient. Hand-authored order within each tier, top of tier = highest attention density.

1.
GitHub Discussions (per-repo)
PrimaryWatchGitHub
Repo-attached discussion surface. Often the first 'we're going commercial' hint.
2.
CNCF Slack
PrimaryWatchSlack
Cloud-native foundation community. Infra-grade deal-flow.
3.
LF AI & Data Slack
PrimaryWatchSlack
Linux Foundation AI / Data sub-foundation. Foundation-pattern repos.
4.
Sustain OSS Discourse
PrimaryReadDiscourse
OSS-sustainability discussion. Maintainer-burnout to commercial flip.
5.
Open Collective Slack
SecondaryReadSlack
OSS-funding community. Watch for transition-to-company patterns.
6.
r/opensource
SecondaryWatchReddit
Maintainership audience.
7.
r/programming
SecondaryWatchReddit
Default tech-news firehose. Slow-engage, high-attention.
8.
crates.io Discord (Rust)
SecondaryWatchDiscord
Rust-package community. Systems-infra startup signal.
9.
npm Community Forum
SecondaryWatchGitHub
Package-ecosystem discussion. Adoption signal.
10.
Apache mailing lists
AmbientReadOther
ASF dev / user lists. Foundation-grade infra signal.
11.
Hacktoberfest Discord
AmbientReadDiscord
Maintainer-meets-contributor event. Ambient annual signal.
12.
Maintainer Month (GitHub)
AmbientReadGitHub
Annual maintainer-spotlight surface. Pattern memory.

Frequently asked

Four questions about this list.

What is the "deal-flow yield" of a community?: Yield is a three-tier rating, primary, secondary, ambient, describing how often a community has been the first public surface where a repo or founder we now surface inside the product appeared. Primary means multiple deals trace back to the room; ambient means the room is read for framing, not sourcing.
Why is open-source maintainer spaces indexed by type instead of by platform?: The platform map at /voices already covers per-platform rosters (Reddit-100, HN-100, X-100). Indexing by type cuts the same audience differently, a Cursor user in a Cursor Discord is a different deal-flow signal than the same user in a CNCF channel, even though both are on Discord.
Do we engage in every community on this page?: No. Each community is tagged with an engagement status (engage / watch / hold / read / blocked). The default for most rooms is "watch" or "read", we listen but do not post. The "engage" tag is reserved for a small number of rooms where comment-only engagement on technical Q&A is allowed by both the room rules and our anonymity rule.
Are the individuals inside these communities listed anywhere?: No. The anonymity rule that governs the entire site applies here: we name communities, not individuals. The specific founders, maintainers, and contributors we surface live inside the paid product, that is the buyer's edge.

Where the deal-flow signal actually lives

Rooms tell us where to look. Telemetry tells us what to fund.

Reading open-source maintainer spacesdoesn’t produce a deal. It sharpens the question we ask the GitHub-side telemetry. The actual deal-flow signal lives at /predicted, /firstlook, and the rest of the signal stack below.

See /predicted →See the platform map →

Open-source maintainer spaces roster regenerated quarterly. Status flags update weekly. Companion platform map at /voices. Master mixed list at /target-list.