Board-Meeting-2026-11-05

From XMPP WIKI
Jump to navigation Jump to search
Board Meeting
Date Thursday, 2026-11-05
Time 17:00-17:30 UTC
Place XSF chatroom
Transcript chat log
Term 2025-2026 Term Summary
Navigation
Previous Board-Meeting-2026-10-22
Next Board-Meeting-2026-11-19

Agenda

Note: this is the first meeting since the European clock change. The Board agreed on 22 October to keep the meeting at 18:00 Paris, Amsterdam and Berlin time, which is now 17:00 UTC rather than 16:00 UTC.

1. Welcome
Opening of the meeting. Roll call and confirmation of quorum.
2. Formalize Agenda (2 min)
Confirm and approve the agenda for this meeting.
3. Action points (5 min)
One line of status each; the minutes record what is reported.
Acknowledgement to the Cisco contact. Agreed 2026-09-24. Ralph to send a short acknowledgement to the contact at Cisco, stating the XSF's intention to formalise matters in due course. Owner: Ralph
Website annotation. Agreed 2026-09-10. Discussed, improved and merged: https://github.com/xsf/xmpp.org/pull/1725 Closed.
trademark@. Confirmed functional and monitored. Closed.
Legal questions: complete the list. Mickaël to review the questions already proposed. The lawyer Arne approached is not specialised in this area and does not have the time, so that avenue is closed. https://wiki.xmpp.org/web/Legal_Questions:_Jabber_Trademark_and_XSF_Legal_Structure Owners: Mickaël, Guus
Role address audit. Guus to raise with the author of the Code of Conduct XEP whether it should carry direct contact references, and whether a conduct@ address is wanted. Owner: Guus
4. Documentation for attendees travelling to XSF events (10 min - decision)
A member travelling from outside the EU to XMPP Summit 30 has asked the XSF for a letter confirming that the Summit is taking place and that they are registered to attend. Per their travel agent, that is the main thing a Schengen application needs from the organiser. Draft text: https://pad.nixnet.services/q0lK5B67R9eIbzh9UhVT4A
This is a confirmation of fact, not a sponsorship letter: no costs, no liability, no guarantees about the traveller. Sponsorship for this trip is arranged separately and does not involve the XSF.
SCAM is supportive and recommends approval, subject to the wording limiting any exposure. Cautions raised there: the XSF could conceivably be exposed if an attendee overstayed, the bar for registering for the Summit being low; and some due diligence on requesters would be sensible. It was also suggested that the letter state explicitly that the XSF provides neither accommodation nor financial support, though that may weaken its usefulness.
The IETF issues such letters, https://www.ietf.org/meeting/visas/ FOSDEM issues them only to accepted speakers, citing legal reasons.
Decisions sought
  1. Whether the XSF issues letters of this kind at all.
  2. That any letter confirms only the event and the registration, and undertakes nothing further.
  3. Process: on request or offered to all registrants; what check is made on the requester and on the registration; who signs; whether a passport number is included and what happens to it; where requests go.
  4. Whether this is announced on members@.
Practical: the letter wants XSF letterhead, which may not exist, and gives a contact address for the embassy to verify the registration, so it has to be one that is monitored. The Summit is on 28 and 29 January 2027, and Schengen applications from India take time.
5. EU Legal Structure: review of the self-assessments (10 min - decision)
All proposal authors provided self-assessments by the deadline of 21 October. That completes step 1 of the process the Board adopted on 4 June. Board members were asked on 22 October to look the assessments over ahead of this meeting.
The agreed process
  1. Proposal authors self-assess against the criteria. Done.
  2. The Board and members review and validate those assessments. This is where we are.
  3. The Board narrows to one or two preferred options and recommends them to members.
  4. Members receive a final opportunity to weigh in.
  5. The Board decides.
Decisions sought
  1. Whether the Board considers the assessments sound enough to work from, or whether any need to go back to their author.
  2. Whether the assessments go to members@ for comment now, in parallel with the Board's review, or after it.
  3. How the two proposals authored by Guus are handled, given he should not be the one validating his own.
  4. A target date for narrowing to one or two preferred options, so that it does not drift the way the self-assessments did.
