XMPP Council - 2025-10-23

> ... why did we rewrite a xep under a new number? And we still need the old one for a real implementation? Are we trying to get people to hate us? 😛 I wonder too why a new XEP has been written instead of updating XEP-0277, but now we have to deal with this. I was not in council at the time. ↺

Also, the way I've understood it, the goal is to deprecate the old one at some point. The profile mechanism is a good thing in PFS to reuse specs and payloads while getting information on how to render the view.

Following up on the article I submitted for publication - as discussed on October 14, Council was to decide whether we need to review it before it's published, or confirm that no review is necessary. Since that decision wasn't finalized at the October 21 meeting, I'd like to ask that we resolve this as soon as possible so we can move forward with publication. Could you please clarify your position on this matter in the next day or two, or agree on a quick way to finalize it? I'd really appreciate your input so that we can keep things moving smoothly.

I think it's relatively safe to assume that council has no opinion

Sorry for not checking with our members in the last meeting

Daniel, I'm more than happy to accept that. Can you please leave a comment that reflects this in https://github.com/xsf/xmpp.org/pull/1576 ? I'm now more or less blocked for some kind of formal reply, given that dwd explicitly asked for one.

(I'm happy to quote you there, but optics are better if it comes from you directly)

I suggested one, I won't hold you to it.

I know, but upon requesting a formal review (of uncertain necessity), progress instantly entered its natural habitat (a holding pattern) as everyone began waiting for someone, somewhere, to decide if anyone needs to decide anything.