On Wed, Feb 8, 2017 at 10:29 AM, Dave Cridland <[email protected]> wrote:
> On 7 February 2017 at 16:25, Georg Lukas <[email protected]> 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)
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
