community · chat

outl is built
in the open.

issues are great at tracking a bug and terrible at answering a question. so there's a discord now — for the half of every conversation that shouldn't have to become a ticket.

join the discord → open an issue

free, no account beyond discord's own, and the maintainer is in there.

where the conversation happens

four places, on purpose.

none of them replaces the others. chat is fast and forgets; issues are slow and never do.

discord →

quick questions, is-this-expected, showing off your workspace, talking through an idea before it becomes an issue.

reply time · minutes to hours
github issues →

reproducible bugs, feature requests, anything that needs to survive the conversation and get closed by a commit.

reply time · days, but it never gets lost
roadmap board →

seeing what is being built right now, and in what order, before asking when a thing lands.

reply time · read-only
blog & rss →

release notes and the long engineering write-ups — how a bug was found, what it cost, what got rejected.

reply time · every few weeks
what goes where

a chat server that isn't routed is just clutter with notifications.

outl did something wrong and you can reproduce it

github issue

a 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?

discord

half 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

discord, then an issue

shape it in chat where disagreeing is cheap, then open the issue with the version that survived.

you're stuck building on outl — CRDT, MCP, the format

discord

the maintainer is in there. so is everyone else who already hit the same wall.

a security problem

email, never a public channel

don't post it in chat or open a public issue. write directly, with "security" in the subject.

contribute

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.

CONTRIBUTING.md

how to build, how to test, what a reviewable PR looks like here.

good first issues

small, scoped, already triaged. a real change, not a typo fix.

docs & RFCs

architecture, the CRDT walkthrough, the markdown dialect, the storage trait.

outl community
$ outl community --rules
1. be decent. disagree with the idea, not the person.
2. no spam, no crypto, no recruiting.
3. reproducible bug? open an issue, then link it in chat.
4. security reports go to email, never a public channel.
maintainer: Thiago Avelino · avelinorun+outl@gmail.com · github.com/outlmd/outl
join the discord → get the beta first