alt Hacker NewsShow HN: RFC Hub
I've worked at several companies during the past two decades and I kept encountering the same issues with internal technical proposals:
- Authors would change a spec after I started writing code
- It's hard to find what proposals would benefit from my review
- It's hard to find the right person to review my proposals
- It's not always obvious if a proposal has reached consensus (e.g. buried comments)
- I'm not notified if a proposal I approved is now ready to be worked on
And that's just scratching the surface. The most popular solutions (like Notion or Google Drive + Docs) mostly lack semantics. For example it's easy as a human to see a table in a document with rows representing reviewers and a checkbox representing review acceptance but it's hard to formally extract meaning and prevent a document from "being published" when criteria isn't met.
RFC Hub aims to solve these issues by building an easy to use interface around all the metadata associated with technical proposals instead of containing it textually within the document itself.
The project is still under heavy development as I work on it most nights and weekends. The next big feature I'm planning is proposal templates and the ability to refer to documents as something other than RFCs (Request for Comments). E.g. a company might have a UIRFC for GUI work (User Interface RFCs), a DBADR (Database Architecture Decision Record), etc. And while there's a built-in notification system I'm still working on a Slack integration. Auth works by sending tokens via email but of course RFC Hub needs Google auth.
Please let me know what you think!
Comments
This would have been very useful at my previous job. We had a gdrive folder with '2024' or '2025' with a bunch of google docs with no inter-linking between them. If you were lucky the title would be vaguely related to the topic you are working on, and maaaaaybe there'd be a link to prior work. Frequently I'd look at an RFC, see no approvals but then find out it _had_ been approved but nobody actually updated the document. Infurating.
I'm not sure the reason for friction. These are developers, they know how to use git etc, but management prefers google docs I suppose (previous iterations were confluence, then markdown on github).
Initial reaction: Looks too complicated & too niche of a problem to appeal to a sustainably large user group.
GDocs might be annoying to track who read the RFC etc. etc. but everyone is familiar with it.
I write RFCs, I share RFCs and your tool seems to require a substantial amount of buy in
- register
- unclear what the writing experience is
- outdated / overloaded UI
The last RFC I wrote was in hackmd (https://hackmd.io/Jjy-afCWS4CAFlHa62anMQ) because
- I wanted Markdown to store the RFC in git eventually
- Google Docs has issues with Markdown rouundtrips
- I didn't want to use git to write with VSCode (although... I actually did. I let CLaude Code write most of the RFC under my guidance, then put it into hackmd for easy sharing)
I hope the feedback helps!