Noted: the Chair observed on 4 June that the status quo remains a possible outcome of this process, and on 24 September that the Board has not yet decided that it is moving at all.
Wiki page: https://wiki.xmpp.org/web/XSF_EU_Legal_Transition_Proposal
6. Volunteer capacity: is this still a live item? (5 min - decision)
Carried since 27 August without being taken up, and deferred from 22 October. It has twice been described publicly as something the Board intends to address, so it should either be taken up properly or closed deliberately.
The item rests on two things said during the July discussion on standards@. One is that work the Board hoped to delegate could not be taken on for want of capacity. The other is a report, at second hand and never confirmed by the person concerned, that the Editor role may not be sustainable if the volume of low-quality submissions rises. Neither has since been followed up with the people concerned.
Decisions sought
  1. Whether to ask the people concerned directly, rather than continuing to rely on what was reported in July. Without that the item has no foundation to work from.
  2. If so, who asks, and what the Board does with the answers.
  3. If not, that the item is closed and recorded as closed.
7. Any Other Business (AOB) (2 min)
8. Date of next meeting (2 min)
Proposed: Thursday, 19 November 2026, 17:00 UTC. Note that this would be the last meeting of this Board's term, the annual meeting at which the next Board is elected being on 26 November.
9. Close

Minutes

1. Welcome

The meeting was opened and chaired by Ralph Meijer.

Attendees

  • Ralph Meijer (Chair)
  • Guus der Kinderen
  • Arne-Brün Vogelsang
  • Mickaël Rémond

Florian Schmaus was not present, having indicated that he was not certain he would be able to attend. Quorum was confirmed with four of five Directors present.

2. Formalization of Agenda

The agenda as published on the wiki was approved without changes. No additional items were added.

3. Action points

Acknowledgement to the Cisco contact. Ralph had not sent it, having forgotten again after the previous meeting. He sent it during the meeting. Closed

Legal questions: complete the list. No progress from Guus. Mickaël had not managed to review the questions already proposed, the past week having been busy, and undertook to do so before the next meeting. Owners: Mickaël, Guus

Role address audit. Guus reported that the author of the Code of Conduct XEP considered this a decision for the Board, saw the logic in the Code of Conduct carrying contact information, and suggested that the contact should be the Board unless and until there is a formal Conduct Team. Guus preferred a conduct@ alias, so that a later organizational change would not require a change to the XEP, and noted that board@ is as he understands it restricted to a few members rather than open to the public. He proposed a conduct@ address forwarding to all Board members, referenced from the XEP. Ralph, Arne and Mickaël agreed. Guus will ask iteam whether the alias can be created and, if so, work with someone to get it into the XEP. Owner: Guus

4. Documentation for attendees travelling to XSF events

Guus declared an interest: where the agenda records that SCAM is supportive, he is himself half of SCAM.

The Board agreed that the XSF will issue such letters. Guus saw no risk and considered that it helps people in the community to contribute to it. Ralph, who was not aware of the XSF having done this before, was content with acknowledgements along the lines of the template and nothing beyond that. Mickaël was in favour provided the letter is clear that it confirms registration and is not an endorsement of the person, over whom the XSF has no authority, and noted that travel has become more difficult in recent years. Arne agreed.

Outcomes:

  • Any letter is limited to acknowledging the event and the recipient's registration for it. It carries no endorsement of the recipient and no undertaking by the XSF.
  • Letters are issued on request and decided case by case, rather than offered to all registrants. Guus noted that offering them generally would call for a streamlined process of the kind the IETF has.
  • No check is made on the requester, and the letter will not imply that one has been. Details supplied by the requester are passed through as given.
  • The XSF keeps no records beyond the letter issued and the correspondence received. Where a passport number is required, it is included as supplied and then deleted from the XSF's records.
  • Eligibility is not formally restricted to XSF members, though in practice letters go to people whom whoever signs considers trustworthy enough to stick the XSF's neck out for. Ralph observed that the XSF does not really vet its members either. Mickaël noted the intent that this should not become a route to a visa for someone with no interest in the XSF.
  • No announcement on members@. Ralph took the view that people can reach out themselves, and abstained. Guus considered a mention cheap and potentially of considerable benefit to someone, but did not press the point. Mickaël suggested the Summit wiki page instead, which Ralph accepted.
  • Letters are signed by SCAM. (Raised under AOB.)

Ralph noted that the XSF has no house style. Arne suggested that an expert might be needed on the handling of identity details. Neither point was resolved.

Not reached. Noting that the meeting was already 45 minutes in, the Chair moved to AOB. This item was also deferred on 22 October.

6. Volunteer capacity

Not reached, as above. This item was also deferred on 22 October.

7. Any Other Business (AOB)

No other business was raised beyond the question of who signs the travel letters, recorded under item 4.

8. Date of Next Meeting

The next Board meeting is scheduled for: Thursday, 19 November 2026, at the usual time.

Guus noted that this will be the last meeting of this composition of the Board.

9. Close

The meeting was closed by the Chair.

All attendees were thanked for their participation.