XMPP Council - 2016-07-21

Dave Cridland: By the way, another reason I went for XEP-0045 is the existing muc#roominfo_pubsub option, which is defined in 0045 and not 0060.

But as I said, putting this in 0313 would be totally fine with me.

Yeah, I think the important thing is to ensure that room options are gethered somewhere sensible for the long term. I'm not keen on updates to '45 for everything we want to add (and this will have a bigger impact on, say, MIX).

Yup, I see the point.

shouldn't that "somewhere sensible" be the XSF registry? We already have the muc statuscodes there. So why not have a registry for well known MUC config options

Then have xep45 say "for a well known list of MUC config options look at xmpp.org/registry/muc-config-options.html", and have xep313 declare the option

Flow, That's exactly what I suggested yesterday.

Which reminds me: Kev Tobias: How can I help getting the registry back online under xmpp.org?

right..it's on my list..need to read a bit into our pelican stuff to see how i can convert the registry to pelican pages on the fly

Tobias: I think the .xsl files in the registrar repo are used to generate html for the registry

so it's possible just a matter of invoking xslproc and putting the generated output to the right place

right...but you probably want the generated XHTML be integrated in a sensible manner in the rest of the site layout

Tobias: That can be done as second step. I think right now it's important that http://xmpp.org/registrar/disco-categories.html starts to work again. The html page can be simply generated by "xsltproc disco-categories.xsl disco-categories.xml > disco-categories.html"

If you want. I could extend the registrar repo with a makefile which generates the html files. so all you have to do is pull it when required, run the makefile and make the directory available as xmpp.org/registrar

if one does it one should do it right...what we currently have is an example of what happens if you don't do it right from the beginning :)