XSF Discussion - 2019-09-24

  1. !xsf_Martin

    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.

  2. Seve

    Somebody has to create an account for you !xsf_Martin

  3. Seve

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

  4. Ge0rG

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

  5. !xsf_Martin

    Seve, Ge0rG: thx

  6. pep.

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

  7. Ge0rG

    pep.: yay!

  8. jcbrand

    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.

  9. Ge0rG

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

  10. jcbrand

    Thanks, I'll do that

  11. Ge0rG

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

  12. jcbrand

    I'm nominally an editor, but inactive

  13. flow

    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

  14. jcbrand

    Thanks flow

  15. Ge0rG

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

  16. flow

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

  17. Ge0rG

    if jcbrand is editing xep.ent already anyway?

  18. jcbrand


  19. flow

    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

  20. jcbrand

    You mean I should add the IETF one?

  21. jcbrand


  22. flow

    if you plan to refer to it, sure.

  23. Ge0rG

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

  24. jcbrand

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

  25. jcbrand

    Should we perhaps wait until that fork is merged?

  26. flow

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

  27. flow

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

  28. flow

    erm, buzy with the kidz

  29. jcbrand

    pep. is too quick, he already merged my PR

  30. jcbrand

    I'll make another one, should be quick

  31. pep.

    merged. Thanks :)