[Standards] Re: XSF Process Change Proposals

I feel the proposed use of Proposed is a little weird here. Right now, Proposed only really means "Last Call issued". I know that we do have 5 XEPs in Proposed state right now (3 of which had their last call more than a year ago) and those should probably either be moved to Stable or back to Experimental soonish. I personally would rather get rid of this state entirely, as it really isn't a state that has any meaning. In my mind the current Experimental state is somewhat similar to a wg- adopted I-D in IETF: it's no longer a personal endeavor of an individual, but rather something we work on together to improve. I don't support the notion of individual I-D being an Experimental XEP, because we do give significant exposure to Experimental XEPs. I'm not saying that everything that is Experimental right now meets this bar and I would argue that is actually a problem: We do have a bunch of "dead" XEPs where the author at some point wrote some stuff down without hugely consulting if that's actually what people - including themselves - want or need, and so they eventually abandon those XEPs themselves - typically without officially retracting it. Those XEPs add to the fact that people always complain about the hundreds of XEPs and uncertainty what to actually implement. So in line with your proposal, here's my suggestion: - Make what is currently Inbox/ProtoXEP a proper own state:    - No requirements, no number assigned, but visible and published on XSF websites if you know the link. Updates announced to standards list.   - Introduce also some rule for naming so that there is no collision on names: like the IETF, have each inbox specification (file) name prefixed with the author name.   - When a XEP is moved from inbox to regular and gets a number assigned, keep a redirect in the inbox.   - XEPs are proposed to Council not by adding it to the Inbox, but by explicit email - Rename Experimental because the name is bad. I would suggest something like "Adopted", but I leave that to a native speaker. We can also reuse the term Proposed here, but given at has an entirely different meaning, that seems odd.   - Maybe add some clarification wording that this means that both Council and the author considers this XEP to be worth to work on by the wider community (either by suggesting changes to the XEP or through experimental implementations) - Stop using the Proposed state completely OR be more rigid to move XEPs back to Experimental if they are not moved to Stable. - Lower the bar for Stable (doesn't strictly need to be fully implemented if there is consensus that the stuff should work and be fine) - Move things to Final when we agree we don't want to do any changes to it that are not backwards compatible and also the requirements from XEP-0001 are fulfilled (2 implementations, 6 months without changes). Does that make sense? Marvin Side note: I feel that IPR related concerns could be largely addressed by a Note Well or other explicit wording that the Standards mailing list and XSF Wiki are covered by the IPR policy and wouldn't strictly need changes to the standards process, but I agree that having a somewhat reasonable equivalent to IETFs individual I-D still makes sense. On Fri, 2026-05-15 at 10:42 +0100, Dave Cridland wrote: