I built a tool for RFCs like Rust's
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
I read in this blog post and in this thread that the Rust community is frustrated with GitHub's UI for discussing RFCs.
I want to share a new kind of tool for RFCs I'm building. It's called CQ2. It's free, open-source, self-hostable, and it's in its early stages.
I took a Discourse discussion on a PEP and simulated it on CQ2: https://cq2.co/app/document/demo/v1. Try opening some threads there! Looks much better organised, easier to follow and easier to engage with, right?
CQ2 offers inline comments, infinite threads, a separate place for general comments, ability to resolve threads (to know what exactly remains to be discussed) and better document versioning.
I believe the Rust community would find CQ2 very delightful and more productive to use than the current GitHub workflow. If you all like it, I would love to get feedback and work with the community to shape it in its early stages.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, or implementation entry points are named. Start by reviewing the linked CQ2 demonstration and the RFC discussion links, then determine whether the Rust RFC process has a concrete integration request; the issue currently defines no specific change or completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100