Merge pull request #204 from steinim/oslo-2016

Added Oslo 2016

content/events/2016-oslo/conduct.md

@@ -0,0 +1,36 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.

content/events/2016-oslo/contact.md

@@ -0,0 +1,17 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}

content/events/2016-oslo/location.md

@@ -0,0 +1,21 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "location"
+type = "event"
+
++++
+
+<h3>Location</h3>
+
+<a href="http://www.gamlemuseet.no/english/">Gamle Museet /The Old Museum</a> is centrally located in Dronningensgate 4. It is close to public communication with all bus and tram lines in the immediate vicinity and 5 minute walk to Oslo central station. A parking garage is located within a two minute walk from the venue.
+
+<div>
+<iframe width="400" height="225" frameborder="0" style="border:0"
+src="https://www.google.com/maps/embed/v1/place?q=place_id:ChIJMRa1nmVuQUYRsofLI9AhgKk&key=AIzaSyCQVseQXE2vOLizZJWabRhrHZJB9GpEwhs" allowfullscreen></iframe>
+</div>
+
+<h3>Accommodation</h3>
+<a href="http://www.thonhotels.com/standalone-pages/block-booking/devopsdays-is-coming-to-oslo-/">Thon Hotel Oslo Panorama</a> offer discounted rates for attendees and is just a two minute walk from the conference.
+
+
+<!-- {{< event_map >}} -->

content/events/2016-oslo/program.md

@@ -0,0 +1,122 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "program"
+type = "event"
+
++++
+
+<hr>
+<div class="span-16 last ">If you are new to the Open Space concept you may <a href="/pages/open-space-format">want to read some more details</a>.</div>
+</center>
+<hr />
+
+
+<center><b><h2>The Schedule</h2></b></center>
+<div class="span-7 append-bottom border">
+
+<div class="span-7 last">
+<h4>Day 1</h4>
+</div>
+
+<div class="span-2">08:00-09:00</div><div class="span-4 box last">Registration, Breakfast, and Sponsor Booths Open</div>
+<div class="span-2">09:00-9:15</div><div class="span-4 box last"><strong></strong>Opening Welcome</div>
+<div class="span-2">09:15-09:45</div><div class="span-4 box last">
+    <br />
+</div>
+<div class="span-2">09:45-09:55</div><div class="span-4 box last">
+  Sponsors
+</div>
+<div class="span-2">09:55-10:25</div><div class="span-4 box last">
+    <br />
+
+</div>
+<div class="span-2">10:25-10:40</div><div class="span-4 box last">
+  Break
+</div>
+
+<div class="span-2">10:40-11:10</div><div class="span-4 box last">
+    <br />
+</div>
+
+<div class="span-2">11:10-11:20</div><div class="span-4 box last">
+  Sponsors
+</div>
+
+<div class="span-2">11:20-11:50</div><div class="span-4 box last">
+    <br />
+</div>
+
+<div class="span-2">11:50-13:00</div><div class="span-4 append-bottom last">Lunch (catered)</div>
+
+<div class="span-2">13:00-13:30</div><div class="span-4 box last"><strong>Ignites</strong> <br />
+</div>
+
+<div class="span-2">13:30-14:00</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space Opening</div>
+
+<div class="span-2">14:00-14:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #1</div>
+
+<div class="span-2">15:00-15:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #2</div>
+
+<div class="span-2">16:00-16:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #3</div>
+
+<div class="span-2">16:45-17:00</div><div class="span-4 box last"><strong></strong>Close Day & Logistics</div>
+
+<div class="span-2">19:00-late</div><div class="span-4 box last"><strong>Evening Event</strong><br /></div>
+
+
+</div>
+
+
+<div class="span-7 append-bottom border">
+
+<div class="span-7 last">
+<h4>Day 2</h4>
+</div>
+
+<div class="span-2">08:00-09:00</div><div class="span-4 box last"> Registration, Breakfast, and Sponsor Booths Open</div>
+<div class="span-2">09:00-9:15</div><div class="span-4 box last"><strong></strong>Opening Welcome</div>
+<div class="span-2">09:15-09:45</div><div class="span-4 box last">
+    <br />
+</div>
+<div class="span-2">09:45-09:55</div><div class="span-4 box last">
+  Sponsors
+</div>
+<div class="span-2">09:55-10:25</div><div class="span-4 box last">
+    <br />
+
+</div>
+<div class="span-2">10:25-10:40</div><div class="span-4 box last">
+  Break
+</div>
+
+<div class="span-2">10:40-11:10</div><div class="span-4 box last" style="height:100px;">
+    <br />
+</div>
+
+<div class="span-2">11:10-11:20</div><div class="span-4 box last">
+  Sponsors
+</div>
+
+<div class="span-2">11:20-11:50</div><div class="span-4 box last">
+    <br />
+</div>
+
+<div class="span-2">11:50-13:00</div><div class="span-4 append-bottom last">Lunch (catered)</div>
+
+<div class="span-2">13:00-13:30</div><div class="span-4 box last"><strong>Ignites</strong> <br />
+
+</div>
+
+<div class="span-2">13:30-14:00</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space Opening</div>
+
+<div class="span-2">14:00-14:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #1</div>
+
+<div class="span-2">15:00-15:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #2</div>
+
+<div class="span-2">16:00-16:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #3</div>
+
+<div class="span-2">17:00</div><div class="span-4 box last"><strong></strong>Close Day & Farewell</div>
+
+
+
+</div>

