XSF Discussion - 2019-10-31

Zash, While I appreciate your Council candidacy page, I feel I should remind you that XEP-0028 was found not to be conformant to RFC 5823 - though this was later revisited in RFC 6634.

https://igniterealtime.org:443/httpfileupload/cde5951a-4db5-484b-92d0-7ba01b854fb3/image.png

You have to reapply every three month?

Every year.

Ok, that's IMHO more reasonable than quarterly.

0. Welcome + Agenda

Hi!

o/

Hi

Guus, nyco?

nyco may not be available, as he had a meeting happening at the same time

<3

Dave Cridland: thanks!

ok, let's go then

1. Publicize XSF Financials

I'm +1 on this, too, for the record.

Can we move this item off the board?

I think so, yes

Yes

2. Board / Council Elections

Current state: 5 for board, 4 for council.

I read that Guus was going to write a blog post on this?

Ohh, forgot about time

I'm here

sorry

Guus: DST hell?

No, just busy

https://github.com/xsf/xmpp.org/pull/626

blogpost: https://github.com/xsf/xmpp.org/pull/626

Either suggest improvements, or we'll merge here/now?

Right. So What's the holdup? I notice we're only days away from the deadline.

There was a request for improvements - I gave feedback, and forgot about the entire thing

Ok.

Is this good to go, even though pep. asked for a change?

I understand his comment, was trying to come up with an alternative.

(we did use this exact wording before - I stole it from an older blogpost)

Yeah, I don't think it is that much of a problem.

I say just publish it as-is, we don't have more time to wordsmith.

I think it is debatable the time we spend.

Is not a fixed amount of time, I would say.

Indeed, some weeks more than others.

That is to much information for such a blogpost.

If what we have is not terribly wrong, let's merge and move on.

ok

Let's go

3. Review of Roadmap

I've just started my new job at Elastic, so yay.

But didn't get to this.

congrats

Congratulations ralphm!

Will look at it for now +2W, will be in Canada next week.

4. AOB

None here

FYI, I put in a request for the Realtime Lounge at FOSDEM 2020 again.

Let's hope we can get more space this year!

Also reminding them of the desire to have more space.

Right

(swag, folders, etc)

If someone has ideas for the lounge - this might be a good tie to start working on them ✏

Definitely. Also demos.

If someone has ideas for the lounge - this might be a good time to start working on them ✏

(I can't type today)

no worries

Ok, if that's it, then:

5 Date of Next

+1W

+1 works for me

+1

+1

(but I won't be there, maybe)

kk

6. Close

Happy Halloween!

:)

And thanks all.

Thanks ralphm

thanks!

Thank you guys!

Guus, ralphm - bottle openers, this time with "Open as in Beer" on them?

wfm 🙂

Dude

Can we think of something something 'Open as in Speech' too? 🙂

Pens?

https://xmpp.org/2019/10/xsf-board-and-council-2019-2020-elections/ is now up, if people want to refer to it in call to actions of their own.

Is "Proxy voting" an established term outside of the XSF? ✏

Yes

Does anyone know whether there is a good reference implementation for parsing the XMPP-URIs (https://tools.ietf.org/html/rfc5122 ) ?

Any URI parser should do

Don't forget to url encode them properly

Rooms in matrix and irc start with #, which is a special character in URLs

Ok, i think it works now with proper escaping with Qt's QUrl/QUrlQuery

What do we currently have for collaborative edition? XEP-0284 for XML, kind of XEP-0301 but that’s only for our own messages, anything else?

What's https://xmpp.org/extensions/xep-0204.html

> This JEP

never noticed that before, wonder how often that happens...

Ah that one. I discovered it a few days ago

Zash, my usecase is a collaborative plain text editor.

Ideally that’ll also be compatible with other collaborative editors, like Inkscape or so.

What's the stuff in Abiword even? IIRC that's XMPP based.

I’ll have a look.

Hum, https://www.abisource.com/developers/download.phtml doesn’t support TLS 1.2, and Firefox doesn’t support anything lower nowadays.

"JEP" is only used in in XEP-204, guess it should probably be changed

Patch it

it's in a couple other ones too, but only "JEP to XEP", 0001 talking about what they used to be called, and in the middle of a base64 image, so those don't count

Hah

Zash, they’re using Telepathy tubes it seems.

Right

I have no recollection of which protocol they are using.

And here I am, writing threaded C++ code. :(

Link Mauve, libinfinity btw

Hmm, I wonder if it might be a better fit than XMPP for this purpose.

Seems quite abandonned though. :/

There are commits from 2015 on the first page, and the latest commit is from 1.5 years ago. :x

Their API documentation is down too: http://infinote.0x539.de/libinfinity/API/libinftext/

Their automake script even fails…

And now I’m missing Rust a lot, message passing without pattern matching makes me very sad.

Hah one of my subordinates whines every day how terrible c++ in comparison to Rust but he still has to use c++ with boost because of the current project. I don't even know what to answer but I agree with him just wrt boost :)

> And here I am, writing threaded C++ code. :( I hope it's some cool PRECIS implementation 😁

From XEP-0001, <xs:element name='authornote' type='empty' minOccurs='0'/>, what's this type empty? Is this a hack for something I don't understand? It seems to allow only the empty string value.

hmm. It seems to add a link to an authornote anchor if it exists.

Where are booleans when you need them