XMPP Council - 2017-06-02


  1. daniel

    Since it's ultimately a decision for the council to make it might be good if some of you would participate in the discussion Kev and I are having right now on whether omemo-next should be developed in xep-0384 or if it should live in its own xep

  2. Kev

    I think making 0.0.3 (or whatever the number is) exactly what's currently deployed, so there's a stable published version that people can choose to implement and interop with, and then making further improvements to 0.0.4 and later is a reasonable compromise. I don't think it's perfect, but it seems to address the desires of both those who want a stable published version that reflects reality and can be implemented for current interop, and those who think that 384 needs to act like a normal standards track XEP with the momentum behind it.

  3. Kev

    It probably means inviting an additional author for 0.0.4 (or whatever), as I don't think Andy particularly wants to do standards work beyond specifying what's out there already.

  4. Kev

    I could be wrong, naturally, but I'm pretty sure he said that in a previous mail in the threads.

  5. daniel

    Kev: yes as I already said merging my pr as 0.3 is a compromise I can live with. But a) it's not really perfect for me either because it doesn't allow me to publish some small non breaking changes to '0.3' that I have in mind and will also push into the implementations. But I guess that's how compromises work b) I already know your opinion and I was asking council to participate in the discussion

  6. daniel

    Kev: i think you are correct about andy

  7. Kev

    Right. I was confirming that I think it's a workable compromise too, and summarising for anyone who hasn't been following the list.

  8. daniel

    Kev: oh OK. I see

  9. Kev

    Plus I like the sound of my own voice, so that too.

  10. daniel

    Since I already mentioned it the 'small non breaking change' I'm talking about is documenting a strategy (using publish options) to change the access model of the pep node to open and the ability to use it in mucs without the requirement to have mutual presence subscription with everyone.

  11. daniel

    That's like the current thing I'm working on

  12. Kev

    So get that is as 0.0.4 before 0.0.5 is more radical?

  13. SamWhited

    That all seems reasonable to me; I like it better than having yet another historical xep.

  14. daniel

    Kev: if that is something that is OK with everyone

  15. daniel

    Also it puts me under some time pressure but I can work with tag

  16. daniel

    *that