diff --git a/content/events/2016-minneapolis/program.md b/content/events/2016-minneapolis/program.md
index 200a1eb8aad..32de9fbb70e 100644
--- a/content/events/2016-minneapolis/program.md
+++ b/content/events/2016-minneapolis/program.md
@@ -8,27 +8,29 @@ type = "event"
+++
-
+With talks in the morning and attendee-suggested
Open Space breakout discussions in the afternoon, we have two full days of content!
-The Schedule
+Schedule
-
Day 1
+Wednesday July 20
08:00-09:00
Registration, Breakfast, and Sponsor Booths Open
09:00-9:15
Opening Welcome
09:15-09:45
09:45-09:55
Sponsors
09:55-10:25
@@ -37,6 +39,7 @@ type = "event"
10:40-11:10
@@ -45,26 +48,27 @@ type = "event"
11:20-11:50
11:50-13:00
Lunch (catered)
-13:00-13:30
Ignites
-
+13:00-14:00
Open Space (Open Space)
Open Space Opening
-13:30-14:00
Open Space (Open Space)
Open Space Opening
+14:00-14:45
attendee-suggested Open Space breakout discussions Open Space #1
-14:00-14:45
Open Space (Open Space)
Open Space #1
+14:45-15:00
Break
-15:00-15:45
Open Space (Open Space)
Open Space #2
+15:00-15:45
attendee-suggested Open Space breakout discussions Open Space #2
-16:00-16:45
Open Space (Open Space)
Open Space #3
+15:45-16:30
attendee-suggested Open Space breakout discussions Open Space #3
-16:45-17:00
Close Day & Logistics
+16:30-16:45
Closing
-19:00-late
Evening Event
+17:00-18:00
Sponsor happy hour
+18:00-20:00
Evening Event
@@ -72,18 +76,20 @@ type = "event"
-
Day 2
+Thursday July 21
08:00-09:00
Registration, Breakfast, and Sponsor Booths Open
09:00-9:15
Opening Welcome
09:15-09:45
09:45-09:55
Sponsors
09:55-10:25
@@ -92,6 +98,7 @@ type = "event"
10:40-11:10
@@ -100,24 +107,23 @@ type = "event"
11:20-11:50
11:50-13:00
Lunch (catered)
-13:00-13:30
Ignites
-
-
+13:00-14:00
Open Space (Open Space)
Sponsor Raffle & Open Space Opening
-13:30-14:00
Open Space (Open Space)
Open Space Opening
+14:00-14:45
attendee-suggested Open Space breakout discussions Open Space #1
-14:00-14:45
Open Space (Open Space)
Open Space #1
+14:45-15:00
Break
-15:00-15:45
Open Space (Open Space)
Open Space #2
+15:00-15:45
attendee-suggested Open Space breakout discussions Open Space #2
-16:00-16:45
Open Space (Open Space)
Open Space #3
+15:45-16:30
attendee-suggested Open Space breakout discussions Open Space #3
-17:00
Close Day & Farewell
+16:30-16:45
Closing
diff --git a/content/events/2016-minneapolis/program/allan-espinosa.md b/content/events/2016-minneapolis/program/allan-espinosa.md
new file mode 100644
index 00000000000..81e7615925f
--- /dev/null
+++ b/content/events/2016-minneapolis/program/allan-espinosa.md
@@ -0,0 +1,29 @@
++++
+City = "Minneapolis"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Allan Espinosa"
+type = "talk"
+aliases = ["/events/2016-minneapolis/program/allanespinosa/"]
+
++++
+
+
+
+
Title:
+Autoscaling Containers... with Math
+
+
+
Description:
+
+
Docker and Kubernetes provide delightful APIs to show various statuses of our applications. Whether CPU, Load average, HTTP response times, etc., we have all that we need to make sure our app is running healthily. When things are on fire, we Ops people twiddle some knobs like spin up more Pods to keep things going. We mostly use our experience and knowledge of the systems that we are running to know what to do.
+
+
+However, if you look at everyday things like your air conditioner and thermostat, they don't have an Ops team that gets paged to set the correct level of the coolant to set your room to the right temperature. They use some math called Control Theory to keep your room's temperature stable. In this talk, I will show how we can use the same concepts to autoscale and manage the health of our applications on Kubernetes.
+
+
+
+
+
+
+
+
Title:
+What if You Can’t Tear Down All The Silos?
+
+
+
Description:
+
+
+We keep hearing that to 'do DevOps right' we need to tear down all the silos in order to get everyone collaborating as well as just cooperating. How do we continue to benefit from DevOps practices when the silos are there for the foreseeable future and may actually have some benefit, even if only perceived?
+
+
+In a large enterprise, dedicated operations groups frequently serve multiple development groups, using the specialization of these groups to increase efficiency by having a smaller operations staff. These organizations use separation of duties to avoid real or apparent conflicts of interest and a higher level of security. Silos become firmly embedded because they work in these situations.
+
+
+When silos are entrenched and can’t be torn down, or even when they’re just dictated above our pay grades, how can we use DevOps to increase collaboration and empathy? What other concepts of DevOps can we use to reduce the pain? What can operations teach development and learn from development to make systems more reliable and IT more successful?
+
+
+In this session, I’ll present my version of the DevOps philosophy and how it can be applied in an enterprise environment without tearing down all the silos. I’ll tell success stories and failures as well as discussing continuing challenges to make improvements and change the culture in the trenches.
+
+
+
+
+
+
+
+
+
+
Title:
+Making good choices with software (and other impossible things) (Closing Keynote)
+
+
+
Description:
+
+
+Once upon a time there was a LAMP stack, and a data center, and making reasonably good technical decisions was a thing that ordinary mortals could do. Over the last few years we've seen an explosion of complexity -- composable infrastructure, polyglot persistence, and third-party platforms or services who claim they can solve your problems for you (sometimes this is even true!).
+
+
+
+What does this mean for you and me? It means that good technical judgment is both more challenging and more important than ever before. In this talk we will cover things like about when to use boring technology, versus when to take a flyer on something new and shiny. We'll also talk about how to resist software sprawl, gating new technologies into production, and how to balance speed of development vs operational impact over time. So don't despair! With just a little bit of discipline, we can still build systems that ordinary humans can understand and maintain, even in the face of skyrocketing complexity and problems of scale."
+
+
+
+
+
+
+
+
Title:
+Intentional Design of Your Monitoring System
+
+
+
Description:
+
+
+A good monitoring stack is more than the software that says ‘monitoring’ on the label. Maybe your monitoring system is a bunch of cron scripts that send email when things happen. Maybe you dropped $100K on licensed software that can email reports and has its own mobile app. When used as part of systemic approach to monitoring, both approaches can lead your organization to success.
+
+
+
+Monitoring is a stack, and like most web applications there are discrete components that all systems have. Sometimes they’re automated, sometimes they’re 100% people-driven. What matters is that you have the system that works for you and your organization.
+
+
+
+We will cover what those components are and how they work together. What’s more, we’ll touch on the conversations you should have as you work to systematize your monitoring practices. We won’t tell you what technology you should use, that’s entirely up to you."
+
+
+
+
+
+
+
+
+
Title:
+DevOps: What’s Buried in the Fine Print
+
+
+
Description:
+
+
+Your organization is rolling out DevOps and everyone is excited and on-board! Life is going to be perfect post-devops, because DevOps is the cure for all that ails your company. Because levels expectations and levels of disappointment seem to have a relationship, I’d like to talk to you about our experience with the DevOps transformation.
+
+
+Come join Jeff Smith as he walks through the trials and tribulations of destroying the silos in your organization. Buried inside all of the hype of DevOps are hurdles, people problems and mission creep that can derail your transformation. We’ll cover areas like:
+
+
+* Toolchain Paralysis - With all the tools out there to help you realize the DevOps dream, its easy to get caught up in the tools/solution hype cycle. Don’t let the community tell you what is a must-do. We’ll talk about making sure you solve your problems instead of Google’s or Facebook’s.
+
+
+* Skill set augmentation - DevOps chats are famous for the adage “Hire the Right People”. But I’m guessing you already thought you were doing that. How do you get developers and ops to gain skills in the other’s discipline?
+
+
+* On Call Support - When you disperse Ops staff into stream teams, you also have the potential to dilute the number of on-call people who can handle issues. There are tons of options and all of them have a downside.
+
+
+and more! Don’t think these hurdles are new or unique. You’ll get through them, and hopefully we’ll help show you how.
+
+
+
+
+
+
+
+
+
+
+
Title:
+How Security Can Win Friends and Influence People
+
+
+
Description:
+
+
+Security 101 principles often conflict with how organizations function in the real world. Developers need flexibility in order to solve hard problems; companies need a stable product to satisfy customers. Employees don’t want to click through ten different screens to complete daily tasks; auditors and regulators demand logs and accountability.
+
+
+
+Legacy systems need to be monitored. New projects need to be nurtured. And, while you’re doing all of that, attackers are constantly rattling the doorknobs to find a foothold in your network. I’ll go over a few lessons I’ve learned about how security departments can lobby for continuous improvement, while collaborating with others and even occasionally saving the organization money.
+
+
+
+Over my career, I’ve worked in .com, retail, and academia. While the challenges in each of these realms are unique, there is a common thread in all of the successful outcomes I’ve witnessed. Effective security departments are optimists who play well with others.
+
+
+
+It's fun to pretend you're the smartest person in the room ... until no one wants to play with you. The “us versus the world” mindset isn’t constructive. In this talk I’ll illustrate how security can work for change without alienating everyone else on the playground.
+
+
+
+
+
+
+
+
Title:
+The Data on DevOps: Making the Case for Awesome
+
+
+
Description:
+
+
+What’s the value proposition of DevOps? Does culture change show up in the bottom line? What practices predict high IT performance? We hear many stories to inspire and inform us, but the plural of anecdote is not data. Let’s dive into the research and find out which DevOps practices drive optimal IT and business outcomes.
+
+
+
+The data shows that the best IT performers have the highest throughput and reliability while contributing to organizational profitability, productivity, and market share goals. Industry trends around security, containers, continuous delivery, and lean management relate to IT performance and quality: let’s talk about how.
+
+
+
+Management and practitioners alike will leave with a better understanding of how to achieve the best outcomes, while armed with the data they need to make the case for change.
+
+
+
+
+
+
+
+
Title:
+Marketing: your unexpected devops allies
+
+
+
Description:
+
+
+Development teams and sales/marketing teams aren't always BFFs. Too often, the relationship is downright dysfunctional: either marketing dictates what the product team builds based solely on what is "sellable" with little consideration to timelines or what non-customer-facing work needs to be done, or the product team does a bunch of random work with little consideration for creating a strong marketing "story". But it doesn't have to be this way.
+
+
+In the devops spirit of cross-team collaboration, why not recruit sales and marketing as your newest allies in the fight against workplace silos?
+
+
+This talk will cover practical and battle-tested ways to work together towards a higher-quality and more marketable piece of software. From semi-obvious things like information radiators, to deeper collaborations in roadmapping and release planning, there's a lot more you can do than just invite the sales team to your stand-ups.
+
+
+
+
+
+
Conference Talks
-
-TBD - need to create a template/shortcode for finding all the proposals
diff --git a/content/events/2016-minneapolis/propose.md b/content/events/2016-minneapolis/propose.md
index 79cf626f54d..214f5f0979f 100644
--- a/content/events/2016-minneapolis/propose.md
+++ b/content/events/2016-minneapolis/propose.md
@@ -6,14 +6,26 @@ title = "propose"
type = "event"
+++
- {{< cfp_dates >}}
+Ignite talks
+
+Want to be part of devopsdays Minneapolis? Got something to say? Can you say it in five minutes? We need you for our evening Ignite event. Have a side project, a unique hobby, a hilarious or tragicomic work story? Any topic is fair game as long as it’s something you’re passionate about. Speakers are limited to exactly 20 slides which auto-advance every 15 seconds. Sound like fun? Submit your Ignite now (or by May 15th)! We'll publish the Ignite schedule by June 1st.
+
+
+
+30 minute talks
+
+The CFP for 30-minute talks is closed and the selected talks have been listed on the program.
-We're now accepting proposals for 30-minute talks. We'll open proposals for 5-minute Ignite presentations much closer to the time of the conference.
+Open Space breakout sessions
+
If you'd like to lead a group discussion during the Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table.
+
+
-
+
+
Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
@@ -24,23 +36,5 @@ Choosing talks is part art, part science; here are some factors we consider when
- _no third-party submissions_: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
-How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
-
- - Proposal title
- - Description (including the actionable takeaway for attendees) - this will be posted on the website
- - Bio (a short summary of your background)
- - Anything else you'd like the organizers to know
- - Whether you live in the local area or work for a locally-based org (this works in your favor, in that we want to promote local voices)
- - Whether you need assistance with travel costs including hotel, flight, and parking (this does not affect our decision-making one way or the other)
- - Multiple proposals welcome; just follow the other guidelines
-
-Rules:
-
- - Be specific... we aren't mind readers (a description of about 20 lines is about right)
- - Detail is good... but not as important as explaining why your proposal would be interesting
- - Propose your own talk; don't have someone else do it for you.
- - Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
- - Multiple proposals welcome... just follow the other rules
-
If your employer does not cover travel expenses you incur as a speaker at devopsdays Minneapolis, the conference can and will help; speakers receive free conference tickets and should not need to incur out-of-pocket travel expenses in order to participate.
diff --git a/content/events/2016-minneapolis/welcome.md b/content/events/2016-minneapolis/welcome.md
index be3f15ea015..8200a566227 100644
--- a/content/events/2016-minneapolis/welcome.md
+++ b/content/events/2016-minneapolis/welcome.md
@@ -11,7 +11,7 @@ aliases = ["/events/2016-minneapolis"]
## {{< event_start >}} - {{< event_end >}}
-**DevOps Days is returning to Minneapolis!**
+**devopsdays is returning to Minneapolis!**
{{< event_logo >}}
@@ -28,16 +28,16 @@ aliases = ["/events/2016-minneapolis"]
| Propose |
- {{< event_link page="propose" text="Propose a 30 minute talk!" >}}. |
+ {{< event_link page="propose" text="Propose an Ignite!" >}} |
| Register |
{{< event_link page="registration" text="Register to attend the conference!" >}} |
-
+
| Sponsors |
{{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization. |
diff --git a/data/events/2016-minneapolis.yml b/data/events/2016-minneapolis.yml
index 71819168c5b..4f9cbdb8eb3 100644
--- a/data/events/2016-minneapolis.yml
+++ b/data/events/2016-minneapolis.yml
@@ -10,7 +10,7 @@ cfp_date_end: 2016-03-31
cfp_date_announce: 2016-05-01
coordinates: "44.972610,-93.272960" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
location: "Downtown Minneapolis Hilton" # The name of your location
-navigationelements: ["welcome", "propose", "location", "registration", "sponsor", "contact", "conduct"] # List of pages you want to show up in the navigation of your page. Remove any that aren't relevent yet.
+navigationelements: ["welcome", "program", "propose", "location", "registration", "sponsor", "contact", "conduct"] # List of pages you want to show up in the navigation of your page. Remove any that aren't relevent yet.
team: ["Tom Duffield", "Bridget Kromhout", "Andy Domeier", "Donnie Berkholz", "Tony Notto", "Joe Laha", "Heather Mickman", "Jeff Williams", "Samantha Grumdahl"]
organizer_email: "organizers-minneapolis-2016@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-minneapolis-2016@devopsdays.org" # Put your proposal email address here
@@ -63,3 +63,26 @@ sponsor_levels: # In this section, list the level of sponsorships and the label
label: Silver
- id: community
label: Community Partner
+
+speakers:
+ - id: "nicole-forsgren"
+ level: talk
+ - id: "megan-carney"
+ level: talk
+ - id: "jamie-riedesel"
+ level: talk
+ - id: "jeff-smith"
+ level: talk
+ - id: "ben-zvan"
+ level: talk
+ - id: "sarah-goff-dupont"
+ level: talk
+ - id: "allan-espinosa"
+ level: talk
+ - id: "charity-majors"
+ level: talk
+
+
+speaker_levels:
+ - id: talk
+ label: Talk
diff --git a/data/speakers/2016minneapolis/allan-espinosa.yml b/data/speakers/2016minneapolis/allan-espinosa.yml
new file mode 100644
index 00000000000..27a4b19e4ae
--- /dev/null
+++ b/data/speakers/2016minneapolis/allan-espinosa.yml
@@ -0,0 +1,3 @@
+name: "Allan Espinosa"
+twitter: "AllanEspinosa"
+bio: "Allan works at Engineyard where he supports customers' Deis, Docker and Kubernetes infrastructures in production. Prior to that, he worked on managing one of the world's largest CloudFoundry deployments using Chef.\n Allan is also the author of _Docker High Performance_ from Packt Publishing. The book contains some worked examples and high level concepts on how to get Docker up and running in production."
diff --git a/data/speakers/2016minneapolis/ben-zvan.yml b/data/speakers/2016minneapolis/ben-zvan.yml
new file mode 100644
index 00000000000..67e4ba11801
--- /dev/null
+++ b/data/speakers/2016minneapolis/ben-zvan.yml
@@ -0,0 +1,3 @@
+name: "Ben Zvan"
+twitter: "BenZvan"
+bio: "Ben Zvan is an IT professional who has been using Linux since 1996. He started his professional Ops career at the University of Minnesota in 2006 and moved to Capella University, a for-profit university in Minnesota, in 2011. He has concentrated on the mantra \"simplify, standardize, automate\" since hearing the phrase from Jim Hall at the U of MN, when he realized that's what he had been doing for years. Learning about agile and DevOps made him an instant evangelist. He currently struggles with change management, production support, and not having enough time for photography or motorcycling."
diff --git a/data/speakers/2016minneapolis/charity-majors.yml b/data/speakers/2016minneapolis/charity-majors.yml
new file mode 100644
index 00000000000..20c1e128e56
--- /dev/null
+++ b/data/speakers/2016minneapolis/charity-majors.yml
@@ -0,0 +1,3 @@
+name: "Charity Majors"
+twitter: "mipsytipsy"
+bio: "Cofounder and CTO of Hound, a new startup focused on mining machine data. Previously running infrastructure at Parse, engineering manager at Facebook. Worked with the RocksDB team to build and deploy world’s first Mongo+Rocks in production. Likes single malt scotch."
diff --git a/data/speakers/2016minneapolis/jamie-reidesel.yml b/data/speakers/2016minneapolis/jamie-reidesel.yml
new file mode 100644
index 00000000000..ad59261e605
--- /dev/null
+++ b/data/speakers/2016minneapolis/jamie-reidesel.yml
@@ -0,0 +1,3 @@
+name: "Jamie Reidesel"
+twitter: "sysadm1138"
+bio: "Jamie Riedesel started out in Government IT for the City of St. Paul and has since moved into the private sector. Currently she’s working remotely for a San Francisco based startup. In the meantime, she’s earned the Chuck Yerkes award from LOPSA for being helpful online, and is trying to become more helpful in person."
diff --git a/data/speakers/2016minneapolis/jeff-smith.yml b/data/speakers/2016minneapolis/jeff-smith.yml
new file mode 100644
index 00000000000..1048f7351c2
--- /dev/null
+++ b/data/speakers/2016minneapolis/jeff-smith.yml
@@ -0,0 +1,3 @@
+name: "Jeff Smith"
+twitter: "DarkAndNerdy"
+bio: "Jeff Smith has been in the technology field for over 15 years, oscillating between manager and individual contributor. He currently serves as the Manager of Site Reliability Engineering at GrubHub. Jeff enjoys discussing the psychological aspect of problems in organizations. Jeff is also one of the co-founders of the Chicago Nerd Social Club. He occasionally musters up the strength to write on his All Things Dork blog."
diff --git a/data/speakers/2016minneapolis/megan-carney.yml b/data/speakers/2016minneapolis/megan-carney.yml
new file mode 100644
index 00000000000..6e4f90d2295
--- /dev/null
+++ b/data/speakers/2016minneapolis/megan-carney.yml
@@ -0,0 +1,3 @@
+name: "Megan Carney"
+twitter: "PwnieFan"
+bio: "Megan Carney is an Infosecurity engineer at Yelp. Previous to working with Yelp, she worked as an analyst at a university and a retail company. She tries to keep her paranoia at healthy levels while protecting Yelp from the evils of the Internet."
diff --git a/data/speakers/2016minneapolis/nicole-forsgren.yml b/data/speakers/2016minneapolis/nicole-forsgren.yml
new file mode 100644
index 00000000000..ef4541eca3e
--- /dev/null
+++ b/data/speakers/2016minneapolis/nicole-forsgren.yml
@@ -0,0 +1,3 @@
+name: "Nicole Forsgren"
+twitter: "nicolefv"
+bio: "Dr. Nicole Forsgren is an IT impacts expert who shows leaders and practitioners how to unlock the potential of technology change in their organizations. Best known for her work with tech professionals and as the lead investigator on the State of DevOps Reports, she is the Director of Organizational Performance and Analytics at Chef and an Academic Partner at Clemson University. In a previous life, she was a professor, sysadmin, and hardware performance analyst."
diff --git a/data/speakers/2016minneapolis/sarah-goff-dupont.yml b/data/speakers/2016minneapolis/sarah-goff-dupont.yml
new file mode 100644
index 00000000000..d003e2f7a14
--- /dev/null
+++ b/data/speakers/2016minneapolis/sarah-goff-dupont.yml
@@ -0,0 +1,3 @@
+name: "Sarah Goff-Dupont"
+twitter: "DevToolSuperFan"
+bio: "Sarah has been working in and around software teams for 14 years – as QA engineer, agile coach, and now a marketer. When not writing about all things agile and/or automated, she can be found reading contemporary fiction, smashing it out & keeping it real at CrossFit, or rolling around on the floor with her kids (possibly all at once)."
diff --git a/themes/devopsdays-legacy/layouts/talk/single.html b/themes/devopsdays-legacy/layouts/talk/single.html
new file mode 100644
index 00000000000..72eabbf1a57
--- /dev/null
+++ b/themes/devopsdays-legacy/layouts/talk/single.html
@@ -0,0 +1,74 @@
+{{ partial "header.html" . }}
+
+{{/*
+ This section is what creates the query to get at all the site data. If you need this somewhere, you can just copy
+ it and paste it. Need to figure out if a partial would expose the variables/elements/array created herein. It could be done in a partial (need to include the trailing .) but I don't think it would work in shortcodes, which is where we need it the most - mattstratton
+*/}}
+
+{{ $path := split $.Source.File.Path "/" }}
+{{ $event_slug := index $path 1 }}
+{{ $event := (print .Params.year (lower .Params.city)) }}
+{{ $e := (index $.Site.Data.events $event_slug) }}
+
+{{/* end site data query */}}
+
+
+
+
+
{{ $e.city }} {{ $e.year }} - {{ title .Title }}
+
+
+
+ {{ .Content }}
+
+
+
+
+ {{ range $fname, $s := index .Site.Data.speakers (printf "%s%s" $e.year (lower $e.city) ) }}
+ {{ if eq $fname ($.Title | urlize) }}
+
Speaker
+
{{ $s.name }}
+
@{{ $s.twitter }}
+
+ {{ $s.bio | markdownify }}
+ {{ end }}
+ {{ end }}
+
+
+
+
+
+
+
+
+
+
+
+
+
+ {{ $sponsors := $e.sponsors }}
+ {{ range $e.sponsor_levels }}
+
{{ .label }} Sponsors
+ {{ range where $sponsors "level" .id }}
+ {{ $s := (index $.Site.Data.sponsors .id) }}
+ {{ if isset $.Site.Data.sponsors .id }}
+
+ {{ end }}
+ {{ end }}
+
+ {{ end }}
+
+
+
+
+
+