XSF Communications Team - 2025-07-07


  1. rtmmunny

    hi

  2. rtmmunny

    i need to submit a screenshot

  3. badrihippo

    Benson, regarding the logo, perhaps you could also ask Raja Sandhu if he can suggest an alternative OFL-licenced font to use for the XMPP logo?

  4. badrihippo

    Which we'll then be free to use in other places as well

  5. badrihippo

    He would know best what factors he took into account when choosing the current font in the first place

  6. ralphm

    Instead, let's first articulate what is actually the thing needed, and why, and present that to the Board. If the XSF is going to have a true logo, it would need to be commissioned by the XSF. Also note that I've already created tons of material over the years, including a table cloth, bean bag, clothing, bottle opener. All using the same font.

  7. ralphm

    Oh, and banner

  8. badrihippo

    Fair enough. I suppose it would be clearer for us (me?) too once we've articulated what exactly the requirement is

  9. ralphm

    As for licensing, the origin of the font is very nebulous, and the company that claimed copyright has been defunct for decades. Also, this font is free for personal use, which includes the use by non-profit organizations like us. We also don't sell swag (people make donations).

  10. badrihippo

    Oh, that's interesting about the licensing (and good to know)

  11. Trung

    if there aren't any actual valid liscensing issue, use the original font.

  12. Trung

    please.

  13. ralphm

    Yes, but first that what/why

  14. Trung

    singpolyma: https://en.wikipedia.org/wiki/Product_Sans created created specifically to do Google's branding. Nothing else. With near infinite budjet they release everynow and then update yes.

  15. Trung

    singpolyma: https://en.wikipedia.org/wiki/Product_Sans created specifically to do Google's branding. Nothing else. With near infinite budjet they release new update every now and then yes.

  16. edhelas

    We need XMPP Sans

  17. ralphm

    edhelas: we named it OPTI Edgar Bold Extended 🤣

  18. edhelas

    Perfect 👌

  19. ralphm

    By the way, for posters and hoodies I also used the non Bold one

  20. emus

    ralphm: Because of these efforts: https://github.com/xsf/xmpp.org/pull/1518/files

  21. emus

    gnemmi: I will read and merge now?

  22. gnemmi

    Hello everyone!

  23. gnemmi

    emus, so sorry for the late reply! Yes, please proceed!

  24. ralphm

    emus: I can't review this right now

  25. emus

    ralphm do you mean you have not time or you cannot access?

  26. emus

    gnemmi - again great work! I just merged. Just a kind request: Create the PR on the xmpp repository ideally. otherwise web edit won't work. And the Italian Community should be under Events actually, right?

    ❤️ 1
  27. gnemmi

    > gnemmi - again great work! I just merged. > > Just a kind request: Create the PR on the xmpp repository ideally. otherwise web edit won't work. > > And the Italian Community should be under Events actually, right? Great!. Thank you and everyone who took part on this edition!!

    ❤️ 1
  28. emus

    badrihippo: could you and benson help me formulating a message to Board to elaborate the situation again?

  29. emus

    >> gnemmi - again great work! I just merged. >> >> Just a kind request: Create the PR on the xmpp repository ideally. otherwise web edit won't work. >> >> And the Italian Community should be under Events actually, right? > Great!. Thank you and everyone who took part on this edition!! ❤️

  30. gnemmi

    In re the PR, I'm pretty positive that I followed the standard procedure as always .. meaning: PR against xmpp/master branch 🤔

  31. gnemmi

    in re the Italian Community: I didn't even get to see that one. I think badrihippo created it in a comment on the PR and cal0pteryx added it to the PR 🤔

  32. gnemmi

    Anyways, I'll make sure to double check that all future PRs are created against xmmp/master branch 👍

  33. ralphm

    emus: no time and not near a computer to look at SVGs

  34. emus

    Ah okay, yeah, we will write an email

  35. emus

    > In re the PR, I'm pretty positive that I followed the standard procedure as always .. meaning: PR against xmpp/master branch 🤔 before you do, maybe next time let us know your planned steps

  36. emus

    The #XMPP Newsletter for May 2025 is out! Read about the latest XMPP universe updates and updates on our #standards! https://xmpp.org/2025/07/the-xmpp-newsletter-june-2025/ Enjoy reading! 📰 ☕ https://mov.im/blog/xmpp-official%40movim.eu/the-xmpp-newsletter-for-june-2025-is-out-tRCQyz https://fosstodon.org/@xmpp/114813864971976673 https://bsky.app/profile/xmpp-official.bsky.social/post/3lrbgpxvqvk2p

  37. emus

    The XMPP Newsletter for May 2025 is out! Read about the latest XMPP universe updates and updates on our standards! https://xmpp.org/2025/07/the-xmpp-newsletter-june-2025/ Enjoy reading! 📰 ☕ https://mov.im/blog/xmpp-official%40movim.eu/the-xmpp-newsletter-for-june-2025-is-out-tRCQyz https://fosstodon.org/@xmpp/114813864971976673 https://bsky.app/profile/xmpp-official.bsky.social/post/3lrbgpxvqvk2p

  38. emus

    If one wants to create a PR with one or two additonal images to the blogpost that would be great!

  39. gnemmi

    Like adding this one under the Gajim entry? https://gajim.org/img/news/main-window-2.3.0.png

    👍 1
  40. cal0pteryx

    gnemmi, there was a "suggestion" on GitHub, which added the Italian Community entry. I applied the suggestion, that's all

  41. cal0pteryx

    > gnemmi - again great work! I just merged. > > Just a kind request: Create the PR on the xmpp repository ideally. otherwise web edit won't work. > > And the Italian Community should be under Events actually, right? I've web-edited the PR just fine, don't know which issue you've experienced, emus?

  42. gnemmi

    cal0pteryx, Oh, I see .. i didn't even get to see that one ( I couldn't have much connection time this weekend so I never knew about that 😔 )

  43. cal0pteryx

    gnemmi, no worries, I took the liberty of applying that comment

    👍 1🤗 1
  44. cal0pteryx

    emus, doing PRs from individual forks is the intended workflow, fyi

  45. gnemmi

    Yeah .. I kept looking around about that one because I also did at least 6 or 7 web edits ( from badrihippo and Benson ) and I dind't have any problems 🤔

  46. gnemmi

    most of them came from "suggestions" on the PR

  47. cal0pteryx

    You editing your own fork should not be an issue in any case :) It _can_ be a problem for others to edit your fork. But that worked fine for me in the past.

  48. gnemmi

    Oh .. understandable ..

  49. emus

    Hmmm, I could not this time for some reason

  50. gnemmi

    Oh .. and just for the record. You guys, I don't have write access to the repo (commit rights), so there's so much that I can do ..

  51. gnemmi

    I can do PR's and make edits on them and so on .. but that's as much as I can do

  52. gnemmi

    I can't smash the bugs, or add tags or anything other that submitting PRs

  53. gnemmi

    Let alone doing merges ..

  54. gnemmi

    I just wanted to clear that out in case you ever happen to be waiting for me to do anything other than creating the PR and doing changes on it

  55. cal0pteryx

    > I just wanted to clear that out in case you ever happen to be waiting for me to do anything other than creating the PR and doing changes on it Ah, that's good to know, I somehow thought you could do merges :)

  56. gnemmi

    I mean, it's not like Im being lazy or anything like

  57. gnemmi

    That was the point I as trying to convey

  58. cal0pteryx

    It's great having you on the team, gnemmi! This is really helping :)

    🤗 1❤️ 1
  59. gnemmi

    > Ah, that's good to know, I somehow thought you could do merges :) Yeah ... I kinda figure that out when I read your comments on the PR

  60. gnemmi

    cal0pteryx, Thank you _so_ much! It really makes me feel great to be a part of this and work along with you guys! ❤️

  61. gnemmi

    Image added to Newsletter https://github.com/xsf/xmpp.org/pull/1536