What to do with the civic-landing-page repo - remove, deprecate?

[MikeTheCanuck]

In my quest to clean up deprecated/unused HackO resources, I stumbled across this repo:

https://github.com/hackoregon/civic-landing-page

It appears from the Travis config that this is the source of the landing page for http://civicpdx.org, published via S3 in the bucket https://s3.console.aws.amazon.com/s3/buckets/civicpdx.org.

However I've been tricked before by the spray of redundant/competing publishing strategies that were hacked together last year during the frantic final days leading up to the 2017 Demo Day (may the gods have mercy on our souls for that fiasco).

So while it's possible that this very S3 bucket still hosts the resources that answer to the URL http://civicpdx.org, I'm not going to believe that until I can prove it to my own eyes.

And further, determine what is a more intelligent home for such a resource. Or even if we intend to continue to host any content whatsoever here, or maybe simply put in a redirect to the new http://civicplatform.org site.

[MikeTheCanuck]

Does the S3 bucket still receive requests?

Let's trace this through the various layers of our system:

• according to the config of the bucket, "bucket hosting" aka static website hosting is still enabled for this bucket, and it still uses index.html as the bucket's index page
• in Route 53, the "A" record for civicpdx.org is still pointing to s3-website-us-west-2.amazonaws.com.

So that's a "yes" then.

[MikeTheCanuck]

What to do now?

We could just leave this in place as an historical artifact, but I'm of the mind to make simple cleanup steps to keep the overall brand strategy clean and to make it less confusing for non-HackO folks to figure out where the intended resources are - even if they're following outdated links from outside or inside our HackO resources (GitHub repos, old emails, blogs, articles...)

Recommendations

1. [x] Leave the URL accessible - it's a domain we own, it probably costs very little to renew at GoDaddy, and there are likely links out in the world that still lead to it. (Not to mention all the APIs are still published via the service.civicpdx.org subdomain.)
2. [ ] Redirect this URL to http://civicplatform.org - the new branding for the current HackOregon digital assets. We can use the "Redirect requests" capability of the static website hosting feature of the existing S3 bucket:
3. [x] Clean out the files - no need to keep the files there (it'd just be more confusion for some future devops nerd - future Mike, or one of our descendents).
4. [ ] Annotate the civic-landing-page repo with a README and/or Description that indicates this content is deprecated, has been replaced with content in the civic repo.

[MikeTheCanuck]

I've left behind this PR 8 to indicate this repo is no longer needed. There's nothing more I have the power to do, and now that the civicpdx.org bucket is gone, and civicpdx.org redirects to 2017.civicpdx.org, I've done all I can to clean up this rot.