[Members] Agenda for the XSF Board Meeting on April 2 2026

Dear Board members, This email announces the agenda for our next Board meeting, scheduled for Thursday, 2 April 2026, from 16:00 to 16:30 UTC. The meeting will take place in the XSF chatroom at xmpp:xsf@muc.xmpp.org?join. *Note: Daylight Savings Time switchover has happened since the last meeting. Scheduling has been modified *(to have the meeting start at the same *local* time for most participants). Brief context is included for each agenda item to support preparation. *1. Welcome*Opening of the meeting. *2. Formalize Agenda*Confirm and approve the agenda for this meeting. *3. Action item follow-up: Keep Android Open letter*Confirm that the Chair sent the signing email on behalf of the XSF following the vote at the March 5 meeting. *4. Discuss with Intent to Vote: Membership Name Disclosure Policy*Review the state of the mailing list discussion initiated on March 3, 2026. Broad member support exists for making real name disclosure optional. However, the March 5 meeting surfaced a substantive Board-level objection: that the XSF, as a legal entity, may have obligations to ensure its members are known, identifiable people. Note that the proposal does not make names unknown to the XSF - only to the general public - but this distinction was not fully resolved. Determine whether the Board is ready to vote, or whether further discussion is needed. Related mailing list thread: https://mail.jabber.org/hyperkitty/list/members@xmpp.org/thread/JLLM2YCWQBL… *5. Discuss with Intent to Vote: Publication of Membership Vote Tallies*Review the state of the mailing list discussion and the exchange at the March 5 meeting. While broad member support exists for ceasing public publication of vote tallies, at least one Board member expressed support for maintaining the current practice. Assess whether sufficient Board consensus exists to proceed to a vote. Related mailing list thread: https://mail.jabber.org/hyperkitty/list/members@xmpp.org/thread/JLLM2YCWQBL… *6. XSF EU legal structure: assess proposals and next steps*Five proposals are now documented on the wiki, covering a range of options from full EU migration to a lightweight representative office. The mailing list discussion has raised several overarching concerns, including transition costs, IP transfer, and long-term sustainability. Assess whether the discussion has matured enough to narrow the field, or whether further input is needed before the Board can act. Wiki page: https://wiki.xmpp.org/web/XSF_EU_Legal_Transition_Proposal *7. Progress report: Second XMPP Summit 2026 (online)*Follow-up on the task assigned to SCAM at the February 19 meeting to explore format and feasibility of a 2026 online Summit. Receive an update. *8. Progress report: Outreach initiatives*Follow-up on the tasks assigned at the February 19 meeting: CommTeam improving XMPP/XSF Wikipedia and public pages, and SCAM developing a plan for attending conferences and events. Receive brief status updates from the responsible teams. *9. XMPP 2: Update and next steps*Since the last meeting, Daniel Gultsch and Marvin attended IETF 125 in Shenzhen, where they report a positive and welcoming reception to the idea of updating the XMPP core RFC. A concrete next step has been identified: producing an initial draft to demonstrate substance, starting with an update to RFC 6120 (core). A side meeting at IETF 126 in Vienna is being planned to gauge broader interest, and participation in the IETF 126 Hackathon (July 18-19, Vienna) has been proposed as a low-barrier opportunity to raise XMPP's visibility at the IETF. Discuss whether the Board wishes to formally acknowledge or support these efforts, and whether any action is needed. Mailing list thread: https://mail.jabber.org/hyperkitty/list/standards@xmpp.org/thread/7LM6LN5VN… *10. Any Other Business (AOB)*Items not listed above that require brief attention. *11. Date of next meeting*Agreement on the date of the next Board meeting. *12. Close*Closing of the meeting. Please review the relevant materials ahead of the meeting so that we can use our time efficiently. Kind regards, Guus