content/events/2016-oslo/proposals/A_DevOps_State_of_Mind_with_Docker_and_Kubernetes.md

@@ -0,0 +1,20 @@
++++
+date = "2016-05-04T12:14:21-07:00"
+type = "talk"
+title = "A DevOps State of Mind with Docker and Kubernetes"
++++
+
+**Abstract:**
+Rapid innovation, changing business landscapes, and new IT demands force businesses to make changes quickly. The DevOps approach is a way to increase business agility through collaboration, communication, and integration across different teams in the IT organization. In this presentation, you’ll learn about:
+<ul>
+  <li>The acceleration of Application Delivery for the Business with DevOps</li>
+  <li>The transformation of IT to a DevOps, Microservices, and Container based Cloud Architecture</li>
+  <li>How DevOps practices can operate in a Docker and Kubernetes, enabled environment.</li>
+  <li>Docker, Kubernetes and DevOps, used together, can reduce software delivery cycle times, drive automation, and increase efficiency.</li>
+  <li>How other organizations are using DevOps and how to replicate their success</li>
+</ul>
+Join Chris Van Tuin, Chief Technologist, West at Red Hat, as he walks through how DevOps can accelerate application delivery for the Business.
+
+**Speaker:**
+Chris Van Tuin, Chief Technologist for the Western US at Red Hat, has over 20 years of experience in IT and Software. Since joining Red Hat in 2005, Chris has been architecting solutions for strategic customers and partners with a focus on emerging technologies including IaaS, PaaS, and DevOps. He started his career at Intel in IT and Managed Hosting followed by leadership roles in services and sales engineering at Loudcloud and Linux startups. Chris holds a Bachelors of Electrical Engineering from Georgia Institute of Technology.
+

content/events/2016-oslo/proposals/Continuous_Delivery_DevOps_Public_Cloud_Computing_and_Microservices_Architecture_How_does_it_all_fit_together.md

@@ -0,0 +1,12 @@
++++
+date = "2016-05-04T12:14:21-07:00"
+type = "talk"
+title = "Continuous Delivery, DevOps, Public Cloud Computing and Microservices Architecture: How does it all fit together?"
++++
+
+**Abstract:**
+These practices can be viewed as the foundation of modern SaaS development and delivery. This talk aims to give a high level overview of what they are, what benefits they bring and more importantly how they are related and how they synergize. People who are already well-versed in these areas might pickup some useful inspiration for how to communicate about these ideas and bring that back into their own organization.
+
+**Speaker:**
+<a href=https://no.linkedin.com/in/alexanderlystad">T. Alexander Lystad, Chief QA Architect, Visma Enterprise Solutions</a>
+

content/events/2016-oslo/proposals/Continuous_Delivery_in_a_250-year_old_company.md

@@ -0,0 +1,16 @@
++++
+date = "2016-05-04T12:14:21-07:00"
+type = "talk"
+title = "Continuous Delivery in a 250-year old company"
++++
+
+**Abstract:**
+The literature and blogosphere around continuous delivery is littered with shining examples describing DevOps teams, container technologies, cloud platforms and green-field implementations. At Storebrand, our challenge was slightly different: We had an existing legacy of monolithic applications, cumbersome platforms, third-party operations teams, ITIL-heavy change processes and heavily orchestrated releases. We wanted something better, but could not throw away what we had and start again. Nor did we have any budgets or executive sponsors.
+
+This talk will relay the story of how we moved into the world of continuous delivery one step at a time, without large rewrites or interruptions of ongoing projects. It will be a story of how ideal solutions seldom match the real-life requirements of an existing architecture, and how these can be overcome if you apply creativity, opportunism and a little bit of patience. We will also demonstrate how a loosely coupled and simplistic architecture can provide more flexibility than relying too much on a single tool or technology.
+
+**Speaker:**
+Terje Løken is a former C++ programmer, Chief Architect and now unit manager for the "Digital & Mobile" unit @ Storebrand. His interests include distributed systems, evolving architectures and ways to make organizations and developers work smarter and faster.
+
+He is also a fan of simplicity, grassroots activism and evolutionary change. He often considers patience, good timing and a keen sense of judgement equally important as technical mastery when evolving an architecture or bringing about change.
+

content/events/2016-oslo/proposals/Continuous_Integration_May_Cause_Troubles.md

