XSF Communications Team - 2025-05-04


  1. emus

    badrihippo, cal0pteryx: We actually also have an article section, right?

  2. emus

    gnemmi: Shall I call for review / setup the PR?

  3. badrihippo

    emus, I didn't think the NLnet grants quite qualified as an article...

  4. badrihippo

    Though I suppose they could if that's how you do it

  5. emus

    Ok, yeah spftware is fine too

    πŸ‘πŸΎοΈ 1
  6. badrihippo

    By the way emus if you're adding the "Fiscal Host" section can you use the new Prav link https://opencollective.com/pravapp rather than https://opencollective.com/prav-ios? We (Prav) messed up and got the iOS thing as a separate project but "pravapp" is where we've consolidated all our other fundraisers

  7. emus

    Yes, do as you think its correct

  8. badrihippo

    There's no fiscal host section yet in the current draft; should I add one? I can copy over from last newsletter and cross-check (assuming there's no automated way this happens)

  9. gnemmi

    > badrihippo, cal0pteryx: We actually also have an article section, right? We do. And NLnet grants go under ## Software news *only after the project makes an official announcement* on their respective blogs or news outlets

  10. gnemmi

    See Monal on https://xmpp.org/2024/07/the-xmpp-newsletter-june-2024/ and https://xmpp.org/2024/08/the-xmpp-newsletter-july-2024/ as just one example

  11. gnemmi

    We should never publish information that a project hasn't decide to make public by themselves. Specially information regarding how anygiven project gets funded.

  12. gnemmi

    We should never publish information that a project hasn't decide to make public by themselves. Specially information regarding how any given project gets funded.

  13. gnemmi

    There's always a reason why a project ( be it Dino or Kaidan in this particular case ) decides *not* to make that information publicly available and it's not on us to decide when nor how to disclose that information.

  14. gnemmi

    We collect and publishc public information for the different projects *only after* they decide to make it public.

  15. gnemmi

    We do not create the News .. they do.

  16. gnemmi

    I'll proceed to delete the NLnet related information from the pad, due to the fact that neither Kaidan nor Dino made any public announcements, and create the PR in a few hours from now

  17. gnemmi

    You can always add the NLnet information ( or any other piece of information for that matter ) on the Newsletter Review stage

  18. cal0pteryx

    Thanks gnemmi

  19. gnemmi

    cal0pteryx, you are very welcome! πŸ€—

  20. gnemmi

    cal0pteryx, just in case, do we support webp images or should I export them as jpg/png before adding them to the newsletter?

  21. emus

    > We should never publish information that a project hasn't decide to make public by themselves. Specially information regarding how any given project gets funded. I think that not 100% correct. If you see something on NLnet or other public websites, also Github releases, I would treat it as public. its not our job to look for anything, but if you want to, you can do such news. What you should not do is to share informal information or hearsay. If you have doubts you can always ask the project owners of course.

    πŸ‘ 1
  22. arne

    >> We should never publish information that a project hasn't decide to make public by themselves. Specially information regarding how any given project gets funded. > I think that not 100% correct. If you see something on NLnet or other public websites, also Github releases, I would treat it as public. its not our job to look for anything, but if you want to, you can do such news. > > What you should not do is to share informal information or hearsay. > > If you have doubts you can always ask the project owners of course. πŸ‘

  23. gnemmi

    Got it. Will create the PR for the information "as is" and leave out to the team to decide what makes it in and what not. πŸ‘

  24. gnemmi

    Got it. Will create the PR with the information "as is" and leave out to the team to decide what makes it in and what not. πŸ‘

  25. emus

    You are the team too :-)

  26. gnemmi

    Got it. Will create the PR with the information "as is" and leave it out to the team to decide what makes it in and what not. πŸ‘

  27. gnemmi

    Im just a contributor!. Not even an XSF member 😊

  28. emus

    Time to change this :-)

  29. gnemmi

    Draft: The XMPP Newsletter April 2025 created

  30. gnemmi

    https://github.com/xsf/xmpp.org/pull/1520

    πŸ‘ 1
  31. gnemmi

    Newsletter April 2025 is ready for review!

    ❀️ 1
  32. gnemmi

    Thank you everyone who helped! πŸ€—

    ❀️ 1
  33. gnemmi

    edhelas, I really want to make sure you are OK with the pictures and the captions I used!. Please review!! 😹

  34. edhelas

    gnemmi did you asked the cats ? πŸ™€

  35. arne

    > Thank you everyone who helped! πŸ€— ❀️

  36. paulo

    > https://github.com/xsf/xmpp.org/pull/1520 πŸ‘

  37. paulo

    > Newsletter April 2025 is ready for review! ❀️

  38. gnemmi

    shoot! I never asked for they consent !!! 😱

  39. gnemmi

    shoot! I never asked for their consent !!! 😱

  40. gnemmi

    I sure hope I won't be getting a cease and desist for this πŸ˜”

  41. gnemmi

    Bob Cat sure looks like someone you don't want to mess with 😰

  42. Kris

    > Newsletter April 2025 is ready for review! lgtm

    πŸ‘ 1
  43. gnemmi

    Kris, thank you!