XSF Discussion - 2019-09-24

For the next newsletters mention of the new profanity release 0.7.0: Right now there is already a bug fix release 0.7.1 https://github.com/profanity-im/profanity/releases/tag/0.7. I don't know if I can add it to the wiki as I didn't find a signup there.

Somebody has to create an account for you !xsf_Martin

I'll will add it for you, thank you :)

!xsf_Martin: instructions to obtain a wiki account: https://wiki.xmpp.org/web/Sysops

Seve, Ge0rG: thx

https://github.com/openssl/openssl/pull/9965 \o/

pep.: yay!

Hi folks, I'm editing a XEP and when I try to refer to the message fastening XEP via &xep0422; I get the error `Entity 'xep0422' not defined`. Is there something I should be generating first? It seems to work with other XEP numbers.

jcbrand: yeah, the new XEPs need to be added to xep.ent periodically

Thanks, I'll do that

This is something that the editor (jonas’) does normally

I'm nominally an editor, but inactive

jcbrand, you could also declare the entity at the beginning of your xep: https://github.com/Flowdalic/xeps/blob/master/xep-jidprep/xep-jidprep.xml#L4

Thanks flow

wouldn't that be better placed in xep.ent as well?

that's meant to be done until it is added to xep.ent as well

if jcbrand is editing xep.ent already anyway?

https://github.com/xsf/xeps/pull/830

so if you develop your xep in a fork of the offical xeps repo, then nothing prevents you from adding it to xep.ent right away

You mean I should add the IETF one?

RFC8264

if you plan to refer to it, sure.

jcbrand: I think it would make sense to add it to xep.ent, yes.

flow: you are referring to it... but I see it's in a fork

Should we perhaps wait until that fork is merged?

jcbrand, there is aready https://github.com/xsf/xeps/pull/825 where I left an editor note to add it

Of course, I could have just added it with the PR, dunno why I didn't, was probably me being lazy

erm, buzy with the kidz

pep. is too quick, he already merged my PR

I'll make another one, should be quick

merged. Thanks :)