From 2cd11e9ce23be2b552906168ecb3233d78e5ed9b Mon Sep 17 00:00:00 2001 From: Artur Shiriev Date: Mon, 13 Jul 2026 23:11:52 +0300 Subject: [PATCH] docs(community): enable Discussions on the three launch repos httpware, faststream-outbox and lite-bootstrap are the repos the launch playbook promotes, but none had a Discussions tab -- launch traffic would have arrived with nowhere native to ask. Enabled on those three. Not enabled org-wide: 20-odd empty Discussion tabs would read as a dead project, which is the same empty-room failure the channel doctrine already rejects for chat rooms. A repo gets a tab when it has traffic to fill it. Records the resulting reality in architecture/community.md, including the org-level forum that SUPPORT.md already routes to, and the fact that only that-depends has real activity so far. --- architecture/community.md | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/architecture/community.md b/architecture/community.md index 1b12b8e..91acf03 100644 --- a/architecture/community.md +++ b/architecture/community.md @@ -6,10 +6,23 @@ dated by git. ## What exists today **GitHub Discussions is the org's only owned channel**, and its primary support -and feedback surface. It is enabled on `modern-di`, `that-depends`, and `.github` -— not yet org-wide. There is deliberately **no Discord and no Telegram room**: -see `planning/deferred.md`, which holds the plan to open them and the reason they -are not open yet. +and feedback surface. It exists at two levels: + +- **Org-level** — [`/orgs/modern-python/discussions`](https://github.com/orgs/modern-python/discussions), + backed by this `.github` repo. This is the catch-all forum, and the one + [`SUPPORT.md`](../SUPPORT.md) routes every project's users to. +- **Per-repo** — enabled on `modern-di`, `that-depends`, and the three repos the + launch promotes: `httpware`, `faststream-outbox`, `lite-bootstrap`. Deliberately + **not** enabled org-wide: 20-odd empty Discussion tabs would read as a dead + project, the same empty-room failure described below. A repo gets its own tab + when it has traffic to fill it. + +Only `that-depends` has real activity today; the other surfaces are seeded but +empty, and launch traffic is what is expected to fill them. + +There is deliberately **no Discord and no Telegram room**: see +`planning/deferred.md`, which holds the plan to open them and the reason they are +not open yet. ## Why Discussions, and why nothing else yet