Re: [Standards] LAST CALL: XEP-0387 (XMPP Compliance Suites 2017)

2017-11-01 Thread Sam Whited
On Wed, Nov 1, 2017, at 11:47, Jonas Wielicki wrote: > On Montag, 16. Oktober 2017 18:38:46 CET Jonas Wielicki wrote: > > This message constitutes notice of a Last Call for comments on > > XEP-0387. What would folks think about changing the title of these compliance suites to "2018" and then

[Standards] 2017-11-01 XSF Council Minutes

2017-11-01 Thread JC Brand
2017-11-01 XSF Council Minutes -- Chat Logs: http://logs.xmpp.org/council/2017-11-01 Chair: * Emmanuel Gil Peyrot (Link Mauve) Present: * Sam Whited (SamWhited) * Dave Cridland (dwd) * Daniel Gultsch (daniel) Minute taker: * JC Brand (jcbrand) --- 1) XEP-0146

Re: [Standards] LAST CALL: XEP-0387 (XMPP Compliance Suites 2017)

2017-11-01 Thread Jonas Wielicki
On Montag, 16. Oktober 2017 18:38:46 CET Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on > XEP-0387. > > Abstract: > This document defines XMPP protocol compliance levels for 2017. > > This Last Call begins today and shall end at the close of business on >

Re: [Standards] LAST CALL: XEP-0286 (Mobile Considerations on LTE Networks)

2017-11-01 Thread Jonas Wielicki
On Freitag, 20. Oktober 2017 11:57:37 CET Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on > XEP-0286. > > Title: Mobile Considerations on LTE Networks > Abstract: > This document provides background information for XMPP implementors > concerned with mobile

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

2017-11-01 Thread Jonas Wielicki
On Montag, 16. Oktober 2017 18:38:45 CET Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on > XEP-0313. > > Abstract: > This document defines a protocol to query and control an archive of > messages stored on a server. > > This Last Call begins today and shall

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

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

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

[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