Hi all,
Thanks Georg for laying this out. I really like the direction you are proposing, and I think it fits with where the discussion has landed so far.
Based on the thread and some follow up discussion, I would suggest the following approach, which I think keeps things moving while avoiding unnecessary process overhead:
First, I do not think we need formal XSF approval to move forward with practical outreach materials like the flyer you describe. If the goal is to help people get started with XMPP, then just doing the work is likely more valuable than waiting for a formal stamp. Trying to frame this as an official XSF endorsed artifact also risks opening discussions about completeness and representation that we simply do not have time for before FOSDEM.
So my suggestion would be: just create the flyer. Mentioning the XSF or linking to
xmpp.org is fine, but without positioning it as an official or comprehensive XSF statement. From my perspective, that removes most of the risk while keeping all of the upside. On the funding side, I am confident we can sort something out one way or another, so I would not let that be a blocker.
Second, building on the earlier discussion, this feels like a good opportunity for the Communications Team to play a more active role than just posting a simple message of support. A blog post on
xmpp.org that:
- mentions and links to the DI.DAY initiative and the shared values around decentralization and digital independence,
- highlights the concrete, user friendly XMPP based projects that already fit well with DI.DAY goals,
- and explicitly invites other XMPP projects to do their own outreach, recipes, or materials,
would be a great way to support this effort. This also shifts the focus slightly from "projects submit a paragraph to XSF" to "projects tell their own story, and we help point people to it", which feels more scalable and more in line with the ecosystem.
This way, we keep the XSF out of the critical path, we support Georgs concrete plans for FOSDEM, and we still give visibility and coordination where it makes sense. It also leaves plenty of room for others to join in, including via the existing chat where coordination is already happening.
If this sounds reasonable to others, I think it gives us a clear and practical next step.
Kind regards,
Guus