@@ -0,0 +1,12 @@
++++
+date = "2016-05-04T12:14:21-07:00"
+type = "talk"
+title = "Continuous Integration May Cause Troubles"
++++
+
+**Abstract:**
+CI is a well-known and popular methodology, which is supposed to help software projects to stabilize their source code and make the entire development more predictable and surprise-free. Even though all this sounds very good in theory, the practice is different. in many companies I’ve been consulting with, the situation is very similar - continuous integration is causing troubles if being aggressively enforced. There is a very logical reason for that, which I will discuss at the session and will suggest a vendor-neutral solution.
+
+**Speaker:**
+Yegor Bugayenko is a CTO at Teamed.io, a software development company with an extremely distributed working model; a VC at SeedRamp.com; a regular blogger at www.yegor256.com; author of Elegant Objects book; a proud holder of PMP and OCMEA certifications; a hands-on Java developer and a lead architect of rultor.com and takes.org. Yegor lives in Palo Alto, CA and Kyiv, Ukraine.
+

content/events/2016-oslo/proposals/Dont_forget_the_humans.md

@@ -0,0 +1,12 @@
++++
+date = "2016-05-04T12:14:21-07:00"
+type = "talk"
+title = "Don’t forget the humans"
++++
+
+**Abstract:**
+Well architected, modern infrastructure is as automated and self-managing as possible, but it still requires human operation for maintenance, upgrades and incident response. This talk will consider the human element and how humans should be considered a part of the system just like any other. It will propose several key principles concerning how systems should work alongside humans and give real world examples of how to implement them with war games and simulation training.
+
+**Speaker:**
+David Mytton is the founder of Server Density, a SaaS monitoring product. David has been programming in Python for 7+ years, having written the original monitoring agent code that now processes over 250TB/month of monitoring data from organisations such Boeing, Greenpeace and the UK’s NHS Ambulance Emergency Response.
+

content/events/2016-oslo/proposals/From_Chaos_to_Confidence.md

@@ -0,0 +1,12 @@
++++
+date = "2016-05-04T12:14:21-07:00"
+type = "talk"
+title = "From Chaos to Confidence - evolving our DevOps operating model at LeanKit"
++++
+
+**Abstract:**
+As a company, LeanKit have believed in Lean, Kanban, Agile, DevOps since our founding. We've alway talked about how important these ideas are - in the community and inside our company. But that doesn't mean that doing those things in practice has been easy. We're a very fast growing startup in a very competitive market space. We've tripled in size in less than a year and nearly came apart at the seams at times. In fact, in the fall of 2015, our technology team were having a very hard team. We were out of synch with our sales & marketing partners and facing a lot of internal conflict. But we came together as a team and worked hard to implement a well coordinated system of values, team structure, cadences, and standard practices. We're now in a much better place as a team and generating much better results for our company. There are no one-size-fits-all answers for companies. I can't promise that if you copy LeanKit you'll succeed. But we do think we have some interesting lessons learned to share and that you just might be able to pick up some ideas that you can take back to your company.
+
+**Speaker:**
+Jon Terry is Chief Operating Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods. Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
+

content/events/2016-oslo/proposals/How_we_built_the_Node_js_Foundation_with_Open_Open_Source.md

@@ -0,0 +1,19 @@
++++
+date = "2016-05-04T12:14:21-07:00"
+type = "talk"
+title = "How we built the Node.js Foundation with Open Open Source"
++++
+
+**Abstract:**
+Rewind to early 2013. Node.js v0.10 had just been released - this is the golden days of Node.js... and the beginning of the end. The <a href="https://en.wikipedia.org/wiki/Benevolent_dictator_for_life">BDFL-model</a> and project stewardship have severely limited contribution (especially from larger corporations), and the lack of communication and transparency around decision making is making life as contributor to Node.js core intolerable. Stagnation of technical progress was unavoidable. Was Node.js doomed to fail before it could take off?
+
+You probably know by now that Node.js did not fail, adoption and usage of Node.js has continued to grow each year. But how did this happen when the project was heading to a certain doom? In this talk I will use the backstory of how Node.js is built around the notion of openness and collaboration - known as <a href="http://openopensource.org/">Open Open Source</a> - to mobilise the community (more than 450 members in the GitHub organisation) and activate more contributors! I also talk about how the Node.js Foundation is structured and how all the bits and pieces works on building Node.js - one way or another.
+
+The Open Open Source mantra:
+
+<blockquote>Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.</blockquote>
+
+**Speaker:**
+Hans Kristian Flaatten is an Open Source and Open Data evangelist. He is an acting member of the Node.js Foundation where he manage the test and release infrastructure for official Node.js versions, as well as the official Docker Image for Node.js.
+
+He is a Senior Systems Developer / DevOps at the Norwegian Trekking Association (Norway's biggest outdoor activities organisation) where he have lead the transition to a microservice oriented architecture on immutable infrastructure and Docker Containers. He have also spear headed DNT's initiative on Open Data through <a href="http://ut.no/">UT.no</a> and Nasjonal Turbase.