XSF Discussion - 2018-01-13


  1. Neustradamus

    After a verification on xmpp.org, I found that the list has been changed, in the past when I managed the list, it will be more important. Psi and Psi+ have not in list, why? https://xmpp.org/software/clients.html

  2. Neustradamus

    http://psi-im.org/ + http://psi-plus.com/

  3. Neustradamus

    Really strange for historical XMPP clients

  4. Neustradamus

    Metronome is not listed too on https://xmpp.org/software/servers.html https://metronome.im/

  5. Neustradamus

    It was before ;)

  6. moparisthebest

    Neustradamus: they adopted an annual renewal policy

  7. moparisthebest

    And apparently those weren't renewed

  8. moparisthebest

    edhelas, la|r|ma: FYI this is the conversations fork that does webrtc audio and video https://github.com/spreedbox/Spreedbox-Android

  9. moparisthebest

    But requires this server for signaling https://github.com/strukturag/spreed-webrtc/

  10. moparisthebest

    la|r|ma: also do you still have that dino audio code

  11. vanitasvitae

    moparisthebest, interesting...

  12. zinid

    edhelas, is it normal I see movim c2s connection on my server even though I closed movim yesterday?

  13. edhelas

    zinid yes it stays open 12 or24h normally

  14. zinid

    edhelas, ok

  15. edhelas

    except if you disconnect

  16. zinid

    disconnect? I have already disconnected 🙂

  17. zinid

    disconnect what?

  18. zinid

    I can only kill the session on the server

  19. edhelas

    closing the tab != disconnect

  20. Ge0rG

    It's awesome how the debates about avatar XEPs and bookmark XEPs got mixed up on standards@ now.

  21. Ge0rG

    I'll just store my avatar in private XML from now on.

  22. SamWhited

    I'm thinking about just retracting the compliance suites and letting someone else deal with it; it's all good discussion, and some of these changes need to be made, but we'll never have compliance suites if we keep bike shedding forever and don't just put *something* through every year. By the time we finally reach consensus the goal posts have shifted and there are newer things that need to be added (like the avatar crossover XEP, which is fantastic, but didn't exist when the compliance suites should have been voted on)

  23. SamWhited

    *grumble, grumble*

  24. SamWhited

    There's basically no point to compliance suites if they can't be published in a timely manner, even if they're not perfect.

  25. Ge0rG

    SamWhited: it was a very unfortunate timing, both with the council election and the holiday season. It's really great that you have kept up pushing this, and I'm really sorry that it didn't work out as intended. I think you are doing a really good job despite all the setbacks you encountered.

  26. SamWhited

    I appreciate it; thanks.

  27. jonasw

    I fully agree with Ge0rG.

  28. jonasw

    but I’d like to mention that as the timings currently are, this will affect all compliance suites

  29. jonasw

    if anything, it’s going to get worse for the next few years if elections continue to shift

  30. Ge0rG

    jonasw: what direction do they shift in?

  31. jonasw

    laterness

  32. jonasw

    IIRC

  33. jonasw

    (I haven’t checked; I just thought that someone mentioned that during last election season)

  34. Ge0rG

    jonasw: that's making things better, as soon as the election happens after new year's eve.

  35. jonasw

    yeah, but that’ll take some time

  36. Ge0rG

    Maybe it would just be better to have the next Compliance Suite ready by Dec 1st.

  37. jonasw

    by the end of council term?

  38. Ge0rG

    Hm.

  39. SamWhited

    I think I had these ready and was trying to get a vote before that, but yah, apparently it needs to be even earlier

  40. SamWhited

    Doesn't matter though; earlier next year is easy, this year is my concern.

  41. Ge0rG

    And then there are the moments where the gremium can't meet due to unforeseen events.

  42. jonasw

    SamWhited, as mentioned in council@, if you and kev can agree, it doesn’t matter what the community thinks (even if that seems harsh). If it’s councils decision that vcard/avatar/private-xml/pep things shall be resolved in the next suites and for now we say "you’ll need both" (or whatever solution you come up with), it can be voted on next meeting I think

  43. Ge0rG

    Yeah, just let the list discussion go on and merge Kev's PR <https://github.com/xsf/xeps/pull/569>

  44. daniel

    should i mention that you can't implement 223 right now?

  45. daniel

    because it will just get rejected by the server

  46. daniel

    because of the unregistered publish-option

  47. moparisthebest

    What if some new xep0001 changes were voted in just for compliance suites, they are published as is on Jan 1st regardless or something

  48. Zash

    force-accepting it at the end of each council term?

  49. Flow

    Simply don't restart votes?

  50. jonasw

    Flow, you mean we should remove the passage from XEP-0001 which states that outstanding votes by outgoing council are to be re-voted on by incoming council?

  51. Flow

    jonasw, yep, that's what causing trouble again and again. Simply announce the voting, and the council at the time of the announcement has X days time to vote

  52. jonasw

    that seems reasonable

  53. jonasw

    maybe bring that up with board?

  54. Flow

    jonasw, unlikely, not a top priority for me, but I would support it

  55. moparisthebest

    Zash: yes if not accepted before, Jan 1st is drop dead date