XMPP Council - 2022-12-04


  1. emus

    Hello XSF Council, I would like to suggest the following point to the agenda: - Review of meaningful changes to simplify the XEP editorial processes & works to reduce work load but also reduce required amount to automate such steps.

  2. gooya

    There should be a possibility to automate XEP status and would indeed be more efficient for newsletter and status purposes. Maybe parse xep specification site once every 3 X days and compare versions for changes and list those changes in a json or text file? I have no coding experience but this seemed the most logical way for me to achieve this?

  3. gooya

    emus: There should be a possibility to automate XEP status and would indeed be more efficient for newsletter and status purposes. Maybe parse xep specification site once every 3 X days and compare versions for changes and list those changes in a json or text file? I have no coding experience but this seemed the most logical way for me to achieve this?

  4. emus

    gooya: thanks, well I cannot elaborate at all. I just wanted to encourage the topic

  5. MSavoritias (fae,ve)

    As a heads up I have been too caught up at work but i am thinking of starting this week to experiment with a pipeline at sr.ht for automatation on the editor side. With input from the editor of course. I just had too much stuff at work lately.

  6. emus

    MSavoritias (fae,ve): That sound awesome. can you write this to @board first? that would e great! we should all align first before doing any step I recommend

  7. emus

    MSavoritias (fae,ve): That sounds awesome. can you write this to @board first? that would e great! we should all align first before doing any step I recommend

  8. emus

    we also should be clear on the open issues and the work Guus started to streamline the works

  9. emus

    MSavoritias (fae,ve): let me do.this for you

  10. emus

    We will discuss this in the upcoming board meeting on thursday, too

  11. MSavoritias (fae,ve)

    emus: I can send an email tomorrow with a rough idea on what i am thinking.

  12. emus

    MSavoritias (fae,ve): cool, but better add your points to the github issue or create a new one. I informed board already about your interest.

  13. MSavoritias (fae,ve)

    emus: Thats the thing i dont have github :) Which is kind of why i wanted to do a sr.ht/codeberg thing

  14. MSavoritias (fae,ve)

    Part of it at least

  15. MSavoritias (fae,ve)

    But i can write a message to the board.

  16. emus

    No need to message board directly. Just put your thoughts to github related issues

  17. emus

    I sent a mail already :-)

  18. emus

    ahh okay I see

  19. emus

    uhm, then just text me and I will update

  20. emus

    > Thats the thing i dont have github :) > Which is kind of why i wanted to do a sr.ht/codeberg thing Okay lets have the discussion with board first before start such adventure :-)

  21. MSavoritias (fae,ve)

    Sounds good :D

  22. MSavoritias (fae,ve)

    I just wanted to have something that works first and something that can be actually useful to the people that would use it before coming up with proposals :)

  23. emus

    I unserstand

  24. emus

    I understand

  25. moparisthebest

    MSavoritias (fae,ve): well the tools need written first, where they run (GitHub/srcht/codeburg) is really an afterthought

  26. MSavoritias (fae,ve)

    I hope so.