XSF Discussion - 2020-06-22


  1. Neustradamus

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

  2. jonas’

    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

  3. jonas’

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

  4. Neustradamus

    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)

  5. Neustradamus

    Marty McFly is here maybe

  6. jonas’

    read what I just said

  7. Neustradamus

    Yes there is a problem

  8. jonas’

    no

  9. jonas’

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

  10. Neustradamus

    It is published date

  11. jonas’

    is it?

  12. jonas’

    where is that written?

  13. Neustradamus

    The date of publication and announcement of the update

  14. jonas’

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

  15. Neustradamus

    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 0.3.2 yet

  16. Neustradamus

    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

  17. jonas’

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

  18. jonas’

    only for 0.x changes

  19. jonas’

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

  20. Neustradamus

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

  21. Neustradamus

    Hope some changes soon

  22. Neustradamus

    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.

  23. MattJ

    I had no idea

  24. jonas’

    about the name chaneg?

  25. jonas’

    about the name change?

  26. MattJ

    :)

  27. Guus

    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?

  28. Guus

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

  29. jonas’

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

  30. jonas’

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

  31. Guus

    No hill for me to die on.

  32. Guus

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

  33. jonas’

    of course not

  34. jonas’

    nobody d oes

  35. jonas’

    nobody does

  36. jonas’

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

  37. jonas’

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

  38. jonas’

    or a piece of cakhe

  39. jonas’

    or a piece of cake

  40. Guus

    Remember that the cake is a lie.

  41. jonas’

    it isn’t always!

  42. Guus

    Famous last words.

  43. jonas’

    you know it isn’t!

  44. jonas’

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

  45. Guus

    If memory recalls that was a browney!

  46. Guus

    brownie?

  47. jonas’

    no