Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-06 Thread Kevin Smith
On 1 Nov 2017, at 14:30, Peter Saint-Andre wrote: > As to the second point, it would be good to define more objective > criteria for advancement (e.g., no significant changes in 12 months, > widespread implementation and deployment, no known security issues). I’m not sure about making them formal

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-06 Thread Kevin Smith
On 1 Nov 2017, at 12:40, Matthew Wild wrote: > > On 1 November 2017 at 12:35, Matthew Wild wrote: >> As such, I've prepared a change of XEP-0001 here: >> https://github.com/mwild1/xeps/commit/9cebf36e11d5918352b49c1a3e27fec2f17d8005 > > Without my Board hat on... a couple of things jumped out a

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-06 Thread Kevin Smith
On 1 Nov 2017, at 12:35, Matthew Wild wrote: > > Guus der Kinderen recently sparked a discussion about revising our XEP > statuses for better clarity about their intention (thread at > https://mail.jabber.org/pipermail/standards/2017-September/033441.html > ). > > Although the thread contains a

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-05 Thread Jonas Wielicki
On Mittwoch, 1. November 2017 08:30:25 CET Peter Saint-Andre wrote: > On 11/1/17 6:40 AM, Matthew Wild wrote: > > [… snip by jwi …] > > 2) "In order for a XEP to advance from Stable status to Final status > > > > (version 2.0), it must be shown to be stable and well-received by the > > XMPP devel

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-05 Thread Jonas Wielicki
On Mittwoch, 1. November 2017 12:40:20 CET Matthew Wild wrote: > On 1 November 2017 at 12:35, Matthew Wild wrote: > > As such, I've prepared a change of XEP-0001 here: > > https://github.com/mwild1/xeps/commit/9cebf36e11d5918352b49c1a3e27fec2f17d > > 8005 > Without my Board hat on... a couple of t

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-05 Thread Jonas Wielicki
On Mittwoch, 1. November 2017 16:01:35 CET Philipp Hancke wrote: > Am 01.11.2017 um 13:40 schrieb Matthew Wild: > > On 1 November 2017 at 12:35, Matthew Wild wrote: > >> As such, I've prepared a change of XEP-0001 here: > >> https://github.com/mwild1/xeps/commit/9cebf36e11d5918352b49c1a3e27fec2f17

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-01 Thread Philipp Hancke
Am 01.11.2017 um 13:40 schrieb Matthew Wild: On 1 November 2017 at 12:35, Matthew Wild wrote: As such, I've prepared a change of XEP-0001 here: https://github.com/mwild1/xeps/commit/9cebf36e11d5918352b49c1a3e27fec2f17d8005 Without my Board hat on... a couple of things jumped out at me with

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-01 Thread Peter Saint-Andre
On 11/1/17 6:40 AM, Matthew Wild wrote: > On 1 November 2017 at 12:35, Matthew Wild wrote: >> As such, I've prepared a change of XEP-0001 here: >> https://github.com/mwild1/xeps/commit/9cebf36e11d5918352b49c1a3e27fec2f17d8005 > > Without my Board hat on... a couple of things jumped out at me with

Re: [Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-01 Thread Matthew Wild
On 1 November 2017 at 12:35, Matthew Wild wrote: > As such, I've prepared a change of XEP-0001 here: > https://github.com/mwild1/xeps/commit/9cebf36e11d5918352b49c1a3e27fec2f17d8005 Without my Board hat on... a couple of things jumped out at me with this change (which currently is mostly a simple

[Standards] Renaming XEP status 'Draft' to 'Stable'

2017-11-01 Thread Matthew Wild
Guus der Kinderen recently sparked a discussion about revising our XEP statuses for better clarity about their intention (thread at https://mail.jabber.org/pipermail/standards/2017-September/033441.html ). Although the thread contains a number of points made by various people, te proposal emerged