XMPP Council - 2023-11-08

  1. jonas’

    yeah, xep-0001 implies (to me) that standards track implies council

  2. jonas’

    actually assigning the approving body seemed, to me, to be a part of the editor's job: you do the same when protoxeps are submitted.

  3. jonas’

    however, I can see how, as an editor, you might want to seek additional support when changing the approver after acceptance

  4. daniel

    Hi. I didn't make it back to my computer in time for the meeting. I'm here but only on mobile. I'll be going through the agenda and ask for your votes but for anyone following along in the spreadsheet please not that I'll be updating that once I get back home

  5. daniel

    It's time

  6. daniel

    1) roll call

  7. Ge0rG ,o/

  8. moparisthebest


  9. daniel

    Is larma still on vacation?

  10. daniel

    2) agenda bashing No bashing necessary I assume

  11. daniel

    3) Editors update A few new proto xeps - UPDATED: XEP-0377 Spam Reporting (https://xmpp.org/extensions/xep-0377.html) - UPDATED: XEP-0424 Message Retraction (https://xmpp.org/extensions/xep-0424.html) - UPDATED: XEP-0458 Community Code of Conduct (https://xmpp.org/extensions/xep-0458.html) - Proposed XMPP Extension: HTTP Online Meetings (https://xmpp.org/extensions/inbox/xep-http_online_meetings.html) - Proposed XMPP Extension: Communicate & Ask to AI (https://xmpp.org/extensions/inbox/xep-ai.html)

  12. daniel

    4) Items for voting

  13. daniel

    a) Proposed XMPP Extension: HTTP Online Meetings (https://xmpp.org/extensions/inbox/xep-http_online_meetings.html)

  14. daniel

    On list

  15. Ge0rG


  16. daniel


  17. moparisthebest

    On list

  18. daniel

    b) Proposed XMPP Extension: Communicate & Ask to AI (https://xmpp.org/extensions/inbox/xep-ai.html)

  19. daniel

    On list

  20. Ge0rG


  21. larma

    Sorry, here now.

  22. moparisthebest

    Marking your messages to the bot is odd, marking messages from the bot seems helpful, the rest is also odd but I see no reason not to +1 it I guess

  23. larma

    On-list for both

  24. daniel

    c) XEP-0060: Release version 1.25.1 (https://github.com/xsf/xeps/pull/1293)

  25. daniel

    On list

  26. moparisthebest


  27. larma

    Comment on a): There is an overlap in features with Call Invites XEP-0482. Comment on b): I think this can't be implemented as is without having further knowledge about the bot, as model is required when sending to the bot, but there is no way to discover valid values.

  28. larma

    c): +1

  29. daniel


  30. daniel

    larma: I think part(s) of http online meetings was even written before call invites. So maybe the author doesn't even know about the overlap

  31. daniel

    Maybe we can resolve the with a friendly chat

  32. daniel

    Instead of blocking the xep (not implying you were going to block)

  33. larma

    daniel: yes, that also wouldn't be a reason for me to veto at this point

  34. Ge0rG


  35. daniel

    d) XEP-0045: roominfo_changesubject does not exist (https://github.com/xsf/xeps/pull/1292)

  36. daniel


  37. moparisthebest


  38. larma


  39. Ge0rG


  40. daniel

    e) XEP-0402: Replace arbitrary max items with 'max' (https://github.com/xsf/xeps/pull/1278)

  41. daniel


  42. moparisthebest


  43. larma


  44. Ge0rG

    we added the `max` syntax into 0060 a year or so ago?

  45. Ge0rG


  46. Ge0rG

    Version 1.20.0 (2021-06-08): Add integer-or-max datatype to use with Data Forms Validation.

  47. Ge0rG

    there is no schema for the form, and I suppose it's a text field, so should be consistent

  48. daniel

    f) Add Council as approver to all Standards Track XEPs where it was missing (https://github.com/xsf/xeps/pull/1265)

  49. daniel


  50. daniel

    I think this could be considered editorial

  51. moparisthebest

    +1, editorial, please do not bump versions etc

  52. Ge0rG

    +1 for accepting and +1 for editorial-only-change

  53. moparisthebest

    imho this was just an editor mistake, new tooling checks that it doesn't happen into future

  54. daniel


  55. daniel

    moparisthebest: by the way I think the current tooling doesn't work well when multiple xeps are being changed

  56. Kev

    Editorial doesn't mean that the version doesn't get bumped, BTW.

  57. Kev

    Every change to a published XEP, editorial or not, needs the version bumped.

  58. daniel

    larma: do you have a vote for (f)?

  59. moparisthebest

    I would super advise not to bump versions, but that's your business

  60. MattJ

    I agree that editorial changes should bump versions, but this is not even that IMHO

  61. MattJ

    Just an oversight in the metadata

  62. moparisthebest

    Note the same change needs made for a bunch of other XEPs where the body should be board and editor

  63. moparisthebest

    > Just an oversight in the metadata +1

  64. daniel

    We are coming up on our time limit so I'm going to move on

  65. daniel

    5) pending votes

  66. daniel


  67. daniel

    6) date of next

  68. daniel

    +1w wfm

  69. Ge0rG

    +1w wfm

  70. moparisthebest

    +2w wfm, +1 I'll be unavailable

  71. daniel

    moparisthebest: noted

  72. daniel

    7) AOB

  73. moparisthebest

    Nothing here

  74. daniel

    8) close

  75. daniel

    Thank you all

  76. moparisthebest

    Thanks daniel !

  77. larma

    daniel: got disconnected. +1 on f), +1w wfm