XSF Discussion - 2023-06-12

  1. Alex

    A reminder that we have our Member meeting today @19:00 UTC When you are a XSF member and have not vote yet, then please take some time and talk to Memberbot until our meeting starts today. Thanks

  2. Zash


    🗳 1
  3. jonas’

    Alex, thank you for the reminder! :)

  4. Alex

    hey guys, its meeting time

  5. Alex

    lets start in 2 minutes

  6. Alex bangs the gavel

  7. Alex

    here is our agenda for today: https://wiki.xmpp.org/web/Meeting-Minutes-2023-06-12

  8. Alex

    1) Call for Quorum

  9. Alex

    as you can see 38 XSF members voted via proxy, so we have a quorum

  10. Alex

    2) Items Subject to a Vote

  11. Alex

    New and Returning members, you can see all applications here: https://wiki.xmpp.org/web/Membership_Applications_Q2_2023

  12. Alex

    3) Opportunity for XSF Members to Vote in the Meeting

  13. Alex

    any members here who have not voted yet and want to vote during out meeting now?

  14. Alex

    looks like there are none

  15. Alex

    I will start working on the results now

  16. Alex

    4) Announcement of Voting Results

  17. Zash


  18. Alex

    when you reload the page at: https://wiki.xmpp.org/web/Meeting-Minutes-2023-06-12 you can see the results

  19. Alex

    all applicants and reappliers are accepted, congrats to everyone

  20. Alex

    5) Any Other Business?

  21. Alex

    looks like there is none

  22. Alex

    6) Formal Adjournment

  23. Alex

    I motion that we adjourn

  24. Guus


  25. Alex


  26. Alex bangs the gavel

  27. Guus

    Thanks once again Alex! Happy to see everyone voted in!

  28. Zash

    Thanks Alex :)

  29. Zash

    Congrats all!

  30. Holger


  31. cal0pteryx


  32. lovetox

    larma, did you consider the use case of replying not to an entire message for XEP 0461?

  33. lovetox

    i hear our users asking for that the minute i implement this

  34. lovetox

    they will consider it a regression to what they have now ..

  35. lovetox

    seems easily fixed though, simply include a "start" and "end" element, inside the <reply>