XSF Discussion - 2020-06-22

https://xmpp.org/extensions/xep-0390.html date problem no?

Neustradamus, depends if you want to go by the date of the development of the change or by the date of the merge of the change

if the authors provide a revision block, we generally use the former

https://xmpp.org/extensions/xep-0390.html Version 0.3.2 (2018-03-05) Explain that ASCII Seperators are only invalid in XML 1.0, but not in XML 1.1. fs Version 0.3.1 (2020-04-28) Add another xml:lang example fs Version 0.3.0 (2018-10-01) Defer due to lack of activity. XEP Editor (jsc)

Marty McFly is here maybe

read what I just said

Yes there is a problem

no

It looks like a problem to you, but I don’t consider it a problem

It is published date

is it?

where is that written?

The date of publication and announcement of the update

I do not have that at hand, can you show me where it specifically says that this is a date of publication?

From Standards ML: https://mail.jabber.org/pipermail/standards/2020-June/ Version 0.3.1 of XEP-0390 (Entity Capabilities 2.0) has been released. Sun Jun 14 13:05:09 UTC 2020 And no 0.3.2 yet ✏

we do not send emails for 0.x.y changes anymore

only for 0.x changes

reduces noise, since 0.x.y are editorial only

I think that a lot of people can see the problems: no emails, and date problems.

Hope some changes soon

If there is a problem about XEP update announcements on Standards ML -> time to create a new list on XMPP.org: xeps@lists.xmpp.org (for example). Do not forget: time to move all jabber.org lists to xmpp.org. Recall, it is XMPP since 2004 and the XMPP Standards Foundation since 2007.

I had no idea

about the name change? ✏

:)

Changing the address of the mailing list for no reason other than referring to 'xmpp' rather than 'jabber' will probably introduce more problems than that it solves. I'd advice against that. If we're going to spin off a new list from 'standards' then we might, but isn't the proposed 'xeps' a pretty much identical (yet potentially more verbose) equivalent?

Subscribing to the source repository might provide people that are interested in the higher verbosity a suitable alternative.

I actually thought about something like xep-announce@, which would be a read-only fanout of fully verbose XEP announcements, no discussion

but then I came to the same conclusion as you, Guus :)

No hill for me to die on.

I'd not like a rename of the list though.

of course not

nobody does ✏

and I don’t suppose it’ll happen, at least not from my side with my iteam hat on

compared to that, moving from github to gitlab is a walk in a park

or a piece of cake ✏

Remember that the cake is a lie.

it isn’t always!

Famous last words.

you know it isn’t!

or at least that I can produe rather photorealistic renderings of cake

If memory recalls that was a browney!

brownie?

no