Migrate events from 2015 and before

[mattstratton]

Migrate data from all past events (2015 and before) to new system.

Here is an attempt of a list of all the events needed to migrate, so we can track.

• 2009
  • Ghent 2009
• 2010
  • Sydney 2010
  • Mountain View 2010
  • Hamburg 2010
  • Sao Paulo 2010
• 2011
  • Boston 2011
  • Mountain View 2011
  • Melbourne 2011
  • Bangalore 2011
  • Göteborg 2011
  • Manila 2011
• 2012
  • Austin 2012
  • Tokyo 2012
  • Delhi 2012
  • Mountain View 2012
  • Rome 2012
  • New York 2012
• 2013
  • New Zealand 2013
  • London 2013
  • Paris 2013
  • Austin 2013
  • Berlin 2013
  • Amsterdam 2013
  • Silicon Valley 2013
  • Downunder 2013
  • Bangalore 2013
  • London Autumn 2013
  • Barcelona 2013
  • Vancouver 2013
  • Portland 2013
  • New York 2013
  • Atlanta 2013
  • Tel Aviv 2013
  • Tokyo 2013
• 2014
  • Nairobi 2014
  • Ljubljana 2014
  • Austin 2014
  • Pittsburgh 2014
  • Amsterdam 2014
  • Silicon Valley 2014
  • Minneapolis 2014
  • Brisbane 2014
  • Boston 2014
  • Toronto 2014
  • New York 2014
  • Warsaw 2014
  • Chicago 2014
  • Berlin 2014
  • Belgium 2014
  • Helsinki 2014
  • Vancouver 2014
  • Tel Aviv 2014
  • Bangalore 2014
• 2015
  • Ljubljana 2015
  • Paris 2015
  • Denver 2015
  • New York 2015
  • Austin 2015
  • Toronto 2015
  • Washington, DC 2015
  • Amsterdam 2015
  • Minneapolis 2015
  • Melbourne 2015
  • Pittsburgh 2015
  • Chicago 2015
  • Bangalore 2015
  • Boston 2015
  • Tel Aviv 2015
  • Singapore 2015
  • Berlin 2015
  • Charlotte 2015
  • Silicon Valley 2015
  • Detroit 2015
  • Ohio 2015
  • Warsaw 2015

[mattstratton]

@jedi4ever if you could offer some insight into the traffic that the older sites get, it will help me make a design decision on how the migration occurs.

Right now, there are a couple different ways to handle it:

1. Create new events (in the new structure) for all the old events. This involves creating a data file for each event, mapping sponsors to the sponsor structure, and updating every file in each "old" event folder to use the new templating language. I would estimate the level of effort per event to be 1-2 hours of VERY boring work.
2. Copy the existing generated HTML files from webby for each event to the corresponding file patths in hugo. Hugo will ignore any .html files, so they would not be evaluated. This is by far the easiest way to do it (the whole thing will probably take an hour or two, as opposed to 1-2 hours per event). The downside is that the legacy/old events become truly static. If/when we change the site design, these old URL's (which will always still work, with the same URL's as today) will just always have the "classic" DevOpsDays look to them.

The larger issue with the second option that I thought of (and just now realized doesn't apply) is the footer that lists all the events. That footer only exists on the homepage as it it is; the single event pages do not use it.

That being said, I see no reason to not go with option 2. Thoughts?

[jedi4ever]

@mattstratton I'm good with option 1 - as long as the URLs stay the same we're good.
On a side note we are currently using disquss for feedback - do you include that? or we don't bother

[bridgetkromhout]

On a side note we are currently using disquss for feedback - do you include that? or we don't bother

We're going to leave off the whole "upload your proposals ahead of time" thing. It's under-used and most places are using an external CFP processing site now.

[mattstratton]

Two notes -

1. My comment was incorrect. Option 2 is the proper option. There is no reason to do all the extra heavy lifting.

2. Disqus can easily be accommodated if needed (it's baked into hugo) but as @bridgetkromhout said, it's not heavily used so we aren't going to bring it along for the ride. It would be easy to add in the future if need be.

[jedi4ever]

@mattstratton me too, I meant indeed option2 is ok

[bridgetkromhout]

As I understand it, after Saturday April 16th @mattstratton will migrate whatever's in the old repo, with consideration for #104, #102, and maybe #142?

At that point we'll stop merging PRs on the old site for anything 2015 and before.

[bridgetkromhout]

This continues to be in progress.

[bridgetkromhout]

@mattstratton, please look over #292 and determine if this issue can now be closed - thanks!

[mattstratton]

I think we can close this one.