Re: [Standards] NEW: XEP-0412 (XMPP Compliance Suites 2019)
Hi Jonas, To clarify: - There is absolutely no indication that anyone tried to pressure anyone into doing anything. Board's comment can be seen as to wanting to prevent such leverage to become possible in the future, by establishing a precedent of keeping prematurely published XEPS published. - Board had another reason for wanting the prematurely published XEP to be retracted: by publishing a XEP, the XSF might (or even: "intends to") trigger third parties to start spending resources (on implementing the XEP). When a XEP is published by mistake, it is therefor important to reduce the risk of more people starting to base work off of it, by retracting it as soon as possible. Thank you for flagging this, and act swiftly to rectify. Mistakes happen. It's how they're followed up on that characterizes them. Regards, Guus On Thu, 20 Dec 2018 at 17:37, Dave Cridland wrote: > Hi Jonas, > > Thanks for sorting this out, and my apologies for the formal process hoops > to jump through. > > I'm amazed this has never happened before, actually. > > Dave. > > On Thu, 20 Dec 2018 at 16:13, Jonas Schäfer wrote: > >> Hi list, >> >> >> I published this specification (XEP-0412) ahead of time. The vote of >> council >> (which I am embarrassingly part of) has not yet completed. >> >> While the stance of Council (including the member who hasn’t voted yet >> and me) >> on this matter was to wait it out and deal with the issue of retraction >> should >> the vote be a -1, the Board has decided to prevent to set a precedent by >> the >> premature publication, which could be used by the Editor to exert >> pressure on >> the not-yet-voted Council members. >> >> I personally fully support the decision of the Board. >> >> I understand the delicacy of the situation especially since in this play, >> I’m >> both the Editor *and* the Author of the specification; I do not want to >> be >> seen as someone who would abuse any role like that, so I’m happy to >> execute >> the Board’s ruling. >> >> I’d also like to sincerely apologize especially to Kev whose vote I have >> forgotten (actually I was 100% sure that everyone had voted, and only >> while >> checking results for other votes I came across the "on list" from Kev :() >> and >> to the community for the extra noise and possible temporary confusion and >> misguidance due to the published compliance suites you had to endure. I’d >> also >> like to apologize for not bringing this matter up to Board immediately. >> >> The specification has been un-published and replaced with a tombstone XEP >> (the >> build is still in progress; the website will thus be updated shortly). It >> will >> stay a tombstone should Kevin decide to vote -1, and it will be replaced >> with >> the actual XEP again should Kevin decide to vote 1 or 0. >> >> >> kind regards, >> Jonas___ >> Standards mailing list >> Info: https://mail.jabber.org/mailman/listinfo/standards >> Unsubscribe: standards-unsubscr...@xmpp.org >> ___ >> > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] NEW: XEP-0412 (XMPP Compliance Suites 2019)
Hi Jonas, Thanks for sorting this out, and my apologies for the formal process hoops to jump through. I'm amazed this has never happened before, actually. Dave. On Thu, 20 Dec 2018 at 16:13, Jonas Schäfer wrote: > Hi list, > > > I published this specification (XEP-0412) ahead of time. The vote of > council > (which I am embarrassingly part of) has not yet completed. > > While the stance of Council (including the member who hasn’t voted yet and > me) > on this matter was to wait it out and deal with the issue of retraction > should > the vote be a -1, the Board has decided to prevent to set a precedent by > the > premature publication, which could be used by the Editor to exert pressure > on > the not-yet-voted Council members. > > I personally fully support the decision of the Board. > > I understand the delicacy of the situation especially since in this play, > I’m > both the Editor *and* the Author of the specification; I do not want to be > seen as someone who would abuse any role like that, so I’m happy to > execute > the Board’s ruling. > > I’d also like to sincerely apologize especially to Kev whose vote I have > forgotten (actually I was 100% sure that everyone had voted, and only > while > checking results for other votes I came across the "on list" from Kev :() > and > to the community for the extra noise and possible temporary confusion and > misguidance due to the published compliance suites you had to endure. I’d > also > like to apologize for not bringing this matter up to Board immediately. > > The specification has been un-published and replaced with a tombstone XEP > (the > build is still in progress; the website will thus be updated shortly). It > will > stay a tombstone should Kevin decide to vote -1, and it will be replaced > with > the actual XEP again should Kevin decide to vote 1 or 0. > > > kind regards, > Jonas___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] NEW: XEP-0412 (XMPP Compliance Suites 2019)
Hi list, I published this specification (XEP-0412) ahead of time. The vote of council (which I am embarrassingly part of) has not yet completed. While the stance of Council (including the member who hasn’t voted yet and me) on this matter was to wait it out and deal with the issue of retraction should the vote be a -1, the Board has decided to prevent to set a precedent by the premature publication, which could be used by the Editor to exert pressure on the not-yet-voted Council members. I personally fully support the decision of the Board. I understand the delicacy of the situation especially since in this play, I’m both the Editor *and* the Author of the specification; I do not want to be seen as someone who would abuse any role like that, so I’m happy to execute the Board’s ruling. I’d also like to sincerely apologize especially to Kev whose vote I have forgotten (actually I was 100% sure that everyone had voted, and only while checking results for other votes I came across the "on list" from Kev :() and to the community for the extra noise and possible temporary confusion and misguidance due to the published compliance suites you had to endure. I’d also like to apologize for not bringing this matter up to Board immediately. The specification has been un-published and replaced with a tombstone XEP (the build is still in progress; the website will thus be updated shortly). It will stay a tombstone should Kevin decide to vote -1, and it will be replaced with the actual XEP again should Kevin decide to vote 1 or 0. kind regards, Jonas signature.asc Description: This is a digitally signed message part. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] NEW: XEP-0412 (XMPP Compliance Suites 2019)
Version 0.1.0 of XEP-0412 (XMPP Compliance Suites 2019) has been released. Abstract: This document defines XMPP protocol compliance levels. Changelog: Accepted by vote of Council on 2018-12-19. (XEP Editor (jsc)) URL: https://xmpp.org/extensions/xep-0412.html Note: The information in the XEP list at https://xmpp.org/extensions/ is updated by a separate automated process and may be stale at the time this email is sent. The XEP documents linked herein are up-to- date. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
