Ask anywhere.
Someone will answer.
2,100 people in Discord, most of whom aren't maintainers and most of whom answer faster than we do. That's the healthiest signal this project has.
People in Discord
Of questions answered by non-maintainers
Median time to a first reply
Countries represented among contributors
Four places, and the difference matters.
Putting a bug in Discord means it gets solved for you and forgotten by everyone else. This is the whole reason the split exists.
GitHub Discussions
searchable"How do I…", "is this the right tool for…", "why does it do this?" Answers here get found by the next person with the same question. That is the point.
GitHub Issues
bugs & featuresSomething is broken, or something should exist. A minimal corpus that reproduces the problem is worth more than a long description of it.
Discord
fast & informalDebugging out loud, showing what you built, arguing about chunking strategies. Fast, friendly and completely un-searchable, so anything worth keeping gets moved to Discussions.
security@quire.dev
privateVulnerabilities only, and never in a public issue. Acknowledged within 24 hours. Details and the PGP key are on the security page.
First Thursday, 16:00 UTC, forty minutes.
Open to anyone. Roughly fifteen people show up, half of whom have never contributed code. No slides.
- What shipped, what's stuck, what nobody wants to work on
- Any RFC that's been open long enough to need a decision
- An open floor that regularly turns into the most useful part
- Recorded and posted, with notes in Discussions for people in bad time zones
The calendar link is pinned in Discord. If the time doesn't work for you, say so. It's moved twice for exactly that reason.
How to ask a question that gets answered
- Say what you ran and what happened, verbatim
- Include the output of
quire config --explain - Say what you expected — half of all issues dissolve at this line
- Ask in public even if it feels basic; someone else has it too
You don't need permission
You don't need to be assigned an issue, introduce yourself first, or ask whether a PR would be welcome. Open it. The worst case is a maintainer explaining why not, and that is more useful than the question was.
The rest of it.
Mailing list
Low traffic. Releases and anything about the licence or governance. Six emails last year.
Fediverse
@quire@fosstodon.org — release notes and the occasional benchmark that made us look bad.
Local meetups
Informal groups in Lisbon, Berlin and Tel Aviv. Started by users, not by us; we just link to them.
Office hours
A maintainer sits in Discord voice for an hour every other Tuesday. Turn up with a broken config.
Translations
Four languages, all community-maintained. Coordination happens in #i18n.
Press & talks
hello@quire.dev. Happy to send someone to a conference if travel is covered.
Be decent, and assume the other person is too.
Contributor Covenant 2.1 applies everywhere with our name on it: Discord, Issues, Discussions, the call. Reports go to conduct@quire.dev, which reaches two maintainers and one person outside the project.
Full text and enforcement process on the contribute page. Maintainers are not exempt.
Lurking counts.
Plenty of people read for months before saying anything, and several of them are maintainers now.