[Members] XEP-0001 Changes

Kevin Smith kevin at kismith.co.uk
Tue Mar 4 13:39:13 UTC 2014


I promised feedback so ...

On Wed, Feb 26, 2014 at 1:17 PM, Dave Cridland <dave at cridland.net> wrote:
sections, "XMPP Council" has been replaced by "Approving
> Body".

This seems fine

>     2) The timeouts for objecting has been removed, and replaced by...

"+  <p>Within 14 days, the Chair of the Approving Body shall poll
members of the Approving Body. "

This isn't consistent with what we currently do (I think it's further
from what we currently do than the current text is)


"In rare cases, the Approving Body may decide that the wrong Approving
Body may have been chosen. If the Approving Body is in doubt, the XSF
Board shall determine the correct Approving Body.</p>"

In what case is this ambiguous? The only case I can think of where the
AB may be in doubt is where the AB is not the thing in doubt, but the
type is.

I'm concerned that the current text seems to be suggesting that the
Board can decide that the AB for a Standards-Track XEP is in doubt and
wants to approve it itself.

What we currently do is essentially that we shove it on the agenda for
the meeting following a reasonable time having passed since submission
(so 5 minutes before the next meeting doesn't count), and then there
is a 14day timer in which people ~vote.

I think this breaks down as the current (not proposed) text plus +
"and will then vote within the usual voting period of the AB" or such.

>     4) Changed the Approving Body for the Humorous XEPs to the Editor.

The Council has (loosely) approved Humorous XEPs in the past. I am not
happy at the thought of the Editor team being an AB, even for
Humorous.

-  <p>Note well that no special criteria (other than acceptance by the
XMPP Council and minimal formatting compliance) need to be met in
order for a XEP to be granted a status of Experimental. The granting
of Experimental status must not be construed as indicating any level
of approval by the XSF, the XMPP Council, or the XMPP developer
community. Implementation of Experimental XEPs is encouraged in an
exploratory fashion (e.g., in a proof of concept) in order to gain
experience with and iteratively improve the protocol defined therein,
but such implementations might not be appropriate for deployment in
production systems.</p>
+  <p>Note well that no special criteria (other than acceptance by the
Approving Body and minimal formatting compliance) need to be met in
order for a XEP to be granted a status of Experimental. The granting
of Experimental status must not be construed as indicating any level
of approval by the XSF, the XMPP Council, or the XMPP developer
community. Implementation of Experimental XEPs is encouraged in an
exploratory fashion (e.g., in a proof of concept) in order to gain
experience with and iteratively improve the protocol defined therein,
but such implementations might not be appropriate for deployment in
production systems.</p>

I think this isn't quite right. Experimental is always done by Council isn't it?

-  <p>If an Experimental XEP is inactive (i.e., no updated versions
are published) for a period of twelve (12) months, the XMPP Extensions
Editor shall automatically change the status of the XEP to Deferred
unless it is in the queue of XEPs under active consideration for
advancement by the XMPP Council; upon submission of an updated
version, the XMPP Extensions Editor shall change the status back to
Experimental.</p>
+  <p>If an Experimental XEP is inactive (i.e., no updated versions
are published) for a period of twelve (12) months, the XMPP Extensions
Editor shall automatically change the status of the XEP to Deferred
unless it is in the queue of XEPs under active consideration for
advancement by the Approving Body; upon submission of an updated
version, the XMPP Extensions Editor shall change the status back to
Experimental.</p>

Similarly. I think changing Council to AB where the AB is exclusively
the Council removes clarity rather than adds it.

I think there are other things worth changing. I don't see why we need
xep1 to define the path in Git of XEPs, for example.

/K


More information about the Members mailing list