Today the RFCs category is under Development, but we’ve seen that often community input is desired. Moving RFCs to its own top level can help with this.
The downside is that too many top level categories also reduces the visibility.
For reference, it came up in RFC - Systemd first boot service for host provisioning - #4 by Marek_Hulan
Thoughts on this?
I’d be +1 for the top-level standalone category for RFCs, because we tend to open a second post under community. RFCs are not always for developers only.
+1
Additionally, we should try to get the feedback about yes/no/maybe regarding the RFC topic within some days - maybe a week. Of course, some features require more discussion but a general answer if the proposal make sense should be given in a pretty short time frame.
There has been some thinking on this put at RFCs-in-hiding & accepting RFCs.
We should probably distinguish between user facing and devs only RFC, so it’s clear who’s input is needed. We could define a template with suggested timeline, as it’s clearly often needed to make a decision before some deadline.
I’ll bring this thread to bigger audience and see if we could have an agreement on this.
I’ve always written RFCs for both developers and the community combined, so I’m indifferent to where I put my RFCs. If having a new section for RFCs alone should help get more views, I’m all for it.