Agenda for XSF Board Meeting on 5 February 2026

Guus der Kinderen <[email protected]>
Newsgroups gmane.network.jabber.standards-jig
Message-ID <CAMJaV9kBao2ENRVciJ4d2n9Fr9j_HZkf9Age6EFavVYOUmCj4A@mail.gmail.com>
Dear Board members,

This email announces the agenda for our next Board meeting, scheduled for
Thursday, 5 February 2026, from 17:00 to 17:30 UTC. The meeting will take
place in the XSF chatroom at xmpp:[email protected]?join.

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. Review and vote on proposed changes to XEP-0001 and XEP-0143*The Board
will review and vote on proposed changes to XEP-0001, which require Board
approval.
The Council has already approved the proposed changes to XEP-0143. This
item is included to ensure process clarity and to determine whether the
Board wishes to formally note or endorse those changes as well.


*4. Summit and FOSDEM report and follow ups*A brief review of the recent
Summit and our presence at FOSDEM. The purpose is to identify any concrete
outcomes, learnings, or potential follow-up topics that may require future
Board or membership attention. No decisions are expected under this item.


*5. Increase Board meeting frequency*Discussion of a proposal to increase
the frequency of Board meetings, with the aim of improving engagement,
continuity, and overall productivity.


*6. Any Other Business*Items not listed above that require brief attention.


*7. Date of Next Meeting*Agreement on the date of the next Board meeting.


*8. 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

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.