Hi, today the current Compliance Sutie work was discussed in xsf@ and I asked again why it needs a new number vs. just updating XEP-0375. This resulted in some yak shaving, and an interesting, albeit controversial, proposal:
Can we make the "Compliance Suite" a stand-alone document that is not an XEP? Alternative solution: designate a fixed XEP number to "Current Compliance Suite". Rationale: - the Compliance Suite should help new developers navigating the zoo of XEPs, having it hidden inside that zoo is counterproductive. - there is only ever one Compliance Suite that matters at any given point in time - it would be great to have a stable link/identifier to spread to developers and reference in documentation - there are so many XEP numbers already that people lose track - We could still use the XEP editorial process to maintain the document, no need to invent (much) new bureaucracy Cons: - developers couldn't just stamp "implements XEP-0375" on their release to indicate a given level of compliance, they would rather need to write "Implements Compliance Suite 2017" - having this as a non-XEP might increase the maintenance burden or reduce the "credibility" of the document Comments? Georg
signature.asc
Description: Digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
