Comment by badmonster
Comment by badmonster 11 hours ago
This addresses a real pain point in technical organizations! I'm curious about your approach to proposal versioning and diff tracking. Since RFCs often go through multiple iterations based on feedback, how does RFC Hub handle showing the evolution of a proposal over time?
Also, you mentioned integration with notification systems - have you considered webhook support or API integrations so teams could build custom workflows (e.g., automatically creating Jira tickets when an RFC reaches a certain approval threshold, or triggering CI/CD pipeline reviews)?
Each proposal has a revision history that can be viewed so that all comments have context at that point in time:
https://rfchub.app/rfchub/rfc1-org-batch-markdown-exporter-j...
Unfortunately it means there's no fancy CRDT system: no multiplayer edits for example.
I haven't looked into webhooks yet or browser notifications. That's all stuff that I would build when left to my own devices but I want more user feedback on basic functionality.