Prepare for full Alpha website go live (24/11)

[giacecco]

To take place between 20-21/11, this is the final prep for the full website to go live on Monday 24/11.

Checklist for go-live

(items marked with NB are non-blocking)

Website

• Move gh-pages website to theodolite #439
• Merge alpha.open and openaddressesuk.org OpenAddressesUK/theodolite#13
• Add Alpha branding and feedback form to site OpenAddressesUK/theodolite#14
• Alpha search page needs a feedback loop OpenAddressesUK/theodolite#15

Contents

• @giacecco's completion of Write Alpha documentation #442, Get OD Certificate for OAD #443
• NB @giacecco and @peterkwells check robustness of licence statements in download page and DCAT
• NB @giacecco to update Add DCAT to download page #449 and Get OD Certificate for OAD #443 to reference actual Open Addresses' launch date (we shouldn't publish the data before OA officially exists as a company)
• rename the downloadable dataset files to reference the exact launch date and change http://openaddressesuk.org/download/ accordingly
• @giacecco to update documentation with real provenance example, using the team's latest format
• @peterkwells to adapt contents for Alpha launch and check consistency with what was written for Write Alpha documentation #442
• @peterkwells have we thought of arranging some time from Legal to have a read of the website before launch?
• @peterkwells' requests on 12/12 described at Requests pack pre-soft launch OpenAddressesUK/OLD_openaddressesuk.github.io#15

Applications

• Generate the first production version of the downloadable OAD #437 and test full download
• Add interactive postcode lookup and reverse lookup features #457
• @Floppy and @pezholio review of software components being deployed for go-live: documentation of known issues / temporary arrangements that OA team needs being aware of (pretend someone else than you was asked to address an issue with the live environment) and general tidying up (suitable log verbosity etc.)
• @MurrayData to do testing samples of published data through both publishing APIs and downloadable version, to check that data appears consistent with expectations

Infrastructure

• @pikesley to inventory deployment resources (see also here), kill temporary components, harden security if necessary, general tidying up, hand over passwords / keys etc to OA team

Actual go-live

• Point openaddressesuk.org to theodolite
• Redirect alpha. to root domain

We will wait to know from Jeni when it is best to schedule making the raw database EC2 instance into something less temporary. In general, I would like the ODI Team to have their innovation week as planned.

[Floppy]

Can we make a checklist here of things that need doing for this?

[giacecco]

@Floppy, done.

[pikesley]

FiIled in inventory spreadsheet as far as I'm able

[pikesley]

So, can @pezholio and @Floppy confirm they're able to do heroku stuff on the following apps pls:

• hidden-bayou-9267
• pacific-beyond-9370
• powerful-depths-1407
• shrouded-caverns-1022

(try heroku ps or something)

[pikesley]

AWS credentials are in the passwords file

[pikesley]

@Floppy has the SSH key for AWS

[pezholio]

I've gone through the components and updated the Readmes appropriately

[giacecco]

Blocked awaiting OA to 'exist'. @peterkwells in my absence please keep the Team updated on any dates being decided for both the soft launch and the official one in January. Thanks.

[peterkwells]

"public Alpha" launch is being scheduled for Wednesday Jan 14th
softlaunch is whenever any of us want to show it to friendlies and get feedback. It's the feedback that's key.

[Floppy]

@peterkwells could you tick off any of the boxes above that are done?

[peterkwells]

I tried but nowt happened, whilst filling in with felt-tip on my screen seemed both inappropriate and silly.

1. licences are fine for now
2. content checked, I've simplified docs.md to reduce overlap with other content, e.g. guidelines for checking third party IP
3. we've checked text before, we can check again before full launch

[peterkwells]

and those comments are for tick boxed (1), (6) and (7) respectively

[Floppy]

@giacecco what's the state of the outstanding tickboxes above with your name on, in the contents section? Can we soft-launch the new site now, without having those completely done if they're waiting on the Thursday board meeting, or do you want us to wait?

[Floppy]

@giacecco @peterkwells.

Right, we've merged the old site content to the main app. It's now live (softly) for you to QA at http://alpha.openaddressesuk.org/, waiting for us to throw the DNS across, which we will do tomorrow unless someone tells us not to!

Content editing can now be done again, and should be done on the code found under https://github.com/OpenAddressesUK/theodolite/tree/master/app/views/static, which you should recognise.

[peterkwells]

Great stuff! Will bounce it around the ODI tomorrow

[giacecco]

Great news @Floppy.

I don't see anything blocking my side but for two items:

• @peterkwells needs approving the latest additions I prepared for the technical documentation this morning. I did not change the page directly as Peter asked us not to, I made them into a pull request here, and
• @pezholio asked me earlier today about moving the APIs to the openaddressesuk.org domain, too. You all were copied. This can be done after the data is re-distilled and re-serialised for download, so that the URIs are consistent.

I also marked as NB in the above list the tasks that are non-blocking, e.g. I believe we should not publish the ODI certificate until OA formally exists as a company.

[JeniT]

Open Addresses does formally exist as a company now, so we can take this forward.

[giacecco]

[edited]
The certificate is published, you can view it here. I have added it to the website on the "Get the data page", it's in pull request OpenAddressesUK/theodolite#26 .

[giacecco]

@Floppy @peterkwells I've started making a few fixes as pull requests directly. I am presuming Peter's invitation not to edit the website does no longer apply.

@Floppy what's the equivalent of jekyll serve in the new setup, to test locally the changes that are less obvious?

[Floppy]

@giacecco rails server, then open http://localhost:3000. Should work. It only needs a database set up if you try to search addresses, the rest should be fine.

[Floppy]

@pezholio @pikesley only thing for us to do before launch is to check that all the system documentation is up to date, I think.

[pezholio]

Yeah, I updated all the docs last week, and there's been no major change since then, so we should be golden

[Floppy]

/me ticks

Right, we're good to go then. Just waiting for @giacecco or @peterkwells to give the OK for domain switchover. When do you want it, chaps?

[pezholio]

Also, we need to sort the domains in the bulk downloads. Could we just download, sed replace and reupload? Would probably be quicker.

[Floppy]

Well, I was wondering that.

[Floppy]

Presumably we'd need to regenerate the torrent file as well., because hashes.

[pezholio]

Ah yeah, but that's easy done

[Floppy]

ok then. Let's do that.

[Floppy]

DNs switch is done. We're now live on alpha.openaddressesuk.org