Returning to the discussion on FEPs, it might be beneficial to consider a more structured process. FEPs could progress through stages such as proposal, implementation, and approval - or something similar that suits our workflow.
A proposed FEP could proceed if it garners at least 3 ACKs without any NACKs. Any disagreements could necessitate further discussions. A resolution team, primarily consisting of project and free software representatives and possibly some members from W3C SWIGC, could facilitate this process, given their availability.
Well-received FEPs could be elevated to the status of W3C Notes, assuming no complications. Ideally, these would have at least 2 implementations and wide acceptance.
For a more formal standard, we can draw inspiration from three notable documents, which offer a structured approach to creating standards:
This is just an outline of what something can look like. FEPs already have a system, a path towards becoming a a W3C spec with note status could be the icing on the cake.
Edit: we should not think about getting W3C REC status. That is a multi year process, and needs a charter and many hoops. The specs are already REC, but some bugs could be fixed. Notes however can happen relatively easily. We should establish the exact criteria for a note and then make one for the FEP process itself, then test it with a FEP that is the most popular and that is already in use, perhaps.
Edit2: There are also W3C Group Reports, which may be a good fit for adopted FEPs. I think it just needs to be proposed as a group work item, to start the ball rolling.