[Standards] On making "Compliance Suite 20xx" a Non-XEP

Nicolas Vérité nicolas.verite at gmail.com
Wed Feb 8 13:22:59 UTC 2017


On Wed, Feb 8, 2017 at 10:29 AM, Dave Cridland <dave at cridland.net> wrote:

> On 7 February 2017 at 16:25, Georg Lukas <georg at op-co.de> wrote:
>
Also, who gets to make changes? How are those agreed?
>

Council, like all XEPs, not much doubt about it. Right?


> All a XEP is, is simply a document with a process wrapped around it.
>

And it’s good, let’s just keep it, and have on doubt about it?


> I'm *all* in favour of linking directly into it, and our boilerplate
> sections are all down at the bottom so they're quick to dive into.
>
> We shouldn't be referring to XEP-0375, really, we should be referring
> to the (deliberately) "Marketing" terms of "Core Server 2017" and so
> on - that's why we created those terms. These need links on the
> website directly into the document, and perhaps some user
> documentation around them.
>

Yes, it is all about lowering the barrier of entry for server+client+… devs.

-- 
Nicolas Vérité (Nÿco)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170208/a9eaeedb/attachment.html>


More information about the Standards mailing list