XMPP Council - 2025-12-09


  1. dan.caseley

    Ahead of today's meeting, I'll quickly record votes I missed last week

  2. dan.caseley

    +1 on clarify muc#roomconfig_allowinvites

  3. dan.caseley

    +1 on IAP (I've reported a couple of rendering oddities to dwd, but they're non-blocking)

  4. dan.caseley

    +1 on Spam Reporting

  5. daniel

    for the record I’m also +1 on allow invites

  6. daniel

    oh. i forgot to write goffi down as a pending vote

  7. goffi

    daniel, no worries, I'm aware of my pending vote.

  8. goffi

    Btw, anybody knows why the XEP names are not properly expanded in `inbox`? I have this in the introduction of iap: `When clients (or initiating servers) connect, thanks to there is now a single waited-for round-trip after the connection itself is established, before the exchange of stanzas can occur.` note the `thanks to there`, while the source XML uses apparently correctly ` thanks to &xep0388;`.

  9. goffi

    Also the xml is not properly shown if we changes `html` for `xml` in the URL (while it works for published XEPs).

  10. Daniel

    Maybe a question for the infra team

  11. dan.caseley

    Interesting, that was one of the rendering issues I reported to dwd!

  12. dan.caseley

    Had assumed an author error

  13. Daniel

    It's time

  14. Daniel

    1) roll call

  15. dan.caseley

    Hello!

  16. goffi

    Here

  17. daniel

    singpolyma, larma?

  18. daniel

    2) Agenda bashing

  19. daniel

    probably a quick one today. I assume nothing to bash?

  20. daniel

    3) Editors update

  21. daniel

    - STABLE: XEP-0440 (SASL Channel-Binding Type Capability) - NEW: XEP-0508 (Forums)

  22. daniel

    4) Items for voting

  23. daniel

    nothing new

  24. daniel

    5) Pending votes

  25. daniel

    since dan.caseley and myself voted in between the agenda and now it's only goffi missing on iap

  26. goffi

    I'm +1 on iap

  27. larma

    > singpolyma, larma? here, but nothing to vote or aob from me anyways

  28. daniel

    6) Date of next

  29. goffi

    +1w wfm

  30. dan.caseley

    +1w wfm

  31. daniel

    we can probably do one more meeting next week and go on a ~2w holiday break after that?

  32. daniel

    +1w wmf

  33. goffi

    daniel, year that seems reasonable. I'm not sure I'll make it on 30 though.

  34. singpolyma

    +1w wfm sorry for my tardiness today

  35. daniel

    oh i meant skipping two meetings. skip the 23rd and the 30th. but yes we can discuss the next week

  36. daniel

    7) AOB

  37. Guus

    Given that we're gearing up towards a summit: maybe Council can have a think next week to see if there's any input from council to the summit that'd be desirable?

  38. Guus

    I have no concrete ideas or anything, but there's an opportunity with a bunch of relevant people sitting in the same room, soonish - if we can benefit from that in any way - lets.

  39. dan.caseley

    "Do _you_ have a XEP that you'd like to promote to stable? Council can help!"

    šŸ‘ 1
  40. daniel

    iirc i did a whole speech about that last year. but I’m happy to repeat that :-)

  41. singpolyma

    Is it worth to suggest discussing a refresh to compliance suites?

  42. Zash

    Only _you_ can prevent ~forest fires~ Deferred XEPs

  43. daniel

    i have ideas for an overhaul of the compliance suite. i hope to have something ready before summit

    šŸ‘ 1
  44. daniel

    as a basis of discussion

  45. goffi

    I think that compliance should be updated yearly, if only to say "compliant XXXX" were XXXX is not 3 years olds (even if it's the latest).

  46. daniel

    assuming no other AOB?

  47. daniel

    8) Close

  48. daniel

    Thank you all. see you next week

  49. singpolyma

    That means a lot of deferred compliance xep specs but we've discussed maybe xep isn't the way

  50. goffi

    Thanks daniel, thanks all.

  51. goffi

    Yeah maybe, let's see what @daniel has to propose, and discuss that at summit.