Saw D11693 and I thought these changes on top might make the README even better? Open for discussion. I like our bug reporting doc a lot so I don't mind funneling users through it and not mentioning the bug reporting link directly in the readme. This notably forces github users to read a bit before they report issues to us for the first time. That said, I think the community chat can be really helpful at no cost to us so why not upsell it? This could fail if people start asking for say epriestley directly and / or the overall chatter is time consuming, but seemed worth tossing out at least.
Details
Details
- Reviewers
epriestley chad - Commits
- Restricted Diffusion Commit
rPdca27279cc55: README update - rely on bug reporting doc and add section about community chat
read the text, asking opinions of cohorts
Diff Detail
Diff Detail
- Repository
- rP Phabricator
- Branch
- bugreport
- Lint
Lint Warnings Severity Location Code Message Warning README.md:22 TXT3 Line Too Long Warning README.md:30 TXT3 Line Too Long - Unit
No Test Coverage - Build Status
Buildable 4353 Build 4366: [Placeholder Plan] Wait for 30 Seconds
Event Timeline
Comment Actions
Elsewhere, I spell out IRC channel (#phabricator on FreeNode) because the link doesn't give users enough information to connect if the irc:// protocol does not work on their machine. In particular, they have to take some extra steps to figure out how to connect with a web client. But I don't know that this is really an issue.
Comment Actions
enough information
(I mean, technically it has all the information, but if you don't really know what IRC is and you don't have a client installed you have less to go on when Googling or whatever.)