diff --git a/content/events/2015-boston/conduct.md b/content/events/2015-boston/conduct.md
deleted file mode 100644
index d2a969fa843..00000000000
--- a/content/events/2015-boston/conduct.md
+++ /dev/null
@@ -1,36 +0,0 @@
-+++
-date = "2016-05-02T13:21:57-05: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.
diff --git a/content/events/2015-boston/location.md b/content/events/2015-boston/location.md
index 2c35dd8a702..ac4a2cea06e 100644
--- a/content/events/2015-boston/location.md
+++ b/content/events/2015-boston/location.md
@@ -5,6 +5,15 @@ type = "event"
+++
-Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+We'll be in Cambridge at the Microsoft NERD Center:
-
+Microsoft NERD Center
+1 Memorial Dr #1
+Cambridge, MA 02142
+
+
+
The closest hotels are the Kendall Hotel and Boston Marriott Cambridge.
+
+If you spend most of your time in places like Portland or Brooklyn, our metro will feel familiar,
+with its bike share stations, beautiful riverfront, and numerous craft brewery tap-rooms with food
+trucks in their parking lots. (Hey, a good excuse to come the weekend before!)
diff --git a/content/events/2015-boston/program.md b/content/events/2015-boston/program.md
index 0aa684a833a..691848a7f03 100644
--- a/content/events/2015-boston/program.md
+++ b/content/events/2015-boston/program.md
@@ -4,119 +4,181 @@ title = "program"
type = "event"
+++
-
-
-The Schedule
-
-
Day 1
-
-
-
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
-
-
-
-
10:25-10:40
- Break
-
-
-
10:40-11:10
-
-
-
-
11:10-11:20
- Sponsors
-
-
-
11:20-11:50
-
-
-
-
11:50-13:00
Lunch (catered)
-
-
13:00-13:30
Ignites
-
-
-
13:30-14:00
Open Space (Open Space)
Open Space Opening
-
-
14:00-14:45
Open Space (Open Space)
Open Space #1
-
-
15:00-15:45
Open Space (Open Space)
Open Space #2
-
-
16:00-16:45
Open Space (Open Space)
Open Space #3
-
-
16:45-17:00
Close Day & Logistics
-
-
19:00-late
Evening Event
-
-
-
-
+
Tuesday, September 15th
+
+
+09:00-10:00
+Registration and Breakfast
+10:00-10:15
+Introduction, voting tool demo
+10:15-10:45
+
+10:45-11:00
+Break
+11:00-11:20
+
+11:20-11:50
+
+11:50-12:10
+Lightning Talks!
+12:10-13:15
+Lunch
+13:15-13:45
+
+13:45-14:00
+Open Space Planning
+14:00-15:00
+
+15:00-16:00
+
+16:00-16:15
+Break
+16:15-17:15
+Open Space 3
+17:15-17:30
+Closing comments and special announcement
+5:30-9:00
+
+
+
+
-
Day 2
-
-
-
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
-
-
-
-
10:25-10:40
- Break
-
-
-
10:40-11:10
-
-
-
-
11:10-11:20
- Sponsors
-
-
-
11:20-11:50
-
-
-
-
11:50-13:00
Lunch (catered)
-
-
13:00-13:30
Ignites
-
-
-
-
13:30-14:00
Open Space (Open Space)
Open Space Opening
-
-
14:00-14:45
Open Space (Open Space)
Open Space #1
-
-
15:00-15:45
Open Space (Open Space)
Open Space #2
-
-
16:00-16:45
Open Space (Open Space)
Open Space #3
-
-
17:00
Close Day & Farewell
-
-
-
+
Wednesday, September 16th
+
+
+09:00-10:00
+Registration and Breakfast
+10:00-10:20
+
+10:20-10:50
+
+10:50-11:00
+Break
+11:00-11:20
+
+11:20-11:50
+
+11:50-13:00
+Lunch
+13:00-13:30
+
+13:30-13:45
+Open Space Planning
+13:45-14:45
+Open Space 4
+14:45-15:45
+Open Space 5
+15:45-16:00
+Break
+16:00-17:00
+Open Space 6
+17:00-17:15
+Closing comments
+
+
+
+
+
+
+
+Talk descriptions
+
+
Cloud Anti-Patterns: Micro services, Containers and Large Scale Search gone wrong by Mallika Iyer
+
The value of micro services, containers, and continuous deployment is powerful only when brought together in a logical, scalable and platform agnostic manner.
+
Moreover, when used in the wrong way, it is fairly easy to shoot your self (and your entire application) in the foot. For eg: Micro services can be used to either create unnecessary pockets of redundancy, or used to isolate functionality and directly be an ally of efficient continuous deployment. I have seen more incorrect usages of containers and micro services than I’d like to admit, and a few key components are frequently left out of the cloud-native architecture while starting down this path.
+
Using the micro service paradigm is not a panacea for all problems, because one is creating a large-scale distributed cluster, in essence. Another aspect that is frequently neglected is large-scale containerized search in a cloud-native environment, a governance model around micro services and cloud orchestration. For instance, API frameworks like swagger.io enhance the usability of micro services by documenting the API functionality in real-time alongside the API contract. A micro service is only as useful as the interface contract that it has with other services in the application eco system.
+
Based on my experience over multiple cloud deployments, I will share a collection of anti-patterns and best practices to build production-ready cloud-native applications.
+
“If you can’t explain it to a six year old, you don’t understand it yourself.” - Albert Einstein
+
As someone who has to explain complex technology for a living, I live by this quote every day.
+
I'm a software engineer by training, and a cloud architect by trade. I work closely with Fortune 100 customers at Pivotal, guiding them towards a cloud native architecture, helping them build the next generation of Internet-of-Things (IoT) applications, and doing all this in a scalable way using technologies like Cloud Foundry, In-memory data technologies, and application architecture paradigms like micro services, setting up continuous deployment pipelines, and making the product reach the customer quickly.
+
+
Remote Calls != Local Calls: Graceful Degradation when Services Fail by Dan Riti
+
In a world where our systems are becoming more distributed then ever due to growing trends to decouple systems into small services, we are becoming dependent on network communication between these services to be reliable. But as we all know the number one fallacy of distributed computing is that the network is reliable.
+
Armed with this knowledge, we know that things will fail. So we must do our best to expect that failure will occur anywhere and everywhere. Thus, let's explore different techniques we can use to build antifragile systems, that degrade gracefully when the network fails and the services we depend on are no longer available.
+
Dan Riti is a software engineer at AppNeta, where his focus is on tracing distributed web applications. Additionally, Dan enjoys Python, Javascript, and music with a lot of bass.
+
+
Scaling Open edX with Kubernetes
+
Over the past few years, massive open online courses (MOOCs) powered by Open edX have become wildly popular, bringing free or low-cost education to millions of students around the world. Such success, however, presents a slew of challenging problems in terms of providing a scalable, robust, and secure platform.
+
At Appsembler, we offer customers a fully managed and supported Open edX stack, all the way from the frontend web application to the backend services like ElasticSearch, MySQL, and MongoDB. With so many moving parts, we have come to realize the value of a multi-container, microservices-oriented architecture using Docker.
+
In contrast to a single-container deployment of the Open edX stack, a multi-container approach allows us to scale different services independently; improves robustness since we can simply spin up new copies of containers if they go down; and results in improved security through greater segmentation and isolation. In addition to discussing these benefits, we'll also cover how we're managing deployments using Kubernetes for orchestration and service discovery along with Google Cloud infrastructure.
+
Nate Aune is a developer and entrepreneur with over 15 years of professional experience building highly scalable web applications. Nate is also the founder and CEO of Appsembler. Morgan Robertson is a DevOps Engineer at Appsembler with experience in Docker, Ansible, Python, and automation tools.
+
+
Effective Tools by Jennifer Davis
+
DevOps does not exist in a vacuum; social structure and culture are inherently intertwined. The hierarchies within organizations, industry connections, and globalization influence culture. Culture influences social structures, impacting how effective some structures are in an environment with a specific culture. Tools can play a large part in instilling behaviors, automation of systems, sharing knowledge, and changing organizational hierarchies.
+
Often technology choices are framed as 'best practices' or the right way to solve a problem. How do we resolve the cognitive dissonance that arrises from this fixed mindset, having chosen the best practice and the need to handle change as problems evolve? As technology accelerates our work, how do we determine what tools and technology to adopt to help effect the right change? This talk will help you frame the choices available to you, identify the fragility in your environment disguised by tools now, and to be more effective and deliberate with technology in your organization.
+
+
+
GridIronOps: What Women's Tackle Football Can Teach Us About Competitive Software Delivery by Katie Rose
+
What can Women’s Tackle Football teach us about building successful software delivery organizations? As it turns out, quite a bit. This presentation will explore how women’s football teams instill the same cultural principles needed to create agile, competitive organizations. We’ll even teach you some techniques based on the methods of winning football teams. Specifically, we will cover how to affect two key features of successful football teams that we can leverage to implement effective DevOps: Specialization and Mission Focus.
+
Breaking Down the Walls: Silos vs Specialization
+
Specialization is one of the key features of building an efficient and profitable product. But often specialization gets confused with – and devolves into – breaking the organization into silos. Being able to maximize the benefits of specialized roles and talents while promoting shared ownership requires a cultural shift. We’ll explore how many women’s football players and coaches have overcome this challenge and how those lessons can be applied to software delivery.
+
Why Are We Here: Mission Focus
+
Ask any football player why they came to the field on any given game day and they will all tell you the same thing: to win the game. In software delivery, the answer to that question can be as varied as the people answering it. While it’s important to have individual and short-term goals, the team must be focused on the same overall mission in order to accomplish it: no one builds agile software or agile infrastructure by accident. The balance between these goals and the ability to define the primary mission of the team is one of the most important cultural lessons we can learn from successful football teams.
+
Katie Rose is a uniquely experienced developer, football player, and comedian. After 15 years in IT Operations and Service Delivery she is now a web developer for GridIronOps, Booz Allen Hamilton’s open-source, DevOps-driven software delivery platform. She uses her eclectic background to foster the cultural changes that produce competitive organizations and effective teams. Building on her experience in Performance Management and ITIL-based IaaS delivery, she is developing methods and principles that can help organizations bridge the gap between people and tools/process.
+
+
+
DevOps operations challenges by Vijaya Kokkili
+
Given the DevOps buzz these days and many organizations struggling to get DevOps ingrained in the process, I would like to share how we have introduced DevOps, the challenges we faced and ideas on how those challenges can be overcome. How is it relavant to QA and DBA teams. How can QA be part of DevOps seamlessly. Focus will be more on how QA teams should take automation testing of an unstable product as an opportunity rather than a blocker. Given DevOps team structures, teams are now more product silo'd. Contract testing in Microservices is key to have a successful DevOps team in an organization.
+
Vijaya Kokkili is a QA Manager at CommerceHub, where her team is responsible for the quality of CommerceHub's external and internal applications. Building the automation from ground up at CommerceHub, she has stumbled upon every issue that you can think of, in the software testing and automation world. 'Automation is a learning experience' is the philosophy she believes in. Teams at CommerceHub have gone through several challenges of DevOps and they came a long way overcoming those challenges. Vijaya would like to take this opportunity to share the kind of challenges an organization will go through when DevOps teams are structured and also want to share few ideas that can be put in place from a process perspective that can help other organizations. This talk will be not be focused on general DevOps challenges, but, more on operations teams (DBA, IT, Technical support...) challenges in a DevOps structured team.
+
+
Managing Network Configurations with Git by Pete Lumbis
+
If we think of git as a way to track changes to text files, we apply this to code every day. Network device configurations, either Cumulus Linux or Cisco IOS, are simply 1 or more text files. If I need to make a change to the network it's the same as making a change to code. Branch off for your change to add a new VLAN or access control list, make the changes and propose a pull request to provide an opportunity to have senior engineers review those changes or tie it to virtual environments and tools like Jenkins to do further validation of your change. It's not really rocket science, but more of showing two different silos how the other side lives.
+
Pete Lumbis is a data center network architect for Cumulus Networks where he helps customers design data centers of all sizes while applying DevOps principals to networking. Before working at Cumulus, Pete was the routing protocols escalation engineer for the global Cisco support organization. Pete is CCIE #28677 and CCDE 2012::3.
+
+
Leveraging DevOps into Application Security by Ed Ray
+
Software and Application development are not slowing down... can your application security efforts keep pace? With agile development, continuous deployment, DevOps, and Cloud the pace of change in the software industry has only increased. Application security professionals face the prospect of rapidly delivering services while simultaneously ensuring that these applications are built both reliably and securely. With deployments deploying sometimes several times a day, weeklong security assessment just do not work anymore.
+
In this talk, I will discuss ways in which the DevOps philosophy can be utilized in application security. What are the key ways to keep your application security program robust enough to maintain relevance in today’s ever-changing environment? This talk will highlight methods for securing infrastructure, apps, APIs and source code.
+
Edward Ray is a Security Solutions Architect at Rackspace, possessing a deep background in Information Security. Ed has provided provided security management and technical leadership as well as performed hundreds of vulnerability assessments, penetration tests, host security reviews, web application assessments and security infrastructure reviews for corporate and governmental agencies in the U.S. and abroad. He has also written articles and technical papers on security and presented to audiences worldwide on computer and network security. In addition, Ed has also provided technical and management consulting on information security incident investigations and forensic analysis.
+
+
Overcoming Regulatory Burden in Startups by Elliot Murphy
+
Real innovation in Healthcare comes from people with lived experience and knowledge of the latest research. Current state of practice in healthcare is a decade or more behind. We need to make it easier for small companies to bring current research and modern technology into healthcare related services - costly regulations like HIPAA scare off most small teams. This is an experience report from 3 years working on a SaaS application that people to use with their psychiatrist (CommonGround). I will cover what works, what doesn't, ways to save money on compliance, and what we can all do to lower the cost of running applications securely. This talk should be interesting for anyone that cares about safeguarding customer data.
+
I'm Elliot Murphy, I want to speak to raise awareness of how security and regulatory issues affect innovation in critical sectors such as healthcare. I currently work at Kindly Ops, but this talk is based on my experiences over the last 3 years as the CTO of a bootstrapped healthcare startup: www.patdeegan.com/commonground
+
+
WORKSHOP: How to Use Kibana 4 for Log Analysis by Asaf Yigal
+
In this workshop, we will explore the value of Kibana 4 for log analysis and will give a real live, hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. We will examine three use cases: IT operations, business intelligence, and security and compliance. This is a hands-on session which will require participants to bring their own laptops, and we will provide the rest.
+
Asaf Yigal is co-founder and VP of Product at log analytics software company Logz.io. In the past, he was co-founder of social-trading platform Currensee, which was later acquired by OANDA. Yigal was also an early employee of server performance-monitoring company Akorri and storage resource-management startup Onaro, both of which were acquired by NetApp (NTAP). Yigal graduated from the Techion -- the Israeli version of MIT -- and he later created an AI algorithm on naval warfare for the Israeli military.
+
Asaf has an extensive presentation experience at both international conferences and local Meetups. Asaf created and gave training programs while he was at Onaro and Akorri and has frequently participated in financial panels in London hosted by the company Finance Magnates. Currently, Asaf presents at at the Tel Aviv ELK meetup and the Boston Elasticsearch meetup.
-There are three ways to propose a session:
-
- - A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
- - An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
- - Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
-
-
-### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
-
-Our main criteria to make it to the top selection are:
-
-- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
-- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
-- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
-
-How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
-
- - Proposal working title (can be changed later)
- - Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
- - Description or abstract
-
-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
-
diff --git a/content/events/2015-boston/registration.md b/content/events/2015-boston/registration.md
deleted file mode 100644
index 7a3d492be3b..00000000000
--- a/content/events/2015-boston/registration.md
+++ /dev/null
@@ -1,13 +0,0 @@
-+++
-date = "2016-05-02T13:21:57-05:00"
-title = "registration"
-type = "event"
-
-
-+++
-
-
-
-Embed registration iframe/link/etc.
-
-
diff --git a/content/events/2015-boston/sponsor.md b/content/events/2015-boston/sponsor.md
deleted file mode 100644
index 21a413599cd..00000000000
--- a/content/events/2015-boston/sponsor.md
+++ /dev/null
@@ -1,49 +0,0 @@
-+++
-date = "2016-05-02T13:21:57-05:00"
-title = "sponsor"
-type = "event"
-
-
-+++
-
-We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
-
-
-
-DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
-
-Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
-
-The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
-
-
-
-
-
diff --git a/content/events/2015-boston/welcome.md b/content/events/2015-boston/welcome.md
index 2841fe09ee3..84ba1b78a45 100644
--- a/content/events/2015-boston/welcome.md
+++ b/content/events/2015-boston/welcome.md
@@ -6,47 +6,41 @@ aliases = ["/events/2015-boston"]
+++
-## {{< event_start >}} - {{< event_end >}}
-
-DevOps Days is coming to {{< event_location >}}!
-
-
-
-
-
- | Dates |
- {{< event_start >}} - {{< event_end >}}
- |
-
-
-
-
-
- | Sponsors |
- {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization. |
-
-
- | Contact |
- {{< event_link page="contact" text="Get in touch with the Organizers" >}} |
-
-
- |
-
- {{< event_twitter devopsdays >}}
- |
-
+
+
+
+ 
+
+
+Microsoft NERD Center
+1 Memorial Dr #1
+Cambridge, MA 02142
+
+
+
+
+
+
+View our speakers
+
+Email the organizers - {{< email_organizers >}}
+
+
+ |
+ On Tuesday, September 15th and Wednesday, September 16th, DevOpsDays is returning to Boston!
+
+The event's schedule will consist of a mixture of traditional sessions, ignite talks,
+and the unique "open space" format that DevOpsDays is known for. We've reserved the first floor of the Microsoft NERD Center
+ and expect to fill it to capacity.
+
+NOTE: Microsoft has been extremely generous in providing us access to their private space to
+host this event. To repay their generosity, we ask that you pay attention to their guidelines.
+Most importantly, you must present identification to sign into the building! If you don't bring
+identification on the day of the event, you will not be permitted to attend.
+ |
+
+
+
diff --git a/data/events/2015-boston.yml b/data/events/2015-boston.yml
index afe4663197e..c91ed779998 100644
--- a/data/events/2015-boston.yml
+++ b/data/events/2015-boston.yml
@@ -5,8 +5,8 @@ friendly: "2015-boston" # Four digit year and the city name in lower-case. Don't
status: "past" # Options are "past" or "current". Use "current" for upcoming.
# All dates are in unquoted 2015-MM-DD, like this: variable: 2016-01-05
-startdate: 2016-01-01 # The start date of your event. Leave blank if you don't have a venue reserved yet.
-enddate: 2016-01-01 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+startdate: 2015-09-15 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2015-09-16 # The end date of your event. Leave blank if you don't have a venue reserved yet.
# Leave CFP dates blank if you don't know yet, or set all three at once.
cfp_date_start: 2016-01-01 # start accepting talk proposals.
cfp_date_end: 2016-01-01 # close your call for proposals.
@@ -20,33 +20,64 @@ location: "Boston" # Defaults to city, but you can make it the venue name.
nav_elements: # List of pages you want to show up in the navigation of your page.
- name: welcome
-# - name: program
+ - name: program
# - name: propose
# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
-# - name: location
+ - name: location
# - name: registration
- - name: sponsor
- name: contact
- - name: conduct
# These are the same people you have on the mailing list and Slack channel.
-team: ["John Doe", "Jane Smith", "Sally Fields"]
team_members: # Name is the only required field for team members.
- - name: "John Doe"
- - name: "Jane Smith"
- twitter: "devopsdays"
- - name: "Sally Fields"
- employer: "Acme Anvil Co."
+ - name: "Dave Fredricks"
+ - name: "James Meickle"
+ - name: "Peter Nealon"
organizer_email: "organizers-boston-2015@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-boston-2015@devopsdays.org" # Put your proposal email address here
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
- - id: samplesponsorname
+ - id: bmc
level: gold
- - id: arresteddevops
- level: community
+ - id: chef
+ level: gold
+ - id: g2
+ level: gold
+ - id: logz
+ level: gold
+ - id: cimpress
+ level: gold
+ - id: conjur
+ level: silver
+ - id: puppetlabs
+ level: silver
+ - id: xebia
+ level: silver
+ - id: nutanix
+ level: silver
+ - id: appneta
+ level: silver
+ - id: booz_allen_hamilton
+ level: silver
+ - id: athenahealth
+ level: bronze
+ - id: battery_ventures
+ level: bronze
+ - id: brainshark
+ level: bronze
+ - id: rackspace
+ level: bronze
+ - id: constantcontact
+ level: bronze
+ - id: sumologic
+ level: bronze
+ - id: motus
+ level: bronze
+ - id: victorops
+ level: bronze
+ - id: microsoft
+ level: host
sponsor_levels: # In this section, list the level of sponsorships and the label to use.
- id: gold
@@ -55,5 +86,7 @@ sponsor_levels: # In this section, list the level of sponsorships and the label
label: Silver
- id: bronze
label: Bronze
- - id: community
- label: Community
+ - id: media
+ label: Media
+ - id: host
+ label: Host
diff --git a/data/sponsors/appneta.yml b/data/sponsors/appneta.yml
new file mode 100644
index 00000000000..50f27b7285c
--- /dev/null
+++ b/data/sponsors/appneta.yml
@@ -0,0 +1,2 @@
+name: appneta
+url: http://www.appneta.com
diff --git a/data/sponsors/athenahealth.yml b/data/sponsors/athenahealth.yml
new file mode 100644
index 00000000000..b749cec6a64
--- /dev/null
+++ b/data/sponsors/athenahealth.yml
@@ -0,0 +1,2 @@
+name: athenahealth
+url: http://www.athenahealth.com
diff --git a/data/sponsors/battery_ventures.yml b/data/sponsors/battery_ventures.yml
new file mode 100644
index 00000000000..d5b6279c677
--- /dev/null
+++ b/data/sponsors/battery_ventures.yml
@@ -0,0 +1,2 @@
+name: battery_ventures
+url: https://www.battery.com
diff --git a/data/sponsors/booz_allen_hamilton.yml b/data/sponsors/booz_allen_hamilton.yml
new file mode 100644
index 00000000000..e404257e8b7
--- /dev/null
+++ b/data/sponsors/booz_allen_hamilton.yml
@@ -0,0 +1,2 @@
+name: booz_allen_hamilton
+url: http://www.boozallen.com
diff --git a/data/sponsors/brainshark.yml b/data/sponsors/brainshark.yml
new file mode 100644
index 00000000000..34f44521f7e
--- /dev/null
+++ b/data/sponsors/brainshark.yml
@@ -0,0 +1,2 @@
+name: brainshark
+url: http://www.brainshark.com
diff --git a/data/sponsors/cimpress.yml b/data/sponsors/cimpress.yml
new file mode 100644
index 00000000000..9e6fc8518c5
--- /dev/null
+++ b/data/sponsors/cimpress.yml
@@ -0,0 +1,2 @@
+name: cimpress
+url: http://cimpress.com
diff --git a/data/sponsors/conjur.yml b/data/sponsors/conjur.yml
new file mode 100644
index 00000000000..3e1740c07ff
--- /dev/null
+++ b/data/sponsors/conjur.yml
@@ -0,0 +1,2 @@
+name: conjur
+url: http://www.conjur.net/
diff --git a/data/sponsors/contstantcontact.yml b/data/sponsors/contstantcontact.yml
new file mode 100644
index 00000000000..bbf569b5a0e
--- /dev/null
+++ b/data/sponsors/contstantcontact.yml
@@ -0,0 +1,2 @@
+name: constantcontact
+url: http://www.constantcontact.com
diff --git a/data/sponsors/g2.yml b/data/sponsors/g2.yml
new file mode 100644
index 00000000000..965d932602a
--- /dev/null
+++ b/data/sponsors/g2.yml
@@ -0,0 +1,2 @@
+name: g2
+url: http://www.g2techgroup.com
diff --git a/data/sponsors/logz.yml b/data/sponsors/logz.yml
new file mode 100644
index 00000000000..f82c443f883
--- /dev/null
+++ b/data/sponsors/logz.yml
@@ -0,0 +1,2 @@
+name: logz
+url: http://on.logz.io/1UnbUiM
diff --git a/data/sponsors/motus.yml b/data/sponsors/motus.yml
new file mode 100644
index 00000000000..82468df368b
--- /dev/null
+++ b/data/sponsors/motus.yml
@@ -0,0 +1,2 @@
+name: motus
+url: http://www.motus.com
diff --git a/data/sponsors/nutanix.yml b/data/sponsors/nutanix.yml
new file mode 100644
index 00000000000..68b6f8b2131
--- /dev/null
+++ b/data/sponsors/nutanix.yml
@@ -0,0 +1,2 @@
+name: nutanix
+url: http://www.nutanix.com
diff --git a/data/sponsors/puppetlabs.yml b/data/sponsors/puppetlabs.yml
new file mode 100644
index 00000000000..59063fe4f95
--- /dev/null
+++ b/data/sponsors/puppetlabs.yml
@@ -0,0 +1,2 @@
+name: puppetlabs
+url: http://www.puppetlabs.com
diff --git a/data/sponsors/rackspace.yml b/data/sponsors/rackspace.yml
new file mode 100644
index 00000000000..9fba9fa6b0e
--- /dev/null
+++ b/data/sponsors/rackspace.yml
@@ -0,0 +1,2 @@
+name: rackspace
+url: http://www.rackspace.com
diff --git a/data/sponsors/xebia.yml b/data/sponsors/xebia.yml
new file mode 100644
index 00000000000..6bda9c10313
--- /dev/null
+++ b/data/sponsors/xebia.yml
@@ -0,0 +1,2 @@
+name: xebia
+url: https://xebialabs.com
diff --git a/static/events/2015-boston/boston.jpg b/static/events/2015-boston/boston.jpg
new file mode 100644
index 00000000000..036cd486c91
Binary files /dev/null and b/static/events/2015-boston/boston.jpg differ
diff --git a/static/img/sponsors/appneta.png b/static/img/sponsors/appneta.png
new file mode 100644
index 00000000000..d7f94b4d559
Binary files /dev/null and b/static/img/sponsors/appneta.png differ
diff --git a/static/img/sponsors/athenahealth.png b/static/img/sponsors/athenahealth.png
new file mode 100644
index 00000000000..2ccc2a45e9b
Binary files /dev/null and b/static/img/sponsors/athenahealth.png differ
diff --git a/static/img/sponsors/battery_ventures.png b/static/img/sponsors/battery_ventures.png
new file mode 100644
index 00000000000..4ee9401f2ce
Binary files /dev/null and b/static/img/sponsors/battery_ventures.png differ
diff --git a/static/img/sponsors/booz_allen_hamilton.png b/static/img/sponsors/booz_allen_hamilton.png
new file mode 100644
index 00000000000..d699a2a87d1
Binary files /dev/null and b/static/img/sponsors/booz_allen_hamilton.png differ
diff --git a/static/img/sponsors/brainshark.png b/static/img/sponsors/brainshark.png
new file mode 100644
index 00000000000..34e0e4d02a4
Binary files /dev/null and b/static/img/sponsors/brainshark.png differ
diff --git a/static/img/sponsors/cimpress.png b/static/img/sponsors/cimpress.png
new file mode 100644
index 00000000000..c90e8a8ee5d
Binary files /dev/null and b/static/img/sponsors/cimpress.png differ
diff --git a/static/img/sponsors/conjur.png b/static/img/sponsors/conjur.png
new file mode 100644
index 00000000000..9f2b41b5224
Binary files /dev/null and b/static/img/sponsors/conjur.png differ
diff --git a/static/img/sponsors/constantcontact.png b/static/img/sponsors/constantcontact.png
new file mode 100644
index 00000000000..8c28b7b312f
Binary files /dev/null and b/static/img/sponsors/constantcontact.png differ
diff --git a/static/img/sponsors/g2.png b/static/img/sponsors/g2.png
new file mode 100644
index 00000000000..ff6abb1217f
Binary files /dev/null and b/static/img/sponsors/g2.png differ
diff --git a/static/img/sponsors/logz.png b/static/img/sponsors/logz.png
new file mode 100644
index 00000000000..b9d7252fe14
Binary files /dev/null and b/static/img/sponsors/logz.png differ
diff --git a/static/img/sponsors/motus.png b/static/img/sponsors/motus.png
new file mode 100644
index 00000000000..1e0d23d3c38
Binary files /dev/null and b/static/img/sponsors/motus.png differ
diff --git a/static/img/sponsors/nutanix.png b/static/img/sponsors/nutanix.png
new file mode 100644
index 00000000000..653a8c71d96
Binary files /dev/null and b/static/img/sponsors/nutanix.png differ
diff --git a/static/img/sponsors/puppetlabs.jpg b/static/img/sponsors/puppetlabs.jpg
new file mode 100644
index 00000000000..564dd947dd0
Binary files /dev/null and b/static/img/sponsors/puppetlabs.jpg differ
diff --git a/static/img/sponsors/rackspace.png b/static/img/sponsors/rackspace.png
new file mode 100644
index 00000000000..79198ca293b
Binary files /dev/null and b/static/img/sponsors/rackspace.png differ
diff --git a/static/img/sponsors/xebia.png b/static/img/sponsors/xebia.png
new file mode 100644
index 00000000000..a76ed6fcf18
Binary files /dev/null and b/static/img/sponsors/xebia.png differ