I can't comment on @withoutboats's perspective. Instead, I'll share my own: Writing an RFC isn't fun. The back-and-forth on an RFC thread is even less fun. Even if the conversation is 100% positive and constructive, it's just not enjoyable to me. I'd rather spend my precious free time doing something else.
I think it's great you're asking these questions, @binomial0, but I'd like to follow up with:
- How can we make the RFC process less draining overall?
My initial thoughts on some steps in the right direction include:
- Embracing the MCP process.
- Banning MCP/RFC discussions from GitHub. GitHub is a terrible forum, IMO. At my $dayjob we use Google Docs with comments to do our designing+discussing. It's not perfect, but it's infinitely better than GitHub. There are other alternatives too; I'm not saying we should move to Google Docs. I'm just saying we should move away from GitHub.
- When an MCP/RFC is posted, linking to all the discussions that have occurred in the past. So much time is spent rehashing the same points. If people could discover past discussions more easily I think it would help. (side note: these discussions need to be easily searchable; GitHub and even Discourse have pretty terrible search and discovery).