Repository files navigation

coder/coder is for end-users to connect with Coder engineers and product managers. Our most important issues will always live there. Bugs/improvements for released features should always live there.

1. A public issue (even in this repo) should never link to a private resource such as a Notion page, Slack thread, etc.
   1. Take screenshots of slack threads, publish notion pages, or simply copyrelevant information into the issue.
2. All issues, regardless of repository, should have a body.
3. If you have an issue and think there's basically zero chance a user would react/comment on it, put it here.
4. Strive to represent as much of your coder/coder work on coder/coder. Try tomake that work interesting to users.

Most companies solve the problem of open source tracker bloat by movinga lot of core development activity into private trackers such as JIRA. Wehave opted for a different approach because:

• Sometimes it's hard to know where an issue should live, GitHub makes it easy to move issues between repositories
• We want developers to be highly comfortable with GitHub as a tool
• GitHub projects makes it easy to track issues across repositories, so we canavoid a painful syncing process between a public and internal tracker
• If a community member begins engaging with the internal tracker, we canuse it as a sign that that type of issue should be moved to coder/coder

On some interval, @ammario and the PMs will move issues between here and thecommunity. Please take this as a sign that the issue should've been originallycreated in a different place.