XMPP Council - 2022-11-02

so did we get a decision about moving it or not ? I'm fine either way just want to know :)

We are not moving it

thanks!

we are not moving it [related to local time in Central Europe]

my calendar entry is in CEST and so it's moved 1 hour for me, but should be at the same time for you all, assuming the calendar did the right thing :)

My Dino is failing to start. So I'll be trying to keep the meeting short

soup2 vs soup3 battle?

Yes

classic

Is that a known thing? I haven't bothered to actually look into it

yes https://github.com/dino/dino/issues/1301

tl;dr your distro messed up, needs recompiled to fix, but possibly dino could make that fail to compile vs fail at runtime

What needs recompiling?

Because I did compile Dino myself

I'm not entirely clear on that, you have to set the flags so only 1 of the soup's is used, or try that branch linked at the bottom of that issue ?

Mhh probably both I guess. The flag to not make it immediately crash. And then the branch to not make it crash under certain conditions I guess...

hello from dino

hello

moparisthebest, fail to compile actually doesn't work because we can't know at compile time if the libsoup version used by libgupnp used by libnice will be 2 or 3, because the update of libgupnp which migrated from 2 to 3 does not bump the .so number, meaning it is updated independently of libnice. Fedora people seem to be the only ones noticing that this is a major issue so they made it something to specifically look at for the next release https://fedoraproject.org/wiki/Changes/libsoup_3:_Part_One

> because the update of libgupnp which migrated from 2 to 3 does not bump the .so number yikes...

well they argue they are ABI compatible which is somewhat true because the libsoup version is not really exposed to apps using it

but yeah, it's a mess. Also it doesn't help that libsoup 3 is still rather unstable (ton of bugs / incorrect behavior in their http/2 implementation)

it's ABI compatible except if you try to use it in your application it'll crash ! :D

only if your application dares to use libsoup 2 😉

I may be late by a few minutes

ETA 1605Z

I'm fine waiting

It's time

1) roll call

walking

good morning!

o/

👋️

2) Agenda bashing

nothing. It's gonna be a quick meeting

3) Editors update none this week

4) Items for voting nothing new this week

5) Pending votes

I'm +1 on everything!

Ge0rG is pending on three proposed xeps

ok thank you Ge0rG

this means all three XEPs from two weeks ago are accepted

6) Date of next

+1w wfm

+1w wfm, back at the normal time for me

I might be at a place without internet connectivity next week

ok noted

o/

+1w wfm

7) AOB

I note we only have one applicant so far

I intend to reapply, just failed to do it yet

it's still 3 days left

I'm not sure yet

which makes it rather likely that I'll miss the deadline

I'm going to reapply too

jonas’, is your decision depending on any external factors that can be controlled?

(just checking)

MattJ, I don't think I'm particularly suited for council given the lack of insight I have nowadays in much of the protocol topics.

that makes it tricky to vote on stuff with sufficient confidence and that's not a nice position to be in

I wonder if that'll improve when I'm not detracted by having to touch xsf/xeps anymore :shrug:

but that's a bet on the future and I'm at this point not quite sure I want to take that bet

Noted

ok. I assume no other AOB

8) Close

thanks daniel

thanks daniel 🙂

thanks daniel

thanks !

jonas’, fwiw I think lack of insight can be a good thing, if the XEP isn't clear in and of itself, if it's only clear given sufficient tribal knowledge, then it's a bad XEP