About this forum
A reading surface over a conversation that already exists.
{{ aboutLead }} That is the right place for it — a thread beside the code and documents it concerns survives, and can be argued with by whoever maintains them. It is also a place most people never look, and never think to answer in.
So this site reads all of it and presents it as what it is: conversation. It keeps no accounts and no database, and asks for nothing. Every reply, proposal and correction is published from your own GitHub account, in the repository where it belongs — which means this forum can disappear tomorrow without a single word of the discussion being lost.
A scheduled workflow rebuilds the site from GitHub (it is set to run every 15 minutes, but GitHub may delay scheduled runs by hours) and republishes it when something changed. A thread page may also ask GitHub for replies newer than the last publication. To follow it without visiting, subscribe to the Atom feeds for new threads (/feed.xml) and for decisions (/decisions/feed.xml).
A thread is not chatter. It is the first step of the public contribution path.
Nothing here is decided in a private meeting or a private vote. In the founding phase the founding steward integrates changes in public, as GOVERNANCE.md documents. A subject is said in the open, routed to whatever owns it, and if it becomes work it ends as a change anyone can read.
01 · SAID IN THE OPEN
Anyone can open a thread without an application or waiting list. Drayker’s membership rules are not operational yet, and no private channel replaces the public record.
02 · ROUTED TO ITS OWNER
If the subject belongs to a component, it moves to that component’s repository, beside the code and the documents it is about.
03 · CUT SMALL ENOUGH
A thread that turns into work is cut into pieces one person can finish. Those carry the label open-function and appear on the board.
04 · ARGUED AGAINST A CHANGE
Whoever claims it opens a pull request to master. From there the discussion is about the actual difference being proposed, not about the idea of it.
05 · MERGED, AND KEPT
The merge is how the decision enters the record. The thread stays where it is as the record of why it was taken.
What this site does not have.
Every absence below is deliberate. A forum that keeps its own accounts, its own copies and its own moderation becomes a second source of truth — and then the argument is about the forum instead of about the work.
Your browser does load code libraries (unpkg, jsDelivr), fonts (Google Fonts), and avatars and images (GitHub). A thread page may ask GitHub’s public API for replies newer than the last update, a thread opened after the last update is read live from GitHub, and the list asks GitHub’s search API for newer activity only when you press Check GitHub.
- NO ACCOUNTS
- Your GitHub account is the only identity involved, and it never touches this site.
- NO DATABASE
- Static pages on GitHub Pages, rebuilt from GitHub’s public API by a scheduled workflow and republished when something changed. Nothing you type here is sent anywhere until you choose to continue on GitHub.
- NO RANKING
- Threads are ordered by last activity unless you choose another order. Nothing is promoted, scored or hidden.
- NO STATUS
- Labels shown here are the repositories’ own. This site never invents a stage, a phase or a badge.