Drayker forum
{{ themeLabel }}
DRAYKER.ORG →
Start a thread
The public conversation of Drayker

Every argument that built this system is still readable.

Threads live in the repositories they belong to, on GitHub. This site reads all of them in one place and lays them out as reading — no account, no moderation queue, and no private channel where the real conversation happens instead. Writing is done on GitHub, under your own name.

{{ st.v }}
{{ st.k }}
GITHUB SYNC
{{ stamp }}
{{ syncDetail }}
REFRESH NOW →
{{ f.t }}
NOBODY ANSWERED YET
CLEAR
{{ r.title }}
{{ r.meta }}
{{ r.kindLabel }}
{{ r.partName }}
{{ r.where }}
WAITING FOR A FIRST REPLY
{{ count }}
Nothing matches that.
These are real threads, so an empty result means nobody has raised this in public yet.
BE THE FIRST →
No public thread is open right now.
Nothing is shown in its place. The repositories and the gaps each of them declares are still there to read, and the first thread on any of them can be yours.
GitHub could not be reached.
The conversation lives there, not here, so there is nothing cached that would still be true. The routing map is written down and stays correct either way.
TRY AGAIN →
← ALL THREADS
READING THE THREAD…
No thread with that address.
It may have been moved to the repository that owns the subject, which is normal here — or the link is wrong.
BACK TO EVERY THREAD →
{{ t.kindLabel }}
{{ t.where }}

{{ t.title }}

{{ t.meta }}

{{ b.text }}

{{ b.text }}
{{ b.text }}
{{ b.text }}
{{ b.text }}

This thread was opened with a title and nothing else.

READING THE REPLIES…
Nobody has replied to this yet. A first answer — even one that says the question is wrong — is a contribution.
{{ c.who }} · {{ c.when }}

{{ b.text }}

{{ b.text }}
{{ b.text }}
{{ b.text }}
{{ b.text }}
Reply on GitHub →
Your reply is published from your own account, in the repository the thread lives in.
Start a thread

Write it here. Publish it there, as yourself.

This site sends you to the repository that owns the subject with the text already written — the routing is the organization's own, not a guess. You read it, edit it and publish it under your account. No email, no handle and no contact detail is collected here, and nothing is stored.

A proposal nobody can disagree with is not a proposal. The second question exists for that reason.

SEE WHERE EACH SUBJECT BELONGS →
{{ k.t }}
{{ k.d }}
WHAT THE PUBLIC THREAD WILL CONTAIN
{{ line }}
Open it on GitHub →
OPENED ON GITHUB
It is not published until you press the button there. If the tab did not open, use the link below.
OPEN THE PREFILLED THREAD →
What was decided

A merged pull request is the only decision this organization makes.

Not an announcement, not a roadmap, not a status somebody set. If something changed, it is in this list, and the discussion that produced it is one click away.

No pull request has been merged in the public organization yet. The first one — a correction, a paper, a specification — is still available to whoever writes it.
Where a subject belongs

There is no single inbox, and that is deliberate.

A conversation sitting beside the thing it is about survives; one piled into a general channel does not. This forum reads them all together, but each thread stays in the repository that owns it — and a thread that turns out to belong somewhere else is moved rather than closed.

{{ r.about }}
{{ r.repo }} →
Every repository this forum reads
{{ p.name }}
{{ p.repo }}
About this forum

A reading surface over a conversation that already exists.

Drayker's discussion has always been public, in the issues of seventeen repositories. 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 writes nothing, stores nothing 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 thread is not chatter. It is the first step of the only process there is.

Nothing here is decided by a meeting, a vote in private or a person with a title. 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 opens a thread. There is no membership, no application, no waiting list and no private channel where the real conversation happens instead.
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 the decision. The thread stays where it is as the record of why it was taken — which is why none of this is deleted.

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.

NO ACCOUNTS
Your GitHub account is the only identity involved, and it never touches this site.
NO DATABASE
Static pages on GitHub Pages, reading the public API. Nothing is transmitted from here.
NO RANKING
Threads are ordered by last activity. Nothing is promoted, scored or hidden.
NO MODERATION
Whatever moderation exists is GitHub's, in the repositories, under the organization's own code of conduct.
NO STATUS
Labels shown here are the repositories' own. This site never invents a stage, a phase or a badge.