XSF Communications Team - 2025-04-05


  1. Mari0

    > Mari0, ralphm: I emailed the author. Well done. Thx

  2. emus

    > Yup .. we just need cal0pteryx and emus thumbs up 😬 👍

  3. emus

    Hey all, I will sit down now and start releasing. Unfortunately, I did not sent the recent newsletters. I would like to sent then first now anyway. Would you agree with that?

  4. emus

    Furthermore, has the XSF decided not to promote the X channel anymore. With this decision, I will also not duplicate our Mastodon posts or so there anymore. I hope that is fine with everyone.

  5. singpolyma

    If you won't do it is there space to get someone else access to the X account so the newsletter can still be posted there?

  6. ralphm

    This. I'd be happy to do so

  7. Kris

    This was an XSF decision, no? So wouldn't that go directly agaist that decision?

  8. Kris

    I think it's best for people to share it on their private X acounts if they want.

  9. emus

    Yes, one can still post there according to the decision. But I don't want to invest resources in a platform that has been officially rejected by the organisation. We can rather make accounts else where.

  10. emus

    So, I hear no rejection to posting the old news for historical reasons?

  11. cal0pteryx

    > So, I hear no rejection to posting the old news for historical reasons? No why not

  12. cal0pteryx

    Kris: the decision was only about linking from xmpp.org or the newsletter

  13. singpolyma

    > This was an XSF decision, no? So wouldn't that go directly agaist that decision? No. The XSF decided to stop linking to the X account from XMPP.org but desired that content still be posted to the account if possible

  14. emus

    >> This was an XSF decision, no? So wouldn't that go directly agaist that decision? > No. The XSF decided to stop linking to the X account from XMPP.org but desired that content still be posted to the account if possible But I object to invest further. People are getting into fights and serious accusations over this and I'd rather stay out and want to keep this away from the team. It's in my view also a not helpful half-baked decision 😕 Anyway, I will be posting missing news now

  15. emus

    I squash and merge the newsletter now ok?

  16. Martin

    The newsletters of November, December and January just arrived in my inbox. 🫣

  17. emus

    I know, it was intentional

  18. singpolyma

    >>> This was an XSF decision, no? So wouldn't that go directly agaist that decision? >> No. The XSF decided to stop linking to the X account from XMPP.org but desired that content still be posted to the account if possible > But I object to invest further. People are getting into fights and serious accusations over this and I'd rather stay out and want to keep this away from the team. > > It's in my view also a not helpful half-baked decision 😕 > > Anyway, I will be posting missing news now Yes it's fine for you personally to stay out of course but we have several volunteers to take over handling that account so probably just need to get credentials to one of them

  19. emus

    You can do so, but this would not be an action that the XSF CommTeam is responsible for. Reach out to Kev for creds

  20. Martin

    > I know, it was intentional Why?

  21. Martin

    Now February and March were also resent.

  22. emus

    >> I know, it was intentional > Why? 👎

  23. emus

    >> I know, it was intentional > Why? Completeness

  24. emus

    > Now February and March were also resent. February hasnt been sent and March has been published

  25. Martin

    >> Why? > 👎 ?

  26. coleman

    I appreciate the back issues of the newsletter. But beware: sending many emails can curse your deliverability with the various spam monitoring mafias

  27. coleman

    Thanks for restarting the newsletter though

  28. emus

    > >> Why? > > 👎 > ? Sorry, I was on mobile and instead of pulling for quote, it triggered the reaction. Was not intended.

  29. emus

    > I appreciate the back issues of the newsletter. But beware: sending many emails can curse your deliverability with the various spam monitoring mafias Yes I know.

  30. badrihippo

    Hi all! Small correction on the latest newsletter: it mentions the FOSSY CfP is open till May 5th but the page itself seems to indicate April 28th as the deadline: https://2025.fossy.us/call-for-proposals/

  31. emus

    Would you like to push a PR?

  32. badrihippo

    Sure

  33. badrihippo

    https://github.com/xsf/xmpp.org/milestone/3 this one?

  34. badrihippo

    https://github.com/xsf/xmpp.org/ this one?

  35. emus

    https://github.com/xsf/xmpp.org/blob/master/content/blog/newsletter/2025-04-05-newsletter.md

  36. badrihippo

    Done: https://github.com/xsf/xmpp.org/pull/1506

  37. emus

    Thanks!

  38. badrihippo

    You're welcome 🙂

  39. badrihippo

    By the way what's the procedure if I want to help with the newsletter? Do I just start editing that HedgeDoc pad or

  40. emus

    Maybe arranngge with gnemmi as he is pushing things at the moment. Maybe you can help him to take some work of his shoulders. But basicallly yes