outl is built
in the open.
issues are great at tracking a bug and terrible at answering a question. that half of the conversation lives in GitHub Discussions instead, so it doesn't have to become a ticket.
free, you just need a github account, and the maintainer reads it.
four places, on purpose.
none of them replaces the others. chat is fast and forgets; issues are slow and never do.
quick questions, is-this-expected, showing off your workspace, talking through an idea before it becomes an issue.
reproducible bugs, feature requests, anything that needs to survive the conversation and get closed by a commit.
seeing what is being built right now, and in what order, before asking when a thing lands.
release notes and the long engineering write-ups — how a bug was found, what it cost, what got rejected.
a chat server that isn't routed
is just clutter with notifications.
outl did something wrong and you can reproduce it
github issuea bug that lives in chat scrolls away. an issue gets a label, a milestone and a commit that closes it.
is this the expected behaviour? am I holding it wrong?
github discussionshalf of these turn out to be a keybinding, not a bug. answering takes one message instead of a whole issue thread.
an idea you want to argue about before it's a feature
github discussions, then an issueshape it in discussions where disagreeing is cheap, then open the issue with the version that survived.
you're stuck building on outl: CRDT, MCP, the format
github discussionsthe maintainer reads it. so does everyone else who already hit the same wall.
a security problem
email, never a public channeldon't post it in chat or open a public issue. write directly, with "security" in the subject.
the code is MIT. so is the argument.
outl is rust, one repo, no CLA. every design decision that mattered is written down in an RFC you can read and disagree with before you write a line.
how to build, how to test, what a reviewable PR looks like here.
small, scoped, already triaged. a real change, not a typo fix.
architecture, the CRDT walkthrough, the markdown dialect, the storage trait.