[Members] new xmpp.org going live in 7 days
kevin.smith at isode.com
Tue Nov 10 12:32:05 UTC 2015
On 9 Nov 2015, at 17:53, Simon Tennant <simon at buddycloud.com> wrote:
> Hi Kev.
> The plan is to run it on Github pages so the only change that is needed is a DNS change.
Hmm. Board making decisions on our infrastructure without consulting the iteam is questionable, but I guess they’re Board so they get to do what they want.
Irrespective of that, are you sure a DNS change is all that’s needed? I’m not sure how that’ll address TLS verification and the like.
> Background: In building the new site, I really wanted us to have something that can be more community driven: fixes and quick deployments so that site gets more love and attention and the content stays fresh.
That seems like a fine goal. It’s not clear to me why hosting on github would be required for it to work.
> The current workflow:
> commits/pull-requests -> travis-ci for building -> auto-deployed on Github pages branch
> As you mention this does raise two interesting problems:
> • https://xmpp.org/extensions/diff/ seems to hang on loading the XEP list. Is this in active use? Would it be possible to put this on it's own subdomain like tools.xmpp.org?
It is used (although as noted, it needs fixing), it’s really very useful for Council in reviewing XEPs.
> • http://xmpp.org/extensions/* we'll need to update the site generation script to also build the XEPs. I'll have a look at this in the morning when my brain is more fresh.
> I'm partial to the "launch and try to patch things up later" but we definitely need the XEPs :)
I’m happy enough for launching and patching things up later, as long as there’s no risk to us serving up our core content.
How are the various rewrite rules getting deployed on github?
More information about the Members