XMPP Council - 2023-03-21

  1. pep.

    https://mail.jabber.org/pipermail/standards/2023-March/039215.html I've sent this today to clarify the situation around the PR (or complicate it rather?)

  2. pep.

    I wouldn't merge it as is but I guess I need a decision to make the new PR

  3. MattJ

    If the only blocking question now is about how to treat "updates", I doubt we'll make more progress than last time I brought it up on the list

  4. pep.

    Someone makes an executive decision?

  5. pep.

    pretty plz

  6. MattJ

    The executive decision was made in favour of (2)

  7. MattJ

    I don't want to say it was by me, because I'm the author of an implementation that already does it that way

  8. pep.

    MattJ, what was the informational text you wanted to get in, regarding pubsub and key/value store

  9. MattJ

    But Ralph probably has the most implementation experience of XEP-0060 out of anyone in the community, and he also says (2)

  10. pep.

    Can you propose wording and a place for me to add it? Or a patch

  11. MattJ

    Shall do that now

  12. pep.

    I guess I'll make a new PR and remove this one, so that council can vote on the new one next week if they want more time

  13. pep.

    And I'll include wording to define "overwrite"

  14. MattJ

    First stab at it: https://pad.nixnet.services/DoGOIieYRuSQvYzK_xIKAw

  15. pep.

    Looks good to me. You also define the order in there, so there's only a few things for me to do

  16. pep.

    That can go into implementation notes?

  17. MattJ

    It would be good to at least also clarify the couple of places it says "overwrite" too

  18. pep.


  19. pep.

    Maybe that can go in there too

  20. pep.

    Since you talk about updates already