Where the discussion lives

No discussion forum, mailing list, chat room, or public repository exists today. There is no async chat (Discord, Slack), no real-time chat, and no forum. If you need help, reach us the way described on the contribute page: send a field report or your question through contact.

This is intentional, not an oversight. A maintaining team of one or two cannot staff a chat room across the time zones this project is meant to serve — an unanswered channel says the project is dead more loudly than having no channel at all. Everything will stay asynchronous, public, and searchable.

One repository, GitHub Discussions and Issues only. No Discord, no Slack, no forum, no real-time chat — they all require someone to monitor them, and a team that can't answer within hours is just a dead channel. Everything will be asynchronous, public, searchable, and in the same place as the code itself.

That's deliberate. If the project ever grows beyond one or two maintainers and enough contributor volume justifies it, a tool like Discourse or Zulip could be added. But we won't reserve channels that look active and aren't.

No response-time promise today. A stated reply window — "we answer within five working days" — is exactly the thing that has to be kept once made. So it will be published alongside the named maintainer when the repository opens, not before.

Silence now does not mean declined. Until then, silence on a field report or question sent through contact means it hasn't been read yet. If your question or report falls through the cracks, send it again — a stalled thread is a bug, not a feature.

A written monthly update once there is something to report. Even a post that says "no new progress this month" is more honest than a dead channel.