From 5c071dd3b28135c4522fbbcd5623e5c87ad1ce1a Mon Sep 17 00:00:00 2001 From: Matt Stratton Date: Mon, 2 May 2016 14:44:18 -0500 Subject: [PATCH 1/4] One big pass at migrating scaffolds of old events --- content/events/2010-brazil/contact.md | 38 ++++++ content/events/2010-brazil/location.md | 12 ++ content/events/2010-brazil/program.md | 36 +++++ content/events/2010-brazil/speakers.md | 42 ++++++ content/events/2010-brazil/welcome.md | 16 +++ content/events/2010-europe/conduct.md | 36 +++++ content/events/2010-europe/contact.md | 17 +++ content/events/2010-europe/location.md | 10 ++ content/events/2010-europe/program.md | 122 +++++++++++++++++ content/events/2010-europe/propose.md | 37 ++++++ content/events/2010-europe/registration.md | 13 ++ content/events/2010-europe/sponsor.md | 49 +++++++ content/events/2010-europe/welcome.md | 52 ++++++++ content/events/2010-sydney/conduct.md | 36 +++++ content/events/2010-sydney/contact.md | 17 +++ content/events/2010-sydney/location.md | 10 ++ content/events/2010-sydney/program.md | 122 +++++++++++++++++ content/events/2010-sydney/propose.md | 37 ++++++ content/events/2010-sydney/registration.md | 13 ++ content/events/2010-sydney/sponsor.md | 49 +++++++ content/events/2010-sydney/welcome.md | 52 ++++++++ content/events/2010-us/conduct.md | 36 +++++ content/events/2010-us/contact.md | 17 +++ content/events/2010-us/location.md | 10 ++ content/events/2010-us/program.md | 122 +++++++++++++++++ content/events/2010-us/propose.md | 37 ++++++ content/events/2010-us/registration.md | 13 ++ content/events/2010-us/sponsor.md | 49 +++++++ content/events/2010-us/welcome.md | 52 ++++++++ content/events/2011-bangalore/conduct.md | 36 +++++ content/events/2011-bangalore/contact.md | 17 +++ content/events/2011-bangalore/location.md | 10 ++ content/events/2011-bangalore/program.md | 122 +++++++++++++++++ content/events/2011-bangalore/propose.md | 37 ++++++ content/events/2011-bangalore/registration.md | 13 ++ content/events/2011-bangalore/sponsor.md | 49 +++++++ content/events/2011-bangalore/welcome.md | 52 ++++++++ content/events/2011-boston/conduct.md | 36 +++++ content/events/2011-boston/contact.md | 17 +++ content/events/2011-boston/location.md | 10 ++ content/events/2011-boston/program.md | 122 +++++++++++++++++ content/events/2011-boston/propose.md | 37 ++++++ content/events/2011-boston/registration.md | 13 ++ content/events/2011-boston/sponsor.md | 49 +++++++ content/events/2011-boston/welcome.md | 52 ++++++++ content/events/2011-goteborg/conduct.md | 36 +++++ content/events/2011-goteborg/contact.md | 17 +++ content/events/2011-goteborg/location.md | 10 ++ content/events/2011-goteborg/program.md | 122 +++++++++++++++++ content/events/2011-goteborg/propose.md | 37 ++++++ content/events/2011-goteborg/registration.md | 13 ++ content/events/2011-goteborg/sponsor.md | 49 +++++++ content/events/2011-goteborg/welcome.md | 52 ++++++++ content/events/2011-manila/conduct.md | 36 +++++ content/events/2011-manila/contact.md | 17 +++ content/events/2011-manila/location.md | 10 ++ content/events/2011-manila/program.md | 122 +++++++++++++++++ content/events/2011-manila/propose.md | 37 ++++++ content/events/2011-manila/registration.md | 13 ++ content/events/2011-manila/sponsor.md | 49 +++++++ content/events/2011-manila/welcome.md | 52 ++++++++ content/events/2011-melbourne/conduct.md | 36 +++++ content/events/2011-melbourne/contact.md | 17 +++ content/events/2011-melbourne/location.md | 10 ++ content/events/2011-melbourne/program.md | 122 +++++++++++++++++ content/events/2011-melbourne/propose.md | 37 ++++++ content/events/2011-melbourne/registration.md | 13 ++ content/events/2011-melbourne/sponsor.md | 49 +++++++ content/events/2011-melbourne/welcome.md | 52 ++++++++ content/events/2011-mountainview/conduct.md | 36 +++++ content/events/2011-mountainview/contact.md | 17 +++ content/events/2011-mountainview/location.md | 10 ++ content/events/2011-mountainview/program.md | 122 +++++++++++++++++ content/events/2011-mountainview/propose.md | 37 ++++++ .../events/2011-mountainview/registration.md | 13 ++ content/events/2011-mountainview/sponsor.md | 49 +++++++ content/events/2011-mountainview/welcome.md | 52 ++++++++ content/events/2012-austin/conduct.md | 36 +++++ content/events/2012-austin/contact.md | 17 +++ content/events/2012-austin/location.md | 10 ++ content/events/2012-austin/program.md | 122 +++++++++++++++++ content/events/2012-austin/propose.md | 37 ++++++ content/events/2012-austin/registration.md | 13 ++ content/events/2012-austin/sponsor.md | 49 +++++++ content/events/2012-austin/welcome.md | 52 ++++++++ .../events/2012-india/sample-event/conduct.md | 37 ++++++ .../events/2012-india/sample-event/contact.md | 18 +++ .../2012-india/sample-event/location.md | 11 ++ .../events/2012-india/sample-event/program.md | 123 ++++++++++++++++++ .../events/2012-india/sample-event/propose.md | 38 ++++++ .../2012-india/sample-event/registration.md | 14 ++ .../events/2012-india/sample-event/sponsor.md | 50 +++++++ .../events/2012-india/sample-event/welcome.md | 53 ++++++++ content/events/2012-italy/conduct.md | 36 +++++ content/events/2012-italy/contact.md | 17 +++ content/events/2012-italy/location.md | 10 ++ content/events/2012-italy/program.md | 122 +++++++++++++++++ content/events/2012-italy/propose.md | 37 ++++++ content/events/2012-italy/registration.md | 13 ++ content/events/2012-italy/sponsor.md | 49 +++++++ content/events/2012-italy/welcome.md | 52 ++++++++ content/events/2012-mountainview/conduct.md | 36 +++++ content/events/2012-mountainview/contact.md | 17 +++ content/events/2012-mountainview/location.md | 10 ++ content/events/2012-mountainview/program.md | 122 +++++++++++++++++ content/events/2012-mountainview/propose.md | 37 ++++++ .../events/2012-mountainview/registration.md | 13 ++ content/events/2012-mountainview/sponsor.md | 49 +++++++ content/events/2012-mountainview/welcome.md | 52 ++++++++ content/events/2012-newyork/conduct.md | 36 +++++ content/events/2012-newyork/contact.md | 17 +++ content/events/2012-newyork/location.md | 10 ++ content/events/2012-newyork/program.md | 122 +++++++++++++++++ content/events/2012-newyork/propose.md | 37 ++++++ content/events/2012-newyork/registration.md | 13 ++ content/events/2012-newyork/sponsor.md | 49 +++++++ content/events/2012-newyork/welcome.md | 52 ++++++++ content/events/2012-tokyo/conduct.md | 36 +++++ content/events/2012-tokyo/contact.md | 17 +++ content/events/2012-tokyo/location.md | 10 ++ content/events/2012-tokyo/program.md | 122 +++++++++++++++++ content/events/2012-tokyo/propose.md | 37 ++++++ content/events/2012-tokyo/registration.md | 13 ++ content/events/2012-tokyo/sponsor.md | 49 +++++++ content/events/2012-tokyo/welcome.md | 52 ++++++++ content/events/2013-amsterdam/conduct.md | 36 +++++ content/events/2013-amsterdam/contact.md | 17 +++ content/events/2013-amsterdam/location.md | 10 ++ content/events/2013-amsterdam/program.md | 122 +++++++++++++++++ content/events/2013-amsterdam/propose.md | 37 ++++++ content/events/2013-amsterdam/registration.md | 13 ++ content/events/2013-amsterdam/sponsor.md | 49 +++++++ content/events/2013-amsterdam/welcome.md | 52 ++++++++ content/events/2013-atlanta/conduct.md | 36 +++++ content/events/2013-atlanta/contact.md | 17 +++ content/events/2013-atlanta/location.md | 10 ++ content/events/2013-atlanta/program.md | 122 +++++++++++++++++ content/events/2013-atlanta/propose.md | 37 ++++++ content/events/2013-atlanta/registration.md | 13 ++ content/events/2013-atlanta/sponsor.md | 49 +++++++ content/events/2013-atlanta/welcome.md | 52 ++++++++ content/events/2013-austin/conduct.md | 36 +++++ content/events/2013-austin/contact.md | 17 +++ content/events/2013-austin/location.md | 10 ++ content/events/2013-austin/program.md | 122 +++++++++++++++++ content/events/2013-austin/propose.md | 37 ++++++ content/events/2013-austin/registration.md | 13 ++ content/events/2013-austin/sponsor.md | 49 +++++++ content/events/2013-austin/welcome.md | 52 ++++++++ content/events/2013-barcelona/conduct.md | 36 +++++ content/events/2013-barcelona/contact.md | 17 +++ content/events/2013-barcelona/location.md | 10 ++ content/events/2013-barcelona/program.md | 122 +++++++++++++++++ content/events/2013-barcelona/propose.md | 37 ++++++ content/events/2013-barcelona/registration.md | 13 ++ content/events/2013-barcelona/sponsor.md | 49 +++++++ content/events/2013-barcelona/welcome.md | 52 ++++++++ content/events/2013-berlin/conduct.md | 36 +++++ content/events/2013-berlin/contact.md | 17 +++ content/events/2013-berlin/location.md | 10 ++ content/events/2013-berlin/program.md | 122 +++++++++++++++++ content/events/2013-berlin/propose.md | 37 ++++++ content/events/2013-berlin/registration.md | 13 ++ content/events/2013-berlin/sponsor.md | 49 +++++++ content/events/2013-berlin/welcome.md | 52 ++++++++ content/events/2013-downunder/conduct.md | 36 +++++ content/events/2013-downunder/contact.md | 17 +++ content/events/2013-downunder/location.md | 10 ++ content/events/2013-downunder/program.md | 122 +++++++++++++++++ content/events/2013-downunder/propose.md | 37 ++++++ content/events/2013-downunder/registration.md | 13 ++ content/events/2013-downunder/sponsor.md | 49 +++++++ content/events/2013-downunder/welcome.md | 52 ++++++++ content/events/2013-india/conduct.md | 36 +++++ content/events/2013-india/contact.md | 17 +++ content/events/2013-india/location.md | 10 ++ content/events/2013-india/program.md | 122 +++++++++++++++++ content/events/2013-india/propose.md | 37 ++++++ content/events/2013-india/registration.md | 13 ++ content/events/2013-india/sponsor.md | 49 +++++++ content/events/2013-india/welcome.md | 52 ++++++++ content/events/2013-london-spring/conduct.md | 36 +++++ content/events/2013-london-spring/contact.md | 17 +++ content/events/2013-london-spring/location.md | 10 ++ content/events/2013-london-spring/program.md | 122 +++++++++++++++++ content/events/2013-london-spring/propose.md | 37 ++++++ .../events/2013-london-spring/registration.md | 13 ++ content/events/2013-london-spring/sponsor.md | 49 +++++++ content/events/2013-london-spring/welcome.md | 52 ++++++++ content/events/2013-london/conduct.md | 36 +++++ content/events/2013-london/contact.md | 17 +++ content/events/2013-london/location.md | 10 ++ content/events/2013-london/program.md | 122 +++++++++++++++++ content/events/2013-london/propose.md | 37 ++++++ content/events/2013-london/registration.md | 13 ++ content/events/2013-london/sponsor.md | 49 +++++++ content/events/2013-london/welcome.md | 52 ++++++++ content/events/2013-mountainview/conduct.md | 36 +++++ content/events/2013-mountainview/contact.md | 17 +++ content/events/2013-mountainview/location.md | 10 ++ content/events/2013-mountainview/program.md | 122 +++++++++++++++++ content/events/2013-mountainview/propose.md | 37 ++++++ .../events/2013-mountainview/registration.md | 13 ++ content/events/2013-mountainview/sponsor.md | 49 +++++++ content/events/2013-mountainview/welcome.md | 52 ++++++++ content/events/2013-newyork/conduct.md | 36 +++++ content/events/2013-newyork/contact.md | 17 +++ content/events/2013-newyork/location.md | 10 ++ content/events/2013-newyork/program.md | 122 +++++++++++++++++ content/events/2013-newyork/propose.md | 37 ++++++ content/events/2013-newyork/registration.md | 13 ++ content/events/2013-newyork/sponsor.md | 49 +++++++ content/events/2013-newyork/welcome.md | 52 ++++++++ content/events/2013-newzealand/conduct.md | 36 +++++ content/events/2013-newzealand/contact.md | 17 +++ content/events/2013-newzealand/location.md | 10 ++ content/events/2013-newzealand/program.md | 122 +++++++++++++++++ content/events/2013-newzealand/propose.md | 37 ++++++ .../events/2013-newzealand/registration.md | 13 ++ content/events/2013-newzealand/sponsor.md | 49 +++++++ content/events/2013-newzealand/welcome.md | 52 ++++++++ content/events/2013-paris/conduct.md | 36 +++++ content/events/2013-paris/contact.md | 17 +++ content/events/2013-paris/location.md | 10 ++ content/events/2013-paris/program.md | 122 +++++++++++++++++ content/events/2013-paris/propose.md | 37 ++++++ content/events/2013-paris/registration.md | 13 ++ content/events/2013-paris/sponsor.md | 49 +++++++ content/events/2013-paris/welcome.md | 52 ++++++++ content/events/2013-portland/conduct.md | 36 +++++ content/events/2013-portland/contact.md | 17 +++ content/events/2013-portland/location.md | 10 ++ content/events/2013-portland/program.md | 122 +++++++++++++++++ content/events/2013-portland/propose.md | 37 ++++++ content/events/2013-portland/registration.md | 13 ++ content/events/2013-portland/sponsor.md | 49 +++++++ content/events/2013-portland/welcome.md | 52 ++++++++ content/events/2013-telaviv/conduct.md | 36 +++++ content/events/2013-telaviv/contact.md | 17 +++ content/events/2013-telaviv/location.md | 10 ++ content/events/2013-telaviv/program.md | 122 +++++++++++++++++ content/events/2013-telaviv/propose.md | 37 ++++++ content/events/2013-telaviv/registration.md | 13 ++ content/events/2013-telaviv/sponsor.md | 49 +++++++ content/events/2013-telaviv/welcome.md | 52 ++++++++ content/events/2013-tokyo/conduct.md | 36 +++++ content/events/2013-tokyo/contact.md | 17 +++ content/events/2013-tokyo/location.md | 10 ++ content/events/2013-tokyo/program.md | 122 +++++++++++++++++ content/events/2013-tokyo/propose.md | 37 ++++++ content/events/2013-tokyo/registration.md | 13 ++ content/events/2013-tokyo/sponsor.md | 49 +++++++ content/events/2013-tokyo/welcome.md | 52 ++++++++ content/events/2013-vancouver/conduct.md | 36 +++++ content/events/2013-vancouver/contact.md | 17 +++ content/events/2013-vancouver/location.md | 10 ++ content/events/2013-vancouver/program.md | 122 +++++++++++++++++ content/events/2013-vancouver/propose.md | 37 ++++++ content/events/2013-vancouver/registration.md | 13 ++ content/events/2013-vancouver/sponsor.md | 49 +++++++ content/events/2013-vancouver/welcome.md | 52 ++++++++ content/events/2014-amsterdam/conduct.md | 36 +++++ content/events/2014-amsterdam/contact.md | 17 +++ content/events/2014-amsterdam/location.md | 10 ++ content/events/2014-amsterdam/program.md | 122 +++++++++++++++++ content/events/2014-amsterdam/propose.md | 37 ++++++ content/events/2014-amsterdam/registration.md | 13 ++ content/events/2014-amsterdam/sponsor.md | 49 +++++++ content/events/2014-amsterdam/welcome.md | 52 ++++++++ content/events/2014-austin/conduct.md | 36 +++++ content/events/2014-austin/contact.md | 17 +++ content/events/2014-austin/location.md | 10 ++ content/events/2014-austin/program.md | 122 +++++++++++++++++ content/events/2014-austin/propose.md | 37 ++++++ content/events/2014-austin/registration.md | 13 ++ content/events/2014-austin/sponsor.md | 49 +++++++ content/events/2014-austin/welcome.md | 52 ++++++++ content/events/2014-bangalore/conduct.md | 36 +++++ content/events/2014-bangalore/contact.md | 17 +++ content/events/2014-bangalore/location.md | 10 ++ content/events/2014-bangalore/program.md | 122 +++++++++++++++++ content/events/2014-bangalore/propose.md | 37 ++++++ content/events/2014-bangalore/registration.md | 13 ++ content/events/2014-bangalore/sponsor.md | 49 +++++++ content/events/2014-bangalore/welcome.md | 52 ++++++++ content/events/2014-belgium/conduct.md | 36 +++++ content/events/2014-belgium/contact.md | 17 +++ content/events/2014-belgium/location.md | 10 ++ content/events/2014-belgium/program.md | 122 +++++++++++++++++ content/events/2014-belgium/propose.md | 37 ++++++ content/events/2014-belgium/registration.md | 13 ++ content/events/2014-belgium/sponsor.md | 49 +++++++ content/events/2014-belgium/welcome.md | 52 ++++++++ content/events/2014-berlin/conduct.md | 36 +++++ content/events/2014-berlin/contact.md | 17 +++ content/events/2014-berlin/location.md | 10 ++ content/events/2014-berlin/program.md | 122 +++++++++++++++++ content/events/2014-berlin/propose.md | 37 ++++++ content/events/2014-berlin/registration.md | 13 ++ content/events/2014-berlin/sponsor.md | 49 +++++++ content/events/2014-berlin/welcome.md | 52 ++++++++ content/events/2014-boston/conduct.md | 36 +++++ content/events/2014-boston/contact.md | 17 +++ content/events/2014-boston/location.md | 10 ++ content/events/2014-boston/program.md | 122 +++++++++++++++++ content/events/2014-boston/propose.md | 37 ++++++ content/events/2014-boston/registration.md | 13 ++ content/events/2014-boston/sponsor.md | 49 +++++++ content/events/2014-boston/welcome.md | 52 ++++++++ content/events/2014-brisbane/conduct.md | 36 +++++ content/events/2014-brisbane/contact.md | 17 +++ content/events/2014-brisbane/location.md | 10 ++ content/events/2014-brisbane/program.md | 122 +++++++++++++++++ content/events/2014-brisbane/propose.md | 37 ++++++ content/events/2014-brisbane/registration.md | 13 ++ content/events/2014-brisbane/sponsor.md | 49 +++++++ content/events/2014-brisbane/welcome.md | 52 ++++++++ content/events/2014-chicago/conduct.md | 36 +++++ content/events/2014-chicago/contact.md | 17 +++ content/events/2014-chicago/location.md | 10 ++ content/events/2014-chicago/program.md | 122 +++++++++++++++++ content/events/2014-chicago/propose.md | 37 ++++++ content/events/2014-chicago/registration.md | 13 ++ content/events/2014-chicago/sponsor.md | 49 +++++++ content/events/2014-chicago/welcome.md | 52 ++++++++ content/events/2014-helsinki/conduct.md | 36 +++++ content/events/2014-helsinki/contact.md | 17 +++ content/events/2014-helsinki/location.md | 10 ++ content/events/2014-helsinki/program.md | 122 +++++++++++++++++ content/events/2014-helsinki/propose.md | 37 ++++++ content/events/2014-helsinki/registration.md | 13 ++ content/events/2014-helsinki/sponsor.md | 49 +++++++ content/events/2014-helsinki/welcome.md | 52 ++++++++ content/events/2014-ljubljana/conduct.md | 36 +++++ content/events/2014-ljubljana/contact.md | 17 +++ content/events/2014-ljubljana/location.md | 10 ++ content/events/2014-ljubljana/program.md | 122 +++++++++++++++++ content/events/2014-ljubljana/propose.md | 37 ++++++ content/events/2014-ljubljana/registration.md | 13 ++ content/events/2014-ljubljana/sponsor.md | 49 +++++++ content/events/2014-ljubljana/welcome.md | 52 ++++++++ content/events/2014-minneapolis/conduct.md | 36 +++++ content/events/2014-minneapolis/contact.md | 17 +++ content/events/2014-minneapolis/location.md | 10 ++ content/events/2014-minneapolis/program.md | 122 +++++++++++++++++ content/events/2014-minneapolis/propose.md | 37 ++++++ .../events/2014-minneapolis/registration.md | 13 ++ content/events/2014-minneapolis/sponsor.md | 49 +++++++ content/events/2014-minneapolis/welcome.md | 52 ++++++++ content/events/2014-nairobi/conduct.md | 36 +++++ content/events/2014-nairobi/contact.md | 17 +++ content/events/2014-nairobi/location.md | 10 ++ content/events/2014-nairobi/program.md | 122 +++++++++++++++++ content/events/2014-nairobi/propose.md | 37 ++++++ content/events/2014-nairobi/registration.md | 13 ++ content/events/2014-nairobi/sponsor.md | 49 +++++++ content/events/2014-nairobi/welcome.md | 52 ++++++++ content/events/2014-newyork/conduct.md | 36 +++++ content/events/2014-newyork/contact.md | 17 +++ content/events/2014-newyork/location.md | 10 ++ content/events/2014-newyork/program.md | 122 +++++++++++++++++ content/events/2014-newyork/propose.md | 37 ++++++ content/events/2014-newyork/registration.md | 13 ++ content/events/2014-newyork/sponsor.md | 49 +++++++ content/events/2014-newyork/welcome.md | 52 ++++++++ .../2014-pittsburgh/sample-event/conduct.md | 37 ++++++ .../2014-pittsburgh/sample-event/contact.md | 18 +++ .../2014-pittsburgh/sample-event/location.md | 11 ++ .../2014-pittsburgh/sample-event/program.md | 123 ++++++++++++++++++ .../2014-pittsburgh/sample-event/propose.md | 38 ++++++ .../sample-event/registration.md | 14 ++ .../2014-pittsburgh/sample-event/sponsor.md | 50 +++++++ .../2014-pittsburgh/sample-event/welcome.md | 53 ++++++++ content/events/2014-siliconvalley/conduct.md | 36 +++++ content/events/2014-siliconvalley/contact.md | 17 +++ content/events/2014-siliconvalley/location.md | 10 ++ content/events/2014-siliconvalley/program.md | 122 +++++++++++++++++ content/events/2014-siliconvalley/propose.md | 37 ++++++ .../events/2014-siliconvalley/registration.md | 13 ++ content/events/2014-siliconvalley/sponsor.md | 49 +++++++ content/events/2014-siliconvalley/welcome.md | 52 ++++++++ content/events/2014-telaviv/conduct.md | 36 +++++ content/events/2014-telaviv/contact.md | 17 +++ content/events/2014-telaviv/location.md | 10 ++ content/events/2014-telaviv/program.md | 122 +++++++++++++++++ content/events/2014-telaviv/propose.md | 37 ++++++ content/events/2014-telaviv/registration.md | 13 ++ content/events/2014-telaviv/sponsor.md | 49 +++++++ content/events/2014-telaviv/welcome.md | 52 ++++++++ content/events/2014-toronto/conduct.md | 36 +++++ content/events/2014-toronto/contact.md | 17 +++ content/events/2014-toronto/location.md | 10 ++ content/events/2014-toronto/program.md | 122 +++++++++++++++++ content/events/2014-toronto/propose.md | 37 ++++++ content/events/2014-toronto/registration.md | 13 ++ content/events/2014-toronto/sponsor.md | 49 +++++++ content/events/2014-toronto/welcome.md | 52 ++++++++ content/events/2014-vancouver/conduct.md | 36 +++++ content/events/2014-vancouver/contact.md | 17 +++ content/events/2014-vancouver/location.md | 10 ++ content/events/2014-vancouver/program.md | 122 +++++++++++++++++ content/events/2014-vancouver/propose.md | 37 ++++++ content/events/2014-vancouver/registration.md | 13 ++ content/events/2014-vancouver/sponsor.md | 49 +++++++ content/events/2014-vancouver/welcome.md | 52 ++++++++ content/events/2014-warsaw/conduct.md | 36 +++++ content/events/2014-warsaw/contact.md | 17 +++ content/events/2014-warsaw/location.md | 10 ++ content/events/2014-warsaw/program.md | 122 +++++++++++++++++ content/events/2014-warsaw/propose.md | 37 ++++++ content/events/2014-warsaw/registration.md | 13 ++ content/events/2014-warsaw/sponsor.md | 49 +++++++ content/events/2014-warsaw/welcome.md | 52 ++++++++ content/events/2015-amsterdam/conduct.md | 36 +++++ content/events/2015-amsterdam/contact.md | 17 +++ content/events/2015-amsterdam/location.md | 10 ++ content/events/2015-amsterdam/program.md | 122 +++++++++++++++++ content/events/2015-amsterdam/propose.md | 37 ++++++ content/events/2015-amsterdam/registration.md | 13 ++ content/events/2015-amsterdam/sponsor.md | 49 +++++++ content/events/2015-amsterdam/welcome.md | 52 ++++++++ content/events/2015-austin/conduct.md | 36 +++++ content/events/2015-austin/contact.md | 17 +++ content/events/2015-austin/location.md | 10 ++ content/events/2015-austin/program.md | 122 +++++++++++++++++ content/events/2015-austin/propose.md | 37 ++++++ content/events/2015-austin/registration.md | 13 ++ content/events/2015-austin/sponsor.md | 49 +++++++ content/events/2015-austin/welcome.md | 52 ++++++++ content/events/2015-bangalore/conduct.md | 36 +++++ content/events/2015-bangalore/contact.md | 17 +++ content/events/2015-bangalore/location.md | 10 ++ content/events/2015-bangalore/program.md | 122 +++++++++++++++++ content/events/2015-bangalore/propose.md | 37 ++++++ content/events/2015-bangalore/registration.md | 13 ++ content/events/2015-bangalore/sponsor.md | 49 +++++++ content/events/2015-bangalore/welcome.md | 52 ++++++++ content/events/2015-berlin/conduct.md | 36 +++++ content/events/2015-berlin/contact.md | 17 +++ content/events/2015-berlin/location.md | 10 ++ content/events/2015-berlin/program.md | 122 +++++++++++++++++ content/events/2015-berlin/propose.md | 37 ++++++ content/events/2015-berlin/registration.md | 13 ++ content/events/2015-berlin/sponsor.md | 49 +++++++ content/events/2015-berlin/welcome.md | 52 ++++++++ content/events/2015-boston/conduct.md | 36 +++++ content/events/2015-boston/contact.md | 17 +++ content/events/2015-boston/location.md | 10 ++ content/events/2015-boston/program.md | 122 +++++++++++++++++ content/events/2015-boston/propose.md | 37 ++++++ content/events/2015-boston/registration.md | 13 ++ content/events/2015-boston/sponsor.md | 49 +++++++ content/events/2015-boston/welcome.md | 52 ++++++++ content/events/2015-charlotte/conduct.md | 36 +++++ content/events/2015-charlotte/contact.md | 17 +++ content/events/2015-charlotte/location.md | 10 ++ content/events/2015-charlotte/program.md | 122 +++++++++++++++++ content/events/2015-charlotte/propose.md | 37 ++++++ content/events/2015-charlotte/registration.md | 13 ++ content/events/2015-charlotte/sponsor.md | 49 +++++++ content/events/2015-charlotte/welcome.md | 52 ++++++++ content/events/2015-chicago/conduct.md | 37 +++++- content/events/2015-chicago/contact.md | 18 ++- content/events/2015-chicago/location.md | 11 +- content/events/2015-chicago/program.md | 123 +++++++++++++++++- content/events/2015-chicago/propose.md | 37 ++++++ content/events/2015-chicago/registration.md | 13 ++ content/events/2015-chicago/sponsor.md | 50 ++++++- content/events/2015-chicago/welcome.md | 52 ++++++-- content/events/2015-denver/conduct.md | 36 +++++ content/events/2015-denver/contact.md | 17 +++ content/events/2015-denver/location.md | 10 ++ content/events/2015-denver/program.md | 122 +++++++++++++++++ content/events/2015-denver/propose.md | 37 ++++++ content/events/2015-denver/registration.md | 13 ++ content/events/2015-denver/sponsor.md | 49 +++++++ content/events/2015-denver/welcome.md | 52 ++++++++ content/events/2015-detroit/conduct.md | 36 +++++ content/events/2015-detroit/contact.md | 17 +++ content/events/2015-detroit/location.md | 10 ++ content/events/2015-detroit/program.md | 122 +++++++++++++++++ content/events/2015-detroit/propose.md | 37 ++++++ content/events/2015-detroit/registration.md | 13 ++ content/events/2015-detroit/sponsor.md | 49 +++++++ content/events/2015-detroit/welcome.md | 52 ++++++++ content/events/2015-ljubljana/conduct.md | 36 +++++ content/events/2015-ljubljana/contact.md | 17 +++ content/events/2015-ljubljana/location.md | 10 ++ content/events/2015-ljubljana/program.md | 122 +++++++++++++++++ content/events/2015-ljubljana/propose.md | 37 ++++++ content/events/2015-ljubljana/registration.md | 13 ++ content/events/2015-ljubljana/sponsor.md | 49 +++++++ content/events/2015-ljubljana/welcome.md | 52 ++++++++ content/events/2015-melbourne/conduct.md | 36 +++++ content/events/2015-melbourne/contact.md | 17 +++ content/events/2015-melbourne/location.md | 10 ++ content/events/2015-melbourne/program.md | 122 +++++++++++++++++ content/events/2015-melbourne/propose.md | 37 ++++++ content/events/2015-melbourne/registration.md | 13 ++ content/events/2015-melbourne/sponsor.md | 49 +++++++ content/events/2015-melbourne/welcome.md | 52 ++++++++ content/events/2015-minneapolis/conduct.md | 36 +++++ content/events/2015-minneapolis/contact.md | 17 +++ content/events/2015-minneapolis/location.md | 10 ++ content/events/2015-minneapolis/program.md | 122 +++++++++++++++++ content/events/2015-minneapolis/propose.md | 37 ++++++ .../events/2015-minneapolis/registration.md | 13 ++ content/events/2015-minneapolis/sponsor.md | 49 +++++++ content/events/2015-minneapolis/welcome.md | 52 ++++++++ .../2015-newyork/sample-event/conduct.md | 37 ++++++ .../2015-newyork/sample-event/contact.md | 18 +++ .../2015-newyork/sample-event/location.md | 11 ++ .../2015-newyork/sample-event/program.md | 123 ++++++++++++++++++ .../2015-newyork/sample-event/propose.md | 38 ++++++ .../2015-newyork/sample-event/registration.md | 14 ++ .../2015-newyork/sample-event/sponsor.md | 50 +++++++ .../2015-newyork/sample-event/welcome.md | 53 ++++++++ content/events/2015-ohio/conduct.md | 36 +++++ content/events/2015-ohio/contact.md | 17 +++ content/events/2015-ohio/location.md | 10 ++ content/events/2015-ohio/program.md | 122 +++++++++++++++++ content/events/2015-ohio/propose.md | 37 ++++++ content/events/2015-ohio/registration.md | 13 ++ content/events/2015-ohio/sponsor.md | 49 +++++++ content/events/2015-ohio/welcome.md | 52 ++++++++ content/events/2015-paris/conduct.md | 36 +++++ content/events/2015-paris/contact.md | 17 +++ content/events/2015-paris/location.md | 10 ++ content/events/2015-paris/program.md | 122 +++++++++++++++++ content/events/2015-paris/propose.md | 37 ++++++ content/events/2015-paris/registration.md | 13 ++ content/events/2015-paris/sponsor.md | 49 +++++++ content/events/2015-paris/welcome.md | 52 ++++++++ content/events/2015-pittsburgh/conduct.md | 36 +++++ content/events/2015-pittsburgh/contact.md | 17 +++ content/events/2015-pittsburgh/location.md | 10 ++ content/events/2015-pittsburgh/program.md | 122 +++++++++++++++++ content/events/2015-pittsburgh/propose.md | 37 ++++++ .../events/2015-pittsburgh/registration.md | 13 ++ content/events/2015-pittsburgh/sponsor.md | 49 +++++++ content/events/2015-pittsburgh/welcome.md | 52 ++++++++ content/events/2015-siliconvalley/conduct.md | 36 +++++ content/events/2015-siliconvalley/contact.md | 17 +++ content/events/2015-siliconvalley/location.md | 10 ++ content/events/2015-siliconvalley/program.md | 122 +++++++++++++++++ content/events/2015-siliconvalley/propose.md | 37 ++++++ .../events/2015-siliconvalley/registration.md | 13 ++ content/events/2015-siliconvalley/sponsor.md | 49 +++++++ content/events/2015-siliconvalley/welcome.md | 52 ++++++++ content/events/2015-singapore/conduct.md | 36 +++++ content/events/2015-singapore/contact.md | 17 +++ content/events/2015-singapore/location.md | 10 ++ content/events/2015-singapore/program.md | 122 +++++++++++++++++ content/events/2015-singapore/propose.md | 37 ++++++ content/events/2015-singapore/registration.md | 13 ++ content/events/2015-singapore/sponsor.md | 49 +++++++ content/events/2015-singapore/welcome.md | 52 ++++++++ content/events/2015-telaviv/conduct.md | 36 +++++ content/events/2015-telaviv/contact.md | 17 +++ content/events/2015-telaviv/location.md | 10 ++ content/events/2015-telaviv/program.md | 122 +++++++++++++++++ content/events/2015-telaviv/propose.md | 37 ++++++ content/events/2015-telaviv/registration.md | 13 ++ content/events/2015-telaviv/sponsor.md | 49 +++++++ content/events/2015-telaviv/welcome.md | 52 ++++++++ content/events/2015-toronto/conduct.md | 36 +++++ content/events/2015-toronto/contact.md | 17 +++ content/events/2015-toronto/location.md | 10 ++ content/events/2015-toronto/program.md | 122 +++++++++++++++++ content/events/2015-toronto/propose.md | 37 ++++++ content/events/2015-toronto/registration.md | 13 ++ content/events/2015-toronto/sponsor.md | 49 +++++++ content/events/2015-toronto/welcome.md | 52 ++++++++ content/events/2015-warsaw/conduct.md | 36 +++++ content/events/2015-warsaw/contact.md | 17 +++ content/events/2015-warsaw/location.md | 10 ++ content/events/2015-warsaw/program.md | 122 +++++++++++++++++ content/events/2015-warsaw/propose.md | 37 ++++++ content/events/2015-warsaw/registration.md | 13 ++ content/events/2015-warsaw/sponsor.md | 49 +++++++ content/events/2015-warsaw/welcome.md | 52 ++++++++ content/events/2015-washington-dc/conduct.md | 36 +++++ content/events/2015-washington-dc/contact.md | 17 +++ content/events/2015-washington-dc/location.md | 10 ++ content/events/2015-washington-dc/program.md | 122 +++++++++++++++++ content/events/2015-washington-dc/propose.md | 37 ++++++ .../events/2015-washington-dc/registration.md | 13 ++ content/events/2015-washington-dc/sponsor.md | 49 +++++++ content/events/2015-washington-dc/welcome.md | 52 ++++++++ .../events/2016-losangeles-1day/conduct.md | 36 +++++ .../events/2016-losangeles-1day/contact.md | 17 +++ .../events/2016-losangeles-1day/location.md | 10 ++ .../events/2016-losangeles-1day/program.md | 122 +++++++++++++++++ .../events/2016-losangeles-1day/propose.md | 37 ++++++ .../2016-losangeles-1day/registration.md | 13 ++ .../events/2016-losangeles-1day/sponsor.md | 49 +++++++ .../events/2016-losangeles-1day/welcome.md | 52 ++++++++ content/events/2016-vancouver/welcome.md | 2 +- data/events/2010-boston.yml | 28 ---- data/events/2010-brazil.yml | 52 ++++++++ data/events/2010-europe.yml | 59 +++++++++ data/events/2010-sydney.yml | 67 +++++++--- data/events/2010-us.yml | 59 +++++++++ data/events/2011-bangalore.yml | 59 +++++++++ data/events/2011-boston.yml | 59 +++++++++ data/events/2011-goteborg.yml | 59 +++++++++ data/events/2011-manila.yml | 59 +++++++++ data/events/2011-melbourne.yml | 59 +++++++++ data/events/2011-mountainview.yml | 59 +++++++++ data/events/2012-austin.yml | 67 +++++++--- data/events/2012-india.yml | 59 +++++++++ data/events/2012-italy.yml | 59 +++++++++ data/events/2012-mountainview.yml | 59 +++++++++ data/events/2012-newyork.yml | 59 +++++++++ data/events/2012-tokyo.yml | 59 +++++++++ data/events/2013-amsterdam.yml | 59 +++++++++ data/events/2013-atlanta.yml | 59 +++++++++ data/events/2013-austin.yml | 59 +++++++++ data/events/2013-barcelona.yml | 59 +++++++++ data/events/2013-berlin.yml | 59 +++++++++ data/events/2013-downunder.yml | 59 +++++++++ data/events/2013-india.yml | 59 +++++++++ data/events/2013-london-spring.yml | 59 +++++++++ data/events/2013-london.yml | 67 +++++++--- data/events/2013-mountainview.yml | 59 +++++++++ data/events/2013-newyork.yml | 59 +++++++++ data/events/2013-newzealand.yml | 59 +++++++++ data/events/2013-paris.yml | 59 +++++++++ data/events/2013-portland.yml | 59 +++++++++ data/events/2013-telaviv.yml | 59 +++++++++ data/events/2013-tokyo.yml | 59 +++++++++ data/events/2013-vancouver.yml | 59 +++++++++ data/events/2014-amsterdam.yml | 59 +++++++++ data/events/2014-austin.yml | 67 +++++++--- data/events/2014-bangalore.yml | 59 +++++++++ data/events/2014-belgium.yml | 59 +++++++++ data/events/2014-berlin.yml | 59 +++++++++ data/events/2014-boston.yml | 59 +++++++++ data/events/2014-brisbane.yml | 59 +++++++++ data/events/2014-chicago.yml | 59 +++++++++ data/events/2014-helsinki.yml | 59 +++++++++ data/events/2014-ljubljana.yml | 59 +++++++++ data/events/2014-minneapolis.yml | 59 +++++++++ data/events/2014-nairobi.yml | 59 +++++++++ data/events/2014-newyork.yml | 59 +++++++++ data/events/2014-pittsburgh.yml | 59 +++++++++ data/events/2014-siliconvalley.yml | 59 +++++++++ data/events/2014-telaviv.yml | 59 +++++++++ data/events/2014-toronto.yml | 59 +++++++++ data/events/2014-vancouver.yml | 59 +++++++++ data/events/2014-warsaw.yml | 59 +++++++++ data/events/2015-amsterdam.yml | 59 +++++++++ data/events/2015-austin.yml | 59 +++++++++ data/events/2015-bangalore.yml | 59 +++++++++ data/events/2015-berlin.yml | 59 +++++++++ data/events/2015-boston.yml | 59 +++++++++ data/events/2015-charlotte.yml | 59 +++++++++ data/events/2015-chicago.yml | 67 +++++++--- data/events/2015-denver.yml | 59 +++++++++ data/events/2015-detroit.yml | 59 +++++++++ data/events/2015-ljubljana.yml | 59 +++++++++ data/events/2015-melbourne.yml | 59 +++++++++ data/events/2015-minneapolis.yml | 59 +++++++++ data/events/2015-newyork.yml | 59 +++++++++ data/events/2015-ohio.yml | 59 +++++++++ data/events/2015-paris.yml | 59 +++++++++ data/events/2015-pittsburgh.yml | 59 +++++++++ data/events/2015-siliconvalley.yml | 59 +++++++++ data/events/2015-singapore.yml | 59 +++++++++ data/events/2015-telaviv.yml | 59 +++++++++ data/events/2015-toronto.yml | 59 +++++++++ data/events/2015-warsaw.yml | 81 ++++++++---- data/events/2015-washington-dc.yml | 59 +++++++++ data/events/2016-atlanta.yml | 4 +- data/events/2016-chicago.yml | 2 +- data/events/2016-london.yml | 2 +- data/events/2016-losangeles-1day.yml | 59 +++++++++ data/events/2016-vancouver.yml | 4 +- data/events/2016-washington-dc.yml | 2 +- data/sponsors/opscode-2010.yml | 2 + static/img/image039klein.jpg | Bin 0 -> 24846 bytes .../layouts/partials/past.html | 2 +- 682 files changed, 29381 insertions(+), 184 deletions(-) create mode 100644 content/events/2010-brazil/contact.md create mode 100644 content/events/2010-brazil/location.md create mode 100644 content/events/2010-brazil/program.md create mode 100644 content/events/2010-brazil/speakers.md create mode 100644 content/events/2010-brazil/welcome.md create mode 100644 content/events/2010-europe/conduct.md create mode 100644 content/events/2010-europe/contact.md create mode 100644 content/events/2010-europe/location.md create mode 100644 content/events/2010-europe/program.md create mode 100644 content/events/2010-europe/propose.md create mode 100644 content/events/2010-europe/registration.md create mode 100644 content/events/2010-europe/sponsor.md create mode 100644 content/events/2010-europe/welcome.md create mode 100644 content/events/2010-sydney/conduct.md create mode 100644 content/events/2010-sydney/contact.md create mode 100644 content/events/2010-sydney/location.md create mode 100644 content/events/2010-sydney/program.md create mode 100644 content/events/2010-sydney/propose.md create mode 100644 content/events/2010-sydney/registration.md create mode 100644 content/events/2010-sydney/sponsor.md create mode 100644 content/events/2010-sydney/welcome.md create mode 100644 content/events/2010-us/conduct.md create mode 100644 content/events/2010-us/contact.md create mode 100644 content/events/2010-us/location.md create mode 100644 content/events/2010-us/program.md create mode 100644 content/events/2010-us/propose.md create mode 100644 content/events/2010-us/registration.md create mode 100644 content/events/2010-us/sponsor.md create mode 100644 content/events/2010-us/welcome.md create mode 100644 content/events/2011-bangalore/conduct.md create mode 100644 content/events/2011-bangalore/contact.md create mode 100644 content/events/2011-bangalore/location.md create mode 100644 content/events/2011-bangalore/program.md create mode 100644 content/events/2011-bangalore/propose.md create mode 100644 content/events/2011-bangalore/registration.md create mode 100644 content/events/2011-bangalore/sponsor.md create mode 100644 content/events/2011-bangalore/welcome.md create mode 100644 content/events/2011-boston/conduct.md create mode 100644 content/events/2011-boston/contact.md create mode 100644 content/events/2011-boston/location.md create mode 100644 content/events/2011-boston/program.md create mode 100644 content/events/2011-boston/propose.md create mode 100644 content/events/2011-boston/registration.md create mode 100644 content/events/2011-boston/sponsor.md create mode 100644 content/events/2011-boston/welcome.md create mode 100644 content/events/2011-goteborg/conduct.md create mode 100644 content/events/2011-goteborg/contact.md create mode 100644 content/events/2011-goteborg/location.md create mode 100644 content/events/2011-goteborg/program.md create mode 100644 content/events/2011-goteborg/propose.md create mode 100644 content/events/2011-goteborg/registration.md create mode 100644 content/events/2011-goteborg/sponsor.md create mode 100644 content/events/2011-goteborg/welcome.md create mode 100644 content/events/2011-manila/conduct.md create mode 100644 content/events/2011-manila/contact.md create mode 100644 content/events/2011-manila/location.md create mode 100644 content/events/2011-manila/program.md create mode 100644 content/events/2011-manila/propose.md create mode 100644 content/events/2011-manila/registration.md create mode 100644 content/events/2011-manila/sponsor.md create mode 100644 content/events/2011-manila/welcome.md create mode 100644 content/events/2011-melbourne/conduct.md create mode 100644 content/events/2011-melbourne/contact.md create mode 100644 content/events/2011-melbourne/location.md create mode 100644 content/events/2011-melbourne/program.md create mode 100644 content/events/2011-melbourne/propose.md create mode 100644 content/events/2011-melbourne/registration.md create mode 100644 content/events/2011-melbourne/sponsor.md create mode 100644 content/events/2011-melbourne/welcome.md create mode 100644 content/events/2011-mountainview/conduct.md create mode 100644 content/events/2011-mountainview/contact.md create mode 100644 content/events/2011-mountainview/location.md create mode 100644 content/events/2011-mountainview/program.md create mode 100644 content/events/2011-mountainview/propose.md create mode 100644 content/events/2011-mountainview/registration.md create mode 100644 content/events/2011-mountainview/sponsor.md create mode 100644 content/events/2011-mountainview/welcome.md create mode 100644 content/events/2012-austin/conduct.md create mode 100644 content/events/2012-austin/contact.md create mode 100644 content/events/2012-austin/location.md create mode 100644 content/events/2012-austin/program.md create mode 100644 content/events/2012-austin/propose.md create mode 100644 content/events/2012-austin/registration.md create mode 100644 content/events/2012-austin/sponsor.md create mode 100644 content/events/2012-austin/welcome.md create mode 100644 content/events/2012-india/sample-event/conduct.md create mode 100644 content/events/2012-india/sample-event/contact.md create mode 100644 content/events/2012-india/sample-event/location.md create mode 100644 content/events/2012-india/sample-event/program.md create mode 100644 content/events/2012-india/sample-event/propose.md create mode 100644 content/events/2012-india/sample-event/registration.md create mode 100644 content/events/2012-india/sample-event/sponsor.md create mode 100644 content/events/2012-india/sample-event/welcome.md create mode 100644 content/events/2012-italy/conduct.md create mode 100644 content/events/2012-italy/contact.md create mode 100644 content/events/2012-italy/location.md create mode 100644 content/events/2012-italy/program.md create mode 100644 content/events/2012-italy/propose.md create mode 100644 content/events/2012-italy/registration.md create mode 100644 content/events/2012-italy/sponsor.md create mode 100644 content/events/2012-italy/welcome.md create mode 100644 content/events/2012-mountainview/conduct.md create mode 100644 content/events/2012-mountainview/contact.md create mode 100644 content/events/2012-mountainview/location.md create mode 100644 content/events/2012-mountainview/program.md create mode 100644 content/events/2012-mountainview/propose.md create mode 100644 content/events/2012-mountainview/registration.md create mode 100644 content/events/2012-mountainview/sponsor.md create mode 100644 content/events/2012-mountainview/welcome.md create mode 100644 content/events/2012-newyork/conduct.md create mode 100644 content/events/2012-newyork/contact.md create mode 100644 content/events/2012-newyork/location.md create mode 100644 content/events/2012-newyork/program.md create mode 100644 content/events/2012-newyork/propose.md create mode 100644 content/events/2012-newyork/registration.md create mode 100644 content/events/2012-newyork/sponsor.md create mode 100644 content/events/2012-newyork/welcome.md create mode 100644 content/events/2012-tokyo/conduct.md create mode 100644 content/events/2012-tokyo/contact.md create mode 100644 content/events/2012-tokyo/location.md create mode 100644 content/events/2012-tokyo/program.md create mode 100644 content/events/2012-tokyo/propose.md create mode 100644 content/events/2012-tokyo/registration.md create mode 100644 content/events/2012-tokyo/sponsor.md create mode 100644 content/events/2012-tokyo/welcome.md create mode 100644 content/events/2013-amsterdam/conduct.md create mode 100644 content/events/2013-amsterdam/contact.md create mode 100644 content/events/2013-amsterdam/location.md create mode 100644 content/events/2013-amsterdam/program.md create mode 100644 content/events/2013-amsterdam/propose.md create mode 100644 content/events/2013-amsterdam/registration.md create mode 100644 content/events/2013-amsterdam/sponsor.md create mode 100644 content/events/2013-amsterdam/welcome.md create mode 100644 content/events/2013-atlanta/conduct.md create mode 100644 content/events/2013-atlanta/contact.md create mode 100644 content/events/2013-atlanta/location.md create mode 100644 content/events/2013-atlanta/program.md create mode 100644 content/events/2013-atlanta/propose.md create mode 100644 content/events/2013-atlanta/registration.md create mode 100644 content/events/2013-atlanta/sponsor.md create mode 100644 content/events/2013-atlanta/welcome.md create mode 100644 content/events/2013-austin/conduct.md create mode 100644 content/events/2013-austin/contact.md create mode 100644 content/events/2013-austin/location.md create mode 100644 content/events/2013-austin/program.md create mode 100644 content/events/2013-austin/propose.md create mode 100644 content/events/2013-austin/registration.md create mode 100644 content/events/2013-austin/sponsor.md create mode 100644 content/events/2013-austin/welcome.md create mode 100644 content/events/2013-barcelona/conduct.md create mode 100644 content/events/2013-barcelona/contact.md create mode 100644 content/events/2013-barcelona/location.md create mode 100644 content/events/2013-barcelona/program.md create mode 100644 content/events/2013-barcelona/propose.md create mode 100644 content/events/2013-barcelona/registration.md create mode 100644 content/events/2013-barcelona/sponsor.md create mode 100644 content/events/2013-barcelona/welcome.md create mode 100644 content/events/2013-berlin/conduct.md create mode 100644 content/events/2013-berlin/contact.md create mode 100644 content/events/2013-berlin/location.md create mode 100644 content/events/2013-berlin/program.md create mode 100644 content/events/2013-berlin/propose.md create mode 100644 content/events/2013-berlin/registration.md create mode 100644 content/events/2013-berlin/sponsor.md create mode 100644 content/events/2013-berlin/welcome.md create mode 100644 content/events/2013-downunder/conduct.md create mode 100644 content/events/2013-downunder/contact.md create mode 100644 content/events/2013-downunder/location.md create mode 100644 content/events/2013-downunder/program.md create mode 100644 content/events/2013-downunder/propose.md create mode 100644 content/events/2013-downunder/registration.md create mode 100644 content/events/2013-downunder/sponsor.md create mode 100644 content/events/2013-downunder/welcome.md create mode 100644 content/events/2013-india/conduct.md create mode 100644 content/events/2013-india/contact.md create mode 100644 content/events/2013-india/location.md create mode 100644 content/events/2013-india/program.md create mode 100644 content/events/2013-india/propose.md create mode 100644 content/events/2013-india/registration.md create mode 100644 content/events/2013-india/sponsor.md create mode 100644 content/events/2013-india/welcome.md create mode 100644 content/events/2013-london-spring/conduct.md create mode 100644 content/events/2013-london-spring/contact.md create mode 100644 content/events/2013-london-spring/location.md create mode 100644 content/events/2013-london-spring/program.md create mode 100644 content/events/2013-london-spring/propose.md create mode 100644 content/events/2013-london-spring/registration.md create mode 100644 content/events/2013-london-spring/sponsor.md create mode 100644 content/events/2013-london-spring/welcome.md create mode 100644 content/events/2013-london/conduct.md create mode 100644 content/events/2013-london/contact.md create mode 100644 content/events/2013-london/location.md create mode 100644 content/events/2013-london/program.md create mode 100644 content/events/2013-london/propose.md create mode 100644 content/events/2013-london/registration.md create mode 100644 content/events/2013-london/sponsor.md create mode 100644 content/events/2013-london/welcome.md create mode 100644 content/events/2013-mountainview/conduct.md create mode 100644 content/events/2013-mountainview/contact.md create mode 100644 content/events/2013-mountainview/location.md create mode 100644 content/events/2013-mountainview/program.md create mode 100644 content/events/2013-mountainview/propose.md create mode 100644 content/events/2013-mountainview/registration.md create mode 100644 content/events/2013-mountainview/sponsor.md create mode 100644 content/events/2013-mountainview/welcome.md create mode 100644 content/events/2013-newyork/conduct.md create mode 100644 content/events/2013-newyork/contact.md create mode 100644 content/events/2013-newyork/location.md create mode 100644 content/events/2013-newyork/program.md create mode 100644 content/events/2013-newyork/propose.md create mode 100644 content/events/2013-newyork/registration.md create mode 100644 content/events/2013-newyork/sponsor.md create mode 100644 content/events/2013-newyork/welcome.md create mode 100644 content/events/2013-newzealand/conduct.md create mode 100644 content/events/2013-newzealand/contact.md create mode 100644 content/events/2013-newzealand/location.md create mode 100644 content/events/2013-newzealand/program.md create mode 100644 content/events/2013-newzealand/propose.md create mode 100644 content/events/2013-newzealand/registration.md create mode 100644 content/events/2013-newzealand/sponsor.md create mode 100644 content/events/2013-newzealand/welcome.md create mode 100644 content/events/2013-paris/conduct.md create mode 100644 content/events/2013-paris/contact.md create mode 100644 content/events/2013-paris/location.md create mode 100644 content/events/2013-paris/program.md create mode 100644 content/events/2013-paris/propose.md create mode 100644 content/events/2013-paris/registration.md create mode 100644 content/events/2013-paris/sponsor.md create mode 100644 content/events/2013-paris/welcome.md create mode 100644 content/events/2013-portland/conduct.md create mode 100644 content/events/2013-portland/contact.md create mode 100644 content/events/2013-portland/location.md create mode 100644 content/events/2013-portland/program.md create mode 100644 content/events/2013-portland/propose.md create mode 100644 content/events/2013-portland/registration.md create mode 100644 content/events/2013-portland/sponsor.md create mode 100644 content/events/2013-portland/welcome.md create mode 100644 content/events/2013-telaviv/conduct.md create mode 100644 content/events/2013-telaviv/contact.md create mode 100644 content/events/2013-telaviv/location.md create mode 100644 content/events/2013-telaviv/program.md create mode 100644 content/events/2013-telaviv/propose.md create mode 100644 content/events/2013-telaviv/registration.md create mode 100644 content/events/2013-telaviv/sponsor.md create mode 100644 content/events/2013-telaviv/welcome.md create mode 100644 content/events/2013-tokyo/conduct.md create mode 100644 content/events/2013-tokyo/contact.md create mode 100644 content/events/2013-tokyo/location.md create mode 100644 content/events/2013-tokyo/program.md create mode 100644 content/events/2013-tokyo/propose.md create mode 100644 content/events/2013-tokyo/registration.md create mode 100644 content/events/2013-tokyo/sponsor.md create mode 100644 content/events/2013-tokyo/welcome.md create mode 100644 content/events/2013-vancouver/conduct.md create mode 100644 content/events/2013-vancouver/contact.md create mode 100644 content/events/2013-vancouver/location.md create mode 100644 content/events/2013-vancouver/program.md create mode 100644 content/events/2013-vancouver/propose.md create mode 100644 content/events/2013-vancouver/registration.md create mode 100644 content/events/2013-vancouver/sponsor.md create mode 100644 content/events/2013-vancouver/welcome.md create mode 100644 content/events/2014-amsterdam/conduct.md create mode 100644 content/events/2014-amsterdam/contact.md create mode 100644 content/events/2014-amsterdam/location.md create mode 100644 content/events/2014-amsterdam/program.md create mode 100644 content/events/2014-amsterdam/propose.md create mode 100644 content/events/2014-amsterdam/registration.md create mode 100644 content/events/2014-amsterdam/sponsor.md create mode 100644 content/events/2014-amsterdam/welcome.md create mode 100644 content/events/2014-austin/conduct.md create mode 100644 content/events/2014-austin/contact.md create mode 100644 content/events/2014-austin/location.md create mode 100644 content/events/2014-austin/program.md create mode 100644 content/events/2014-austin/propose.md create mode 100644 content/events/2014-austin/registration.md create mode 100644 content/events/2014-austin/sponsor.md create mode 100644 content/events/2014-austin/welcome.md create mode 100644 content/events/2014-bangalore/conduct.md create mode 100644 content/events/2014-bangalore/contact.md create mode 100644 content/events/2014-bangalore/location.md create mode 100644 content/events/2014-bangalore/program.md create mode 100644 content/events/2014-bangalore/propose.md create mode 100644 content/events/2014-bangalore/registration.md create mode 100644 content/events/2014-bangalore/sponsor.md create mode 100644 content/events/2014-bangalore/welcome.md create mode 100644 content/events/2014-belgium/conduct.md create mode 100644 content/events/2014-belgium/contact.md create mode 100644 content/events/2014-belgium/location.md create mode 100644 content/events/2014-belgium/program.md create mode 100644 content/events/2014-belgium/propose.md create mode 100644 content/events/2014-belgium/registration.md create mode 100644 content/events/2014-belgium/sponsor.md create mode 100644 content/events/2014-belgium/welcome.md create mode 100644 content/events/2014-berlin/conduct.md create mode 100644 content/events/2014-berlin/contact.md create mode 100644 content/events/2014-berlin/location.md create mode 100644 content/events/2014-berlin/program.md create mode 100644 content/events/2014-berlin/propose.md create mode 100644 content/events/2014-berlin/registration.md create mode 100644 content/events/2014-berlin/sponsor.md create mode 100644 content/events/2014-berlin/welcome.md create mode 100644 content/events/2014-boston/conduct.md create mode 100644 content/events/2014-boston/contact.md create mode 100644 content/events/2014-boston/location.md create mode 100644 content/events/2014-boston/program.md create mode 100644 content/events/2014-boston/propose.md create mode 100644 content/events/2014-boston/registration.md create mode 100644 content/events/2014-boston/sponsor.md create mode 100644 content/events/2014-boston/welcome.md create mode 100644 content/events/2014-brisbane/conduct.md create mode 100644 content/events/2014-brisbane/contact.md create mode 100644 content/events/2014-brisbane/location.md create mode 100644 content/events/2014-brisbane/program.md create mode 100644 content/events/2014-brisbane/propose.md create mode 100644 content/events/2014-brisbane/registration.md create mode 100644 content/events/2014-brisbane/sponsor.md create mode 100644 content/events/2014-brisbane/welcome.md create mode 100644 content/events/2014-chicago/conduct.md create mode 100644 content/events/2014-chicago/contact.md create mode 100644 content/events/2014-chicago/location.md create mode 100644 content/events/2014-chicago/program.md create mode 100644 content/events/2014-chicago/propose.md create mode 100644 content/events/2014-chicago/registration.md create mode 100644 content/events/2014-chicago/sponsor.md create mode 100644 content/events/2014-chicago/welcome.md create mode 100644 content/events/2014-helsinki/conduct.md create mode 100644 content/events/2014-helsinki/contact.md create mode 100644 content/events/2014-helsinki/location.md create mode 100644 content/events/2014-helsinki/program.md create mode 100644 content/events/2014-helsinki/propose.md create mode 100644 content/events/2014-helsinki/registration.md create mode 100644 content/events/2014-helsinki/sponsor.md create mode 100644 content/events/2014-helsinki/welcome.md create mode 100644 content/events/2014-ljubljana/conduct.md create mode 100644 content/events/2014-ljubljana/contact.md create mode 100644 content/events/2014-ljubljana/location.md create mode 100644 content/events/2014-ljubljana/program.md create mode 100644 content/events/2014-ljubljana/propose.md create mode 100644 content/events/2014-ljubljana/registration.md create mode 100644 content/events/2014-ljubljana/sponsor.md create mode 100644 content/events/2014-ljubljana/welcome.md create mode 100644 content/events/2014-minneapolis/conduct.md create mode 100644 content/events/2014-minneapolis/contact.md create mode 100644 content/events/2014-minneapolis/location.md create mode 100644 content/events/2014-minneapolis/program.md create mode 100644 content/events/2014-minneapolis/propose.md create mode 100644 content/events/2014-minneapolis/registration.md create mode 100644 content/events/2014-minneapolis/sponsor.md create mode 100644 content/events/2014-minneapolis/welcome.md create mode 100644 content/events/2014-nairobi/conduct.md create mode 100644 content/events/2014-nairobi/contact.md create mode 100644 content/events/2014-nairobi/location.md create mode 100644 content/events/2014-nairobi/program.md create mode 100644 content/events/2014-nairobi/propose.md create mode 100644 content/events/2014-nairobi/registration.md create mode 100644 content/events/2014-nairobi/sponsor.md create mode 100644 content/events/2014-nairobi/welcome.md create mode 100644 content/events/2014-newyork/conduct.md create mode 100644 content/events/2014-newyork/contact.md create mode 100644 content/events/2014-newyork/location.md create mode 100644 content/events/2014-newyork/program.md create mode 100644 content/events/2014-newyork/propose.md create mode 100644 content/events/2014-newyork/registration.md create mode 100644 content/events/2014-newyork/sponsor.md create mode 100644 content/events/2014-newyork/welcome.md create mode 100644 content/events/2014-pittsburgh/sample-event/conduct.md create mode 100644 content/events/2014-pittsburgh/sample-event/contact.md create mode 100644 content/events/2014-pittsburgh/sample-event/location.md create mode 100644 content/events/2014-pittsburgh/sample-event/program.md create mode 100644 content/events/2014-pittsburgh/sample-event/propose.md create mode 100644 content/events/2014-pittsburgh/sample-event/registration.md create mode 100644 content/events/2014-pittsburgh/sample-event/sponsor.md create mode 100644 content/events/2014-pittsburgh/sample-event/welcome.md create mode 100644 content/events/2014-siliconvalley/conduct.md create mode 100644 content/events/2014-siliconvalley/contact.md create mode 100644 content/events/2014-siliconvalley/location.md create mode 100644 content/events/2014-siliconvalley/program.md create mode 100644 content/events/2014-siliconvalley/propose.md create mode 100644 content/events/2014-siliconvalley/registration.md create mode 100644 content/events/2014-siliconvalley/sponsor.md create mode 100644 content/events/2014-siliconvalley/welcome.md create mode 100644 content/events/2014-telaviv/conduct.md create mode 100644 content/events/2014-telaviv/contact.md create mode 100644 content/events/2014-telaviv/location.md create mode 100644 content/events/2014-telaviv/program.md create mode 100644 content/events/2014-telaviv/propose.md create mode 100644 content/events/2014-telaviv/registration.md create mode 100644 content/events/2014-telaviv/sponsor.md create mode 100644 content/events/2014-telaviv/welcome.md create mode 100644 content/events/2014-toronto/conduct.md create mode 100644 content/events/2014-toronto/contact.md create mode 100644 content/events/2014-toronto/location.md create mode 100644 content/events/2014-toronto/program.md create mode 100644 content/events/2014-toronto/propose.md create mode 100644 content/events/2014-toronto/registration.md create mode 100644 content/events/2014-toronto/sponsor.md create mode 100644 content/events/2014-toronto/welcome.md create mode 100644 content/events/2014-vancouver/conduct.md create mode 100644 content/events/2014-vancouver/contact.md create mode 100644 content/events/2014-vancouver/location.md create mode 100644 content/events/2014-vancouver/program.md create mode 100644 content/events/2014-vancouver/propose.md create mode 100644 content/events/2014-vancouver/registration.md create mode 100644 content/events/2014-vancouver/sponsor.md create mode 100644 content/events/2014-vancouver/welcome.md create mode 100644 content/events/2014-warsaw/conduct.md create mode 100644 content/events/2014-warsaw/contact.md create mode 100644 content/events/2014-warsaw/location.md create mode 100644 content/events/2014-warsaw/program.md create mode 100644 content/events/2014-warsaw/propose.md create mode 100644 content/events/2014-warsaw/registration.md create mode 100644 content/events/2014-warsaw/sponsor.md create mode 100644 content/events/2014-warsaw/welcome.md create mode 100644 content/events/2015-amsterdam/conduct.md create mode 100644 content/events/2015-amsterdam/contact.md create mode 100644 content/events/2015-amsterdam/location.md create mode 100644 content/events/2015-amsterdam/program.md create mode 100644 content/events/2015-amsterdam/propose.md create mode 100644 content/events/2015-amsterdam/registration.md create mode 100644 content/events/2015-amsterdam/sponsor.md create mode 100644 content/events/2015-amsterdam/welcome.md create mode 100644 content/events/2015-austin/conduct.md create mode 100644 content/events/2015-austin/contact.md create mode 100644 content/events/2015-austin/location.md create mode 100644 content/events/2015-austin/program.md create mode 100644 content/events/2015-austin/propose.md create mode 100644 content/events/2015-austin/registration.md create mode 100644 content/events/2015-austin/sponsor.md create mode 100644 content/events/2015-austin/welcome.md create mode 100644 content/events/2015-bangalore/conduct.md create mode 100644 content/events/2015-bangalore/contact.md create mode 100644 content/events/2015-bangalore/location.md create mode 100644 content/events/2015-bangalore/program.md create mode 100644 content/events/2015-bangalore/propose.md create mode 100644 content/events/2015-bangalore/registration.md create mode 100644 content/events/2015-bangalore/sponsor.md create mode 100644 content/events/2015-bangalore/welcome.md create mode 100644 content/events/2015-berlin/conduct.md create mode 100644 content/events/2015-berlin/contact.md create mode 100644 content/events/2015-berlin/location.md create mode 100644 content/events/2015-berlin/program.md create mode 100644 content/events/2015-berlin/propose.md create mode 100644 content/events/2015-berlin/registration.md create mode 100644 content/events/2015-berlin/sponsor.md create mode 100644 content/events/2015-berlin/welcome.md create mode 100644 content/events/2015-boston/conduct.md create mode 100644 content/events/2015-boston/contact.md create mode 100644 content/events/2015-boston/location.md create mode 100644 content/events/2015-boston/program.md create mode 100644 content/events/2015-boston/propose.md create mode 100644 content/events/2015-boston/registration.md create mode 100644 content/events/2015-boston/sponsor.md create mode 100644 content/events/2015-boston/welcome.md create mode 100644 content/events/2015-charlotte/conduct.md create mode 100644 content/events/2015-charlotte/contact.md create mode 100644 content/events/2015-charlotte/location.md create mode 100644 content/events/2015-charlotte/program.md create mode 100644 content/events/2015-charlotte/propose.md create mode 100644 content/events/2015-charlotte/registration.md create mode 100644 content/events/2015-charlotte/sponsor.md create mode 100644 content/events/2015-charlotte/welcome.md create mode 100644 content/events/2015-chicago/propose.md create mode 100644 content/events/2015-chicago/registration.md create mode 100644 content/events/2015-denver/conduct.md create mode 100644 content/events/2015-denver/contact.md create mode 100644 content/events/2015-denver/location.md create mode 100644 content/events/2015-denver/program.md create mode 100644 content/events/2015-denver/propose.md create mode 100644 content/events/2015-denver/registration.md create mode 100644 content/events/2015-denver/sponsor.md create mode 100644 content/events/2015-denver/welcome.md create mode 100644 content/events/2015-detroit/conduct.md create mode 100644 content/events/2015-detroit/contact.md create mode 100644 content/events/2015-detroit/location.md create mode 100644 content/events/2015-detroit/program.md create mode 100644 content/events/2015-detroit/propose.md create mode 100644 content/events/2015-detroit/registration.md create mode 100644 content/events/2015-detroit/sponsor.md create mode 100644 content/events/2015-detroit/welcome.md create mode 100644 content/events/2015-ljubljana/conduct.md create mode 100644 content/events/2015-ljubljana/contact.md create mode 100644 content/events/2015-ljubljana/location.md create mode 100644 content/events/2015-ljubljana/program.md create mode 100644 content/events/2015-ljubljana/propose.md create mode 100644 content/events/2015-ljubljana/registration.md create mode 100644 content/events/2015-ljubljana/sponsor.md create mode 100644 content/events/2015-ljubljana/welcome.md create mode 100644 content/events/2015-melbourne/conduct.md create mode 100644 content/events/2015-melbourne/contact.md create mode 100644 content/events/2015-melbourne/location.md create mode 100644 content/events/2015-melbourne/program.md create mode 100644 content/events/2015-melbourne/propose.md create mode 100644 content/events/2015-melbourne/registration.md create mode 100644 content/events/2015-melbourne/sponsor.md create mode 100644 content/events/2015-melbourne/welcome.md create mode 100644 content/events/2015-minneapolis/conduct.md create mode 100644 content/events/2015-minneapolis/contact.md create mode 100644 content/events/2015-minneapolis/location.md create mode 100644 content/events/2015-minneapolis/program.md create mode 100644 content/events/2015-minneapolis/propose.md create mode 100644 content/events/2015-minneapolis/registration.md create mode 100644 content/events/2015-minneapolis/sponsor.md create mode 100644 content/events/2015-minneapolis/welcome.md create mode 100644 content/events/2015-newyork/sample-event/conduct.md create mode 100644 content/events/2015-newyork/sample-event/contact.md create mode 100644 content/events/2015-newyork/sample-event/location.md create mode 100644 content/events/2015-newyork/sample-event/program.md create mode 100644 content/events/2015-newyork/sample-event/propose.md create mode 100644 content/events/2015-newyork/sample-event/registration.md create mode 100644 content/events/2015-newyork/sample-event/sponsor.md create mode 100644 content/events/2015-newyork/sample-event/welcome.md create mode 100644 content/events/2015-ohio/conduct.md create mode 100644 content/events/2015-ohio/contact.md create mode 100644 content/events/2015-ohio/location.md create mode 100644 content/events/2015-ohio/program.md create mode 100644 content/events/2015-ohio/propose.md create mode 100644 content/events/2015-ohio/registration.md create mode 100644 content/events/2015-ohio/sponsor.md create mode 100644 content/events/2015-ohio/welcome.md create mode 100644 content/events/2015-paris/conduct.md create mode 100644 content/events/2015-paris/contact.md create mode 100644 content/events/2015-paris/location.md create mode 100644 content/events/2015-paris/program.md create mode 100644 content/events/2015-paris/propose.md create mode 100644 content/events/2015-paris/registration.md create mode 100644 content/events/2015-paris/sponsor.md create mode 100644 content/events/2015-paris/welcome.md create mode 100644 content/events/2015-pittsburgh/conduct.md create mode 100644 content/events/2015-pittsburgh/contact.md create mode 100644 content/events/2015-pittsburgh/location.md create mode 100644 content/events/2015-pittsburgh/program.md create mode 100644 content/events/2015-pittsburgh/propose.md create mode 100644 content/events/2015-pittsburgh/registration.md create mode 100644 content/events/2015-pittsburgh/sponsor.md create mode 100644 content/events/2015-pittsburgh/welcome.md create mode 100644 content/events/2015-siliconvalley/conduct.md create mode 100644 content/events/2015-siliconvalley/contact.md create mode 100644 content/events/2015-siliconvalley/location.md create mode 100644 content/events/2015-siliconvalley/program.md create mode 100644 content/events/2015-siliconvalley/propose.md create mode 100644 content/events/2015-siliconvalley/registration.md create mode 100644 content/events/2015-siliconvalley/sponsor.md create mode 100644 content/events/2015-siliconvalley/welcome.md create mode 100644 content/events/2015-singapore/conduct.md create mode 100644 content/events/2015-singapore/contact.md create mode 100644 content/events/2015-singapore/location.md create mode 100644 content/events/2015-singapore/program.md create mode 100644 content/events/2015-singapore/propose.md create mode 100644 content/events/2015-singapore/registration.md create mode 100644 content/events/2015-singapore/sponsor.md create mode 100644 content/events/2015-singapore/welcome.md create mode 100644 content/events/2015-telaviv/conduct.md create mode 100644 content/events/2015-telaviv/contact.md create mode 100644 content/events/2015-telaviv/location.md create mode 100644 content/events/2015-telaviv/program.md create mode 100644 content/events/2015-telaviv/propose.md create mode 100644 content/events/2015-telaviv/registration.md create mode 100644 content/events/2015-telaviv/sponsor.md create mode 100644 content/events/2015-telaviv/welcome.md create mode 100644 content/events/2015-toronto/conduct.md create mode 100644 content/events/2015-toronto/contact.md create mode 100644 content/events/2015-toronto/location.md create mode 100644 content/events/2015-toronto/program.md create mode 100644 content/events/2015-toronto/propose.md create mode 100644 content/events/2015-toronto/registration.md create mode 100644 content/events/2015-toronto/sponsor.md create mode 100644 content/events/2015-toronto/welcome.md create mode 100644 content/events/2015-warsaw/conduct.md create mode 100644 content/events/2015-warsaw/contact.md create mode 100644 content/events/2015-warsaw/location.md create mode 100644 content/events/2015-warsaw/program.md create mode 100644 content/events/2015-warsaw/propose.md create mode 100644 content/events/2015-warsaw/registration.md create mode 100644 content/events/2015-warsaw/sponsor.md create mode 100644 content/events/2015-warsaw/welcome.md create mode 100644 content/events/2015-washington-dc/conduct.md create mode 100644 content/events/2015-washington-dc/contact.md create mode 100644 content/events/2015-washington-dc/location.md create mode 100644 content/events/2015-washington-dc/program.md create mode 100644 content/events/2015-washington-dc/propose.md create mode 100644 content/events/2015-washington-dc/registration.md create mode 100644 content/events/2015-washington-dc/sponsor.md create mode 100644 content/events/2015-washington-dc/welcome.md create mode 100644 content/events/2016-losangeles-1day/conduct.md create mode 100644 content/events/2016-losangeles-1day/contact.md create mode 100644 content/events/2016-losangeles-1day/location.md create mode 100644 content/events/2016-losangeles-1day/program.md create mode 100644 content/events/2016-losangeles-1day/propose.md create mode 100644 content/events/2016-losangeles-1day/registration.md create mode 100644 content/events/2016-losangeles-1day/sponsor.md create mode 100644 content/events/2016-losangeles-1day/welcome.md delete mode 100644 data/events/2010-boston.yml create mode 100644 data/events/2010-brazil.yml create mode 100644 data/events/2010-europe.yml create mode 100644 data/events/2010-us.yml create mode 100644 data/events/2011-bangalore.yml create mode 100644 data/events/2011-boston.yml create mode 100644 data/events/2011-goteborg.yml create mode 100644 data/events/2011-manila.yml create mode 100644 data/events/2011-melbourne.yml create mode 100644 data/events/2011-mountainview.yml create mode 100644 data/events/2012-india.yml create mode 100644 data/events/2012-italy.yml create mode 100644 data/events/2012-mountainview.yml create mode 100644 data/events/2012-newyork.yml create mode 100644 data/events/2012-tokyo.yml create mode 100644 data/events/2013-amsterdam.yml create mode 100644 data/events/2013-atlanta.yml create mode 100644 data/events/2013-austin.yml create mode 100644 data/events/2013-barcelona.yml create mode 100644 data/events/2013-berlin.yml create mode 100644 data/events/2013-downunder.yml create mode 100644 data/events/2013-india.yml create mode 100644 data/events/2013-london-spring.yml create mode 100644 data/events/2013-mountainview.yml create mode 100644 data/events/2013-newyork.yml create mode 100644 data/events/2013-newzealand.yml create mode 100644 data/events/2013-paris.yml create mode 100644 data/events/2013-portland.yml create mode 100644 data/events/2013-telaviv.yml create mode 100644 data/events/2013-tokyo.yml create mode 100644 data/events/2013-vancouver.yml create mode 100644 data/events/2014-amsterdam.yml create mode 100644 data/events/2014-bangalore.yml create mode 100644 data/events/2014-belgium.yml create mode 100644 data/events/2014-berlin.yml create mode 100644 data/events/2014-boston.yml create mode 100644 data/events/2014-brisbane.yml create mode 100644 data/events/2014-chicago.yml create mode 100644 data/events/2014-helsinki.yml create mode 100644 data/events/2014-ljubljana.yml create mode 100644 data/events/2014-minneapolis.yml create mode 100644 data/events/2014-nairobi.yml create mode 100644 data/events/2014-newyork.yml create mode 100644 data/events/2014-pittsburgh.yml create mode 100644 data/events/2014-siliconvalley.yml create mode 100644 data/events/2014-telaviv.yml create mode 100644 data/events/2014-toronto.yml create mode 100644 data/events/2014-vancouver.yml create mode 100644 data/events/2014-warsaw.yml create mode 100644 data/events/2015-amsterdam.yml create mode 100644 data/events/2015-austin.yml create mode 100644 data/events/2015-bangalore.yml create mode 100644 data/events/2015-berlin.yml create mode 100644 data/events/2015-boston.yml create mode 100644 data/events/2015-charlotte.yml create mode 100644 data/events/2015-denver.yml create mode 100644 data/events/2015-detroit.yml create mode 100644 data/events/2015-ljubljana.yml create mode 100644 data/events/2015-melbourne.yml create mode 100644 data/events/2015-minneapolis.yml create mode 100644 data/events/2015-newyork.yml create mode 100644 data/events/2015-ohio.yml create mode 100644 data/events/2015-paris.yml create mode 100644 data/events/2015-pittsburgh.yml create mode 100644 data/events/2015-siliconvalley.yml create mode 100644 data/events/2015-singapore.yml create mode 100644 data/events/2015-telaviv.yml create mode 100644 data/events/2015-toronto.yml create mode 100644 data/events/2015-washington-dc.yml create mode 100644 data/events/2016-losangeles-1day.yml create mode 100644 data/sponsors/opscode-2010.yml create mode 100644 static/img/image039klein.jpg diff --git a/content/events/2010-brazil/contact.md b/content/events/2010-brazil/contact.md new file mode 100644 index 00000000000..a87d3461a88 --- /dev/null +++ b/content/events/2010-brazil/contact.md @@ -0,0 +1,38 @@ ++++ +date = "2016-05-02T12:47:01-05:00" +title = "contact" +type = "event" + + ++++ + +
+ + + + + + + +
Está sentindo falta de alguma informação? Está inquieto com alguma pergunta? + +Não se preocupe! Nós vamos cuidar disso: mande-nos um e-mail em organizers-brazil-2010@devopsdays.org - +o time devopsdays Brasil: +
    +
  • Daniel Cukier
    • +
  • Patrick Debois
    • +
  • Carlos Villela
    • +
+
+Missing some information? Having a burning question? + +Don't worry! We will take care of it: you can send us an email at organizers-brazil-2010@devopsdays.org + +the devopsdays Brazil team +
    +
  • Daniel Cukier
    • +
  • Patrick Debois
    • +
  • Carlos Villela
    • +
+
+
diff --git a/content/events/2010-brazil/location.md b/content/events/2010-brazil/location.md new file mode 100644 index 00000000000..8829a029134 --- /dev/null +++ b/content/events/2010-brazil/location.md @@ -0,0 +1,12 @@ ++++ +date = "2016-05-02T12:47:01-05:00" +title = "location" +type = "event" + ++++ + +A conferência será na Rua Arabé 71 , Sao Paulo, Brazil + +The conference will be held at : Rua Arabé 71 , Sao Paulo, Brazil + +
View Larger Map diff --git a/content/events/2010-brazil/program.md b/content/events/2010-brazil/program.md new file mode 100644 index 00000000000..c3d54de0008 --- /dev/null +++ b/content/events/2010-brazil/program.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:47:01-05:00" +title = "program" +type = "event" + ++++ + +Sábado, 4 de Dezembro de 2010, das 9h as 18h DevOps Day Brasil acontecerá num único dia - uma única trilha organizada sobre uma série de painéis/apresentações onde encorajamos fortemente a discussão aberta entre os participantes. + +Saturday December 4, 2010, 9am - 6pm DevOps Day Brazil is a single day - single track conference organized around a series of panels/presentations where open discussion amongst all conference participants is encouraged. + +
+

John Willis: Keynote: The Agile Enterprise, Devops and Clouds

+No começo, TI era limitada pelo tempo que levava para provisionar e colocar no ar uma nova infra-estrutura. Porém, com o surgimento do Cloud, podemos montar - e desmontar - um datacenter vitual inteiro instantaneamente. Isso acelera o ciclo de tempo de TI. Isso é análogo a dois outros grandes passos tecnológicos: métodos ágeis de desenvolvimento de software e o movimento "devops" de arquiteturas auto-escaláveis e auto-configuráveis. Vamos ver como o destino da nuvem, código ágil e devops estão entrelaçados, e o que isso significa para os profissionais de TI. + +Nessa sessão, John Willis (o co-apresentador dos famosos podcasts Devops Café e IT Management & Cloud) nos fará entender o que é Devops e como ele pode ajudar (ou atrapalhar!) você. Essa sessão dará uma visão pragmática sobre devops, esclarecendo como Devops se aplica para você e sua empresa. + +Once, IT was limited by the time it took to provision and deploy new infrastructure. With clouds, however, we can launch -- and decommission -- entire virtual data centers instantly. This accelerates the cycle time of IT. It's analogous to two other shifts in technology: agile software development methodologies, and the "devops" movement of self-scaling, self-healing architectures. We'll see how the fates of clouds, agile coding, and devops are intertwined, and what this means for IT professionals. + +In this session, John Willis (the co-host of the popular Devops Café and the IT Management & Cloud Podcast) will catch you up on what Devops is looking like and how it might help (or harm!) you. This session will give you a pragmatic overview of Devops and leave with a better idea of how Devops applies to you and your organization. + +
+

Carla Souza: Automagicaly manage your configuration

+Puppet é um software open source poderoso, flexível e extensível que consiste numa linguagem declarativa para expressão configurações de sistemas, além de um cliente e um servidor para distribui-la e uma biblioteca para perceber a configuração desejada. Nessa sessão, Carla Souza mostrará as funcionalidades do Puppet, os requisitos, como funciona e porque um sysadmin irá ama-lo. + +Puppet is a powerful, flexible and extensible open source software that consists in a declarative language for expressing system configuration, a client and server for distributing it, and a library for realizing the desired configuration. In this session, Carla Souza will show all Puppet’s features, requirements, how it works and why a sysadmin will love it. + +
+

Fabio Kung: Cloud e automação: tome o controle da sua infraestrutura!

+Um dos principais conceitos trazidos pelo movimento DevOps é a automação de tudo que for possível na infraestrutura. Durante esse tempo em que venho desenvolvendo produtos de Cloud, juntei algumas ideias e possibilidades que gostaria de compartilhar. + +Como algumas das principais ideias e serviços do que chamamos de "Cloud" podem ajudar? Como automatizar a infraestrutura? Como isso beneficia os meus sistemas? Como isso acelera a entrega de novas funcionalidades? E a escalabilidade? Performance? Confiabilidade? + +
+

Guilherme Silveira: Deploy contínuo: pois integração contínua não basta

+Integrar continuamente é uma das primeiras práticas de engenharia de software defendidas por nós agilistas. Mas ser ágil é poder se adaptar rapidamente, requer feedback rápido, inclusive do cliente. Como colocar logo em produção? Em homologação? Depois de ganhar experiência, passamos ao próximo passo natural: automatizar os processos de deploy para homologação e produção, mas passamos por questões desde dificuldades com a infraestrutura até problemas de segurança de dados. Passando por aplicações pequenas, desktop, médias, web e grandes, veremos qual a importância de efetuar deploy sempre. diff --git a/content/events/2010-brazil/speakers.md b/content/events/2010-brazil/speakers.md new file mode 100644 index 00000000000..9989956373f --- /dev/null +++ b/content/events/2010-brazil/speakers.md @@ -0,0 +1,42 @@ ++++ +date = "2016-05-02T12:47:01-05:00" +title = "speakers" +type = "event" + ++++ +
+ + + + + + + + + + + + + + + + + + + +
+

John Willis

+John M. Willis is currently the VP of Services at Opscode, Inc. John has worked in the IT management industry for 30 years. He began his professional career at Exxon as an IT infrastructure analyst. He is the founder of four successful startups over the past 20 years Willis is known internationally for his IT Management and Cloud blog. He also has two podcast series on clouds called ‚”Cloud Cafe‚ and Droplets”. Willis is also the co-host of Redmonk’s IT Management Guys‚ podcast series. + +John M. Willis é atualmente VP de serviços na Opscode Inc. John trabalha na indústria de tecnologia há 30 anos. Começou sua carreira profissional na Exxon como analista de infra-estrutura de TI. Fundador de quatro start-ups bem sucedidas nos últimos 20 anos, Willis é conhecido internacionalmente por seu blog de Gerenciamento de TI e Cloud. Ele também possui duas séries de podcasts sobre cloud chamada "Cloud Cafe e Droplets". Willis também é co-apresentador do Redmonk's IT Management Guis, uma série de podcast.
+

Carla Souza

+Carla Souza is a Sysadmin/Developer from Campina Grande, Brazil. Bachelor in Computer Science, currently is MSc candidate at Federal University of Campina Grande researching in distributed systems. She works with OurGrid, an opensource P2P grid computing, and BeeFS, a java distributed file system. She has 5 years of experience in Unix systems administration and has participated at Google Summer of Code 2010 working with Puppet Labs in a new module for virtualization management using libvirt library.
+

Guilherme Silveira

+Líder técnico da Caelum, graduando em matemática aplicada na USP, ministrou diversas palestras relacionadas ao desenvolvimento na web. Junto com Paulo Silveira, criou o VRaptor em 2003. Atualmente tem o foco na implementação de integração de sistemas através de api's rest e seu impacto positivo no plano de negócios dos clientes da Caelum e é commiter de projetos como restfulie, xstream, paranamer e waffle com ênfase em Java e Ruby. É também responsável pelo conteúdo técnico dos cursos.
+

Fabio Kung

+Gerente e líder técnico de Cloud Computing na Locaweb e Engenheiro da Computação pela Escola Politécnica da USP. Junto do seu time na Locaweb, é responsável por alguns dos maiores projetos de Cloud Computing e virtualização (com Xen e VMWare) da America Latina, onde a estrutura já suporta mais de 4000 máquinas virtuais. + +Desenvolvedor apaixonado por linguagens, compiladores, máquinas virtuais, sistemas operacionais, redes e virtualização. É um dos autores do livro “Arquitetura e Design de Software”, além de estar sempre palestrando e envolvido em grandes eventos de tecnologia como o Conexão Java, JustJava, Falando em Java, QCon SP, WebMobile TechWeek 2007, RejectConf SP’07, FISL, Maré de Agilidade, Ruby e Rails no mundo Real e Rails Summit Latin America. Tem alguns artigos na revista MundoJava e possui as certificações de Java SCJP, SCBCD 5 e SCEA 5; além da Certified Ruby Programmer Silver. + +Também é apaixonado por Macs e usuário de Linux desde a época do Linux Guarani 3.0, começou a programar seriamente com java em 2002, com Ruby em 2005 e possui experiência na Alemanha, onde trabalhou com desenvolvimento de sistemas em Java para a Web. Dá aulas na Caelum, já deu alguns cursos de verão no IME-USP e diversos in-company. Adora opensource, sendo membro de alguns projetos como o VRaptor, o Codehaus Waffle, o JettyRails e o Caelum Stella.
+
diff --git a/content/events/2010-brazil/welcome.md b/content/events/2010-brazil/welcome.md new file mode 100644 index 00000000000..ca7f3dc8e7f --- /dev/null +++ b/content/events/2010-brazil/welcome.md @@ -0,0 +1,16 @@ ++++ +date = "2016-05-02T12:47:01-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2010-brazil"] + ++++ + +Agradecendo a ajuda do Daniel Cukier, temos o prazer de anunciar para vocês que um novo devopsdays está chegando. Dia 4 de dezembro de 2010, todos os devops vão para São Paulo - Brazil - Rua Arabé, 71 - Vila Clementino - perto do metrô Santa Cruz . + +With many thanks to Daniel Cukier, on 4 december 2010, all samba rocking devops have head over to Brazil - Sao Paulo - Rua Arabé, 71 - Vila Clementino - near metrô Santa Cruz . + + +
+ +
diff --git a/content/events/2010-europe/conduct.md b/content/events/2010-europe/conduct.md new file mode 100644 index 00000000000..d1038fb1dc3 --- /dev/null +++ b/content/events/2010-europe/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:42:53-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/2010-europe/contact.md b/content/events/2010-europe/contact.md new file mode 100644 index 00000000000..b2e0d0a5a21 --- /dev/null +++ b/content/events/2010-europe/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:42:53-05: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 >}} diff --git a/content/events/2010-europe/location.md b/content/events/2010-europe/location.md new file mode 100644 index 00000000000..bc3027656cb --- /dev/null +++ b/content/events/2010-europe/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2010-europe/program.md b/content/events/2010-europe/program.md new file mode 100644 index 00000000000..627f0709e5b --- /dev/null +++ b/content/events/2010-europe/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2010-europe/propose.md b/content/events/2010-europe/propose.md new file mode 100644 index 00000000000..c246db3da08 --- /dev/null +++ b/content/events/2010-europe/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2010-europe/registration.md b/content/events/2010-europe/registration.md new file mode 100644 index 00000000000..2f98b40e66e --- /dev/null +++ b/content/events/2010-europe/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2010-europe/sponsor.md b/content/events/2010-europe/sponsor.md new file mode 100644 index 00000000000..cfeb27e40e4 --- /dev/null +++ b/content/events/2010-europe/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:42:53-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/2010-europe/welcome.md b/content/events/2010-europe/welcome.md new file mode 100644 index 00000000000..324c6687a5e --- /dev/null +++ b/content/events/2010-europe/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2010-europe"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2010-sydney/conduct.md b/content/events/2010-sydney/conduct.md new file mode 100644 index 00000000000..3707c625d9f --- /dev/null +++ b/content/events/2010-sydney/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:42:19-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/2010-sydney/contact.md b/content/events/2010-sydney/contact.md new file mode 100644 index 00000000000..f94e779facd --- /dev/null +++ b/content/events/2010-sydney/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:42:19-05: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 >}} diff --git a/content/events/2010-sydney/location.md b/content/events/2010-sydney/location.md new file mode 100644 index 00000000000..721d5b4e93c --- /dev/null +++ b/content/events/2010-sydney/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:42:19-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2010-sydney/program.md b/content/events/2010-sydney/program.md new file mode 100644 index 00000000000..38446549b80 --- /dev/null +++ b/content/events/2010-sydney/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:42:19-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2010-sydney/propose.md b/content/events/2010-sydney/propose.md new file mode 100644 index 00000000000..c3d3d9069e5 --- /dev/null +++ b/content/events/2010-sydney/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:42:19-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2010-sydney/registration.md b/content/events/2010-sydney/registration.md new file mode 100644 index 00000000000..6f2be2bb63e --- /dev/null +++ b/content/events/2010-sydney/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:42:19-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2010-sydney/sponsor.md b/content/events/2010-sydney/sponsor.md new file mode 100644 index 00000000000..1897600b1be --- /dev/null +++ b/content/events/2010-sydney/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:42:19-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/2010-sydney/welcome.md b/content/events/2010-sydney/welcome.md new file mode 100644 index 00000000000..e0c7480ddee --- /dev/null +++ b/content/events/2010-sydney/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:42:19-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2010-sydney"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2010-us/conduct.md b/content/events/2010-us/conduct.md new file mode 100644 index 00000000000..2350160a609 --- /dev/null +++ b/content/events/2010-us/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:40:32-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/2010-us/contact.md b/content/events/2010-us/contact.md new file mode 100644 index 00000000000..069d9b4c492 --- /dev/null +++ b/content/events/2010-us/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:40:32-05: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 >}} diff --git a/content/events/2010-us/location.md b/content/events/2010-us/location.md new file mode 100644 index 00000000000..ab8c50e823e --- /dev/null +++ b/content/events/2010-us/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:40:32-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2010-us/program.md b/content/events/2010-us/program.md new file mode 100644 index 00000000000..d2025f5e17d --- /dev/null +++ b/content/events/2010-us/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:40:32-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2010-us/propose.md b/content/events/2010-us/propose.md new file mode 100644 index 00000000000..09920c135ae --- /dev/null +++ b/content/events/2010-us/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:40:32-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2010-us/registration.md b/content/events/2010-us/registration.md new file mode 100644 index 00000000000..3afa0535d5d --- /dev/null +++ b/content/events/2010-us/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:40:32-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2010-us/sponsor.md b/content/events/2010-us/sponsor.md new file mode 100644 index 00000000000..91c3365c9db --- /dev/null +++ b/content/events/2010-us/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:40:32-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/2010-us/welcome.md b/content/events/2010-us/welcome.md new file mode 100644 index 00000000000..01dbabe462a --- /dev/null +++ b/content/events/2010-us/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:40:32-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2010-us"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2011-bangalore/conduct.md b/content/events/2011-bangalore/conduct.md new file mode 100644 index 00000000000..d774fd207fc --- /dev/null +++ b/content/events/2011-bangalore/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:49:39-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/2011-bangalore/contact.md b/content/events/2011-bangalore/contact.md new file mode 100644 index 00000000000..05e74bc03cf --- /dev/null +++ b/content/events/2011-bangalore/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:49:39-05: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 >}} diff --git a/content/events/2011-bangalore/location.md b/content/events/2011-bangalore/location.md new file mode 100644 index 00000000000..0f5773e5650 --- /dev/null +++ b/content/events/2011-bangalore/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:49:39-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2011-bangalore/program.md b/content/events/2011-bangalore/program.md new file mode 100644 index 00000000000..16fa3e06f31 --- /dev/null +++ b/content/events/2011-bangalore/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:49:39-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2011-bangalore/propose.md b/content/events/2011-bangalore/propose.md new file mode 100644 index 00000000000..7bfe8cbadca --- /dev/null +++ b/content/events/2011-bangalore/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:49:39-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2011-bangalore/registration.md b/content/events/2011-bangalore/registration.md new file mode 100644 index 00000000000..2867f102044 --- /dev/null +++ b/content/events/2011-bangalore/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:49:39-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2011-bangalore/sponsor.md b/content/events/2011-bangalore/sponsor.md new file mode 100644 index 00000000000..8681d23bb9e --- /dev/null +++ b/content/events/2011-bangalore/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:49:39-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/2011-bangalore/welcome.md b/content/events/2011-bangalore/welcome.md new file mode 100644 index 00000000000..53dd4c33a67 --- /dev/null +++ b/content/events/2011-bangalore/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:49:39-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2011-bangalore"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2011-boston/conduct.md b/content/events/2011-boston/conduct.md new file mode 100644 index 00000000000..ae0ae9eeb37 --- /dev/null +++ b/content/events/2011-boston/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:47:46-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/2011-boston/contact.md b/content/events/2011-boston/contact.md new file mode 100644 index 00000000000..f54634af0e8 --- /dev/null +++ b/content/events/2011-boston/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:47:46-05: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 >}} diff --git a/content/events/2011-boston/location.md b/content/events/2011-boston/location.md new file mode 100644 index 00000000000..a1aadb1ee3c --- /dev/null +++ b/content/events/2011-boston/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:47:46-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2011-boston/program.md b/content/events/2011-boston/program.md new file mode 100644 index 00000000000..aed14ef93f9 --- /dev/null +++ b/content/events/2011-boston/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:47:46-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2011-boston/propose.md b/content/events/2011-boston/propose.md new file mode 100644 index 00000000000..6d58a54954b --- /dev/null +++ b/content/events/2011-boston/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:47:46-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2011-boston/registration.md b/content/events/2011-boston/registration.md new file mode 100644 index 00000000000..818f3a9a1fd --- /dev/null +++ b/content/events/2011-boston/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:47:46-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2011-boston/sponsor.md b/content/events/2011-boston/sponsor.md new file mode 100644 index 00000000000..53d66643ac4 --- /dev/null +++ b/content/events/2011-boston/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:47:46-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/2011-boston/welcome.md b/content/events/2011-boston/welcome.md new file mode 100644 index 00000000000..100c4fdd4d5 --- /dev/null +++ b/content/events/2011-boston/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:47:46-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2011-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 >}} +
diff --git a/content/events/2011-goteborg/conduct.md b/content/events/2011-goteborg/conduct.md new file mode 100644 index 00000000000..6e0afa47ec9 --- /dev/null +++ b/content/events/2011-goteborg/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:49:55-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/2011-goteborg/contact.md b/content/events/2011-goteborg/contact.md new file mode 100644 index 00000000000..f68d5d9c5c6 --- /dev/null +++ b/content/events/2011-goteborg/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:49:55-05: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 >}} diff --git a/content/events/2011-goteborg/location.md b/content/events/2011-goteborg/location.md new file mode 100644 index 00000000000..86e4b3a6305 --- /dev/null +++ b/content/events/2011-goteborg/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:49:55-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2011-goteborg/program.md b/content/events/2011-goteborg/program.md new file mode 100644 index 00000000000..3a4e7e64d1c --- /dev/null +++ b/content/events/2011-goteborg/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:49:55-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2011-goteborg/propose.md b/content/events/2011-goteborg/propose.md new file mode 100644 index 00000000000..001c17356b0 --- /dev/null +++ b/content/events/2011-goteborg/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:49:55-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2011-goteborg/registration.md b/content/events/2011-goteborg/registration.md new file mode 100644 index 00000000000..dd3a4bb28ec --- /dev/null +++ b/content/events/2011-goteborg/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:49:55-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2011-goteborg/sponsor.md b/content/events/2011-goteborg/sponsor.md new file mode 100644 index 00000000000..ea21cdf4956 --- /dev/null +++ b/content/events/2011-goteborg/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:49:55-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/2011-goteborg/welcome.md b/content/events/2011-goteborg/welcome.md new file mode 100644 index 00000000000..9c5ac03cd17 --- /dev/null +++ b/content/events/2011-goteborg/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:49:55-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2011-goteborg"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2011-manila/conduct.md b/content/events/2011-manila/conduct.md new file mode 100644 index 00000000000..366ee0068cf --- /dev/null +++ b/content/events/2011-manila/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:50:20-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/2011-manila/contact.md b/content/events/2011-manila/contact.md new file mode 100644 index 00000000000..57598bb26f6 --- /dev/null +++ b/content/events/2011-manila/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:50:20-05: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 >}} diff --git a/content/events/2011-manila/location.md b/content/events/2011-manila/location.md new file mode 100644 index 00000000000..e628dac1c10 --- /dev/null +++ b/content/events/2011-manila/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:50:20-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2011-manila/program.md b/content/events/2011-manila/program.md new file mode 100644 index 00000000000..8ee98e5405f --- /dev/null +++ b/content/events/2011-manila/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:50:20-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2011-manila/propose.md b/content/events/2011-manila/propose.md new file mode 100644 index 00000000000..3bc48ec61d3 --- /dev/null +++ b/content/events/2011-manila/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:50:20-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2011-manila/registration.md b/content/events/2011-manila/registration.md new file mode 100644 index 00000000000..55034cc7422 --- /dev/null +++ b/content/events/2011-manila/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:50:20-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2011-manila/sponsor.md b/content/events/2011-manila/sponsor.md new file mode 100644 index 00000000000..d20d4c57baa --- /dev/null +++ b/content/events/2011-manila/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:50:20-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/2011-manila/welcome.md b/content/events/2011-manila/welcome.md new file mode 100644 index 00000000000..c0fc004566d --- /dev/null +++ b/content/events/2011-manila/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:50:20-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2011-manila"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2011-melbourne/conduct.md b/content/events/2011-melbourne/conduct.md new file mode 100644 index 00000000000..ff412f45716 --- /dev/null +++ b/content/events/2011-melbourne/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:49:31-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/2011-melbourne/contact.md b/content/events/2011-melbourne/contact.md new file mode 100644 index 00000000000..4a660b61189 --- /dev/null +++ b/content/events/2011-melbourne/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:49:31-05: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 >}} diff --git a/content/events/2011-melbourne/location.md b/content/events/2011-melbourne/location.md new file mode 100644 index 00000000000..8d9e79d948c --- /dev/null +++ b/content/events/2011-melbourne/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:49:31-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2011-melbourne/program.md b/content/events/2011-melbourne/program.md new file mode 100644 index 00000000000..967e8f22f6a --- /dev/null +++ b/content/events/2011-melbourne/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:49:31-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2011-melbourne/propose.md b/content/events/2011-melbourne/propose.md new file mode 100644 index 00000000000..205ebab5589 --- /dev/null +++ b/content/events/2011-melbourne/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:49:31-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2011-melbourne/registration.md b/content/events/2011-melbourne/registration.md new file mode 100644 index 00000000000..6d4b41f7170 --- /dev/null +++ b/content/events/2011-melbourne/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:49:31-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2011-melbourne/sponsor.md b/content/events/2011-melbourne/sponsor.md new file mode 100644 index 00000000000..8abb715bf76 --- /dev/null +++ b/content/events/2011-melbourne/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:49:31-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/2011-melbourne/welcome.md b/content/events/2011-melbourne/welcome.md new file mode 100644 index 00000000000..bbe8e7fb912 --- /dev/null +++ b/content/events/2011-melbourne/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:49:31-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2011-melbourne"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2011-mountainview/conduct.md b/content/events/2011-mountainview/conduct.md new file mode 100644 index 00000000000..9276526a921 --- /dev/null +++ b/content/events/2011-mountainview/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:49:15-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/2011-mountainview/contact.md b/content/events/2011-mountainview/contact.md new file mode 100644 index 00000000000..5e5129b40c6 --- /dev/null +++ b/content/events/2011-mountainview/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:49:15-05: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 >}} diff --git a/content/events/2011-mountainview/location.md b/content/events/2011-mountainview/location.md new file mode 100644 index 00000000000..3de326e6e15 --- /dev/null +++ b/content/events/2011-mountainview/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:49:15-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2011-mountainview/program.md b/content/events/2011-mountainview/program.md new file mode 100644 index 00000000000..f05b0908af0 --- /dev/null +++ b/content/events/2011-mountainview/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:49:15-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2011-mountainview/propose.md b/content/events/2011-mountainview/propose.md new file mode 100644 index 00000000000..3bcb15e7e7d --- /dev/null +++ b/content/events/2011-mountainview/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:49:15-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2011-mountainview/registration.md b/content/events/2011-mountainview/registration.md new file mode 100644 index 00000000000..3755920c378 --- /dev/null +++ b/content/events/2011-mountainview/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:49:15-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2011-mountainview/sponsor.md b/content/events/2011-mountainview/sponsor.md new file mode 100644 index 00000000000..24cdd45e423 --- /dev/null +++ b/content/events/2011-mountainview/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:49:15-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/2011-mountainview/welcome.md b/content/events/2011-mountainview/welcome.md new file mode 100644 index 00000000000..396407bbc96 --- /dev/null +++ b/content/events/2011-mountainview/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:49:15-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2011-mountainview"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2012-austin/conduct.md b/content/events/2012-austin/conduct.md new file mode 100644 index 00000000000..87cfad61628 --- /dev/null +++ b/content/events/2012-austin/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:50:29-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/2012-austin/contact.md b/content/events/2012-austin/contact.md new file mode 100644 index 00000000000..0777ba107b3 --- /dev/null +++ b/content/events/2012-austin/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:50:29-05: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 >}} diff --git a/content/events/2012-austin/location.md b/content/events/2012-austin/location.md new file mode 100644 index 00000000000..19c68631ad2 --- /dev/null +++ b/content/events/2012-austin/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:50:29-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2012-austin/program.md b/content/events/2012-austin/program.md new file mode 100644 index 00000000000..82b4e406404 --- /dev/null +++ b/content/events/2012-austin/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:50:29-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2012-austin/propose.md b/content/events/2012-austin/propose.md new file mode 100644 index 00000000000..4cc2ef04173 --- /dev/null +++ b/content/events/2012-austin/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:50:29-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2012-austin/registration.md b/content/events/2012-austin/registration.md new file mode 100644 index 00000000000..f8fe70e6704 --- /dev/null +++ b/content/events/2012-austin/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:50:29-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2012-austin/sponsor.md b/content/events/2012-austin/sponsor.md new file mode 100644 index 00000000000..4a21dce64f3 --- /dev/null +++ b/content/events/2012-austin/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:50:29-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/2012-austin/welcome.md b/content/events/2012-austin/welcome.md new file mode 100644 index 00000000000..7f16260db94 --- /dev/null +++ b/content/events/2012-austin/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:50:29-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2012-austin"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2012-india/sample-event/conduct.md b/content/events/2012-india/sample-event/conduct.md new file mode 100644 index 00000000000..41689ed7809 --- /dev/null +++ b/content/events/2012-india/sample-event/conduct.md @@ -0,0 +1,37 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "conduct" +type = "event" +draft = true + ++++ + +## 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/2012-india/sample-event/contact.md b/content/events/2012-india/sample-event/contact.md new file mode 100644 index 00000000000..d6fc715f175 --- /dev/null +++ b/content/events/2012-india/sample-event/contact.md @@ -0,0 +1,18 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "contact" +type = "event" +draft = true + + ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + +**The core devopsdays organizer group** + +{{< list_core >}} diff --git a/content/events/2012-india/sample-event/location.md b/content/events/2012-india/sample-event/location.md new file mode 100644 index 00000000000..1533593efe4 --- /dev/null +++ b/content/events/2012-india/sample-event/location.md @@ -0,0 +1,11 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "location" +type = "event" +draft = true + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2012-india/sample-event/program.md b/content/events/2012-india/sample-event/program.md new file mode 100644 index 00000000000..4e39e69b951 --- /dev/null +++ b/content/events/2012-india/sample-event/program.md @@ -0,0 +1,123 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "program" +type = "event" +draft = true + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2012-india/sample-event/propose.md b/content/events/2012-india/sample-event/propose.md new file mode 100644 index 00000000000..ba528d96ed6 --- /dev/null +++ b/content/events/2012-india/sample-event/propose.md @@ -0,0 +1,38 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "propose" +type = "event" +draft = true ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2012-india/sample-event/registration.md b/content/events/2012-india/sample-event/registration.md new file mode 100644 index 00000000000..9e12f87a388 --- /dev/null +++ b/content/events/2012-india/sample-event/registration.md @@ -0,0 +1,14 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "registration" +type = "event" +draft = true + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2012-india/sample-event/sponsor.md b/content/events/2012-india/sample-event/sponsor.md new file mode 100644 index 00000000000..91398b5b367 --- /dev/null +++ b/content/events/2012-india/sample-event/sponsor.md @@ -0,0 +1,50 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "sponsor" +type = "event" +draft = true + + ++++ + +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/2012-india/sample-event/welcome.md b/content/events/2012-india/sample-event/welcome.md new file mode 100644 index 00000000000..913384cea7b --- /dev/null +++ b/content/events/2012-india/sample-event/welcome.md @@ -0,0 +1,53 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "welcome" +type = "event" +aliases = ["/events/YYYY-city"] +draft = true + ++++ + +## {{< 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 devopsdaysyourtown >}} +
diff --git a/content/events/2012-italy/conduct.md b/content/events/2012-italy/conduct.md new file mode 100644 index 00000000000..56af46bf9b0 --- /dev/null +++ b/content/events/2012-italy/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:51:41-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/2012-italy/contact.md b/content/events/2012-italy/contact.md new file mode 100644 index 00000000000..fd97f2fe1c7 --- /dev/null +++ b/content/events/2012-italy/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:51:41-05: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 >}} diff --git a/content/events/2012-italy/location.md b/content/events/2012-italy/location.md new file mode 100644 index 00000000000..f136e544a53 --- /dev/null +++ b/content/events/2012-italy/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:51:41-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2012-italy/program.md b/content/events/2012-italy/program.md new file mode 100644 index 00000000000..32f535d83e9 --- /dev/null +++ b/content/events/2012-italy/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:51:41-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2012-italy/propose.md b/content/events/2012-italy/propose.md new file mode 100644 index 00000000000..93582594b1c --- /dev/null +++ b/content/events/2012-italy/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:51:41-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2012-italy/registration.md b/content/events/2012-italy/registration.md new file mode 100644 index 00000000000..5561fec5f78 --- /dev/null +++ b/content/events/2012-italy/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:51:41-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2012-italy/sponsor.md b/content/events/2012-italy/sponsor.md new file mode 100644 index 00000000000..7dee87663ad --- /dev/null +++ b/content/events/2012-italy/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:51:41-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/2012-italy/welcome.md b/content/events/2012-italy/welcome.md new file mode 100644 index 00000000000..f3542e37e1d --- /dev/null +++ b/content/events/2012-italy/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:51:41-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2012-italy"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2012-mountainview/conduct.md b/content/events/2012-mountainview/conduct.md new file mode 100644 index 00000000000..809a6307789 --- /dev/null +++ b/content/events/2012-mountainview/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:51:27-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/2012-mountainview/contact.md b/content/events/2012-mountainview/contact.md new file mode 100644 index 00000000000..5d03301e35f --- /dev/null +++ b/content/events/2012-mountainview/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:51:27-05: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 >}} diff --git a/content/events/2012-mountainview/location.md b/content/events/2012-mountainview/location.md new file mode 100644 index 00000000000..44b458e54fc --- /dev/null +++ b/content/events/2012-mountainview/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:51:27-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2012-mountainview/program.md b/content/events/2012-mountainview/program.md new file mode 100644 index 00000000000..dd3a9a97318 --- /dev/null +++ b/content/events/2012-mountainview/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:51:27-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2012-mountainview/propose.md b/content/events/2012-mountainview/propose.md new file mode 100644 index 00000000000..8b13abf0a38 --- /dev/null +++ b/content/events/2012-mountainview/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:51:27-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2012-mountainview/registration.md b/content/events/2012-mountainview/registration.md new file mode 100644 index 00000000000..ceb9ffa555c --- /dev/null +++ b/content/events/2012-mountainview/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:51:27-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2012-mountainview/sponsor.md b/content/events/2012-mountainview/sponsor.md new file mode 100644 index 00000000000..e2b0c9b89a3 --- /dev/null +++ b/content/events/2012-mountainview/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:51:27-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/2012-mountainview/welcome.md b/content/events/2012-mountainview/welcome.md new file mode 100644 index 00000000000..a50225cce78 --- /dev/null +++ b/content/events/2012-mountainview/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:51:27-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2012-mountainview"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2012-newyork/conduct.md b/content/events/2012-newyork/conduct.md new file mode 100644 index 00000000000..2fbb8d23dc5 --- /dev/null +++ b/content/events/2012-newyork/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:52:27-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/2012-newyork/contact.md b/content/events/2012-newyork/contact.md new file mode 100644 index 00000000000..e87e185dece --- /dev/null +++ b/content/events/2012-newyork/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:52:27-05: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 >}} diff --git a/content/events/2012-newyork/location.md b/content/events/2012-newyork/location.md new file mode 100644 index 00000000000..a389094dbfd --- /dev/null +++ b/content/events/2012-newyork/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:52:27-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2012-newyork/program.md b/content/events/2012-newyork/program.md new file mode 100644 index 00000000000..9ad1dc31543 --- /dev/null +++ b/content/events/2012-newyork/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:52:27-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2012-newyork/propose.md b/content/events/2012-newyork/propose.md new file mode 100644 index 00000000000..ca088de1476 --- /dev/null +++ b/content/events/2012-newyork/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:52:27-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2012-newyork/registration.md b/content/events/2012-newyork/registration.md new file mode 100644 index 00000000000..27dd12d54ea --- /dev/null +++ b/content/events/2012-newyork/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:52:27-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2012-newyork/sponsor.md b/content/events/2012-newyork/sponsor.md new file mode 100644 index 00000000000..f6d0f0c2f90 --- /dev/null +++ b/content/events/2012-newyork/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:52:27-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/2012-newyork/welcome.md b/content/events/2012-newyork/welcome.md new file mode 100644 index 00000000000..597f26f37d3 --- /dev/null +++ b/content/events/2012-newyork/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:52:27-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2012-newyork"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2012-tokyo/conduct.md b/content/events/2012-tokyo/conduct.md new file mode 100644 index 00000000000..7c6ec0f7c64 --- /dev/null +++ b/content/events/2012-tokyo/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:50:52-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/2012-tokyo/contact.md b/content/events/2012-tokyo/contact.md new file mode 100644 index 00000000000..b9105a1c90f --- /dev/null +++ b/content/events/2012-tokyo/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:50:52-05: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 >}} diff --git a/content/events/2012-tokyo/location.md b/content/events/2012-tokyo/location.md new file mode 100644 index 00000000000..8f00f7713fd --- /dev/null +++ b/content/events/2012-tokyo/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:50:52-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2012-tokyo/program.md b/content/events/2012-tokyo/program.md new file mode 100644 index 00000000000..cc1b6457f11 --- /dev/null +++ b/content/events/2012-tokyo/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:50:52-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2012-tokyo/propose.md b/content/events/2012-tokyo/propose.md new file mode 100644 index 00000000000..7edffa37b16 --- /dev/null +++ b/content/events/2012-tokyo/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:50:52-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2012-tokyo/registration.md b/content/events/2012-tokyo/registration.md new file mode 100644 index 00000000000..84f54230dda --- /dev/null +++ b/content/events/2012-tokyo/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:50:52-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2012-tokyo/sponsor.md b/content/events/2012-tokyo/sponsor.md new file mode 100644 index 00000000000..384a47df751 --- /dev/null +++ b/content/events/2012-tokyo/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:50:52-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/2012-tokyo/welcome.md b/content/events/2012-tokyo/welcome.md new file mode 100644 index 00000000000..4579da00598 --- /dev/null +++ b/content/events/2012-tokyo/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:50:52-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2012-tokyo"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-amsterdam/conduct.md b/content/events/2013-amsterdam/conduct.md new file mode 100644 index 00000000000..4afdc5b0a59 --- /dev/null +++ b/content/events/2013-amsterdam/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:54: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/2013-amsterdam/contact.md b/content/events/2013-amsterdam/contact.md new file mode 100644 index 00000000000..ed2dd534fca --- /dev/null +++ b/content/events/2013-amsterdam/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:54:57-05: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 >}} diff --git a/content/events/2013-amsterdam/location.md b/content/events/2013-amsterdam/location.md new file mode 100644 index 00000000000..08a89da68aa --- /dev/null +++ b/content/events/2013-amsterdam/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:54:57-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-amsterdam/program.md b/content/events/2013-amsterdam/program.md new file mode 100644 index 00000000000..77856381d46 --- /dev/null +++ b/content/events/2013-amsterdam/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:54:57-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-amsterdam/propose.md b/content/events/2013-amsterdam/propose.md new file mode 100644 index 00000000000..25c552f5e90 --- /dev/null +++ b/content/events/2013-amsterdam/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:54:57-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-amsterdam/registration.md b/content/events/2013-amsterdam/registration.md new file mode 100644 index 00000000000..791347f9ac7 --- /dev/null +++ b/content/events/2013-amsterdam/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:54:57-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-amsterdam/sponsor.md b/content/events/2013-amsterdam/sponsor.md new file mode 100644 index 00000000000..d50ee6f03f6 --- /dev/null +++ b/content/events/2013-amsterdam/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:54: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/2013-amsterdam/welcome.md b/content/events/2013-amsterdam/welcome.md new file mode 100644 index 00000000000..3ae26f908d3 --- /dev/null +++ b/content/events/2013-amsterdam/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:54:57-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-amsterdam"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-atlanta/conduct.md b/content/events/2013-atlanta/conduct.md new file mode 100644 index 00000000000..6094dc9d7b9 --- /dev/null +++ b/content/events/2013-atlanta/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:58:06-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/2013-atlanta/contact.md b/content/events/2013-atlanta/contact.md new file mode 100644 index 00000000000..f80a37e99e9 --- /dev/null +++ b/content/events/2013-atlanta/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:58:06-05: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 >}} diff --git a/content/events/2013-atlanta/location.md b/content/events/2013-atlanta/location.md new file mode 100644 index 00000000000..6834d7b0b21 --- /dev/null +++ b/content/events/2013-atlanta/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:58:06-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-atlanta/program.md b/content/events/2013-atlanta/program.md new file mode 100644 index 00000000000..a3fa0365d59 --- /dev/null +++ b/content/events/2013-atlanta/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:58:06-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-atlanta/propose.md b/content/events/2013-atlanta/propose.md new file mode 100644 index 00000000000..1e13d659797 --- /dev/null +++ b/content/events/2013-atlanta/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:58:06-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-atlanta/registration.md b/content/events/2013-atlanta/registration.md new file mode 100644 index 00000000000..64ef9f2df36 --- /dev/null +++ b/content/events/2013-atlanta/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:58:06-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-atlanta/sponsor.md b/content/events/2013-atlanta/sponsor.md new file mode 100644 index 00000000000..fe4e6705e3a --- /dev/null +++ b/content/events/2013-atlanta/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:58:06-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/2013-atlanta/welcome.md b/content/events/2013-atlanta/welcome.md new file mode 100644 index 00000000000..82c5e80a57f --- /dev/null +++ b/content/events/2013-atlanta/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:58:06-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-atlanta"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-austin/conduct.md b/content/events/2013-austin/conduct.md new file mode 100644 index 00000000000..f49182a7a7f --- /dev/null +++ b/content/events/2013-austin/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:54:43-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/2013-austin/contact.md b/content/events/2013-austin/contact.md new file mode 100644 index 00000000000..dea5d07af78 --- /dev/null +++ b/content/events/2013-austin/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:54:43-05: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 >}} diff --git a/content/events/2013-austin/location.md b/content/events/2013-austin/location.md new file mode 100644 index 00000000000..205b0eb06a8 --- /dev/null +++ b/content/events/2013-austin/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:54:43-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-austin/program.md b/content/events/2013-austin/program.md new file mode 100644 index 00000000000..55051dfdc18 --- /dev/null +++ b/content/events/2013-austin/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:54:43-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-austin/propose.md b/content/events/2013-austin/propose.md new file mode 100644 index 00000000000..8e649132282 --- /dev/null +++ b/content/events/2013-austin/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:54:43-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-austin/registration.md b/content/events/2013-austin/registration.md new file mode 100644 index 00000000000..7f0112103a9 --- /dev/null +++ b/content/events/2013-austin/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:54:43-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-austin/sponsor.md b/content/events/2013-austin/sponsor.md new file mode 100644 index 00000000000..a08f55fc450 --- /dev/null +++ b/content/events/2013-austin/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:54:43-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/2013-austin/welcome.md b/content/events/2013-austin/welcome.md new file mode 100644 index 00000000000..21d9dc24507 --- /dev/null +++ b/content/events/2013-austin/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:54:43-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-austin"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-barcelona/conduct.md b/content/events/2013-barcelona/conduct.md new file mode 100644 index 00000000000..c0117a69e7b --- /dev/null +++ b/content/events/2013-barcelona/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:57:20-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/2013-barcelona/contact.md b/content/events/2013-barcelona/contact.md new file mode 100644 index 00000000000..60d30706f03 --- /dev/null +++ b/content/events/2013-barcelona/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:57:20-05: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 >}} diff --git a/content/events/2013-barcelona/location.md b/content/events/2013-barcelona/location.md new file mode 100644 index 00000000000..98ddabd83a9 --- /dev/null +++ b/content/events/2013-barcelona/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:57:20-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-barcelona/program.md b/content/events/2013-barcelona/program.md new file mode 100644 index 00000000000..7eb9991a358 --- /dev/null +++ b/content/events/2013-barcelona/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:57:20-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-barcelona/propose.md b/content/events/2013-barcelona/propose.md new file mode 100644 index 00000000000..33e918d3e9f --- /dev/null +++ b/content/events/2013-barcelona/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:57:20-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-barcelona/registration.md b/content/events/2013-barcelona/registration.md new file mode 100644 index 00000000000..7f16b384d43 --- /dev/null +++ b/content/events/2013-barcelona/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:57:20-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-barcelona/sponsor.md b/content/events/2013-barcelona/sponsor.md new file mode 100644 index 00000000000..ba4390748a2 --- /dev/null +++ b/content/events/2013-barcelona/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:57:20-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/2013-barcelona/welcome.md b/content/events/2013-barcelona/welcome.md new file mode 100644 index 00000000000..1c273d77f17 --- /dev/null +++ b/content/events/2013-barcelona/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:57:20-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-barcelona"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-berlin/conduct.md b/content/events/2013-berlin/conduct.md new file mode 100644 index 00000000000..0903dc17bcb --- /dev/null +++ b/content/events/2013-berlin/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:54:50-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/2013-berlin/contact.md b/content/events/2013-berlin/contact.md new file mode 100644 index 00000000000..ec5ec4e628b --- /dev/null +++ b/content/events/2013-berlin/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:54:50-05: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 >}} diff --git a/content/events/2013-berlin/location.md b/content/events/2013-berlin/location.md new file mode 100644 index 00000000000..c84fba1478f --- /dev/null +++ b/content/events/2013-berlin/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:54:50-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-berlin/program.md b/content/events/2013-berlin/program.md new file mode 100644 index 00000000000..d41218ea2d8 --- /dev/null +++ b/content/events/2013-berlin/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:54:50-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-berlin/propose.md b/content/events/2013-berlin/propose.md new file mode 100644 index 00000000000..3a5c1a51c8c --- /dev/null +++ b/content/events/2013-berlin/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:54:50-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-berlin/registration.md b/content/events/2013-berlin/registration.md new file mode 100644 index 00000000000..c0633994b52 --- /dev/null +++ b/content/events/2013-berlin/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:54:50-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-berlin/sponsor.md b/content/events/2013-berlin/sponsor.md new file mode 100644 index 00000000000..1eab2c83222 --- /dev/null +++ b/content/events/2013-berlin/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:54:50-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/2013-berlin/welcome.md b/content/events/2013-berlin/welcome.md new file mode 100644 index 00000000000..d4dbdd075ff --- /dev/null +++ b/content/events/2013-berlin/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:54:50-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-berlin"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-downunder/conduct.md b/content/events/2013-downunder/conduct.md new file mode 100644 index 00000000000..74ef31921ca --- /dev/null +++ b/content/events/2013-downunder/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:55:49-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/2013-downunder/contact.md b/content/events/2013-downunder/contact.md new file mode 100644 index 00000000000..be53899b5a4 --- /dev/null +++ b/content/events/2013-downunder/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:55:49-05: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 >}} diff --git a/content/events/2013-downunder/location.md b/content/events/2013-downunder/location.md new file mode 100644 index 00000000000..35504d0d3bd --- /dev/null +++ b/content/events/2013-downunder/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:55:49-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-downunder/program.md b/content/events/2013-downunder/program.md new file mode 100644 index 00000000000..00d3f0db7ae --- /dev/null +++ b/content/events/2013-downunder/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:55:49-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-downunder/propose.md b/content/events/2013-downunder/propose.md new file mode 100644 index 00000000000..5e872b0b8aa --- /dev/null +++ b/content/events/2013-downunder/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:55:49-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-downunder/registration.md b/content/events/2013-downunder/registration.md new file mode 100644 index 00000000000..212217034b1 --- /dev/null +++ b/content/events/2013-downunder/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:55:49-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-downunder/sponsor.md b/content/events/2013-downunder/sponsor.md new file mode 100644 index 00000000000..fe4a74f3544 --- /dev/null +++ b/content/events/2013-downunder/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:55:49-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/2013-downunder/welcome.md b/content/events/2013-downunder/welcome.md new file mode 100644 index 00000000000..b6bed449c8b --- /dev/null +++ b/content/events/2013-downunder/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:55:49-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-downunder"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-india/conduct.md b/content/events/2013-india/conduct.md new file mode 100644 index 00000000000..b48d6c267d2 --- /dev/null +++ b/content/events/2013-india/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:56:18-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/2013-india/contact.md b/content/events/2013-india/contact.md new file mode 100644 index 00000000000..afaeed7ce67 --- /dev/null +++ b/content/events/2013-india/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:56:18-05: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 >}} diff --git a/content/events/2013-india/location.md b/content/events/2013-india/location.md new file mode 100644 index 00000000000..d1a3a745e96 --- /dev/null +++ b/content/events/2013-india/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:56:18-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-india/program.md b/content/events/2013-india/program.md new file mode 100644 index 00000000000..1e8ed279170 --- /dev/null +++ b/content/events/2013-india/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:56:18-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-india/propose.md b/content/events/2013-india/propose.md new file mode 100644 index 00000000000..de097956434 --- /dev/null +++ b/content/events/2013-india/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:56:18-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-india/registration.md b/content/events/2013-india/registration.md new file mode 100644 index 00000000000..ef3456d648a --- /dev/null +++ b/content/events/2013-india/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:56:18-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-india/sponsor.md b/content/events/2013-india/sponsor.md new file mode 100644 index 00000000000..dae8b56e097 --- /dev/null +++ b/content/events/2013-india/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:56:18-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/2013-india/welcome.md b/content/events/2013-india/welcome.md new file mode 100644 index 00000000000..2f8e90a713b --- /dev/null +++ b/content/events/2013-india/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:56:18-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-india"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-london-spring/conduct.md b/content/events/2013-london-spring/conduct.md new file mode 100644 index 00000000000..b0335faea81 --- /dev/null +++ b/content/events/2013-london-spring/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:52: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/2013-london-spring/contact.md b/content/events/2013-london-spring/contact.md new file mode 100644 index 00000000000..4144b7ae78b --- /dev/null +++ b/content/events/2013-london-spring/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:52:57-05: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 >}} diff --git a/content/events/2013-london-spring/location.md b/content/events/2013-london-spring/location.md new file mode 100644 index 00000000000..23ce6d27858 --- /dev/null +++ b/content/events/2013-london-spring/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:52:57-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-london-spring/program.md b/content/events/2013-london-spring/program.md new file mode 100644 index 00000000000..182341ff46d --- /dev/null +++ b/content/events/2013-london-spring/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:52:57-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-london-spring/propose.md b/content/events/2013-london-spring/propose.md new file mode 100644 index 00000000000..aadf107d863 --- /dev/null +++ b/content/events/2013-london-spring/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:52:57-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-london-spring/registration.md b/content/events/2013-london-spring/registration.md new file mode 100644 index 00000000000..718389f3c1d --- /dev/null +++ b/content/events/2013-london-spring/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:52:57-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-london-spring/sponsor.md b/content/events/2013-london-spring/sponsor.md new file mode 100644 index 00000000000..65ee50254b4 --- /dev/null +++ b/content/events/2013-london-spring/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:52: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/2013-london-spring/welcome.md b/content/events/2013-london-spring/welcome.md new file mode 100644 index 00000000000..03edeb367d0 --- /dev/null +++ b/content/events/2013-london-spring/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:52:57-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-london-spring"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-london/conduct.md b/content/events/2013-london/conduct.md new file mode 100644 index 00000000000..e872d8a1229 --- /dev/null +++ b/content/events/2013-london/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:56:54-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/2013-london/contact.md b/content/events/2013-london/contact.md new file mode 100644 index 00000000000..e9222e0309f --- /dev/null +++ b/content/events/2013-london/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:56:54-05: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 >}} diff --git a/content/events/2013-london/location.md b/content/events/2013-london/location.md new file mode 100644 index 00000000000..e4bfa6773bc --- /dev/null +++ b/content/events/2013-london/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:56:54-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-london/program.md b/content/events/2013-london/program.md new file mode 100644 index 00000000000..6524e91b8ab --- /dev/null +++ b/content/events/2013-london/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:56:54-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-london/propose.md b/content/events/2013-london/propose.md new file mode 100644 index 00000000000..65998ceaede --- /dev/null +++ b/content/events/2013-london/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:56:54-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-london/registration.md b/content/events/2013-london/registration.md new file mode 100644 index 00000000000..e0ed696507b --- /dev/null +++ b/content/events/2013-london/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:56:54-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-london/sponsor.md b/content/events/2013-london/sponsor.md new file mode 100644 index 00000000000..77b96ccbb0c --- /dev/null +++ b/content/events/2013-london/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:56:54-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/2013-london/welcome.md b/content/events/2013-london/welcome.md new file mode 100644 index 00000000000..798f0e93488 --- /dev/null +++ b/content/events/2013-london/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:56:54-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-london"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-mountainview/conduct.md b/content/events/2013-mountainview/conduct.md new file mode 100644 index 00000000000..7a083d88657 --- /dev/null +++ b/content/events/2013-mountainview/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:55:05-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/2013-mountainview/contact.md b/content/events/2013-mountainview/contact.md new file mode 100644 index 00000000000..3cb84ee9879 --- /dev/null +++ b/content/events/2013-mountainview/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:55:05-05: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 >}} diff --git a/content/events/2013-mountainview/location.md b/content/events/2013-mountainview/location.md new file mode 100644 index 00000000000..e8d3b6122a7 --- /dev/null +++ b/content/events/2013-mountainview/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:55:05-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-mountainview/program.md b/content/events/2013-mountainview/program.md new file mode 100644 index 00000000000..2f7f8dd2fca --- /dev/null +++ b/content/events/2013-mountainview/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:55:05-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-mountainview/propose.md b/content/events/2013-mountainview/propose.md new file mode 100644 index 00000000000..c6fa09d5096 --- /dev/null +++ b/content/events/2013-mountainview/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:55:05-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-mountainview/registration.md b/content/events/2013-mountainview/registration.md new file mode 100644 index 00000000000..27eff6bf08f --- /dev/null +++ b/content/events/2013-mountainview/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:55:05-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-mountainview/sponsor.md b/content/events/2013-mountainview/sponsor.md new file mode 100644 index 00000000000..3de3bd80f38 --- /dev/null +++ b/content/events/2013-mountainview/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:55:05-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/2013-mountainview/welcome.md b/content/events/2013-mountainview/welcome.md new file mode 100644 index 00000000000..e7c983afb48 --- /dev/null +++ b/content/events/2013-mountainview/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:55:05-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-mountainview"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-newyork/conduct.md b/content/events/2013-newyork/conduct.md new file mode 100644 index 00000000000..ea46a85c291 --- /dev/null +++ b/content/events/2013-newyork/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:57:42-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/2013-newyork/contact.md b/content/events/2013-newyork/contact.md new file mode 100644 index 00000000000..ab3a3d750a9 --- /dev/null +++ b/content/events/2013-newyork/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:57:42-05: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 >}} diff --git a/content/events/2013-newyork/location.md b/content/events/2013-newyork/location.md new file mode 100644 index 00000000000..43418a1aa65 --- /dev/null +++ b/content/events/2013-newyork/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:57:42-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-newyork/program.md b/content/events/2013-newyork/program.md new file mode 100644 index 00000000000..ec45ad86273 --- /dev/null +++ b/content/events/2013-newyork/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:57:42-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-newyork/propose.md b/content/events/2013-newyork/propose.md new file mode 100644 index 00000000000..8192a4155fb --- /dev/null +++ b/content/events/2013-newyork/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:57:42-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-newyork/registration.md b/content/events/2013-newyork/registration.md new file mode 100644 index 00000000000..60365bd8e1f --- /dev/null +++ b/content/events/2013-newyork/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:57:42-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-newyork/sponsor.md b/content/events/2013-newyork/sponsor.md new file mode 100644 index 00000000000..c9cce924fc5 --- /dev/null +++ b/content/events/2013-newyork/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:57:42-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/2013-newyork/welcome.md b/content/events/2013-newyork/welcome.md new file mode 100644 index 00000000000..f45456840ba --- /dev/null +++ b/content/events/2013-newyork/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:57:42-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-newyork"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-newzealand/conduct.md b/content/events/2013-newzealand/conduct.md new file mode 100644 index 00000000000..385367ac4e1 --- /dev/null +++ b/content/events/2013-newzealand/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:52:40-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/2013-newzealand/contact.md b/content/events/2013-newzealand/contact.md new file mode 100644 index 00000000000..7898e5c5899 --- /dev/null +++ b/content/events/2013-newzealand/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:52:40-05: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 >}} diff --git a/content/events/2013-newzealand/location.md b/content/events/2013-newzealand/location.md new file mode 100644 index 00000000000..8a55053c3ed --- /dev/null +++ b/content/events/2013-newzealand/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:52:40-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-newzealand/program.md b/content/events/2013-newzealand/program.md new file mode 100644 index 00000000000..76ca5dac112 --- /dev/null +++ b/content/events/2013-newzealand/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:52:40-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-newzealand/propose.md b/content/events/2013-newzealand/propose.md new file mode 100644 index 00000000000..d5fc86c3d3d --- /dev/null +++ b/content/events/2013-newzealand/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:52:40-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-newzealand/registration.md b/content/events/2013-newzealand/registration.md new file mode 100644 index 00000000000..b6054d404b8 --- /dev/null +++ b/content/events/2013-newzealand/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:52:40-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-newzealand/sponsor.md b/content/events/2013-newzealand/sponsor.md new file mode 100644 index 00000000000..e11675e557d --- /dev/null +++ b/content/events/2013-newzealand/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:52:40-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/2013-newzealand/welcome.md b/content/events/2013-newzealand/welcome.md new file mode 100644 index 00000000000..3c449f9efc4 --- /dev/null +++ b/content/events/2013-newzealand/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:52:40-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-newzealand"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-paris/conduct.md b/content/events/2013-paris/conduct.md new file mode 100644 index 00000000000..e2b65e0e455 --- /dev/null +++ b/content/events/2013-paris/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:54:35-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/2013-paris/contact.md b/content/events/2013-paris/contact.md new file mode 100644 index 00000000000..7d08e8c6a33 --- /dev/null +++ b/content/events/2013-paris/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:54:35-05: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 >}} diff --git a/content/events/2013-paris/location.md b/content/events/2013-paris/location.md new file mode 100644 index 00000000000..078a5463079 --- /dev/null +++ b/content/events/2013-paris/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:54:35-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-paris/program.md b/content/events/2013-paris/program.md new file mode 100644 index 00000000000..8e29ba3e95d --- /dev/null +++ b/content/events/2013-paris/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:54:35-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-paris/propose.md b/content/events/2013-paris/propose.md new file mode 100644 index 00000000000..38f6765b984 --- /dev/null +++ b/content/events/2013-paris/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:54:35-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-paris/registration.md b/content/events/2013-paris/registration.md new file mode 100644 index 00000000000..053c0e19bb4 --- /dev/null +++ b/content/events/2013-paris/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:54:35-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-paris/sponsor.md b/content/events/2013-paris/sponsor.md new file mode 100644 index 00000000000..64e95c4d0d1 --- /dev/null +++ b/content/events/2013-paris/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:54:35-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/2013-paris/welcome.md b/content/events/2013-paris/welcome.md new file mode 100644 index 00000000000..62a5f4ba803 --- /dev/null +++ b/content/events/2013-paris/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:54:35-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-paris"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-portland/conduct.md b/content/events/2013-portland/conduct.md new file mode 100644 index 00000000000..52d77147011 --- /dev/null +++ b/content/events/2013-portland/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:57:35-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/2013-portland/contact.md b/content/events/2013-portland/contact.md new file mode 100644 index 00000000000..dc84e0f9a08 --- /dev/null +++ b/content/events/2013-portland/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:57:35-05: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 >}} diff --git a/content/events/2013-portland/location.md b/content/events/2013-portland/location.md new file mode 100644 index 00000000000..3079b6008a1 --- /dev/null +++ b/content/events/2013-portland/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:57:35-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-portland/program.md b/content/events/2013-portland/program.md new file mode 100644 index 00000000000..4bfe2944394 --- /dev/null +++ b/content/events/2013-portland/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:57:35-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-portland/propose.md b/content/events/2013-portland/propose.md new file mode 100644 index 00000000000..f51ee277ecc --- /dev/null +++ b/content/events/2013-portland/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:57:35-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-portland/registration.md b/content/events/2013-portland/registration.md new file mode 100644 index 00000000000..0cc4ad8dd1d --- /dev/null +++ b/content/events/2013-portland/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:57:35-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-portland/sponsor.md b/content/events/2013-portland/sponsor.md new file mode 100644 index 00000000000..14b34d70ac1 --- /dev/null +++ b/content/events/2013-portland/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:57:35-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/2013-portland/welcome.md b/content/events/2013-portland/welcome.md new file mode 100644 index 00000000000..4b3c352c949 --- /dev/null +++ b/content/events/2013-portland/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:57:35-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-portland"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-telaviv/conduct.md b/content/events/2013-telaviv/conduct.md new file mode 100644 index 00000000000..ea025c0f731 --- /dev/null +++ b/content/events/2013-telaviv/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:58:16-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/2013-telaviv/contact.md b/content/events/2013-telaviv/contact.md new file mode 100644 index 00000000000..d0a07811d6d --- /dev/null +++ b/content/events/2013-telaviv/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:58:16-05: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 >}} diff --git a/content/events/2013-telaviv/location.md b/content/events/2013-telaviv/location.md new file mode 100644 index 00000000000..9654f998e9d --- /dev/null +++ b/content/events/2013-telaviv/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:58:16-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-telaviv/program.md b/content/events/2013-telaviv/program.md new file mode 100644 index 00000000000..9d2820e663b --- /dev/null +++ b/content/events/2013-telaviv/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:58:16-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-telaviv/propose.md b/content/events/2013-telaviv/propose.md new file mode 100644 index 00000000000..5f5385ed32d --- /dev/null +++ b/content/events/2013-telaviv/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:58:16-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-telaviv/registration.md b/content/events/2013-telaviv/registration.md new file mode 100644 index 00000000000..cfff0918007 --- /dev/null +++ b/content/events/2013-telaviv/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:58:16-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-telaviv/sponsor.md b/content/events/2013-telaviv/sponsor.md new file mode 100644 index 00000000000..0d8321e42f9 --- /dev/null +++ b/content/events/2013-telaviv/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:58:16-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/2013-telaviv/welcome.md b/content/events/2013-telaviv/welcome.md new file mode 100644 index 00000000000..8f2a35643a5 --- /dev/null +++ b/content/events/2013-telaviv/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:58:16-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-telaviv"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-tokyo/conduct.md b/content/events/2013-tokyo/conduct.md new file mode 100644 index 00000000000..d969a911cb0 --- /dev/null +++ b/content/events/2013-tokyo/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:58:34-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/2013-tokyo/contact.md b/content/events/2013-tokyo/contact.md new file mode 100644 index 00000000000..cc5e5a71ffe --- /dev/null +++ b/content/events/2013-tokyo/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:58:34-05: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 >}} diff --git a/content/events/2013-tokyo/location.md b/content/events/2013-tokyo/location.md new file mode 100644 index 00000000000..f8c12b6a969 --- /dev/null +++ b/content/events/2013-tokyo/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:58:34-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-tokyo/program.md b/content/events/2013-tokyo/program.md new file mode 100644 index 00000000000..69b4668e1bf --- /dev/null +++ b/content/events/2013-tokyo/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:58:34-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-tokyo/propose.md b/content/events/2013-tokyo/propose.md new file mode 100644 index 00000000000..f9a8153b112 --- /dev/null +++ b/content/events/2013-tokyo/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:58:34-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-tokyo/registration.md b/content/events/2013-tokyo/registration.md new file mode 100644 index 00000000000..81d89776aca --- /dev/null +++ b/content/events/2013-tokyo/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:58:34-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-tokyo/sponsor.md b/content/events/2013-tokyo/sponsor.md new file mode 100644 index 00000000000..2d78886807d --- /dev/null +++ b/content/events/2013-tokyo/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:58:34-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/2013-tokyo/welcome.md b/content/events/2013-tokyo/welcome.md new file mode 100644 index 00000000000..71e39a9a313 --- /dev/null +++ b/content/events/2013-tokyo/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:58:34-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-tokyo"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2013-vancouver/conduct.md b/content/events/2013-vancouver/conduct.md new file mode 100644 index 00000000000..7271cdfef49 --- /dev/null +++ b/content/events/2013-vancouver/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:57:27-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/2013-vancouver/contact.md b/content/events/2013-vancouver/contact.md new file mode 100644 index 00000000000..2eeb8564f75 --- /dev/null +++ b/content/events/2013-vancouver/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:57:27-05: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 >}} diff --git a/content/events/2013-vancouver/location.md b/content/events/2013-vancouver/location.md new file mode 100644 index 00000000000..dd5ffb9aed4 --- /dev/null +++ b/content/events/2013-vancouver/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:57:27-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2013-vancouver/program.md b/content/events/2013-vancouver/program.md new file mode 100644 index 00000000000..849a71b1496 --- /dev/null +++ b/content/events/2013-vancouver/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:57:27-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2013-vancouver/propose.md b/content/events/2013-vancouver/propose.md new file mode 100644 index 00000000000..9e523276dba --- /dev/null +++ b/content/events/2013-vancouver/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:57:27-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2013-vancouver/registration.md b/content/events/2013-vancouver/registration.md new file mode 100644 index 00000000000..6a9591d8e70 --- /dev/null +++ b/content/events/2013-vancouver/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:57:27-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2013-vancouver/sponsor.md b/content/events/2013-vancouver/sponsor.md new file mode 100644 index 00000000000..9ae02c12ad2 --- /dev/null +++ b/content/events/2013-vancouver/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:57:27-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/2013-vancouver/welcome.md b/content/events/2013-vancouver/welcome.md new file mode 100644 index 00000000000..15659e8044b --- /dev/null +++ b/content/events/2013-vancouver/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:57:27-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2013-vancouver"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-amsterdam/conduct.md b/content/events/2014-amsterdam/conduct.md new file mode 100644 index 00000000000..2da081049b8 --- /dev/null +++ b/content/events/2014-amsterdam/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:00:15-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/2014-amsterdam/contact.md b/content/events/2014-amsterdam/contact.md new file mode 100644 index 00000000000..a23251288e3 --- /dev/null +++ b/content/events/2014-amsterdam/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:00:15-05: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 >}} diff --git a/content/events/2014-amsterdam/location.md b/content/events/2014-amsterdam/location.md new file mode 100644 index 00000000000..43e52a1d1fe --- /dev/null +++ b/content/events/2014-amsterdam/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:00:15-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-amsterdam/program.md b/content/events/2014-amsterdam/program.md new file mode 100644 index 00000000000..fa1b048b5b4 --- /dev/null +++ b/content/events/2014-amsterdam/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:00:15-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-amsterdam/propose.md b/content/events/2014-amsterdam/propose.md new file mode 100644 index 00000000000..fd2118ee02f --- /dev/null +++ b/content/events/2014-amsterdam/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:00:15-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-amsterdam/registration.md b/content/events/2014-amsterdam/registration.md new file mode 100644 index 00000000000..37059c83061 --- /dev/null +++ b/content/events/2014-amsterdam/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:00:15-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-amsterdam/sponsor.md b/content/events/2014-amsterdam/sponsor.md new file mode 100644 index 00000000000..f0ec9cfc247 --- /dev/null +++ b/content/events/2014-amsterdam/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:00:15-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/2014-amsterdam/welcome.md b/content/events/2014-amsterdam/welcome.md new file mode 100644 index 00000000000..a6841f6aa34 --- /dev/null +++ b/content/events/2014-amsterdam/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:00:15-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-amsterdam"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-austin/conduct.md b/content/events/2014-austin/conduct.md new file mode 100644 index 00000000000..e394f6720b1 --- /dev/null +++ b/content/events/2014-austin/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:59:22-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/2014-austin/contact.md b/content/events/2014-austin/contact.md new file mode 100644 index 00000000000..a69b1a86cc1 --- /dev/null +++ b/content/events/2014-austin/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:59:22-05: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 >}} diff --git a/content/events/2014-austin/location.md b/content/events/2014-austin/location.md new file mode 100644 index 00000000000..b3a6c8abe59 --- /dev/null +++ b/content/events/2014-austin/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:59:22-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-austin/program.md b/content/events/2014-austin/program.md new file mode 100644 index 00000000000..ae3ee00a220 --- /dev/null +++ b/content/events/2014-austin/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:59:22-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-austin/propose.md b/content/events/2014-austin/propose.md new file mode 100644 index 00000000000..19ebe5f8821 --- /dev/null +++ b/content/events/2014-austin/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:59:22-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-austin/registration.md b/content/events/2014-austin/registration.md new file mode 100644 index 00000000000..c229c5bc087 --- /dev/null +++ b/content/events/2014-austin/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:59:22-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-austin/sponsor.md b/content/events/2014-austin/sponsor.md new file mode 100644 index 00000000000..6982f95708f --- /dev/null +++ b/content/events/2014-austin/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:59:22-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/2014-austin/welcome.md b/content/events/2014-austin/welcome.md new file mode 100644 index 00000000000..4a648f293a3 --- /dev/null +++ b/content/events/2014-austin/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:59:22-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-austin"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-bangalore/conduct.md b/content/events/2014-bangalore/conduct.md new file mode 100644 index 00000000000..644fdca75c0 --- /dev/null +++ b/content/events/2014-bangalore/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:02:44-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/2014-bangalore/contact.md b/content/events/2014-bangalore/contact.md new file mode 100644 index 00000000000..0da948cea45 --- /dev/null +++ b/content/events/2014-bangalore/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:02:44-05: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 >}} diff --git a/content/events/2014-bangalore/location.md b/content/events/2014-bangalore/location.md new file mode 100644 index 00000000000..28ffc845c71 --- /dev/null +++ b/content/events/2014-bangalore/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:02:44-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-bangalore/program.md b/content/events/2014-bangalore/program.md new file mode 100644 index 00000000000..176934660e2 --- /dev/null +++ b/content/events/2014-bangalore/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:02:44-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-bangalore/propose.md b/content/events/2014-bangalore/propose.md new file mode 100644 index 00000000000..b8df6f4d0c9 --- /dev/null +++ b/content/events/2014-bangalore/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:02:44-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-bangalore/registration.md b/content/events/2014-bangalore/registration.md new file mode 100644 index 00000000000..34e31029b59 --- /dev/null +++ b/content/events/2014-bangalore/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:02:44-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-bangalore/sponsor.md b/content/events/2014-bangalore/sponsor.md new file mode 100644 index 00000000000..15a1428e77b --- /dev/null +++ b/content/events/2014-bangalore/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:02:44-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/2014-bangalore/welcome.md b/content/events/2014-bangalore/welcome.md new file mode 100644 index 00000000000..e007fb6a7f5 --- /dev/null +++ b/content/events/2014-bangalore/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:02:44-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-bangalore"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-belgium/conduct.md b/content/events/2014-belgium/conduct.md new file mode 100644 index 00000000000..ca6434cc116 --- /dev/null +++ b/content/events/2014-belgium/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:02:15-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/2014-belgium/contact.md b/content/events/2014-belgium/contact.md new file mode 100644 index 00000000000..bae37fa1e78 --- /dev/null +++ b/content/events/2014-belgium/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:02:15-05: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 >}} diff --git a/content/events/2014-belgium/location.md b/content/events/2014-belgium/location.md new file mode 100644 index 00000000000..0566f9e4c02 --- /dev/null +++ b/content/events/2014-belgium/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:02:15-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-belgium/program.md b/content/events/2014-belgium/program.md new file mode 100644 index 00000000000..08cf867be7a --- /dev/null +++ b/content/events/2014-belgium/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:02:15-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-belgium/propose.md b/content/events/2014-belgium/propose.md new file mode 100644 index 00000000000..0ba85f644fd --- /dev/null +++ b/content/events/2014-belgium/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:02:15-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-belgium/registration.md b/content/events/2014-belgium/registration.md new file mode 100644 index 00000000000..57155f6a93c --- /dev/null +++ b/content/events/2014-belgium/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:02:15-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-belgium/sponsor.md b/content/events/2014-belgium/sponsor.md new file mode 100644 index 00000000000..0854f23c53d --- /dev/null +++ b/content/events/2014-belgium/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:02:15-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/2014-belgium/welcome.md b/content/events/2014-belgium/welcome.md new file mode 100644 index 00000000000..e6bc93bddac --- /dev/null +++ b/content/events/2014-belgium/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:02:15-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-belgium"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-berlin/conduct.md b/content/events/2014-berlin/conduct.md new file mode 100644 index 00000000000..19d7474be58 --- /dev/null +++ b/content/events/2014-berlin/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:02:07-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/2014-berlin/contact.md b/content/events/2014-berlin/contact.md new file mode 100644 index 00000000000..f3080db81ef --- /dev/null +++ b/content/events/2014-berlin/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:02:07-05: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 >}} diff --git a/content/events/2014-berlin/location.md b/content/events/2014-berlin/location.md new file mode 100644 index 00000000000..a5aaddcfec6 --- /dev/null +++ b/content/events/2014-berlin/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:02:07-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-berlin/program.md b/content/events/2014-berlin/program.md new file mode 100644 index 00000000000..ed7b6166ef0 --- /dev/null +++ b/content/events/2014-berlin/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:02:07-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-berlin/propose.md b/content/events/2014-berlin/propose.md new file mode 100644 index 00000000000..8b877c64f33 --- /dev/null +++ b/content/events/2014-berlin/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:02:07-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-berlin/registration.md b/content/events/2014-berlin/registration.md new file mode 100644 index 00000000000..66589c84b6c --- /dev/null +++ b/content/events/2014-berlin/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:02:07-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-berlin/sponsor.md b/content/events/2014-berlin/sponsor.md new file mode 100644 index 00000000000..c3bf7281ebe --- /dev/null +++ b/content/events/2014-berlin/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:02:07-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/2014-berlin/welcome.md b/content/events/2014-berlin/welcome.md new file mode 100644 index 00000000000..ec69642cf90 --- /dev/null +++ b/content/events/2014-berlin/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:02:07-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-berlin"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-boston/conduct.md b/content/events/2014-boston/conduct.md new file mode 100644 index 00000000000..e3dcd381284 --- /dev/null +++ b/content/events/2014-boston/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:00:50-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/2014-boston/contact.md b/content/events/2014-boston/contact.md new file mode 100644 index 00000000000..97dba96fe23 --- /dev/null +++ b/content/events/2014-boston/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:00:50-05: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 >}} diff --git a/content/events/2014-boston/location.md b/content/events/2014-boston/location.md new file mode 100644 index 00000000000..e005aca1510 --- /dev/null +++ b/content/events/2014-boston/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:00:50-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-boston/program.md b/content/events/2014-boston/program.md new file mode 100644 index 00000000000..5bc4d013f6d --- /dev/null +++ b/content/events/2014-boston/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:00:50-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-boston/propose.md b/content/events/2014-boston/propose.md new file mode 100644 index 00000000000..945b9937253 --- /dev/null +++ b/content/events/2014-boston/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:00:50-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-boston/registration.md b/content/events/2014-boston/registration.md new file mode 100644 index 00000000000..8094af211f5 --- /dev/null +++ b/content/events/2014-boston/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:00:50-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-boston/sponsor.md b/content/events/2014-boston/sponsor.md new file mode 100644 index 00000000000..6741384254a --- /dev/null +++ b/content/events/2014-boston/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:00:50-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/2014-boston/welcome.md b/content/events/2014-boston/welcome.md new file mode 100644 index 00000000000..3717a2a07c2 --- /dev/null +++ b/content/events/2014-boston/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:00:50-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-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 >}} +
diff --git a/content/events/2014-brisbane/conduct.md b/content/events/2014-brisbane/conduct.md new file mode 100644 index 00000000000..c689c925277 --- /dev/null +++ b/content/events/2014-brisbane/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:00:43-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/2014-brisbane/contact.md b/content/events/2014-brisbane/contact.md new file mode 100644 index 00000000000..421d13c8ad7 --- /dev/null +++ b/content/events/2014-brisbane/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:00:43-05: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 >}} diff --git a/content/events/2014-brisbane/location.md b/content/events/2014-brisbane/location.md new file mode 100644 index 00000000000..18443877bd2 --- /dev/null +++ b/content/events/2014-brisbane/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:00:43-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-brisbane/program.md b/content/events/2014-brisbane/program.md new file mode 100644 index 00000000000..9a548ad69ad --- /dev/null +++ b/content/events/2014-brisbane/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:00:43-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-brisbane/propose.md b/content/events/2014-brisbane/propose.md new file mode 100644 index 00000000000..2e40eeff6e2 --- /dev/null +++ b/content/events/2014-brisbane/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:00:43-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-brisbane/registration.md b/content/events/2014-brisbane/registration.md new file mode 100644 index 00000000000..44d0252cc4d --- /dev/null +++ b/content/events/2014-brisbane/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:00:43-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-brisbane/sponsor.md b/content/events/2014-brisbane/sponsor.md new file mode 100644 index 00000000000..bf547d2ed94 --- /dev/null +++ b/content/events/2014-brisbane/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:00:43-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/2014-brisbane/welcome.md b/content/events/2014-brisbane/welcome.md new file mode 100644 index 00000000000..03df26cdef8 --- /dev/null +++ b/content/events/2014-brisbane/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:00:43-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-brisbane"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-chicago/conduct.md b/content/events/2014-chicago/conduct.md new file mode 100644 index 00000000000..87a912e5974 --- /dev/null +++ b/content/events/2014-chicago/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:02:01-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/2014-chicago/contact.md b/content/events/2014-chicago/contact.md new file mode 100644 index 00000000000..f6581dfe834 --- /dev/null +++ b/content/events/2014-chicago/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:02:01-05: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 >}} diff --git a/content/events/2014-chicago/location.md b/content/events/2014-chicago/location.md new file mode 100644 index 00000000000..7c87ab4a9c3 --- /dev/null +++ b/content/events/2014-chicago/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:02:01-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-chicago/program.md b/content/events/2014-chicago/program.md new file mode 100644 index 00000000000..41f25b65004 --- /dev/null +++ b/content/events/2014-chicago/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:02:01-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-chicago/propose.md b/content/events/2014-chicago/propose.md new file mode 100644 index 00000000000..30ed36dd597 --- /dev/null +++ b/content/events/2014-chicago/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:02:01-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-chicago/registration.md b/content/events/2014-chicago/registration.md new file mode 100644 index 00000000000..3298e908538 --- /dev/null +++ b/content/events/2014-chicago/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:02:01-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-chicago/sponsor.md b/content/events/2014-chicago/sponsor.md new file mode 100644 index 00000000000..0810938fb42 --- /dev/null +++ b/content/events/2014-chicago/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:02:01-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/2014-chicago/welcome.md b/content/events/2014-chicago/welcome.md new file mode 100644 index 00000000000..e8496cd476e --- /dev/null +++ b/content/events/2014-chicago/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:02:01-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-chicago"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-helsinki/conduct.md b/content/events/2014-helsinki/conduct.md new file mode 100644 index 00000000000..4b9ee28e7a7 --- /dev/null +++ b/content/events/2014-helsinki/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:02:23-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/2014-helsinki/contact.md b/content/events/2014-helsinki/contact.md new file mode 100644 index 00000000000..3496ebca89c --- /dev/null +++ b/content/events/2014-helsinki/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:02:23-05: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 >}} diff --git a/content/events/2014-helsinki/location.md b/content/events/2014-helsinki/location.md new file mode 100644 index 00000000000..34f6fe28874 --- /dev/null +++ b/content/events/2014-helsinki/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:02:23-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-helsinki/program.md b/content/events/2014-helsinki/program.md new file mode 100644 index 00000000000..39925a92812 --- /dev/null +++ b/content/events/2014-helsinki/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:02:23-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-helsinki/propose.md b/content/events/2014-helsinki/propose.md new file mode 100644 index 00000000000..6c08645919f --- /dev/null +++ b/content/events/2014-helsinki/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:02:23-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-helsinki/registration.md b/content/events/2014-helsinki/registration.md new file mode 100644 index 00000000000..4142739ea1d --- /dev/null +++ b/content/events/2014-helsinki/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:02:23-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-helsinki/sponsor.md b/content/events/2014-helsinki/sponsor.md new file mode 100644 index 00000000000..b3425349e0d --- /dev/null +++ b/content/events/2014-helsinki/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:02:23-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/2014-helsinki/welcome.md b/content/events/2014-helsinki/welcome.md new file mode 100644 index 00000000000..8385ad6cc54 --- /dev/null +++ b/content/events/2014-helsinki/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:02:23-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-helsinki"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-ljubljana/conduct.md b/content/events/2014-ljubljana/conduct.md new file mode 100644 index 00000000000..c323fd59818 --- /dev/null +++ b/content/events/2014-ljubljana/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:59:07-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/2014-ljubljana/contact.md b/content/events/2014-ljubljana/contact.md new file mode 100644 index 00000000000..3c8e315482c --- /dev/null +++ b/content/events/2014-ljubljana/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:59:07-05: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 >}} diff --git a/content/events/2014-ljubljana/location.md b/content/events/2014-ljubljana/location.md new file mode 100644 index 00000000000..d969fc02e60 --- /dev/null +++ b/content/events/2014-ljubljana/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:59:07-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-ljubljana/program.md b/content/events/2014-ljubljana/program.md new file mode 100644 index 00000000000..19fc7eeb15a --- /dev/null +++ b/content/events/2014-ljubljana/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:59:07-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-ljubljana/propose.md b/content/events/2014-ljubljana/propose.md new file mode 100644 index 00000000000..949ffb7529e --- /dev/null +++ b/content/events/2014-ljubljana/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:59:07-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-ljubljana/registration.md b/content/events/2014-ljubljana/registration.md new file mode 100644 index 00000000000..95703d67e39 --- /dev/null +++ b/content/events/2014-ljubljana/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:59:07-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-ljubljana/sponsor.md b/content/events/2014-ljubljana/sponsor.md new file mode 100644 index 00000000000..032423ab579 --- /dev/null +++ b/content/events/2014-ljubljana/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:59:07-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/2014-ljubljana/welcome.md b/content/events/2014-ljubljana/welcome.md new file mode 100644 index 00000000000..99c053f82af --- /dev/null +++ b/content/events/2014-ljubljana/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:59:07-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-ljubljana"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-minneapolis/conduct.md b/content/events/2014-minneapolis/conduct.md new file mode 100644 index 00000000000..65153121162 --- /dev/null +++ b/content/events/2014-minneapolis/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:00:35-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/2014-minneapolis/contact.md b/content/events/2014-minneapolis/contact.md new file mode 100644 index 00000000000..8777f2cc38a --- /dev/null +++ b/content/events/2014-minneapolis/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:00:35-05: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 >}} diff --git a/content/events/2014-minneapolis/location.md b/content/events/2014-minneapolis/location.md new file mode 100644 index 00000000000..6d1c7096d56 --- /dev/null +++ b/content/events/2014-minneapolis/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:00:35-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-minneapolis/program.md b/content/events/2014-minneapolis/program.md new file mode 100644 index 00000000000..b9465837b72 --- /dev/null +++ b/content/events/2014-minneapolis/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:00:35-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-minneapolis/propose.md b/content/events/2014-minneapolis/propose.md new file mode 100644 index 00000000000..3d64bfd5ed3 --- /dev/null +++ b/content/events/2014-minneapolis/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:00:35-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-minneapolis/registration.md b/content/events/2014-minneapolis/registration.md new file mode 100644 index 00000000000..45f9139fd89 --- /dev/null +++ b/content/events/2014-minneapolis/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:00:35-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-minneapolis/sponsor.md b/content/events/2014-minneapolis/sponsor.md new file mode 100644 index 00000000000..ef8cfa20c82 --- /dev/null +++ b/content/events/2014-minneapolis/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:00:35-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/2014-minneapolis/welcome.md b/content/events/2014-minneapolis/welcome.md new file mode 100644 index 00000000000..e0cea5d2876 --- /dev/null +++ b/content/events/2014-minneapolis/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:00:35-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-minneapolis"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-nairobi/conduct.md b/content/events/2014-nairobi/conduct.md new file mode 100644 index 00000000000..d89ed125083 --- /dev/null +++ b/content/events/2014-nairobi/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T12:58:48-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/2014-nairobi/contact.md b/content/events/2014-nairobi/contact.md new file mode 100644 index 00000000000..ffd0ed1efe9 --- /dev/null +++ b/content/events/2014-nairobi/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:58:48-05: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 >}} diff --git a/content/events/2014-nairobi/location.md b/content/events/2014-nairobi/location.md new file mode 100644 index 00000000000..d586d5efe13 --- /dev/null +++ b/content/events/2014-nairobi/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T12:58:48-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-nairobi/program.md b/content/events/2014-nairobi/program.md new file mode 100644 index 00000000000..9b3605d11f6 --- /dev/null +++ b/content/events/2014-nairobi/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T12:58:48-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-nairobi/propose.md b/content/events/2014-nairobi/propose.md new file mode 100644 index 00000000000..1a8777dbe99 --- /dev/null +++ b/content/events/2014-nairobi/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T12:58:48-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-nairobi/registration.md b/content/events/2014-nairobi/registration.md new file mode 100644 index 00000000000..d58d956df5d --- /dev/null +++ b/content/events/2014-nairobi/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:58:48-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-nairobi/sponsor.md b/content/events/2014-nairobi/sponsor.md new file mode 100644 index 00000000000..f160862ded1 --- /dev/null +++ b/content/events/2014-nairobi/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T12:58:48-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/2014-nairobi/welcome.md b/content/events/2014-nairobi/welcome.md new file mode 100644 index 00000000000..89c324cfd67 --- /dev/null +++ b/content/events/2014-nairobi/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:58:48-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-nairobi"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-newyork/conduct.md b/content/events/2014-newyork/conduct.md new file mode 100644 index 00000000000..995f3e675b0 --- /dev/null +++ b/content/events/2014-newyork/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:01:10-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/2014-newyork/contact.md b/content/events/2014-newyork/contact.md new file mode 100644 index 00000000000..4364efc28cb --- /dev/null +++ b/content/events/2014-newyork/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:01:10-05: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 >}} diff --git a/content/events/2014-newyork/location.md b/content/events/2014-newyork/location.md new file mode 100644 index 00000000000..32e8141f129 --- /dev/null +++ b/content/events/2014-newyork/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:01:10-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-newyork/program.md b/content/events/2014-newyork/program.md new file mode 100644 index 00000000000..d51b9385fae --- /dev/null +++ b/content/events/2014-newyork/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:01:10-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-newyork/propose.md b/content/events/2014-newyork/propose.md new file mode 100644 index 00000000000..0aa7f994c16 --- /dev/null +++ b/content/events/2014-newyork/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:01:10-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-newyork/registration.md b/content/events/2014-newyork/registration.md new file mode 100644 index 00000000000..3dcf9720e01 --- /dev/null +++ b/content/events/2014-newyork/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:01:10-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-newyork/sponsor.md b/content/events/2014-newyork/sponsor.md new file mode 100644 index 00000000000..f3dc20b90d3 --- /dev/null +++ b/content/events/2014-newyork/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:01:10-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/2014-newyork/welcome.md b/content/events/2014-newyork/welcome.md new file mode 100644 index 00000000000..188546b813b --- /dev/null +++ b/content/events/2014-newyork/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:01:10-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-newyork"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-pittsburgh/sample-event/conduct.md b/content/events/2014-pittsburgh/sample-event/conduct.md new file mode 100644 index 00000000000..41689ed7809 --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/conduct.md @@ -0,0 +1,37 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "conduct" +type = "event" +draft = true + ++++ + +## 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/2014-pittsburgh/sample-event/contact.md b/content/events/2014-pittsburgh/sample-event/contact.md new file mode 100644 index 00000000000..d6fc715f175 --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/contact.md @@ -0,0 +1,18 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "contact" +type = "event" +draft = true + + ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + +**The core devopsdays organizer group** + +{{< list_core >}} diff --git a/content/events/2014-pittsburgh/sample-event/location.md b/content/events/2014-pittsburgh/sample-event/location.md new file mode 100644 index 00000000000..1533593efe4 --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/location.md @@ -0,0 +1,11 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "location" +type = "event" +draft = true + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-pittsburgh/sample-event/program.md b/content/events/2014-pittsburgh/sample-event/program.md new file mode 100644 index 00000000000..4e39e69b951 --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/program.md @@ -0,0 +1,123 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "program" +type = "event" +draft = true + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-pittsburgh/sample-event/propose.md b/content/events/2014-pittsburgh/sample-event/propose.md new file mode 100644 index 00000000000..ba528d96ed6 --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/propose.md @@ -0,0 +1,38 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "propose" +type = "event" +draft = true ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-pittsburgh/sample-event/registration.md b/content/events/2014-pittsburgh/sample-event/registration.md new file mode 100644 index 00000000000..9e12f87a388 --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/registration.md @@ -0,0 +1,14 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "registration" +type = "event" +draft = true + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-pittsburgh/sample-event/sponsor.md b/content/events/2014-pittsburgh/sample-event/sponsor.md new file mode 100644 index 00000000000..91398b5b367 --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/sponsor.md @@ -0,0 +1,50 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "sponsor" +type = "event" +draft = true + + ++++ + +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/2014-pittsburgh/sample-event/welcome.md b/content/events/2014-pittsburgh/sample-event/welcome.md new file mode 100644 index 00000000000..913384cea7b --- /dev/null +++ b/content/events/2014-pittsburgh/sample-event/welcome.md @@ -0,0 +1,53 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "welcome" +type = "event" +aliases = ["/events/YYYY-city"] +draft = true + ++++ + +## {{< 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 devopsdaysyourtown >}} +
diff --git a/content/events/2014-siliconvalley/conduct.md b/content/events/2014-siliconvalley/conduct.md new file mode 100644 index 00000000000..7956ba6fd2f --- /dev/null +++ b/content/events/2014-siliconvalley/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:00:25-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/2014-siliconvalley/contact.md b/content/events/2014-siliconvalley/contact.md new file mode 100644 index 00000000000..e2596c61a24 --- /dev/null +++ b/content/events/2014-siliconvalley/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:00:25-05: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 >}} diff --git a/content/events/2014-siliconvalley/location.md b/content/events/2014-siliconvalley/location.md new file mode 100644 index 00000000000..07f836852c4 --- /dev/null +++ b/content/events/2014-siliconvalley/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:00:25-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-siliconvalley/program.md b/content/events/2014-siliconvalley/program.md new file mode 100644 index 00000000000..215362ea29e --- /dev/null +++ b/content/events/2014-siliconvalley/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:00:25-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-siliconvalley/propose.md b/content/events/2014-siliconvalley/propose.md new file mode 100644 index 00000000000..86d791ce663 --- /dev/null +++ b/content/events/2014-siliconvalley/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:00:25-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-siliconvalley/registration.md b/content/events/2014-siliconvalley/registration.md new file mode 100644 index 00000000000..4ee6e1c1bb2 --- /dev/null +++ b/content/events/2014-siliconvalley/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:00:25-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-siliconvalley/sponsor.md b/content/events/2014-siliconvalley/sponsor.md new file mode 100644 index 00000000000..63c2d834119 --- /dev/null +++ b/content/events/2014-siliconvalley/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:00:25-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/2014-siliconvalley/welcome.md b/content/events/2014-siliconvalley/welcome.md new file mode 100644 index 00000000000..b5a962e3cdd --- /dev/null +++ b/content/events/2014-siliconvalley/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:00:25-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-siliconvalley"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-telaviv/conduct.md b/content/events/2014-telaviv/conduct.md new file mode 100644 index 00000000000..1a17763763a --- /dev/null +++ b/content/events/2014-telaviv/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:02:37-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/2014-telaviv/contact.md b/content/events/2014-telaviv/contact.md new file mode 100644 index 00000000000..dd913fbe930 --- /dev/null +++ b/content/events/2014-telaviv/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:02:37-05: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 >}} diff --git a/content/events/2014-telaviv/location.md b/content/events/2014-telaviv/location.md new file mode 100644 index 00000000000..8e2b5e9d7a0 --- /dev/null +++ b/content/events/2014-telaviv/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:02:37-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-telaviv/program.md b/content/events/2014-telaviv/program.md new file mode 100644 index 00000000000..9a57616f44d --- /dev/null +++ b/content/events/2014-telaviv/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:02:37-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-telaviv/propose.md b/content/events/2014-telaviv/propose.md new file mode 100644 index 00000000000..f259413cda4 --- /dev/null +++ b/content/events/2014-telaviv/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:02:37-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-telaviv/registration.md b/content/events/2014-telaviv/registration.md new file mode 100644 index 00000000000..50d0cc0d24d --- /dev/null +++ b/content/events/2014-telaviv/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:02:37-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-telaviv/sponsor.md b/content/events/2014-telaviv/sponsor.md new file mode 100644 index 00000000000..f0f20e82622 --- /dev/null +++ b/content/events/2014-telaviv/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:02:37-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/2014-telaviv/welcome.md b/content/events/2014-telaviv/welcome.md new file mode 100644 index 00000000000..10720d402b8 --- /dev/null +++ b/content/events/2014-telaviv/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:02:37-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-telaviv"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-toronto/conduct.md b/content/events/2014-toronto/conduct.md new file mode 100644 index 00000000000..2942fa2bcc9 --- /dev/null +++ b/content/events/2014-toronto/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:01:03-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/2014-toronto/contact.md b/content/events/2014-toronto/contact.md new file mode 100644 index 00000000000..b9a26963eb6 --- /dev/null +++ b/content/events/2014-toronto/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:01:03-05: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 >}} diff --git a/content/events/2014-toronto/location.md b/content/events/2014-toronto/location.md new file mode 100644 index 00000000000..b9d5fa7d695 --- /dev/null +++ b/content/events/2014-toronto/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:01:03-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-toronto/program.md b/content/events/2014-toronto/program.md new file mode 100644 index 00000000000..c96b77d5343 --- /dev/null +++ b/content/events/2014-toronto/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:01:03-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-toronto/propose.md b/content/events/2014-toronto/propose.md new file mode 100644 index 00000000000..dbcb3441a97 --- /dev/null +++ b/content/events/2014-toronto/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:01:03-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-toronto/registration.md b/content/events/2014-toronto/registration.md new file mode 100644 index 00000000000..3ed99790a15 --- /dev/null +++ b/content/events/2014-toronto/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:01:03-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-toronto/sponsor.md b/content/events/2014-toronto/sponsor.md new file mode 100644 index 00000000000..b0791ad6f38 --- /dev/null +++ b/content/events/2014-toronto/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:01:03-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/2014-toronto/welcome.md b/content/events/2014-toronto/welcome.md new file mode 100644 index 00000000000..09044be1879 --- /dev/null +++ b/content/events/2014-toronto/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:01:03-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-toronto"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-vancouver/conduct.md b/content/events/2014-vancouver/conduct.md new file mode 100644 index 00000000000..aa5d5a4ee3e --- /dev/null +++ b/content/events/2014-vancouver/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:02:30-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/2014-vancouver/contact.md b/content/events/2014-vancouver/contact.md new file mode 100644 index 00000000000..b20d0f8c6e5 --- /dev/null +++ b/content/events/2014-vancouver/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:02:30-05: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 >}} diff --git a/content/events/2014-vancouver/location.md b/content/events/2014-vancouver/location.md new file mode 100644 index 00000000000..8ec4268f954 --- /dev/null +++ b/content/events/2014-vancouver/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:02:30-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-vancouver/program.md b/content/events/2014-vancouver/program.md new file mode 100644 index 00000000000..cc7e1f5e996 --- /dev/null +++ b/content/events/2014-vancouver/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:02:30-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-vancouver/propose.md b/content/events/2014-vancouver/propose.md new file mode 100644 index 00000000000..831d1e1e01b --- /dev/null +++ b/content/events/2014-vancouver/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:02:30-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-vancouver/registration.md b/content/events/2014-vancouver/registration.md new file mode 100644 index 00000000000..92c8a0f93fa --- /dev/null +++ b/content/events/2014-vancouver/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:02:30-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-vancouver/sponsor.md b/content/events/2014-vancouver/sponsor.md new file mode 100644 index 00000000000..93d69a74b90 --- /dev/null +++ b/content/events/2014-vancouver/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:02:30-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/2014-vancouver/welcome.md b/content/events/2014-vancouver/welcome.md new file mode 100644 index 00000000000..a2baeed4c30 --- /dev/null +++ b/content/events/2014-vancouver/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:02:30-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-vancouver"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2014-warsaw/conduct.md b/content/events/2014-warsaw/conduct.md new file mode 100644 index 00000000000..81c9242a6c0 --- /dev/null +++ b/content/events/2014-warsaw/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:01:54-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/2014-warsaw/contact.md b/content/events/2014-warsaw/contact.md new file mode 100644 index 00000000000..e13e7b76602 --- /dev/null +++ b/content/events/2014-warsaw/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:01:54-05: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 >}} diff --git a/content/events/2014-warsaw/location.md b/content/events/2014-warsaw/location.md new file mode 100644 index 00000000000..8bc3e1de672 --- /dev/null +++ b/content/events/2014-warsaw/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:01:54-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2014-warsaw/program.md b/content/events/2014-warsaw/program.md new file mode 100644 index 00000000000..0cc1679cc65 --- /dev/null +++ b/content/events/2014-warsaw/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:01:54-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2014-warsaw/propose.md b/content/events/2014-warsaw/propose.md new file mode 100644 index 00000000000..a219059ceb0 --- /dev/null +++ b/content/events/2014-warsaw/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:01:54-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2014-warsaw/registration.md b/content/events/2014-warsaw/registration.md new file mode 100644 index 00000000000..a07806c8329 --- /dev/null +++ b/content/events/2014-warsaw/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:01:54-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2014-warsaw/sponsor.md b/content/events/2014-warsaw/sponsor.md new file mode 100644 index 00000000000..78a60c9edbc --- /dev/null +++ b/content/events/2014-warsaw/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:01:54-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/2014-warsaw/welcome.md b/content/events/2014-warsaw/welcome.md new file mode 100644 index 00000000000..dccc7b3efff --- /dev/null +++ b/content/events/2014-warsaw/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:01:54-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2014-warsaw"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-amsterdam/conduct.md b/content/events/2015-amsterdam/conduct.md new file mode 100644 index 00000000000..41a0845f05b --- /dev/null +++ b/content/events/2015-amsterdam/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:06:03-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-amsterdam/contact.md b/content/events/2015-amsterdam/contact.md new file mode 100644 index 00000000000..ae6567fbda4 --- /dev/null +++ b/content/events/2015-amsterdam/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:06:03-05: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 >}} diff --git a/content/events/2015-amsterdam/location.md b/content/events/2015-amsterdam/location.md new file mode 100644 index 00000000000..e415f183346 --- /dev/null +++ b/content/events/2015-amsterdam/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:06:03-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-amsterdam/program.md b/content/events/2015-amsterdam/program.md new file mode 100644 index 00000000000..c9650d80cb3 --- /dev/null +++ b/content/events/2015-amsterdam/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:06:03-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-amsterdam/propose.md b/content/events/2015-amsterdam/propose.md new file mode 100644 index 00000000000..a88206241d3 --- /dev/null +++ b/content/events/2015-amsterdam/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:06:03-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-amsterdam/registration.md b/content/events/2015-amsterdam/registration.md new file mode 100644 index 00000000000..81255f16585 --- /dev/null +++ b/content/events/2015-amsterdam/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:06:03-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-amsterdam/sponsor.md b/content/events/2015-amsterdam/sponsor.md new file mode 100644 index 00000000000..4da05c2e2ba --- /dev/null +++ b/content/events/2015-amsterdam/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:06:03-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-amsterdam/welcome.md b/content/events/2015-amsterdam/welcome.md new file mode 100644 index 00000000000..bea1afaa0d1 --- /dev/null +++ b/content/events/2015-amsterdam/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:06:03-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-amsterdam"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-austin/conduct.md b/content/events/2015-austin/conduct.md new file mode 100644 index 00000000000..a41daba2c08 --- /dev/null +++ b/content/events/2015-austin/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:04:01-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-austin/contact.md b/content/events/2015-austin/contact.md new file mode 100644 index 00000000000..e5e47da3128 --- /dev/null +++ b/content/events/2015-austin/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:04:01-05: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 >}} diff --git a/content/events/2015-austin/location.md b/content/events/2015-austin/location.md new file mode 100644 index 00000000000..070774b6be5 --- /dev/null +++ b/content/events/2015-austin/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:04:01-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-austin/program.md b/content/events/2015-austin/program.md new file mode 100644 index 00000000000..781c76967d3 --- /dev/null +++ b/content/events/2015-austin/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:04:01-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-austin/propose.md b/content/events/2015-austin/propose.md new file mode 100644 index 00000000000..2355abe16d8 --- /dev/null +++ b/content/events/2015-austin/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:04:01-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-austin/registration.md b/content/events/2015-austin/registration.md new file mode 100644 index 00000000000..606510a293a --- /dev/null +++ b/content/events/2015-austin/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:04:01-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-austin/sponsor.md b/content/events/2015-austin/sponsor.md new file mode 100644 index 00000000000..d56e96c2496 --- /dev/null +++ b/content/events/2015-austin/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:04:01-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-austin/welcome.md b/content/events/2015-austin/welcome.md new file mode 100644 index 00000000000..73d14c4c0f0 --- /dev/null +++ b/content/events/2015-austin/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:04:01-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-austin"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-bangalore/conduct.md b/content/events/2015-bangalore/conduct.md new file mode 100644 index 00000000000..1bd3f4f28bb --- /dev/null +++ b/content/events/2015-bangalore/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:21:47-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-bangalore/contact.md b/content/events/2015-bangalore/contact.md new file mode 100644 index 00000000000..81f170764b3 --- /dev/null +++ b/content/events/2015-bangalore/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:21:47-05: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 >}} diff --git a/content/events/2015-bangalore/location.md b/content/events/2015-bangalore/location.md new file mode 100644 index 00000000000..c82735b39e6 --- /dev/null +++ b/content/events/2015-bangalore/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:21:47-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-bangalore/program.md b/content/events/2015-bangalore/program.md new file mode 100644 index 00000000000..394976e79cc --- /dev/null +++ b/content/events/2015-bangalore/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:21:47-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-bangalore/propose.md b/content/events/2015-bangalore/propose.md new file mode 100644 index 00000000000..60b6cf17f95 --- /dev/null +++ b/content/events/2015-bangalore/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:21:47-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-bangalore/registration.md b/content/events/2015-bangalore/registration.md new file mode 100644 index 00000000000..85485ea8730 --- /dev/null +++ b/content/events/2015-bangalore/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:21:47-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-bangalore/sponsor.md b/content/events/2015-bangalore/sponsor.md new file mode 100644 index 00000000000..4deab831ffd --- /dev/null +++ b/content/events/2015-bangalore/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:21:47-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-bangalore/welcome.md b/content/events/2015-bangalore/welcome.md new file mode 100644 index 00000000000..f5904610f83 --- /dev/null +++ b/content/events/2015-bangalore/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:21:47-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-bangalore"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-berlin/conduct.md b/content/events/2015-berlin/conduct.md new file mode 100644 index 00000000000..177944dacda --- /dev/null +++ b/content/events/2015-berlin/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:22:22-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-berlin/contact.md b/content/events/2015-berlin/contact.md new file mode 100644 index 00000000000..1784ef5be24 --- /dev/null +++ b/content/events/2015-berlin/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:22:22-05: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 >}} diff --git a/content/events/2015-berlin/location.md b/content/events/2015-berlin/location.md new file mode 100644 index 00000000000..0dee1bfd8cd --- /dev/null +++ b/content/events/2015-berlin/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:22:22-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-berlin/program.md b/content/events/2015-berlin/program.md new file mode 100644 index 00000000000..67afea2fa7a --- /dev/null +++ b/content/events/2015-berlin/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:22:22-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-berlin/propose.md b/content/events/2015-berlin/propose.md new file mode 100644 index 00000000000..527482c534d --- /dev/null +++ b/content/events/2015-berlin/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:22:22-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-berlin/registration.md b/content/events/2015-berlin/registration.md new file mode 100644 index 00000000000..caee0c0ac23 --- /dev/null +++ b/content/events/2015-berlin/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:22:22-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-berlin/sponsor.md b/content/events/2015-berlin/sponsor.md new file mode 100644 index 00000000000..599304a4457 --- /dev/null +++ b/content/events/2015-berlin/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:22:22-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-berlin/welcome.md b/content/events/2015-berlin/welcome.md new file mode 100644 index 00000000000..a8d1a24369f --- /dev/null +++ b/content/events/2015-berlin/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:22:22-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-berlin"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-boston/conduct.md b/content/events/2015-boston/conduct.md new file mode 100644 index 00000000000..d2a969fa843 --- /dev/null +++ b/content/events/2015-boston/conduct.md @@ -0,0 +1,36 @@ ++++ +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/contact.md b/content/events/2015-boston/contact.md new file mode 100644 index 00000000000..b5a0efee6d7 --- /dev/null +++ b/content/events/2015-boston/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:21:57-05: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 >}} diff --git a/content/events/2015-boston/location.md b/content/events/2015-boston/location.md new file mode 100644 index 00000000000..2c35dd8a702 --- /dev/null +++ b/content/events/2015-boston/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:21:57-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-boston/program.md b/content/events/2015-boston/program.md new file mode 100644 index 00000000000..0aa684a833a --- /dev/null +++ b/content/events/2015-boston/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:21:57-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-boston/propose.md b/content/events/2015-boston/propose.md new file mode 100644 index 00000000000..522a0b86f04 --- /dev/null +++ b/content/events/2015-boston/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:21:57-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-boston/registration.md b/content/events/2015-boston/registration.md new file mode 100644 index 00000000000..7a3d492be3b --- /dev/null +++ b/content/events/2015-boston/registration.md @@ -0,0 +1,13 @@ ++++ +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 new file mode 100644 index 00000000000..21a413599cd --- /dev/null +++ b/content/events/2015-boston/sponsor.md @@ -0,0 +1,49 @@ ++++ +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 new file mode 100644 index 00000000000..2841fe09ee3 --- /dev/null +++ b/content/events/2015-boston/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:21:57-05:00" +title = "welcome" +type = "event" +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 >}} +
diff --git a/content/events/2015-charlotte/conduct.md b/content/events/2015-charlotte/conduct.md new file mode 100644 index 00000000000..8e059cb6c03 --- /dev/null +++ b/content/events/2015-charlotte/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:22:37-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-charlotte/contact.md b/content/events/2015-charlotte/contact.md new file mode 100644 index 00000000000..fba5253d8fa --- /dev/null +++ b/content/events/2015-charlotte/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:22:37-05: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 >}} diff --git a/content/events/2015-charlotte/location.md b/content/events/2015-charlotte/location.md new file mode 100644 index 00000000000..f5de3241b7c --- /dev/null +++ b/content/events/2015-charlotte/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:22:37-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-charlotte/program.md b/content/events/2015-charlotte/program.md new file mode 100644 index 00000000000..2539396e729 --- /dev/null +++ b/content/events/2015-charlotte/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:22:37-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-charlotte/propose.md b/content/events/2015-charlotte/propose.md new file mode 100644 index 00000000000..9061998acad --- /dev/null +++ b/content/events/2015-charlotte/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:22:37-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-charlotte/registration.md b/content/events/2015-charlotte/registration.md new file mode 100644 index 00000000000..3322bcfe267 --- /dev/null +++ b/content/events/2015-charlotte/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:22:37-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-charlotte/sponsor.md b/content/events/2015-charlotte/sponsor.md new file mode 100644 index 00000000000..291ac6e24f3 --- /dev/null +++ b/content/events/2015-charlotte/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:22:37-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-charlotte/welcome.md b/content/events/2015-charlotte/welcome.md new file mode 100644 index 00000000000..384b7d6b146 --- /dev/null +++ b/content/events/2015-charlotte/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:22:37-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-charlotte"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-chicago/conduct.md b/content/events/2015-chicago/conduct.md index c29ff168c6f..093490223e5 100644 --- a/content/events/2015-chicago/conduct.md +++ b/content/events/2015-chicago/conduct.md @@ -1,9 +1,36 @@ +++ -Description = "" -event = "2015chicago" -date = "2015-11-09T17:40:56-06:00" +date = "2016-05-02T13:21:25-05:00" title = "conduct" -City = "Chicago" -Year = "2015" 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-chicago/contact.md b/content/events/2015-chicago/contact.md index af6222fd852..3e584ca0430 100644 --- a/content/events/2015-chicago/contact.md +++ b/content/events/2015-chicago/contact.md @@ -1,9 +1,17 @@ +++ -Description = "" -event = "2015chicago" -date = "2015-11-09T17:40:56-06:00" +date = "2016-05-02T13:21:25-05:00" title = "contact" -City = "Chicago" -Year = "2015" 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 >}} diff --git a/content/events/2015-chicago/location.md b/content/events/2015-chicago/location.md index df9feb3c52e..6bb2b88798a 100644 --- a/content/events/2015-chicago/location.md +++ b/content/events/2015-chicago/location.md @@ -1,9 +1,10 @@ +++ -Description = "" -event = "2015chicago" -date = "2015-11-09T17:40:56-06:00" +date = "2016-05-02T13:21:25-05:00" title = "location" -City = "Chicago" -Year = "2015" type = "event" + +++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-chicago/program.md b/content/events/2015-chicago/program.md index 6a5c69ff135..a876dcef92b 100644 --- a/content/events/2015-chicago/program.md +++ b/content/events/2015-chicago/program.md @@ -1,9 +1,122 @@ +++ -Description = "" -event = "2015chicago" -date = "2015-11-09T17:40:56-06:00" +date = "2016-05-02T13:21:25-05:00" title = "program" -City = "Chicago" -Year = "2015" type = "event" + +++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-chicago/propose.md b/content/events/2015-chicago/propose.md new file mode 100644 index 00000000000..0f82df37639 --- /dev/null +++ b/content/events/2015-chicago/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:21:25-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-chicago/registration.md b/content/events/2015-chicago/registration.md new file mode 100644 index 00000000000..02d0db016ec --- /dev/null +++ b/content/events/2015-chicago/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:21:25-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-chicago/sponsor.md b/content/events/2015-chicago/sponsor.md index c6e4e89e7cd..72edf2ac2ce 100644 --- a/content/events/2015-chicago/sponsor.md +++ b/content/events/2015-chicago/sponsor.md @@ -1,9 +1,49 @@ +++ -Description = "" -event = "2015chicago" -date = "2015-11-09T17:40:56-06:00" +date = "2016-05-02T13:21:25-05:00" title = "sponsor" -City = "Chicago" -Year = "2015" 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-chicago/welcome.md b/content/events/2015-chicago/welcome.md index e3745aa1dbb..2e574673573 100644 --- a/content/events/2015-chicago/welcome.md +++ b/content/events/2015-chicago/welcome.md @@ -1,16 +1,52 @@ +++ -Description = "" -event = "2015chicago" -date = "2015-11-09T17:40:56-06:00" +date = "2016-05-02T13:21:25-05:00" title = "welcome" -City = "Chicago" -Year = "2015" type = "event" aliases = ["/events/2015-chicago"] + +++ -

Tuesday, August 25th and Wednesday, August 26th

+## {{< event_start >}} - {{< event_end >}} + +DevOps Days is coming to {{< event_location >}}! -Welcome! The group that brought you DevOpsDays Chicago 2014 is back together and planning the 2015 event. We're encouraged by the feedback from last year's event and are determined to bring an improved experience and continue the DevOps conversation this August in Chicago. + - + + + + + + + + + + + + + + + + + + + + +
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 devopsdayschi >}} +
diff --git a/content/events/2015-denver/conduct.md b/content/events/2015-denver/conduct.md new file mode 100644 index 00000000000..164d82226d4 --- /dev/null +++ b/content/events/2015-denver/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:03:46-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-denver/contact.md b/content/events/2015-denver/contact.md new file mode 100644 index 00000000000..7201cd8bcc0 --- /dev/null +++ b/content/events/2015-denver/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:03:46-05: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 >}} diff --git a/content/events/2015-denver/location.md b/content/events/2015-denver/location.md new file mode 100644 index 00000000000..b513bf94484 --- /dev/null +++ b/content/events/2015-denver/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:03:46-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-denver/program.md b/content/events/2015-denver/program.md new file mode 100644 index 00000000000..c55a276fd40 --- /dev/null +++ b/content/events/2015-denver/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:03:46-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-denver/propose.md b/content/events/2015-denver/propose.md new file mode 100644 index 00000000000..7aadc5a7bb8 --- /dev/null +++ b/content/events/2015-denver/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:03:46-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-denver/registration.md b/content/events/2015-denver/registration.md new file mode 100644 index 00000000000..acbc4169e4e --- /dev/null +++ b/content/events/2015-denver/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:03:46-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-denver/sponsor.md b/content/events/2015-denver/sponsor.md new file mode 100644 index 00000000000..bbbfb808220 --- /dev/null +++ b/content/events/2015-denver/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:03:46-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-denver/welcome.md b/content/events/2015-denver/welcome.md new file mode 100644 index 00000000000..1c734ba7ab7 --- /dev/null +++ b/content/events/2015-denver/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:03:46-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-denver"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-detroit/conduct.md b/content/events/2015-detroit/conduct.md new file mode 100644 index 00000000000..be24d6d0590 --- /dev/null +++ b/content/events/2015-detroit/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:22:54-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-detroit/contact.md b/content/events/2015-detroit/contact.md new file mode 100644 index 00000000000..fc566690876 --- /dev/null +++ b/content/events/2015-detroit/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:22:54-05: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 >}} diff --git a/content/events/2015-detroit/location.md b/content/events/2015-detroit/location.md new file mode 100644 index 00000000000..947baa184ee --- /dev/null +++ b/content/events/2015-detroit/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:22:54-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-detroit/program.md b/content/events/2015-detroit/program.md new file mode 100644 index 00000000000..5b85bfbdafd --- /dev/null +++ b/content/events/2015-detroit/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:22:54-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-detroit/propose.md b/content/events/2015-detroit/propose.md new file mode 100644 index 00000000000..83565043ece --- /dev/null +++ b/content/events/2015-detroit/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:22:54-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-detroit/registration.md b/content/events/2015-detroit/registration.md new file mode 100644 index 00000000000..a66b57c8951 --- /dev/null +++ b/content/events/2015-detroit/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:22:54-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-detroit/sponsor.md b/content/events/2015-detroit/sponsor.md new file mode 100644 index 00000000000..a38101f00da --- /dev/null +++ b/content/events/2015-detroit/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:22:54-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-detroit/welcome.md b/content/events/2015-detroit/welcome.md new file mode 100644 index 00000000000..923131e4cbb --- /dev/null +++ b/content/events/2015-detroit/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:22:54-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-detroit"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-ljubljana/conduct.md b/content/events/2015-ljubljana/conduct.md new file mode 100644 index 00000000000..2ced6db39a4 --- /dev/null +++ b/content/events/2015-ljubljana/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:03:33-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-ljubljana/contact.md b/content/events/2015-ljubljana/contact.md new file mode 100644 index 00000000000..dd1db3f493a --- /dev/null +++ b/content/events/2015-ljubljana/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:03:33-05: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 >}} diff --git a/content/events/2015-ljubljana/location.md b/content/events/2015-ljubljana/location.md new file mode 100644 index 00000000000..286cfa8a7b7 --- /dev/null +++ b/content/events/2015-ljubljana/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:03:33-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-ljubljana/program.md b/content/events/2015-ljubljana/program.md new file mode 100644 index 00000000000..40282372597 --- /dev/null +++ b/content/events/2015-ljubljana/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:03:33-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-ljubljana/propose.md b/content/events/2015-ljubljana/propose.md new file mode 100644 index 00000000000..4c84843f3e8 --- /dev/null +++ b/content/events/2015-ljubljana/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:03:33-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-ljubljana/registration.md b/content/events/2015-ljubljana/registration.md new file mode 100644 index 00000000000..d6b1e0ebf7f --- /dev/null +++ b/content/events/2015-ljubljana/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:03:33-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-ljubljana/sponsor.md b/content/events/2015-ljubljana/sponsor.md new file mode 100644 index 00000000000..8c775817f9b --- /dev/null +++ b/content/events/2015-ljubljana/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:03:33-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-ljubljana/welcome.md b/content/events/2015-ljubljana/welcome.md new file mode 100644 index 00000000000..29d27f0082f --- /dev/null +++ b/content/events/2015-ljubljana/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:03:33-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-ljubljana"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-melbourne/conduct.md b/content/events/2015-melbourne/conduct.md new file mode 100644 index 00000000000..1caf86164c0 --- /dev/null +++ b/content/events/2015-melbourne/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:06:20-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-melbourne/contact.md b/content/events/2015-melbourne/contact.md new file mode 100644 index 00000000000..3a6c144b607 --- /dev/null +++ b/content/events/2015-melbourne/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:06:20-05: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 >}} diff --git a/content/events/2015-melbourne/location.md b/content/events/2015-melbourne/location.md new file mode 100644 index 00000000000..a5c8d51b935 --- /dev/null +++ b/content/events/2015-melbourne/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:06:20-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-melbourne/program.md b/content/events/2015-melbourne/program.md new file mode 100644 index 00000000000..c023619e142 --- /dev/null +++ b/content/events/2015-melbourne/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:06:20-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-melbourne/propose.md b/content/events/2015-melbourne/propose.md new file mode 100644 index 00000000000..04d3c498418 --- /dev/null +++ b/content/events/2015-melbourne/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:06:20-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-melbourne/registration.md b/content/events/2015-melbourne/registration.md new file mode 100644 index 00000000000..97470aa2b81 --- /dev/null +++ b/content/events/2015-melbourne/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:06:20-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-melbourne/sponsor.md b/content/events/2015-melbourne/sponsor.md new file mode 100644 index 00000000000..0471f9ab683 --- /dev/null +++ b/content/events/2015-melbourne/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:06:20-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-melbourne/welcome.md b/content/events/2015-melbourne/welcome.md new file mode 100644 index 00000000000..8ee3921fffb --- /dev/null +++ b/content/events/2015-melbourne/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:06:20-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-melbourne"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-minneapolis/conduct.md b/content/events/2015-minneapolis/conduct.md new file mode 100644 index 00000000000..02bce6d9d36 --- /dev/null +++ b/content/events/2015-minneapolis/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:06:12-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-minneapolis/contact.md b/content/events/2015-minneapolis/contact.md new file mode 100644 index 00000000000..b7d59cda22a --- /dev/null +++ b/content/events/2015-minneapolis/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:06:12-05: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 >}} diff --git a/content/events/2015-minneapolis/location.md b/content/events/2015-minneapolis/location.md new file mode 100644 index 00000000000..b34876979d3 --- /dev/null +++ b/content/events/2015-minneapolis/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:06:12-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-minneapolis/program.md b/content/events/2015-minneapolis/program.md new file mode 100644 index 00000000000..73c895e3fbf --- /dev/null +++ b/content/events/2015-minneapolis/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:06:12-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-minneapolis/propose.md b/content/events/2015-minneapolis/propose.md new file mode 100644 index 00000000000..c618bdcdca2 --- /dev/null +++ b/content/events/2015-minneapolis/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:06:12-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-minneapolis/registration.md b/content/events/2015-minneapolis/registration.md new file mode 100644 index 00000000000..3ed073df13f --- /dev/null +++ b/content/events/2015-minneapolis/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:06:12-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-minneapolis/sponsor.md b/content/events/2015-minneapolis/sponsor.md new file mode 100644 index 00000000000..d2449285d88 --- /dev/null +++ b/content/events/2015-minneapolis/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:06:12-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-minneapolis/welcome.md b/content/events/2015-minneapolis/welcome.md new file mode 100644 index 00000000000..72a5ee0b54c --- /dev/null +++ b/content/events/2015-minneapolis/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:06:12-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-minneapolis"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-newyork/sample-event/conduct.md b/content/events/2015-newyork/sample-event/conduct.md new file mode 100644 index 00000000000..41689ed7809 --- /dev/null +++ b/content/events/2015-newyork/sample-event/conduct.md @@ -0,0 +1,37 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "conduct" +type = "event" +draft = true + ++++ + +## 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-newyork/sample-event/contact.md b/content/events/2015-newyork/sample-event/contact.md new file mode 100644 index 00000000000..d6fc715f175 --- /dev/null +++ b/content/events/2015-newyork/sample-event/contact.md @@ -0,0 +1,18 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "contact" +type = "event" +draft = true + + ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + +**The core devopsdays organizer group** + +{{< list_core >}} diff --git a/content/events/2015-newyork/sample-event/location.md b/content/events/2015-newyork/sample-event/location.md new file mode 100644 index 00000000000..1533593efe4 --- /dev/null +++ b/content/events/2015-newyork/sample-event/location.md @@ -0,0 +1,11 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "location" +type = "event" +draft = true + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-newyork/sample-event/program.md b/content/events/2015-newyork/sample-event/program.md new file mode 100644 index 00000000000..4e39e69b951 --- /dev/null +++ b/content/events/2015-newyork/sample-event/program.md @@ -0,0 +1,123 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "program" +type = "event" +draft = true + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-newyork/sample-event/propose.md b/content/events/2015-newyork/sample-event/propose.md new file mode 100644 index 00000000000..ba528d96ed6 --- /dev/null +++ b/content/events/2015-newyork/sample-event/propose.md @@ -0,0 +1,38 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "propose" +type = "event" +draft = true ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-newyork/sample-event/registration.md b/content/events/2015-newyork/sample-event/registration.md new file mode 100644 index 00000000000..9e12f87a388 --- /dev/null +++ b/content/events/2015-newyork/sample-event/registration.md @@ -0,0 +1,14 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "registration" +type = "event" +draft = true + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-newyork/sample-event/sponsor.md b/content/events/2015-newyork/sample-event/sponsor.md new file mode 100644 index 00000000000..91398b5b367 --- /dev/null +++ b/content/events/2015-newyork/sample-event/sponsor.md @@ -0,0 +1,50 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "sponsor" +type = "event" +draft = true + + ++++ + +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-newyork/sample-event/welcome.md b/content/events/2015-newyork/sample-event/welcome.md new file mode 100644 index 00000000000..913384cea7b --- /dev/null +++ b/content/events/2015-newyork/sample-event/welcome.md @@ -0,0 +1,53 @@ ++++ +date = "2000-01-01T01:01:01-06:00" +title = "welcome" +type = "event" +aliases = ["/events/YYYY-city"] +draft = true + ++++ + +## {{< 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 devopsdaysyourtown >}} +
diff --git a/content/events/2015-ohio/conduct.md b/content/events/2015-ohio/conduct.md new file mode 100644 index 00000000000..3cabfe0caf8 --- /dev/null +++ b/content/events/2015-ohio/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:23:02-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-ohio/contact.md b/content/events/2015-ohio/contact.md new file mode 100644 index 00000000000..442125c1b35 --- /dev/null +++ b/content/events/2015-ohio/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:23:02-05: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 >}} diff --git a/content/events/2015-ohio/location.md b/content/events/2015-ohio/location.md new file mode 100644 index 00000000000..d0e2d03fd20 --- /dev/null +++ b/content/events/2015-ohio/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:23:02-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-ohio/program.md b/content/events/2015-ohio/program.md new file mode 100644 index 00000000000..848e7c9bb8e --- /dev/null +++ b/content/events/2015-ohio/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:23:02-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-ohio/propose.md b/content/events/2015-ohio/propose.md new file mode 100644 index 00000000000..0bff5bc605d --- /dev/null +++ b/content/events/2015-ohio/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:23:02-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-ohio/registration.md b/content/events/2015-ohio/registration.md new file mode 100644 index 00000000000..dade94518be --- /dev/null +++ b/content/events/2015-ohio/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:23:02-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-ohio/sponsor.md b/content/events/2015-ohio/sponsor.md new file mode 100644 index 00000000000..54e40e34f63 --- /dev/null +++ b/content/events/2015-ohio/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:23:02-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-ohio/welcome.md b/content/events/2015-ohio/welcome.md new file mode 100644 index 00000000000..11eb40ca785 --- /dev/null +++ b/content/events/2015-ohio/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:23:02-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-ohio"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-paris/conduct.md b/content/events/2015-paris/conduct.md new file mode 100644 index 00000000000..f4b87cf9ead --- /dev/null +++ b/content/events/2015-paris/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:03:40-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-paris/contact.md b/content/events/2015-paris/contact.md new file mode 100644 index 00000000000..32189067690 --- /dev/null +++ b/content/events/2015-paris/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:03:40-05: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 >}} diff --git a/content/events/2015-paris/location.md b/content/events/2015-paris/location.md new file mode 100644 index 00000000000..c00c824b080 --- /dev/null +++ b/content/events/2015-paris/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:03:40-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-paris/program.md b/content/events/2015-paris/program.md new file mode 100644 index 00000000000..e4bc9210aea --- /dev/null +++ b/content/events/2015-paris/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:03:40-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-paris/propose.md b/content/events/2015-paris/propose.md new file mode 100644 index 00000000000..71e9275b88c --- /dev/null +++ b/content/events/2015-paris/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:03:40-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-paris/registration.md b/content/events/2015-paris/registration.md new file mode 100644 index 00000000000..36782fd13dd --- /dev/null +++ b/content/events/2015-paris/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:03:40-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-paris/sponsor.md b/content/events/2015-paris/sponsor.md new file mode 100644 index 00000000000..65defb87b35 --- /dev/null +++ b/content/events/2015-paris/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:03:40-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-paris/welcome.md b/content/events/2015-paris/welcome.md new file mode 100644 index 00000000000..0e129fc0701 --- /dev/null +++ b/content/events/2015-paris/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:03:40-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-paris"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-pittsburgh/conduct.md b/content/events/2015-pittsburgh/conduct.md new file mode 100644 index 00000000000..73d52fb6feb --- /dev/null +++ b/content/events/2015-pittsburgh/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:06:30-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-pittsburgh/contact.md b/content/events/2015-pittsburgh/contact.md new file mode 100644 index 00000000000..22e1439f21a --- /dev/null +++ b/content/events/2015-pittsburgh/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:06:30-05: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 >}} diff --git a/content/events/2015-pittsburgh/location.md b/content/events/2015-pittsburgh/location.md new file mode 100644 index 00000000000..72b63ab0f64 --- /dev/null +++ b/content/events/2015-pittsburgh/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:06:30-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-pittsburgh/program.md b/content/events/2015-pittsburgh/program.md new file mode 100644 index 00000000000..a458b05771e --- /dev/null +++ b/content/events/2015-pittsburgh/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:06:30-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-pittsburgh/propose.md b/content/events/2015-pittsburgh/propose.md new file mode 100644 index 00000000000..64d07ac505a --- /dev/null +++ b/content/events/2015-pittsburgh/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:06:30-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-pittsburgh/registration.md b/content/events/2015-pittsburgh/registration.md new file mode 100644 index 00000000000..c98e77d85ff --- /dev/null +++ b/content/events/2015-pittsburgh/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:06:30-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-pittsburgh/sponsor.md b/content/events/2015-pittsburgh/sponsor.md new file mode 100644 index 00000000000..908b30d56f3 --- /dev/null +++ b/content/events/2015-pittsburgh/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:06:30-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-pittsburgh/welcome.md b/content/events/2015-pittsburgh/welcome.md new file mode 100644 index 00000000000..2ddb572e01f --- /dev/null +++ b/content/events/2015-pittsburgh/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:06:30-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-pittsburgh"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-siliconvalley/conduct.md b/content/events/2015-siliconvalley/conduct.md new file mode 100644 index 00000000000..5616520c67b --- /dev/null +++ b/content/events/2015-siliconvalley/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:22:47-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-siliconvalley/contact.md b/content/events/2015-siliconvalley/contact.md new file mode 100644 index 00000000000..a771940ef27 --- /dev/null +++ b/content/events/2015-siliconvalley/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:22:47-05: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 >}} diff --git a/content/events/2015-siliconvalley/location.md b/content/events/2015-siliconvalley/location.md new file mode 100644 index 00000000000..3cbba71eea3 --- /dev/null +++ b/content/events/2015-siliconvalley/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:22:47-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-siliconvalley/program.md b/content/events/2015-siliconvalley/program.md new file mode 100644 index 00000000000..7f65a519d8a --- /dev/null +++ b/content/events/2015-siliconvalley/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:22:47-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-siliconvalley/propose.md b/content/events/2015-siliconvalley/propose.md new file mode 100644 index 00000000000..856ed4f2280 --- /dev/null +++ b/content/events/2015-siliconvalley/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:22:47-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-siliconvalley/registration.md b/content/events/2015-siliconvalley/registration.md new file mode 100644 index 00000000000..e2999d27b3f --- /dev/null +++ b/content/events/2015-siliconvalley/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:22:47-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-siliconvalley/sponsor.md b/content/events/2015-siliconvalley/sponsor.md new file mode 100644 index 00000000000..5c17414a75c --- /dev/null +++ b/content/events/2015-siliconvalley/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:22:47-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-siliconvalley/welcome.md b/content/events/2015-siliconvalley/welcome.md new file mode 100644 index 00000000000..a9c60b54322 --- /dev/null +++ b/content/events/2015-siliconvalley/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:22:47-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-siliconvalley"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-singapore/conduct.md b/content/events/2015-singapore/conduct.md new file mode 100644 index 00000000000..261f75039a6 --- /dev/null +++ b/content/events/2015-singapore/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:22:15-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-singapore/contact.md b/content/events/2015-singapore/contact.md new file mode 100644 index 00000000000..71b0ffca90a --- /dev/null +++ b/content/events/2015-singapore/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:22:15-05: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 >}} diff --git a/content/events/2015-singapore/location.md b/content/events/2015-singapore/location.md new file mode 100644 index 00000000000..e771e008f3c --- /dev/null +++ b/content/events/2015-singapore/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:22:15-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-singapore/program.md b/content/events/2015-singapore/program.md new file mode 100644 index 00000000000..b09e1f3e656 --- /dev/null +++ b/content/events/2015-singapore/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:22:15-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-singapore/propose.md b/content/events/2015-singapore/propose.md new file mode 100644 index 00000000000..2715db2d0b3 --- /dev/null +++ b/content/events/2015-singapore/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:22:15-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-singapore/registration.md b/content/events/2015-singapore/registration.md new file mode 100644 index 00000000000..5af78eb3e95 --- /dev/null +++ b/content/events/2015-singapore/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:22:15-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-singapore/sponsor.md b/content/events/2015-singapore/sponsor.md new file mode 100644 index 00000000000..9a91d0da988 --- /dev/null +++ b/content/events/2015-singapore/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:22:15-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-singapore/welcome.md b/content/events/2015-singapore/welcome.md new file mode 100644 index 00000000000..e55b6876faf --- /dev/null +++ b/content/events/2015-singapore/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:22:15-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-singapore"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-telaviv/conduct.md b/content/events/2015-telaviv/conduct.md new file mode 100644 index 00000000000..4c0e6954d66 --- /dev/null +++ b/content/events/2015-telaviv/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:22:07-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-telaviv/contact.md b/content/events/2015-telaviv/contact.md new file mode 100644 index 00000000000..27efe722f55 --- /dev/null +++ b/content/events/2015-telaviv/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:22:07-05: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 >}} diff --git a/content/events/2015-telaviv/location.md b/content/events/2015-telaviv/location.md new file mode 100644 index 00000000000..e5e25541559 --- /dev/null +++ b/content/events/2015-telaviv/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:22:07-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-telaviv/program.md b/content/events/2015-telaviv/program.md new file mode 100644 index 00000000000..e8c989decc2 --- /dev/null +++ b/content/events/2015-telaviv/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:22:07-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-telaviv/propose.md b/content/events/2015-telaviv/propose.md new file mode 100644 index 00000000000..3388712d745 --- /dev/null +++ b/content/events/2015-telaviv/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:22:07-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-telaviv/registration.md b/content/events/2015-telaviv/registration.md new file mode 100644 index 00000000000..ab534d70b0a --- /dev/null +++ b/content/events/2015-telaviv/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:22:07-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-telaviv/sponsor.md b/content/events/2015-telaviv/sponsor.md new file mode 100644 index 00000000000..95f57b8e660 --- /dev/null +++ b/content/events/2015-telaviv/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:22:07-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-telaviv/welcome.md b/content/events/2015-telaviv/welcome.md new file mode 100644 index 00000000000..5e22aefd30b --- /dev/null +++ b/content/events/2015-telaviv/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:22:07-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-telaviv"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-toronto/conduct.md b/content/events/2015-toronto/conduct.md new file mode 100644 index 00000000000..bc7ec468713 --- /dev/null +++ b/content/events/2015-toronto/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:04:08-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-toronto/contact.md b/content/events/2015-toronto/contact.md new file mode 100644 index 00000000000..121e8644ab3 --- /dev/null +++ b/content/events/2015-toronto/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:04:08-05: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 >}} diff --git a/content/events/2015-toronto/location.md b/content/events/2015-toronto/location.md new file mode 100644 index 00000000000..6c6bb8285ca --- /dev/null +++ b/content/events/2015-toronto/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:04:08-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-toronto/program.md b/content/events/2015-toronto/program.md new file mode 100644 index 00000000000..77cf056635a --- /dev/null +++ b/content/events/2015-toronto/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:04:08-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-toronto/propose.md b/content/events/2015-toronto/propose.md new file mode 100644 index 00000000000..09b611c00a6 --- /dev/null +++ b/content/events/2015-toronto/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:04:08-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-toronto/registration.md b/content/events/2015-toronto/registration.md new file mode 100644 index 00000000000..f8c07556c38 --- /dev/null +++ b/content/events/2015-toronto/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:04:08-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-toronto/sponsor.md b/content/events/2015-toronto/sponsor.md new file mode 100644 index 00000000000..03b3dea0c33 --- /dev/null +++ b/content/events/2015-toronto/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:04:08-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-toronto/welcome.md b/content/events/2015-toronto/welcome.md new file mode 100644 index 00000000000..f17f0f5151d --- /dev/null +++ b/content/events/2015-toronto/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:04:08-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-toronto"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-warsaw/conduct.md b/content/events/2015-warsaw/conduct.md new file mode 100644 index 00000000000..3a84f332e80 --- /dev/null +++ b/content/events/2015-warsaw/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:23:09-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-warsaw/contact.md b/content/events/2015-warsaw/contact.md new file mode 100644 index 00000000000..a56f35a730e --- /dev/null +++ b/content/events/2015-warsaw/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:23:09-05: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 >}} diff --git a/content/events/2015-warsaw/location.md b/content/events/2015-warsaw/location.md new file mode 100644 index 00000000000..ffcfac10ce3 --- /dev/null +++ b/content/events/2015-warsaw/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:23:09-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-warsaw/program.md b/content/events/2015-warsaw/program.md new file mode 100644 index 00000000000..137bf9ae2fd --- /dev/null +++ b/content/events/2015-warsaw/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:23:09-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-warsaw/propose.md b/content/events/2015-warsaw/propose.md new file mode 100644 index 00000000000..a818ca90d5b --- /dev/null +++ b/content/events/2015-warsaw/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:23:09-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-warsaw/registration.md b/content/events/2015-warsaw/registration.md new file mode 100644 index 00000000000..953286f28a4 --- /dev/null +++ b/content/events/2015-warsaw/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:23:09-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-warsaw/sponsor.md b/content/events/2015-warsaw/sponsor.md new file mode 100644 index 00000000000..d08d357923c --- /dev/null +++ b/content/events/2015-warsaw/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:23:09-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-warsaw/welcome.md b/content/events/2015-warsaw/welcome.md new file mode 100644 index 00000000000..92d5bcb39cb --- /dev/null +++ b/content/events/2015-warsaw/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:23:09-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-warsaw"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2015-washington-dc/conduct.md b/content/events/2015-washington-dc/conduct.md new file mode 100644 index 00000000000..69d2adf129f --- /dev/null +++ b/content/events/2015-washington-dc/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:04:23-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-washington-dc/contact.md b/content/events/2015-washington-dc/contact.md new file mode 100644 index 00000000000..4c1379653e8 --- /dev/null +++ b/content/events/2015-washington-dc/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:04:23-05: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 >}} diff --git a/content/events/2015-washington-dc/location.md b/content/events/2015-washington-dc/location.md new file mode 100644 index 00000000000..3522be0f16d --- /dev/null +++ b/content/events/2015-washington-dc/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:04:23-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2015-washington-dc/program.md b/content/events/2015-washington-dc/program.md new file mode 100644 index 00000000000..2865a147465 --- /dev/null +++ b/content/events/2015-washington-dc/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:04:23-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2015-washington-dc/propose.md b/content/events/2015-washington-dc/propose.md new file mode 100644 index 00000000000..a5d722bfd89 --- /dev/null +++ b/content/events/2015-washington-dc/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:04:23-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2015-washington-dc/registration.md b/content/events/2015-washington-dc/registration.md new file mode 100644 index 00000000000..ca04a63744e --- /dev/null +++ b/content/events/2015-washington-dc/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:04:23-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2015-washington-dc/sponsor.md b/content/events/2015-washington-dc/sponsor.md new file mode 100644 index 00000000000..7abd38f08b5 --- /dev/null +++ b/content/events/2015-washington-dc/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:04:23-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-washington-dc/welcome.md b/content/events/2015-washington-dc/welcome.md new file mode 100644 index 00000000000..c6e8ce80fea --- /dev/null +++ b/content/events/2015-washington-dc/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:04:23-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2015-washington-dc"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2016-losangeles-1day/conduct.md b/content/events/2016-losangeles-1day/conduct.md new file mode 100644 index 00000000000..83ca24cf2da --- /dev/null +++ b/content/events/2016-losangeles-1day/conduct.md @@ -0,0 +1,36 @@ ++++ +date = "2016-05-02T13:23:30-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/2016-losangeles-1day/contact.md b/content/events/2016-losangeles-1day/contact.md new file mode 100644 index 00000000000..bed1f4e8b5f --- /dev/null +++ b/content/events/2016-losangeles-1day/contact.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T13:23:30-05: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 >}} diff --git a/content/events/2016-losangeles-1day/location.md b/content/events/2016-losangeles-1day/location.md new file mode 100644 index 00000000000..7916a985332 --- /dev/null +++ b/content/events/2016-losangeles-1day/location.md @@ -0,0 +1,10 @@ ++++ +date = "2016-05-02T13:23:30-05:00" +title = "location" +type = "event" + ++++ + +Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. + + diff --git a/content/events/2016-losangeles-1day/program.md b/content/events/2016-losangeles-1day/program.md new file mode 100644 index 00000000000..3fd6022b532 --- /dev/null +++ b/content/events/2016-losangeles-1day/program.md @@ -0,0 +1,122 @@ ++++ +date = "2016-05-02T13:23:30-05:00" +title = "program" +type = "event" + ++++ + +
+
If you are new to the Open Space concept you may want to read some more details.
+ +
+ + +

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
+ + +
+ + +
+ +
+

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
+ + + +
diff --git a/content/events/2016-losangeles-1day/propose.md b/content/events/2016-losangeles-1day/propose.md new file mode 100644 index 00000000000..0071f459076 --- /dev/null +++ b/content/events/2016-losangeles-1day/propose.md @@ -0,0 +1,37 @@ ++++ +date = "2016-05-02T13:23:30-05:00" +title = "propose" +type = "event" ++++ + {{< cfp_dates >}} + +
+There are three ways to propose a session: +
    +
  1. 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.
    2. +
  2. 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
    3. +
  3. 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 +
    +
  1. Proposal working title (can be changed later)
    2. +
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. +
  3. Description or abstract
    4. +
+Rules: + diff --git a/content/events/2016-losangeles-1day/registration.md b/content/events/2016-losangeles-1day/registration.md new file mode 100644 index 00000000000..73808a0f4b4 --- /dev/null +++ b/content/events/2016-losangeles-1day/registration.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T13:23:30-05:00" +title = "registration" +type = "event" + + ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2016-losangeles-1day/sponsor.md b/content/events/2016-losangeles-1day/sponsor.md new file mode 100644 index 00000000000..920170417e0 --- /dev/null +++ b/content/events/2016-losangeles-1day/sponsor.md @@ -0,0 +1,49 @@ ++++ +date = "2016-05-02T13:23:30-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/2016-losangeles-1day/welcome.md b/content/events/2016-losangeles-1day/welcome.md new file mode 100644 index 00000000000..43907b4349f --- /dev/null +++ b/content/events/2016-losangeles-1day/welcome.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T13:23:30-05:00" +title = "welcome" +type = "event" +aliases = ["/events/2016-losangeles-1day"] + ++++ + +## {{< 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 >}} +
diff --git a/content/events/2016-vancouver/welcome.md b/content/events/2016-vancouver/welcome.md index 5951c046efc..ab14d9d5d73 100644 --- a/content/events/2016-vancouver/welcome.md +++ b/content/events/2016-vancouver/welcome.md @@ -4,7 +4,7 @@ Year ="2016" date = "2016-03-06T21:15:25-06:00" title = "welcome" type = "event" -aliases = ["/events/2016-detroit"] +aliases = ["/events/2016-vancouver"] +++ diff --git a/data/events/2010-boston.yml b/data/events/2010-boston.yml deleted file mode 100644 index e61b93fbd78..00000000000 --- a/data/events/2010-boston.yml +++ /dev/null @@ -1,28 +0,0 @@ -name: 2010-boston -year: 2010 -city: Boston -friendly: 2010-boston -status: past -startdate: 2010-10-01 -enddate: 2010-10-02 -coordinates: "47.609895, -122.330259" -navigationelements: ["welcome", "contact","location", "conduct","sponsor"] -sponsors: - - id: chef - level: platinum - - id: datadog - level: gold - - id: arresteddevops - level: media - -sponsor_levels: - - id: platinum - label: Platinum - - id: gold - label: Gold - - id: silver - label: Silver - - id: bronze - label: Bronze - - id: media - label: Media diff --git a/data/events/2010-brazil.yml b/data/events/2010-brazil.yml new file mode 100644 index 00000000000..9c391c8a16f --- /dev/null +++ b/data/events/2010-brazil.yml @@ -0,0 +1,52 @@ +name: "2010-brazil" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2010 # The year of the event. Make sure it is in quotes. +city: "Sao Paulo" # The city name of the event. Capitalize it. +friendly: "2010-brazil" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2010-MM-DD, like this: variable: 2016-01-05 +startdate: 2010-12-04 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2010-12-04 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "brazil" # 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: location + - name: contact + +# 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." +organizer_email: "organizers-brazil-2010@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-brazil-2010@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: thoughtworks-2010 + level: sponsor + - id: puppet-2010 + level: sponsor + - id: opscode-2010 + level: sponsor + - id: locaweb-2010 + level: sponsor + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: sponsor + label: diff --git a/data/events/2010-europe.yml b/data/events/2010-europe.yml new file mode 100644 index 00000000000..5b80cf4a524 --- /dev/null +++ b/data/events/2010-europe.yml @@ -0,0 +1,59 @@ +name: "2010-europe" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2010 # The year of the event. Make sure it is in quotes. +city: "Hamburg" # The city name of the event. Capitalize it. +friendly: "2010-europe" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2010-MM-DD, like this: variable: 2016-01-05 +startdate: 2010-10-15 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2010-10-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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "europe" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-europe-2010@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-europe-2010@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2010-sydney.yml b/data/events/2010-sydney.yml index 75ef4dc2425..f8fb8fbf076 100644 --- a/data/events/2010-sydney.yml +++ b/data/events/2010-sydney.yml @@ -1,28 +1,59 @@ -name: 2010-sydney -year: 2010 -city: Sydney -friendly: 2010-sydney -status: past -startdate: 2010-01-01 -enddate: 2010-01-02 -coordinates: "47.609895, -122.330259" -navigationelements: ["welcome", "contact","location", "conduct","sponsor"] +name: "2010-sydney" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2010 # The year of the event. Make sure it is in quotes. +city: "Sydney" # The city name of the event. Capitalize it. +friendly: "2010-sydney" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2010-MM-DD, like this: variable: 2016-01-05 +startdate: 2010-01-02 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2010-01-02 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Sydney" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-sydney-2010@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-sydney-2010@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: chef - level: platinum - - id: datadog + - id: samplesponsorname level: gold - id: arresteddevops - level: media + level: community -sponsor_levels: - - id: platinum - label: Platinum +sponsor_levels: # In this section, list the level of sponsorships and the label to use. - id: gold label: Gold - id: silver label: Silver - id: bronze label: Bronze - - id: media - label: Media + - id: community + label: Community diff --git a/data/events/2010-us.yml b/data/events/2010-us.yml new file mode 100644 index 00000000000..5b733136e17 --- /dev/null +++ b/data/events/2010-us.yml @@ -0,0 +1,59 @@ +name: "2010-us" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2010 # The year of the event. Make sure it is in quotes. +city: "Mountain View" # The city name of the event. Capitalize it. +friendly: "2010-us" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2010-MM-DD, like this: variable: 2016-01-05 +startdate: 2010-06-25 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2010-06-25 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "us" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-us-2010@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-us-2010@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2011-bangalore.yml b/data/events/2011-bangalore.yml new file mode 100644 index 00000000000..2c6977a6bf4 --- /dev/null +++ b/data/events/2011-bangalore.yml @@ -0,0 +1,59 @@ +name: "2011-bangalore" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2011 # The year of the event. Make sure it is in quotes. +city: "Bangalore" # The city name of the event. Capitalize it. +friendly: "2011-bangalore" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2011-MM-DD, like this: variable: 2016-01-05 +startdate: 2011-08-28 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2011-08-28 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Bangalore" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-bangalore-2011@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-bangalore-2011@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2011-boston.yml b/data/events/2011-boston.yml new file mode 100644 index 00000000000..c3d7fb4ead7 --- /dev/null +++ b/data/events/2011-boston.yml @@ -0,0 +1,59 @@ +name: "2011-boston" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2011 # The year of the event. Make sure it is in quotes. +city: "Boston" # The city name of the event. Capitalize it. +friendly: "2011-boston" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2011-MM-DD, like this: variable: 2016-01-05 +startdate: 2011-03-07 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2011-03-08 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-boston-2011@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-boston-2011@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2011-goteborg.yml b/data/events/2011-goteborg.yml new file mode 100644 index 00000000000..e5e6956910f --- /dev/null +++ b/data/events/2011-goteborg.yml @@ -0,0 +1,59 @@ +name: "2011-goteborg" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2011 # The year of the event. Make sure it is in quotes. +city: "goteborg" # The city name of the event. Capitalize it. +friendly: "2011-goteborg" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2011-MM-DD, like this: variable: 2016-01-05 +startdate: 2011-10-14 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2011-10-15 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "goteborg" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-goteborg-2011@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-goteborg-2011@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2011-manila.yml b/data/events/2011-manila.yml new file mode 100644 index 00000000000..e68d9ffaa55 --- /dev/null +++ b/data/events/2011-manila.yml @@ -0,0 +1,59 @@ +name: "2011-manila" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2011 # The year of the event. Make sure it is in quotes. +city: "Manila" # The city name of the event. Capitalize it. +friendly: "2011-manila" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2011-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Manila" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-manila-2011@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-manila-2011@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2011-melbourne.yml b/data/events/2011-melbourne.yml new file mode 100644 index 00000000000..12ac190b8a8 --- /dev/null +++ b/data/events/2011-melbourne.yml @@ -0,0 +1,59 @@ +name: "2011-melbourne" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2011 # The year of the event. Make sure it is in quotes. +city: "Melbourne" # The city name of the event. Capitalize it. +friendly: "2011-melbourne" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2011-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Melbourne" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-melbourne-2011@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-melbourne-2011@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2011-mountainview.yml b/data/events/2011-mountainview.yml new file mode 100644 index 00000000000..d6aaaa42849 --- /dev/null +++ b/data/events/2011-mountainview.yml @@ -0,0 +1,59 @@ +name: "2011-mountainview" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2011 # The year of the event. Make sure it is in quotes. +city: "Mountain View" # The city name of the event. Capitalize it. +friendly: "2011-mountainview" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2011-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "mountainview" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-mountainview-2011@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-mountainview-2011@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2012-austin.yml b/data/events/2012-austin.yml index dcaca8e228f..39f924317df 100644 --- a/data/events/2012-austin.yml +++ b/data/events/2012-austin.yml @@ -1,28 +1,59 @@ -name: 2012-austin -year: 2012 -city: Austin -friendly: 2012-austin -status: past -startdate: 2012-01-01 -enddate: 2012-01-02 -coordinates: "47.609895, -122.330259" -navigationelements: ["welcome", "contact","location", "conduct","sponsor"] +name: "2012-austin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2012 # The year of the event. Make sure it is in quotes. +city: "Austin" # The city name of the event. Capitalize it. +friendly: "2012-austin" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2012-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Austin" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-austin-2012@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-austin-2012@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: chef - level: platinum - - id: datadog + - id: samplesponsorname level: gold - id: arresteddevops - level: media + level: community -sponsor_levels: - - id: platinum - label: Platinum +sponsor_levels: # In this section, list the level of sponsorships and the label to use. - id: gold label: Gold - id: silver label: Silver - id: bronze label: Bronze - - id: media - label: Media + - id: community + label: Community diff --git a/data/events/2012-india.yml b/data/events/2012-india.yml new file mode 100644 index 00000000000..d302272aa0c --- /dev/null +++ b/data/events/2012-india.yml @@ -0,0 +1,59 @@ +name: "2012-india" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2012 # The year of the event. Make sure it is in quotes. +city: "Delhi" # The city name of the event. Capitalize it. +friendly: "2012-india" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2012-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "india" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-india-2012@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-india-2012@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2012-italy.yml b/data/events/2012-italy.yml new file mode 100644 index 00000000000..38cf7422b28 --- /dev/null +++ b/data/events/2012-italy.yml @@ -0,0 +1,59 @@ +name: "2012-italy" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2012 # The year of the event. Make sure it is in quotes. +city: "Rome" # The city name of the event. Capitalize it. +friendly: "2012-italy" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2012-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "italy" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-italy-2012@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-italy-2012@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2012-mountainview.yml b/data/events/2012-mountainview.yml new file mode 100644 index 00000000000..dd06f98bc79 --- /dev/null +++ b/data/events/2012-mountainview.yml @@ -0,0 +1,59 @@ +name: "2012-mountainview" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2012 # The year of the event. Make sure it is in quotes. +city: "mountainview" # The city name of the event. Capitalize it. +friendly: "2012-mountainview" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2012-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "mountainview" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-mountainview-2012@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-mountainview-2012@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2012-newyork.yml b/data/events/2012-newyork.yml new file mode 100644 index 00000000000..a6a5cfd2ada --- /dev/null +++ b/data/events/2012-newyork.yml @@ -0,0 +1,59 @@ +name: "2012-newyork" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2012 # The year of the event. Make sure it is in quotes. +city: "newyork" # The city name of the event. Capitalize it. +friendly: "2012-newyork" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2012-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "newyork" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-newyork-2012@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-newyork-2012@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2012-tokyo.yml b/data/events/2012-tokyo.yml new file mode 100644 index 00000000000..7510caf556f --- /dev/null +++ b/data/events/2012-tokyo.yml @@ -0,0 +1,59 @@ +name: "2012-tokyo" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2012 # The year of the event. Make sure it is in quotes. +city: "Tokyo" # The city name of the event. Capitalize it. +friendly: "2012-tokyo" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2012-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Tokyo" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-tokyo-2012@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-tokyo-2012@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-amsterdam.yml b/data/events/2013-amsterdam.yml new file mode 100644 index 00000000000..f876c9f48e3 --- /dev/null +++ b/data/events/2013-amsterdam.yml @@ -0,0 +1,59 @@ +name: "2013-amsterdam" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Amsterdam" # The city name of the event. Capitalize it. +friendly: "2013-amsterdam" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Amsterdam" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-amsterdam-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-amsterdam-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-atlanta.yml b/data/events/2013-atlanta.yml new file mode 100644 index 00000000000..4d20b7550c1 --- /dev/null +++ b/data/events/2013-atlanta.yml @@ -0,0 +1,59 @@ +name: "2013-atlanta" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Atlanta" # The city name of the event. Capitalize it. +friendly: "2013-atlanta" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Atlanta" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-atlanta-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-atlanta-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-austin.yml b/data/events/2013-austin.yml new file mode 100644 index 00000000000..5fcae7f80bd --- /dev/null +++ b/data/events/2013-austin.yml @@ -0,0 +1,59 @@ +name: "2013-austin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Austin" # The city name of the event. Capitalize it. +friendly: "2013-austin" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Austin" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-austin-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-austin-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-barcelona.yml b/data/events/2013-barcelona.yml new file mode 100644 index 00000000000..6c901ab6384 --- /dev/null +++ b/data/events/2013-barcelona.yml @@ -0,0 +1,59 @@ +name: "2013-barcelona" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Barcelona" # The city name of the event. Capitalize it. +friendly: "2013-barcelona" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Barcelona" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-barcelona-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-barcelona-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-berlin.yml b/data/events/2013-berlin.yml new file mode 100644 index 00000000000..851fad80d95 --- /dev/null +++ b/data/events/2013-berlin.yml @@ -0,0 +1,59 @@ +name: "2013-berlin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Berlin" # The city name of the event. Capitalize it. +friendly: "2013-berlin" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Berlin" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-berlin-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-berlin-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-downunder.yml b/data/events/2013-downunder.yml new file mode 100644 index 00000000000..4e92377753e --- /dev/null +++ b/data/events/2013-downunder.yml @@ -0,0 +1,59 @@ +name: "2013-downunder" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "downunder" # The city name of the event. Capitalize it. +friendly: "2013-downunder" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "downunder" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-downunder-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-downunder-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-india.yml b/data/events/2013-india.yml new file mode 100644 index 00000000000..27b98f5969c --- /dev/null +++ b/data/events/2013-india.yml @@ -0,0 +1,59 @@ +name: "2013-india" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Bangalore" # The city name of the event. Capitalize it. +friendly: "2013-india" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Bangalore" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-india-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-india-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-london-spring.yml b/data/events/2013-london-spring.yml new file mode 100644 index 00000000000..f07cf77280a --- /dev/null +++ b/data/events/2013-london-spring.yml @@ -0,0 +1,59 @@ +name: "2013-london-spring" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "London" # The city name of the event. Capitalize it. +friendly: "2013-londonspring" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "london-spring" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-londonspring-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-londonspring-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-london.yml b/data/events/2013-london.yml index ec8f906f0df..9270ce13c06 100644 --- a/data/events/2013-london.yml +++ b/data/events/2013-london.yml @@ -1,28 +1,59 @@ -name: 2013-london -year: 2013 -city: London -friendly: 2013-london -status: past -startdate: 2013-01-01 -enddate: 2013-01-02 -coordinates: "47.609895, -122.330259" -navigationelements: ["welcome", "contact","location", "conduct","sponsor"] +name: "2013-london" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "London Autumn" # The city name of the event. Capitalize it. +friendly: "2013-london" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "london" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-london-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-london-2013@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: chef - level: platinum - - id: datadog + - id: samplesponsorname level: gold - id: arresteddevops - level: media + level: community -sponsor_levels: - - id: platinum - label: Platinum +sponsor_levels: # In this section, list the level of sponsorships and the label to use. - id: gold label: Gold - id: silver label: Silver - id: bronze label: Bronze - - id: media - label: Media + - id: community + label: Community diff --git a/data/events/2013-mountainview.yml b/data/events/2013-mountainview.yml new file mode 100644 index 00000000000..113f48d8c13 --- /dev/null +++ b/data/events/2013-mountainview.yml @@ -0,0 +1,59 @@ +name: "2013-mountainview" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Silcon Valley" # The city name of the event. Capitalize it. +friendly: "2013-mountainview" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Silcon Valley" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-mountainview-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-mountainview-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-newyork.yml b/data/events/2013-newyork.yml new file mode 100644 index 00000000000..3de663568a3 --- /dev/null +++ b/data/events/2013-newyork.yml @@ -0,0 +1,59 @@ +name: "2013-newyork" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "New York" # The city name of the event. Capitalize it. +friendly: "2013-newyork" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "New York" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-newyork-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-newyork-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-newzealand.yml b/data/events/2013-newzealand.yml new file mode 100644 index 00000000000..c53a4307922 --- /dev/null +++ b/data/events/2013-newzealand.yml @@ -0,0 +1,59 @@ +name: "2013-newzealand" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "newzealand" # The city name of the event. Capitalize it. +friendly: "2013-newzealand" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "newzealand" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-newzealand-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-newzealand-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-paris.yml b/data/events/2013-paris.yml new file mode 100644 index 00000000000..62e61f035a1 --- /dev/null +++ b/data/events/2013-paris.yml @@ -0,0 +1,59 @@ +name: "2013-paris" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Paris" # The city name of the event. Capitalize it. +friendly: "2013-paris" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Paris" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-paris-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-paris-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-portland.yml b/data/events/2013-portland.yml new file mode 100644 index 00000000000..c99592c5c98 --- /dev/null +++ b/data/events/2013-portland.yml @@ -0,0 +1,59 @@ +name: "2013-portland" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Portland" # The city name of the event. Capitalize it. +friendly: "2013-portland" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Portland" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-portland-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-portland-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-telaviv.yml b/data/events/2013-telaviv.yml new file mode 100644 index 00000000000..68224e47430 --- /dev/null +++ b/data/events/2013-telaviv.yml @@ -0,0 +1,59 @@ +name: "2013-telaviv" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Tel Aviv" # The city name of the event. Capitalize it. +friendly: "2013-telaviv" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Tel Aviv" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-telaviv-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-telaviv-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-tokyo.yml b/data/events/2013-tokyo.yml new file mode 100644 index 00000000000..d1fc880f4d1 --- /dev/null +++ b/data/events/2013-tokyo.yml @@ -0,0 +1,59 @@ +name: "2013-tokyo" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Tokyo" # The city name of the event. Capitalize it. +friendly: "2013-tokyo" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Tokyo" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-tokyo-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-tokyo-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2013-vancouver.yml b/data/events/2013-vancouver.yml new file mode 100644 index 00000000000..c3d65e078cb --- /dev/null +++ b/data/events/2013-vancouver.yml @@ -0,0 +1,59 @@ +name: "2013-vancouver" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2013 # The year of the event. Make sure it is in quotes. +city: "Vancouver" # The city name of the event. Capitalize it. +friendly: "2013-vancouver" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2013-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Vancouver" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-vancouver-2013@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-vancouver-2013@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-amsterdam.yml b/data/events/2014-amsterdam.yml new file mode 100644 index 00000000000..cfaf6c5446d --- /dev/null +++ b/data/events/2014-amsterdam.yml @@ -0,0 +1,59 @@ +name: "2014-amsterdam" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Amsterdam" # The city name of the event. Capitalize it. +friendly: "2014-amsterdam" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Amsterdam" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-amsterdam-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-amsterdam-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-austin.yml b/data/events/2014-austin.yml index 7d47bc6cedd..506bd7c952b 100644 --- a/data/events/2014-austin.yml +++ b/data/events/2014-austin.yml @@ -1,28 +1,59 @@ -name: 2014-austin -year: 2014 -city: Austin -friendly: 2014-austin -status: past -startdate: 2014-01-01 -enddate: 2014-01-02 -coordinates: "47.609895, -122.330259" -navigationelements: ["welcome", "contact","location", "conduct","sponsor"] +name: "2014-austin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Austin" # The city name of the event. Capitalize it. +friendly: "2014-austin" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Austin" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-austin-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-austin-2014@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: chef - level: platinum - - id: datadog + - id: samplesponsorname level: gold - id: arresteddevops - level: media + level: community -sponsor_levels: - - id: platinum - label: Platinum +sponsor_levels: # In this section, list the level of sponsorships and the label to use. - id: gold label: Gold - id: silver label: Silver - id: bronze label: Bronze - - id: media - label: Media + - id: community + label: Community diff --git a/data/events/2014-bangalore.yml b/data/events/2014-bangalore.yml new file mode 100644 index 00000000000..f65a52e7662 --- /dev/null +++ b/data/events/2014-bangalore.yml @@ -0,0 +1,59 @@ +name: "2014-bangalor" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Bangalor" # The city name of the event. Capitalize it. +friendly: "2014-bangalor" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Bangalor" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-bangalor-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-bangalor-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-belgium.yml b/data/events/2014-belgium.yml new file mode 100644 index 00000000000..059ad724461 --- /dev/null +++ b/data/events/2014-belgium.yml @@ -0,0 +1,59 @@ +name: "2014-belgium" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Belgium" # The city name of the event. Capitalize it. +friendly: "2014-belgium" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Belgium" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-belgium-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-belgium-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-berlin.yml b/data/events/2014-berlin.yml new file mode 100644 index 00000000000..f0bc0284bed --- /dev/null +++ b/data/events/2014-berlin.yml @@ -0,0 +1,59 @@ +name: "2014-berlin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Berlin" # The city name of the event. Capitalize it. +friendly: "2014-berlin" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Berlin" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-berlin-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-berlin-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-boston.yml b/data/events/2014-boston.yml new file mode 100644 index 00000000000..cba063da090 --- /dev/null +++ b/data/events/2014-boston.yml @@ -0,0 +1,59 @@ +name: "2014-boston" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Boston" # The city name of the event. Capitalize it. +friendly: "2014-boston" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-boston-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-boston-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-brisbane.yml b/data/events/2014-brisbane.yml new file mode 100644 index 00000000000..4f4bbc2bbd8 --- /dev/null +++ b/data/events/2014-brisbane.yml @@ -0,0 +1,59 @@ +name: "2014-brisbane" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Brisbane" # The city name of the event. Capitalize it. +friendly: "2014-brisbane" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Brisbane" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-brisbane-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-brisbane-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-chicago.yml b/data/events/2014-chicago.yml new file mode 100644 index 00000000000..0298f5d33aa --- /dev/null +++ b/data/events/2014-chicago.yml @@ -0,0 +1,59 @@ +name: "2014-chicago" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Chicago" # The city name of the event. Capitalize it. +friendly: "2014-chicago" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Chicago" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-chicago-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-chicago-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-helsinki.yml b/data/events/2014-helsinki.yml new file mode 100644 index 00000000000..dc08ba1e307 --- /dev/null +++ b/data/events/2014-helsinki.yml @@ -0,0 +1,59 @@ +name: "2014-helsinki" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Helsinki" # The city name of the event. Capitalize it. +friendly: "2014-helsinki" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Helsinki" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-helsinki-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-helsinki-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-ljubljana.yml b/data/events/2014-ljubljana.yml new file mode 100644 index 00000000000..b7551d29272 --- /dev/null +++ b/data/events/2014-ljubljana.yml @@ -0,0 +1,59 @@ +name: "2014-ljubljana" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Ljubljana" # The city name of the event. Capitalize it. +friendly: "2014-ljubljana" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Ljubljana" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-ljubljana-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-ljubljana-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-minneapolis.yml b/data/events/2014-minneapolis.yml new file mode 100644 index 00000000000..54c5dcda95d --- /dev/null +++ b/data/events/2014-minneapolis.yml @@ -0,0 +1,59 @@ +name: "2014-minneapolis" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Minneapolis" # The city name of the event. Capitalize it. +friendly: "2014-minneapolis" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Minneapolis" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-minneapolis-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-minneapolis-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-nairobi.yml b/data/events/2014-nairobi.yml new file mode 100644 index 00000000000..7bbbced7163 --- /dev/null +++ b/data/events/2014-nairobi.yml @@ -0,0 +1,59 @@ +name: "2014-nairobi" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Nairobi" # The city name of the event. Capitalize it. +friendly: "2014-nairobi" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Nairobi" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-nairobi-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-nairobi-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-newyork.yml b/data/events/2014-newyork.yml new file mode 100644 index 00000000000..ac6dba95e58 --- /dev/null +++ b/data/events/2014-newyork.yml @@ -0,0 +1,59 @@ +name: "2014-newyork" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "New York" # The city name of the event. Capitalize it. +friendly: "2014-newyork" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "New York" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-newyork-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-newyork-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-pittsburgh.yml b/data/events/2014-pittsburgh.yml new file mode 100644 index 00000000000..2dcd094ec46 --- /dev/null +++ b/data/events/2014-pittsburgh.yml @@ -0,0 +1,59 @@ +name: "2014-pittsburgh" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Pittsburgh" # The city name of the event. Capitalize it. +friendly: "2014-pittsburgh" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Pittsburgh" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-pittsburgh-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-pittsburgh-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-siliconvalley.yml b/data/events/2014-siliconvalley.yml new file mode 100644 index 00000000000..c212e4bbec7 --- /dev/null +++ b/data/events/2014-siliconvalley.yml @@ -0,0 +1,59 @@ +name: "2014-siliconvalley" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "siliconvalley" # The city name of the event. Capitalize it. +friendly: "2014-siliconvalley" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "siliconvalley" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-siliconvalley-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-siliconvalley-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-telaviv.yml b/data/events/2014-telaviv.yml new file mode 100644 index 00000000000..614393bf909 --- /dev/null +++ b/data/events/2014-telaviv.yml @@ -0,0 +1,59 @@ +name: "2014-telaviv" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Tel Aviv" # The city name of the event. Capitalize it. +friendly: "2014-telaviv" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-MM-DD, like this: variable: 2016-01-05 +startdate: 2010-01-01 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2010-01-01 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Tel Aviv" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-telaviv-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-telaviv-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-toronto.yml b/data/events/2014-toronto.yml new file mode 100644 index 00000000000..be23b3a0761 --- /dev/null +++ b/data/events/2014-toronto.yml @@ -0,0 +1,59 @@ +name: "2014-toronto" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Toronto" # The city name of the event. Capitalize it. +friendly: "2014-toronto" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Toronto" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-toronto-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-toronto-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-vancouver.yml b/data/events/2014-vancouver.yml new file mode 100644 index 00000000000..f87ce2a177e --- /dev/null +++ b/data/events/2014-vancouver.yml @@ -0,0 +1,59 @@ +name: "2014-vancouver" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Vancouver" # The city name of the event. Capitalize it. +friendly: "2014-vancouver" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-MM-DD, like this: variable: 2016-01-05 +startdate: 2014-01-01 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2014-01-01 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Vancouver" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-vancouver-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-vancouver-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2014-warsaw.yml b/data/events/2014-warsaw.yml new file mode 100644 index 00000000000..3a849efcbca --- /dev/null +++ b/data/events/2014-warsaw.yml @@ -0,0 +1,59 @@ +name: "2014-warsaw" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2014 # The year of the event. Make sure it is in quotes. +city: "Warsaw" # The city name of the event. Capitalize it. +friendly: "2014-warsaw" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2014-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Warsaw" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-warsaw-2014@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-warsaw-2014@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-amsterdam.yml b/data/events/2015-amsterdam.yml new file mode 100644 index 00000000000..92d35323b83 --- /dev/null +++ b/data/events/2015-amsterdam.yml @@ -0,0 +1,59 @@ +name: "2015-amsterdam" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Amsterdam" # The city name of the event. Capitalize it. +friendly: "2015-amsterdam" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Amsterdam" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-amsterdam-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-amsterdam-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-austin.yml b/data/events/2015-austin.yml new file mode 100644 index 00000000000..5324449c661 --- /dev/null +++ b/data/events/2015-austin.yml @@ -0,0 +1,59 @@ +name: "2015-austin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Austin" # The city name of the event. Capitalize it. +friendly: "2015-austin" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Austin" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-austin-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-austin-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-bangalore.yml b/data/events/2015-bangalore.yml new file mode 100644 index 00000000000..1d9ba0acfc1 --- /dev/null +++ b/data/events/2015-bangalore.yml @@ -0,0 +1,59 @@ +name: "2015-bangalore" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Bangalore" # The city name of the event. Capitalize it. +friendly: "2015-bangalore" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Bangalore" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-bangalore-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-bangalore-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-berlin.yml b/data/events/2015-berlin.yml new file mode 100644 index 00000000000..ae05de8b1ec --- /dev/null +++ b/data/events/2015-berlin.yml @@ -0,0 +1,59 @@ +name: "2015-berlin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Berlin" # The city name of the event. Capitalize it. +friendly: "2015-berlin" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Berlin" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-berlin-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-berlin-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-boston.yml b/data/events/2015-boston.yml new file mode 100644 index 00000000000..afe4663197e --- /dev/null +++ b/data/events/2015-boston.yml @@ -0,0 +1,59 @@ +name: "2015-boston" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Boston" # The city name of the event. Capitalize it. +friendly: "2015-boston" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-charlotte.yml b/data/events/2015-charlotte.yml new file mode 100644 index 00000000000..7411983e198 --- /dev/null +++ b/data/events/2015-charlotte.yml @@ -0,0 +1,59 @@ +name: "2015-charlotte" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Charlotte" # The city name of the event. Capitalize it. +friendly: "2015-charlotte" # Four digit year and the city name in lower-case. Don't forget the dash! +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: 2015-01-01 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2015-01-01 # 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Charlotte" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-charlotte-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-charlotte-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-chicago.yml b/data/events/2015-chicago.yml index eb0911dcf1b..9f7e476582e 100644 --- a/data/events/2015-chicago.yml +++ b/data/events/2015-chicago.yml @@ -1,28 +1,59 @@ -name: 2015-chicago -year: "2015" -city: "Chicago" -friendly: "2015-chicago" -status: "past" -startdate: 2015-08-25 -enddate: 2015-08-26 -coordinates: "47.609895, -122.330259" -navigationelements: ["welcome", "contact","location", "conduct","sponsor"] +name: "2015-chicago" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Chicago" # The city name of the event. Capitalize it. +friendly: "2015-chicago" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Chicago" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-chicago-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-chicago-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: chef - level: platinum - - id: datadog + - id: samplesponsorname level: gold - id: arresteddevops - level: media + level: community -sponsor_levels: - - id: platinum - label: Platinum +sponsor_levels: # In this section, list the level of sponsorships and the label to use. - id: gold label: Gold - id: silver label: Silver - id: bronze label: Bronze - - id: media - label: Media + - id: community + label: Community diff --git a/data/events/2015-denver.yml b/data/events/2015-denver.yml new file mode 100644 index 00000000000..0a12d719626 --- /dev/null +++ b/data/events/2015-denver.yml @@ -0,0 +1,59 @@ +name: "2015-denver" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Denver" # The city name of the event. Capitalize it. +friendly: "2015-denver" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Denver" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-denver-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-denver-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-detroit.yml b/data/events/2015-detroit.yml new file mode 100644 index 00000000000..a0cfa49fa85 --- /dev/null +++ b/data/events/2015-detroit.yml @@ -0,0 +1,59 @@ +name: "2015-detroit" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Detroit" # The city name of the event. Capitalize it. +friendly: "2015-detroit" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Detroit" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-detroit-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-detroit-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-ljubljana.yml b/data/events/2015-ljubljana.yml new file mode 100644 index 00000000000..6af84eec85d --- /dev/null +++ b/data/events/2015-ljubljana.yml @@ -0,0 +1,59 @@ +name: "2015-ljubljana" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Ljubljana" # The city name of the event. Capitalize it. +friendly: "2015-ljubljana" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Ljubljana" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-ljubljana-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-ljubljana-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-melbourne.yml b/data/events/2015-melbourne.yml new file mode 100644 index 00000000000..7792e859f0f --- /dev/null +++ b/data/events/2015-melbourne.yml @@ -0,0 +1,59 @@ +name: "2015-melbourne" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Melbourne" # The city name of the event. Capitalize it. +friendly: "2015-melbourne" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Melbourne" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-melbourne-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-melbourne-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-minneapolis.yml b/data/events/2015-minneapolis.yml new file mode 100644 index 00000000000..3f17233d4f5 --- /dev/null +++ b/data/events/2015-minneapolis.yml @@ -0,0 +1,59 @@ +name: "2015-minneapolis" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Minneapolis" # The city name of the event. Capitalize it. +friendly: "2015-minneapolis" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Minneapolis" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-minneapolis-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-minneapolis-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-newyork.yml b/data/events/2015-newyork.yml new file mode 100644 index 00000000000..c992118a9aa --- /dev/null +++ b/data/events/2015-newyork.yml @@ -0,0 +1,59 @@ +name: "2015-newyork" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "New York" # The city name of the event. Capitalize it. +friendly: "2015-newyork" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "New York" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-newyork-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-newyork-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-ohio.yml b/data/events/2015-ohio.yml new file mode 100644 index 00000000000..9f75e49f69b --- /dev/null +++ b/data/events/2015-ohio.yml @@ -0,0 +1,59 @@ +name: "2015-ohio" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Ohio" # The city name of the event. Capitalize it. +friendly: "2015-ohio" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Ohio" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-ohio-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-ohio-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-paris.yml b/data/events/2015-paris.yml new file mode 100644 index 00000000000..96aaaca13fc --- /dev/null +++ b/data/events/2015-paris.yml @@ -0,0 +1,59 @@ +name: "2015-paris" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Paris" # The city name of the event. Capitalize it. +friendly: "2015-paris" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Paris" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-paris-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-paris-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-pittsburgh.yml b/data/events/2015-pittsburgh.yml new file mode 100644 index 00000000000..2f657ba32bb --- /dev/null +++ b/data/events/2015-pittsburgh.yml @@ -0,0 +1,59 @@ +name: "2015-pittsburgh" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Pittsburgh" # The city name of the event. Capitalize it. +friendly: "2015-pittsburgh" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Pittsburgh" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-pittsburgh-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-pittsburgh-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-siliconvalley.yml b/data/events/2015-siliconvalley.yml new file mode 100644 index 00000000000..a59f9e7f366 --- /dev/null +++ b/data/events/2015-siliconvalley.yml @@ -0,0 +1,59 @@ +name: "2015-siliconvalley" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Silicon Valley" # The city name of the event. Capitalize it. +friendly: "2015-siliconvalley" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Silicon Valley" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-siliconvalley-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-siliconvalley-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-singapore.yml b/data/events/2015-singapore.yml new file mode 100644 index 00000000000..10782aaae94 --- /dev/null +++ b/data/events/2015-singapore.yml @@ -0,0 +1,59 @@ +name: "2015-singapore" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Singapore" # The city name of the event. Capitalize it. +friendly: "2015-singapore" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Singapore" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-singapore-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-singapore-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-telaviv.yml b/data/events/2015-telaviv.yml new file mode 100644 index 00000000000..a2bf47d9d4d --- /dev/null +++ b/data/events/2015-telaviv.yml @@ -0,0 +1,59 @@ +name: "2015-telaviv" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Tel Aviv" # The city name of the event. Capitalize it. +friendly: "2015-telaviv" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Tel Aviv" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-telaviv-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-telaviv-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-toronto.yml b/data/events/2015-toronto.yml new file mode 100644 index 00000000000..ff3fdf1d4b2 --- /dev/null +++ b/data/events/2015-toronto.yml @@ -0,0 +1,59 @@ +name: "2015-toronto" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Toronto" # The city name of the event. Capitalize it. +friendly: "2015-toronto" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Toronto" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-toronto-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-toronto-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-warsaw.yml b/data/events/2015-warsaw.yml index 6593207f31f..b1df7d1ddc8 100644 --- a/data/events/2015-warsaw.yml +++ b/data/events/2015-warsaw.yml @@ -1,26 +1,59 @@ -name: 2015-warsaw -year: "2015" -city: "Warsaw" -friendly: "2015-warsaw" -status: "past" -startdate: 2015-11-24 -enddate: 2015-11-25 -coordinates: "52.1800879, 20.9788363" -navigationelements: ["welcome", "location", "register", "program", "ignites", "partners", "contact", "conduct"] +name: "2015-warsaw" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Warsaw" # The city name of the event. Capitalize it. +friendly: "2015-warsaw" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Warsaw" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-warsaw-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-warsaw-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: allegro - level: main - - id: uniteam - level: platinum - - id: kainos + - id: samplesponsorname level: gold - - id: connectis - level: regeneration-zone - - id: codersmill - level: sponsor - - id: eventory - level: partners - - id: kamea - level: partners - - id: teetbee - level: partners + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2015-washington-dc.yml b/data/events/2015-washington-dc.yml new file mode 100644 index 00000000000..4a73e1dd477 --- /dev/null +++ b/data/events/2015-washington-dc.yml @@ -0,0 +1,59 @@ +name: "2015-washington-dc" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: 2015 # The year of the event. Make sure it is in quotes. +city: "Washington, D.C." # The city name of the event. Capitalize it. +friendly: "2015-washington-dc" # Four digit year and the city name in lower-case. Don't forget the dash! +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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Washington, D.C." # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-washingtondc-2015@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-washingtondc-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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2016-atlanta.yml b/data/events/2016-atlanta.yml index 3c458fc42a1..3484bed8b08 100644 --- a/data/events/2016-atlanta.yml +++ b/data/events/2016-atlanta.yml @@ -1,8 +1,8 @@ name: 2016-atlanta # The name of the event. Four digit year with the city name in lower-case, with no spaces. -year: "2016" # The year of the event. Make sure it is in quotes. +year: 2016 # The year of the event. Make sure it is in quotes. city: "Atlanta" # The city name of the event. Capitalize it. friendly: "2016-atlanta" # Four digit year and the city name in lower-case. Don't forget the dash! -status: "current" # Options are "past" or "current". +status: "past" # Options are "past" or "current". startdate: 2016-04-26 # The start date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet. enddate: 2016-04-27 # The end date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet. cfp_date_start: 2016-04-01 diff --git a/data/events/2016-chicago.yml b/data/events/2016-chicago.yml index 61f9d7c4776..1dd7918cca2 100644 --- a/data/events/2016-chicago.yml +++ b/data/events/2016-chicago.yml @@ -1,5 +1,5 @@ name: 2016-chicago -year: "2016" +year: 2016 city: "Chicago" friendly: "2016-chicago" status: "current" diff --git a/data/events/2016-london.yml b/data/events/2016-london.yml index 004911193dc..bbf62e28b18 100644 --- a/data/events/2016-london.yml +++ b/data/events/2016-london.yml @@ -1,5 +1,5 @@ name: 2016-london # The name of the event. Four digit year with the city name in lower-case, with no spaces. -year: "2016" # The year of the event. Make sure it is in quotes. +year: 2016 # The year of the event. Make sure it is in quotes. city: "London" # The city name of the event. Capitalize it. friendly: "2016-london" # Four digit year and the city name in lower-case. Don't forget the dash! status: "current" # Options are "past" or "current". diff --git a/data/events/2016-losangeles-1day.yml b/data/events/2016-losangeles-1day.yml new file mode 100644 index 00000000000..8dc6fa6eb40 --- /dev/null +++ b/data/events/2016-losangeles-1day.yml @@ -0,0 +1,59 @@ +name: "2016-losangele1sday" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2016" # The year of the event. Make sure it is in quotes. +city: "Los Angeles" # The city name of the event. Capitalize it. +friendly: "2016-losangeles-1day" # Four digit year and the city name in lower-case. Don't forget the dash! +status: "past" # Options are "past" or "current". Use "current" for upcoming. + +# All dates are in unquoted 2016-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. +# 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. +cfp_date_announce: 2016-01-01 # inform proposers of status + +# Location +# +coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Los Angeles" # 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: propose +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site +# - 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." +organizer_email: "organizers-losangelesday-2016@devopsdays.org" # Put your organizer email address here +proposal_email: "proposals-losangelesday-2016@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 + level: gold + - id: arresteddevops + level: community + +sponsor_levels: # In this section, list the level of sponsorships and the label to use. + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2016-vancouver.yml b/data/events/2016-vancouver.yml index cffbb40f10f..f6a5fed29d3 100644 --- a/data/events/2016-vancouver.yml +++ b/data/events/2016-vancouver.yml @@ -1,8 +1,8 @@ name: 2016-vancouver # The name of the event. Four digit year with the city name in lower-case, with no spaces. -year: "2016" # The year of the event. Make sure it is in quotes. +year: 2016 # The year of the event. Make sure it is in quotes. city: "Vancouver" # The city name of the event. Capitalize it. friendly: "2016-vancouver" # Four digit year and the city name in lower-case. Don't forget the dash! -status: "current" # Options are "past" or "current". +status: "past" # Options are "past" or "current". startdate: 2016-04-15 # The start date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet. enddate: 2016-04-16 # The end date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet. cfp_date_start: 2016-04-01 diff --git a/data/events/2016-washington-dc.yml b/data/events/2016-washington-dc.yml index 07306854d69..26844959998 100644 --- a/data/events/2016-washington-dc.yml +++ b/data/events/2016-washington-dc.yml @@ -1,4 +1,4 @@ -name: 2016-washingtondc # The name of the event. Four digit year with the city name in lower-case, with no spaces. +name: 2016-washington-dc # The name of the event. Four digit year with the city name in lower-case, with no spaces. year: "2016" # The year of the event. Make sure it is in quotes. city: "Washington, D.C. " # The city name of the event. Capitalize it. friendly: "2016-washington-dc" # Four digit year and the city name in lower-case. Don't forget the dash! diff --git a/data/sponsors/opscode-2010.yml b/data/sponsors/opscode-2010.yml new file mode 100644 index 00000000000..56703bb3e1c --- /dev/null +++ b/data/sponsors/opscode-2010.yml @@ -0,0 +1,2 @@ +name: "Opscode" +url: "http://www.wobe-team.com/" diff --git a/static/img/image039klein.jpg b/static/img/image039klein.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfa0b6ab918efa7a33b0bdf2b15637ad3160eb3f GIT binary patch literal 24846 zcmeHv2UJr{)9?)_Ak_vcNKsK#q&KON2c(FA(mP@ZEr9?bARt6V1uKFAN(&Z1N>F+e zP(e`Xy*EKhsA571B>8TzJU-?9{`dL6|9j8*&*A3Wdv|AMcV}m3_ikp+4y}te1Z+K} zrK<%%7$ATS_ycIeJV#DmaCHIzeSP34001liGh{o!2&N$54}kCjo7d9-a2~?%!^CvXtFy&=-;>78IYCe#(!^u25*`0fI4utj>U-`?tusPk~4GcG6}6xs#l zDRdGEcZYlUpoL__C56mgJseSfXh2$0^0<99W()3G%Id8VvxF z7=E@xN@Dz(eh<>oFD3}%cV3x(?GNP8@BM*@|Jol=HsAS%$TR$`d*{@*>i*aV+TY1^ z24G+Bo4tlUz(AV?IM;K4<0Y^L2(1^m3b3=Vuxw#r-?D{$8yhRzHf}CW zzrfIPJWp~$4r$&uaXk6=zo7T3FLLzO)TsU;w$@w9XSV(`LDK7WPSP-vn~twSUKE>B|v2 z=^VTtT0O|NJ{%G(c(YY^^q57U|}w`6HP6R`u=zXgZ;{zd7f{xy)emjIQp7kC216Fn+m9>4A1?i@PM^r2|reLWl+O1FOiaLf5bO zV+Pr_Jj@kLk=8FVG%{=QD?Vm@JVxxM0m!m_Zov->UVUA&CJp4{F2Lq0M3XIQYI?P% z2-)|vpFZp;oN22-$2rk}u?p?A&SjLw$y2(*kw%fa!VjKB>K;5I9I5*gKm%w^MDe26 zgrnlXWoQ4r`GfJQ^)?D;$ob7^83VDR+o z5&ZlX8`Rbd9dhu+^(#RY6Y(YXnak4|N2hqlrK06hyA}q00#~tvF@o;yyX312%`M&r z0vct5QCf#EyK=rl%nj~mmuHqVYQjc)hGaR>`77io8qg*-8_`mt>d!5mY1Ua%aYk_( zfjgvHnn_xu0g2h!2#Vjt6t7_{!TPQXOa_ak= z9Pp1GrpTgQGsFx1Z+UtT(ttBL-fHP81r_>BGusX&;v!t{S$*nNm7YnQ1CjWrw{0#a zSlY?eW0hSd6?Z^uD?d!E2rhFyPj)uI_XtGWEo$%*N?bjKIB=)3^7E%rW5qI8ZI`CY zKM20NV=G34-?B9{3Dn-?^Hsyix!*U~^q3U}b3g9tY@C6raNpW>9;Gi4=xfpJF-*fm zoGmp&o_c4oKl~(i7}=F0cv*k@_$Slbn`i*^+GR}|(5X~tTuTEQxlX?RP*7)XYMHh? z@O+?tra07ZqHLcQzpYHFYQ?;ui~hE-CJt8Jh_-~p5kfLvap_DwpO%~k^0<2>CDXUy z>{}|1}P(b)TH_H zb;cJ33bIAAO4v6j94b322uFHBOgGrK+l&7aZ1|7~zf^=TI=;`GH~XQUZ6qKb7@9v_ z!`V-Ss*PifDhAK^X;w?P<8v1K29E9O*^A9oHPi)FFvu?Uvs7^5OkvB1$@0sY(}6Dj z9$l?287t8D-V4|?KS{fbG7FK*&G`}1GK6p8l-u-Q>6K>PxxXy!p%xA zjatYnQ~NT&seUO{aj{d-Z z)RelI)#>xu2EH;w+0^(gJwYYfX|oPwJ_K5T1`tmNnbH77x8SfRT{VQ={vz%QQjIh~ zTk;FVErCa2tsQPu5-V+8xIcZ4G5l;&#I}*r2^t_m4uhV9+c&?c*b0F>9(c+uIJB^N z8bxtuH7#*HHc!Rt?wI&2Q+_v@2CQZq(|~zl!yc2|l|@VKh4>b08sK3{FpJ{0@DRRU zJDL5sz3c^|{D$kMotoR}QwK_GA@(iKzPqp-e5NR|Q1806c-k`?L4gcavvPTBzMKH# z-Zsmc<%>4g`rsg^*vjQBy-c&3&oH^yDz_e5wdR$cg<&;2D+KpdkU78=z*;}C_Q}GM z)2+RG-18kRd6m{~^9^v30tR*&)X{)Kfh&t6yc&Xb$BT*-7t8O4&Gb!9QqrTbX6^Yg z9%eFD;st~*=BD72?OdyB)Lq;fwgD}MaAAbGHTHk>XvjInAlCXl~8k_PyWOO6!XU!ei6Q}W{&1axXQ zk_LqQM#`h!Q59J(Me~#HC;q_S74|trHG`==7Qg`)rdzy z6SlJvPbcL_XXcsogFi71H3%0x8FMEimmE6{mkm$7aGsP#nq?I7j2z2r=Dci`3-S3>xsZU(sbG$aOMY zS-zwsv=A#~0zJ_SK!>5u=f>=50DpW`i;sl=gkuX-Yg{fwo%c1W0E@R))usW%ab>I1 zW?!n&>HT7`DxSQMFFkYpU5(CEmSXX!&Ymd(dtQr;2L7Ddn?lm7n>{tNG=MEm>mc@v zS#ZE4;=Swk&eeo8nKWvv@l$0&Ud@{lY3VqD6t&_0_98*D__aog6S?1x+v#os9AjVT zt7SV_KayR|oJ(zkcMCp#hgyT}& zp3}P+YBdf`g>|VW8FZ3VqNzbK%4AXKo0c0d%y?SBny;HD&aJA%oWX`L2Lu2CYjP|E(6k7-5sEDAu zH4W#2&1p!=$d?sJ4{{KWG&H8QlGr1T&k5+o z6HHM%zpha;;M6NZGR8#rRu+bYV}4^5S)sB~+1Nc#9>!^S0s(1tyzzZQ-0{As0xM_ zpgrGnN2sK`d@O;a&E<*6a9%8gp6{9(H2o58>}R?v(wjXin0ZFHJYy4A!C7OrAk-4k=v+~9r;?n?*CzyrpgbNdQm)!dV04ZQDJ3h+O+6ij*1O}%4~nbReav=yrK z@WR^Qyhk@WI0PzR)uJP7e)E9#4he#qXdkLFhyPG@o6miTk8pSBm%Ec)?KI#`JN%Z& z0fPP6q=IOThckJhcOYEH%M`GSlg?*9fXi5oZMB*K|5f>%ma(c_vscoF6azz3ed=;NwR2jb|k91`3KSnxm!ZwXs z8}pJidzuSIz)xqtYlQW5%GInCqivwgZ69gC^LHU_)TAI=!ai!02*c8ZSWQ9_Zkbuo z(3#|W;KVFXGvBU6RcD2%U3%#mOf@zqInfu7c?IiNtZp%Tms?P9<5D$8rppij)i!kp zD|2g{ERq|}Ay`Ye^SqL*&O+>uZ5SkUWcI4R7hBc6slGU}ATTmRQ3-;MN>yk~KILZ$ z`GCwS}s;d-AjM8!>MYrI3X1e+E{ti@Wx!4=@yyS=NK8242E*Oq~?%y(P-RC~*B zLABmJB?+clMv;;!`qLD9=AE5-;bgspTI`g5v2uVFSxHwoK9$x+oSxQl8t%X4Am&~t zHZWji*qn{4#SbisE2oc-4K=w;$(Cd=PKh<(vyLw^S=7W7lV(?y2dYuvj^c9GuoMuc z6w=KgCe&Kh-X0LFsdPIwQ6;e{cw|y^d8uuz(jD>i&Fd*DIy%L?Jv^h^L%brjX`ElL z=XH(XEkf646N(l&3p=w-kS$9vabl~<;Al#`_q@)-FWx1BC(CQ4$k$=L#;$#2Ps9?i#DUK}G%{Pz^Kg6y0o5$gc)}yq z*D}P2Aj?5kpXyRujy_<8+@7_APN7burjHgL9RBpN%G@1=7HD1zm7TFEeOdl;NU(iD z3l6)vpw&qOocC8yc9)%+_U)2mz1Dvu9Ooh(cerPw^Zt0~6r&|K>7sV?UbSlapA09$ zn_en{Cq?i~%A!Zr$G*3++r^zqg1ty_wH1}(*J(fosc0*+YH3hyVk7zfO*{9j+>;fP zE{6)SO^d}^=U(Zo6n5iWWZ-s5GP6muRP(R$$XseKDe9HYbReER>$M$wY+XM1KN8uE zqHO+9kxDuL8k$sAd|U9*g)SNp)xL^tI6aqnCzCaxf&bymUZv`Q{EOBI1#o{L$MG9d zeh*oBpvGnI(o1kNguXX@5gDxUPAu(nv$QQEIP&pw=B3Zic?4Y*2Auin$(lWl=!H424@F)5*WSFr<4L*pO=NfHHS11pk|<%o z(4KIN&`sLb;$=%XbBx!qZ!n2cadMeBvo_cSDy4G<8G$6R5mGv?4|Mmyv)Z;|{lifu zg;>+wA%4q8-x-+@l2+}M9Sv+X?ru)PHfPPPanOJ-H{Y3cBKY9WXdB_3q!+YylF5&M zx27dwUX|JP33Yr`=xOCTtfT0W$o=mQ^UCMSN9X0p-;=M|)~#y_iwhgpt1~)n^0m@= zjjfUDPXh{Qzzew0lM)x!UH1CygXj=G$t|;nV}(ocSEu9l+VmVjhqVUbo`PE~6tQBl zU&lh9=Z(u@)Z@FO`>v1443@30!Ant+5$;YV{}qyoh7S>I_-jJivUpXu_g{ zEmw3E@g~ChwY$t(x+n*{g7mHnxka%KrWdba)hwI7h9E z)siyig;uj31pNUcOBTrvyo4jS2R}I^6x^v)|D@*l96MQBwY+UOrgXB47m5j?Qb)C< zGF=dwz)c*js;Zwh&1TFoS?&hGTupB?=WI0Kl#_FW-zU+#` zMiQQ1R``~>-5Jtmh451&M0K@J?Eu^g_$Q2tvG}bdy6bHXuqa^hr8spogPN}uwGF0h z?ldXbmM7PM#@?d=Uz_w5xV4$#y&O{EXUX>E^MS!%kAmw_#TU1I6pj6^7!83!7R-$Q zA*gRk@oirk@VRtCG%7nkJM&ym^`(wHPoQa2p;@iDDW;)$(}KSUxxvUF@~{!uX&kMS zWD@f+O*obC?B9MpnEGrIX-qQG`{hOJrp@p!|8A@WZM4Ag-*oji(apX9u=Ts8@aKz; zW1LyfZvAdDW%%)4FL!7i$N94W0KEi!tC3?JMmNCR^amo4c+hz z0mOcXtk<~=<^fQ>0ovbQj1zS9-=b*$6WqFFSm<@H%O31E!-;SAcPR>h7+~Fy{Y^f+ z^em$x`1sZzdKLiaMsm7TH~?3`9dH1g0XQHD$N-7}0ziUkSHJ_r(oOb%zJ7(#YxrSq z|4H{N!4DvPSiZwOFi0erqk9gR&Z96Mj%dU4Zm{3+Mlc^KFh^Gdzy$OTAWqX<-63^^5TT2+>D7!~XzbazOf+I5__S#tDNXktXm9 zKDuZf6aCZYQ79z6LY5!kKM-$mL3szLBVC<;NQ&!Q=XHL7!II35a3=>0(g#d#@r8T) z{0+I;5AYw!+0Hv_ppYo8}6kI_tJ)YX~Vs=;a=KsFa7`SUixMu-3MAh0l*);L8~bMnn2Y7 zM*sz!2VD_Dz!|^=O#6U0dOhU{!cMNcDcnK42Z*8D_xJweGD4ukLmYH_&<(Ncmf3F} z5@!100y-bG;oTfAK0cmG5)vM0aR>Ub1#uY4UE+d+r-YQaqy(S>z2NBpL%@B6&ci{^ zfU3w`X@!W8tD~xjxtzYFzNZG<#Z@Q38*Ut6U;+z3z!V)tplYlt7nClzd%DAY9E2{o zBR$Yc7gR;oD^~*3bg+bo&^n0^LRG{<|BR3iXm3Zj`q0luh)EwmCgkMp;12ggc_W0R z#N|c63cVejl#DdBzE=n4R7Jk??dRtw?k6LT@^+SxQdCrwkd&5?mKFmk#L)g8J`NYe zJkSTg*4Ei@wfI@=58ZXOSnn;^5UbF7Q<`uz%-hw|#}(xvL~q&w^yB!bieNCVj!JTp z3W{>_(l9ZYB3xcfO3D!?<{)!iR?NZ40WNdi@w}`e%u$3@=zEiJ@CeG^H%iC+XjVu_ zg`QPfx9=N+5{IkFN-N4L$}31K%Be{F83)$>jsA@51vt_|(-k~jf(Ch2la~EK{b$S{ zi&*|rL{jp51M5Y8!GN-mpm+WkVf-%$$n%%6{KKGt2v9sS65y!(XBhc$T<7nH%ku~N zmofVZQ_^uo`=Gr2)l?+@3j5En@8jz9FBFZA`GskERta?Kfd`Tt=nAeTr6Tbc7+qb~ zffhz^Gzy7XCsdG@_(A(C_$RI9-_!mI{z>~gsi}vnkDBy%9{vRW&xj6O?f!nue=LJ^ z6%ls^jVqa0nG{QsT8zfk@x z3@)3F4n7Y5R`FkHe^ju}I_Opems+*;V_W}+18To?<9n(9*l6hM|M%nJ?!LY%tPhF4 zzLF*ihM}LY)74b__LXr&!N7(3_nG*8$v*$zE!pec{bObSnf^M$es-dy|<1qB`1`(yMvFKtGk0UT*A#0?yMs5JM{1Q{kDjMA5ZWzD)IBfOxNiD z{cEFmNzr9}#b8*M_+Mkp%t`@rHJ7 zi0dCo;2#lhXxE0g{*eU!5%K@6cCr3$+J}39_Iy9kaR0XveYS%Ec(!tKZ{5l*uw&Z} zfdjnU+`I?&@1kG(|DAw5kexer@a*B?+qH}De-hE>JwWa0%P@&3Ok=gkQd-|E6l;BcT=Dz7j8)a&)^A+FEMiUFp)bmM$ z_#j6?#F1AQSZF}AS+ZMTUd%!5jo;iTIY}IacaXBXz_a|N&#M|Hb5yEpleu$t z>l$tzb*haZ9I2BAo&Y;VKL+*y47QUD#@RXYF9A4O(^Scwg7#3vWXt>OI0o~0c)tOE zgQC!9r&4pd(d*LKR_F?N@)yzS0kq9)PMFKZv}Su-leOfi279qajVYIn-`cl%XQ|wb zz2NT7E;z10yqSiMhgTJ?M78&mu)M94Z8nwmW1%{HWrM?3xzprQ*lD?09LM895>K*& ztc~wgv!Gh_vhBl^G zg6RD0QQ4Mjua#=H2XcVNcPnhJ-JJxAcYcN&VKorl{FkMu=bNhD2M6Jw5X!Vm)!p5D zhOhxNz>pZolcJzq=^m${P{iSP97j%w$_m-VT9R>zwv6X?t~Cwb zAg`KqWu%XB#{9t%z~r^;R$1edte_nK5@_e|0boR<=9$3^{&`XEnZrhCkHs

zCss*d7)Kco}9cC4qluvGRogGX=jSaQLVM@ujlo3_AWv`%}@rZtl< zec?QNko-Lraj4fvo*S>V21E2!-TpRK)3=C2zXWgk9!F)Ci;bsOK7WHLI?r0eqRlv4oW_;?s z8iYGMBP~X;s%OJy6AtaPcyoa35Kak6+Ko+{eBK!$GT+|%H@r4vOOZdtLR+XZ-37%b<$FU zEp$?RyKgOa2D-N2Z_*xsgR)5Oia+FtLJHWy0z>=1^c5$Vz?@8-$b~0{7*33ST zk0;k(Fusu@OmaNFE#>jaCWDC7Bl~W7PxxNzH4M2vNPc#1NHgTX2cSUnID>NdDq-8Z z6nL(6MWmilvZaS`+H~EE2@5d+9xlorD{OvG1)UezJkj_g0O`<7T65$NNa(u)d;7?ecZQry^D-j zwvmVDw)%mAA=s;!hAtg^=pp#=-3KWutbIDBq|~C-x1N9cqtjwd;hK!8Z?kP=aIHqw z#I$t*ZWV<#L3FXsITr~$w(v+U?L7w`mc1$d-anJeJdLsII)aiC5SEqEx|q8|!M^|H zBqgu2ZLwnzbtV!kwTh$UnKowznI~`=7X+SgrmTFF|HL1;W_@5OXD)n=qdZn-GJk{& zJ(EjbB*Rv9P}ML#5uWr$nOI<2B$dv%!IPo3F{jS ztidB_Kw$425e$xGTwt&x3@rc==&6!3tpLR*rumfsHt%Kd2j6pwoXVo&UQ1}1*{%d3oyR2y z%;C=l(%QUq@FOQ=H|gxNubSG|z)}7ZGPYANyw#qeFZB3bp+m=ayW<ODWf<(eRl!8U`JH+>utO#4M@SGJJmUW8Lmopu&b=8NCrJh?k4i)@-+ zaJ_rqpmV9+G1p{*+>A!62(`tcQE5&J3>nwdAA-=meYz8}S{Mc;nub_@J(jW}o3*7LfBZ2%)9RBt$wHn3>RmxZ$S8~V#m6Er1wB^s zWYbGv5P{z^tk>FgIznv+)*?m(os*r(j-%4}($qB$k6wG|a85s!LrKK+8d3Z)wwo-P zPyl}%=e%^cF{M}=Q<`42v+?`w4%3f?TUtVtSf-rZthVuh^mG&TMZ6?A11~ z2NAMonC{49vvRgwKX`3+)@Tcg zj=8C>yL~nJFHao2b8cA?j6JyNz0J@RWcHXqhbpN}<#{z9xDP4JG;^DhQz@v)(@SvD zD0P8qhZ=1Oa2jp0;T?V%%5!6_OHiK%)M|3)REJn!-V_)t_^P<)Ygd!-2Yk}K!2WwL z9C|99a9SxhSICBBGmEJ7g!F4jVXo_Q2W4yxr&%*Q!AY6zxRo~mktgqBI!nY{zAq?AMxjM0| zE;TiRnqE)j`))FQnyKHLlCz2<8dNVrb_k5CSvsXCeqlM17G0lQ*g7K~nipQ5k9&rw zsIwho()n1KDulgyPGn?dDhz!-G?%iY>LM4_rv#P3De^2k^{c>Qc!Z8eDqJ|yV0}{r z?t$88xkW4Dy-U&tR6ie7ROEiwUL;9@CR^UsC{J)J(0{qFGmne?W+B(AS31?gMNY9& z{oM8)ma|Ct{?xoXm215_SnP%rGha^Bv29uqAT+MTwUk6Sgy(!xExYj^{D3?zv(05Z zSgqZC>?`IB7>b9els@dx`ctkI3uZ8a-$p}BU@ zg`;;o&dC4<8FmCt?bA8g#IS=E9RiEu@JCVd*@P=K9Gr1Q)F(dEJGGs?qVq1LJ37Gn z7AQ|WUBjm;x(SMAH9WTDQ~m4$Or|+@1CFa&746=;`VPgHk{S21i7N5uhabwDEr0hL zH5`4ck8egI2**l5O;j}6p78G<@PjS{8iz7I=H2>Qn-pSdb~)=yPwkmTHCmQ*#fs;L8*~Q-l&+9BsELI!+Awv0!W_b*(DO@Niwo zE9Km2Oep!mo&0AF85m_D0(|zXgjKOEN8RI9Ik~2facddw*vSriqlriPcAt7`r(7Ue z3_dQ@QzlAJ%?-jc(U8%6w-Hi_hi9g;`R>i0;`nJvb>=sGyRexoP;H|q-y@&q1A_4n zralnsO2z{)D+&__q_0b-7!5wQxIDg=Y?bcRbE^oS!@LmxB8+!&%NvJtyPLZuU6{`A zFh_&4rCt&{mu?{0a@L3~NxpT2Es2b$0m7ldr0@fCHszR7sp$hTC)i$+%XCwpo_`tU z(VQXV!+5eO$Xa?#P&i8Z)tO{!{g4bmP*&fyhRu`&gzu$ z$=fRJx2rGk00<>W9s54Z1#vQN6Au`3ZoZMbW-CGn*Q>7XF%{>>~tX(e-kKUkJF#d6va? zxX=iaIC7r`*qnFDm{#)UqU>8rji3QW&tyPdDyx3IV7%GYMut@8sFe4 z0$Nv|POAD0*Fw`d-oChTMCf{0PxGr4wV#9Aqi*vp2vq@Indgo-;b4C$xexpwc$B^c z2IH*EawF@Myr;UIuDW${TA4nGG_D&Z&ZcSjzGP2V=j0I7>!krqa}@6L=>hlCl~Ktg zK}Eq8lJA!Ijv|dqp7Tm650|qxf8NtBwGtE5N&|w;_OyM0nQK>Z=TYM>eHE|C#1XDS zyC{-0pvNibz2}23%=;+DTZ6rzKw5A6?oS+;;vv`1U}#G3$+%XfK()Ja*fB7mr^($T z$xryKPt0>{*?qs=#_({hQuLXdk0wI~*l9qkRhdMp^b=%>dk!Wr->QJ8(>fm5DtozK zQ_t6AKr8DAOUGE7{&YOJ%bD70SO1CiL&a8KHqRUCK_`-o1ndu_nmf*&6IG-fAw8N88E@bRIGa)3SClv7B3h;{&Yput z$zHSG<}Ob-w=6KSs&fZ}r+U;YON|6#8y9VI23zdU#s~7-$2dZ*pO4^LWZGP22hO~B z;y$oPUSZ{9UGP`VFI4A(QTE>Sf&#_6oIMiY+YqLeUEw1aPq140`nlv zutT!Gp=a0f@=dRV@!t)pymAA95Pl?+9wN}o_wu1<+u^d=b60|Sbq({cA&^0_L9DBd z;->cZc_ht+5=1#h8^^JoTNhA0EPmJVD!ApDih5HpE+usvl43C_Z|gj>H+lm4h;tU( zGNVICA|98uzolU_7Rr1H3DZ;z1!Jn>!Kh~i7DL0MiLeLChhYti3DLo;STH>C@D zo%+eTjO{s($qq%>XXjd1ky?n5OG58ecAhC&*Q+Mb;Pj_J$;WVGHvV^DLx~Xw{6CY^ zUU|5p!uGN4#_7oQC?yB!r{^cd3)lw$O~4<+gn#sb|Q;!D`U`&93IKqq|jv(XoDYB z{h;&!XemeyJ9`dstk*KS)M&7uYUHJ1*oscPSch#ply)0Gi`b-qi`6|1_Ar#z{8tIx zOXTp7&(ndPz6e$27JiUxvlqgoK9s61r+PJ3XGbkR5u3YugV~WQ*#gRp9ldwTF$xx} z8GVy|Iff%GPQO8UMjGq0``oE^-Gm@9-XgL)1+-(+>!y(;ox4y?{StywIKaHjVNAn&$60Q%lV~lm&Iq~>R z?2c!V(O2gqZw++F7WZv>kXn|BEFEPQAwT!R#1@hDDb3)rnnz;VRo45-w&w!)$F?P` zJi@QlOHJd%6^p{=^b@0B``wKaBYu4XShBMC;_7aenHUymRl?+k6})i zz>BQ9I+1w!wxFc)ihihWMb8@XE=;=xKXjq$v0KUq)1iU+xq1DO744-5LH2ofqONoV z2Zr5&dflwG;svAptOuyN1YCamLot8<=hQm8-EME>si1cUhd&6X_8I-7%;9zFS1)%C k+*c;NIw|~MH4I?k<=PYz3NFfCx);24k1Xx{YlhbSUsz^}4FCWD literal 0 HcmV?d00001 diff --git a/themes/devopsdays-legacy/layouts/partials/past.html b/themes/devopsdays-legacy/layouts/partials/past.html index eca3c53a99d..9c937378018 100644 --- a/themes/devopsdays-legacy/layouts/partials/past.html +++ b/themes/devopsdays-legacy/layouts/partials/past.html @@ -9,7 +9,7 @@ {{ range seq 2009 2020 }} {{ $r_year := . }} {{ range $.Site.Data.events }} - {{ if eq .year $r_year }} + {{ if and (eq .year $r_year) (eq .status "past") }} {{ $.Scratch.SetInMap "active_years" (chomp .year) (chomp .year) }} {{ $.Scratch.SetInMap (chomp .year) .startdate (.name) }} {{ end }} From bb831851b4b3db22e7df74de68f1790128699d92 Mon Sep 17 00:00:00 2001 From: Matt Stratton Date: Mon, 2 May 2016 15:05:55 -0500 Subject: [PATCH 2/4] Add 2010 Hamburg --- content/events/2010-europe/conduct.md | 36 --- content/events/2010-europe/contact.md | 31 ++- content/events/2010-europe/lightning-talks.md | 17 ++ content/events/2010-europe/location.md | 11 +- content/events/2010-europe/places-to-stay.md | 13 + content/events/2010-europe/program.md | 223 +++++++++--------- content/events/2010-europe/propose.md | 37 --- content/events/2010-europe/reactions.md | 43 ++++ content/events/2010-europe/registration.md | 13 - content/events/2010-europe/speakers.md | 52 ++++ content/events/2010-europe/sponsor.md | 49 ---- content/events/2010-europe/welcome.md | 45 +--- data/events/2010-europe.yml | 45 ++-- 13 files changed, 304 insertions(+), 311 deletions(-) delete mode 100644 content/events/2010-europe/conduct.md create mode 100644 content/events/2010-europe/lightning-talks.md create mode 100644 content/events/2010-europe/places-to-stay.md delete mode 100644 content/events/2010-europe/propose.md create mode 100644 content/events/2010-europe/reactions.md delete mode 100644 content/events/2010-europe/registration.md create mode 100644 content/events/2010-europe/speakers.md delete mode 100644 content/events/2010-europe/sponsor.md diff --git a/content/events/2010-europe/conduct.md b/content/events/2010-europe/conduct.md deleted file mode 100644 index d1038fb1dc3..00000000000 --- a/content/events/2010-europe/conduct.md +++ /dev/null @@ -1,36 +0,0 @@ -+++ -date = "2016-05-02T12:42:53-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/2010-europe/contact.md b/content/events/2010-europe/contact.md index b2e0d0a5a21..e56a2d24b01 100644 --- a/content/events/2010-europe/contact.md +++ b/content/events/2010-europe/contact.md @@ -5,13 +5,28 @@ type = "event" +++ +

+ + + + + + + +
Missing some information? Having a burning question? -If you'd like to contact us by email: {{< email_organizers >}} +Don't worry! We will take care of it: you can send us an email at organizers-eu-2010@devopsdays.org -**Our local team** - -{{< list_organizers >}} - -**The core devopsdays organizer group** - -{{< list_core >}} +the devopsdays Europe team (Alphabetically) +
    +
  • Gildas Le Nadan
    • +
  • Julian Simpson
    • +
  • Kris Buytaert
    • +
  • Marcel Wegermann
    • +
  • Matthias Marshall
    • +
  • Nikolay Sturm
    • +
  • Patrick Debois
    • +
  • Stephen Nelson-Smith
    • +
+
+
diff --git a/content/events/2010-europe/lightning-talks.md b/content/events/2010-europe/lightning-talks.md new file mode 100644 index 00000000000..784978d8e8e --- /dev/null +++ b/content/events/2010-europe/lightning-talks.md @@ -0,0 +1,17 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "lightning talks" +type = "event" + + ++++ + +Below you will find the links to the lightning talks presented during devopsdays Europe 2010, in their order of appearance. + +- Alexis Le Quoc: ops scrumban from chaos to sanity +- Erik Doernenburg: 10 things you need to know about continuous integration +- Fabian Lange: monitoring application performance using appdynamics +- Guido Serra: load testing +- John Willis: devops culture why should you care? +- Matthew Skelton: Culture shock winning people to devops +- Nikolay Sturm: cucumber-puppet diff --git a/content/events/2010-europe/location.md b/content/events/2010-europe/location.md index bc3027656cb..bcc4ccf1cd8 100644 --- a/content/events/2010-europe/location.md +++ b/content/events/2010-europe/location.md @@ -5,6 +5,13 @@ type = "event" +++ -Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. +The location for DevOpsDays Europe 2010 is the EAST HOTEL Hamburg - +Simon-von-Utrecht-Strasse 31 +1st Floor +20359 Hamburg +Germany + + + +
Größere Kartenansicht diff --git a/content/events/2010-europe/places-to-stay.md b/content/events/2010-europe/places-to-stay.md new file mode 100644 index 00000000000..b572379d1c9 --- /dev/null +++ b/content/events/2010-europe/places-to-stay.md @@ -0,0 +1,13 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "places to stay" +type = "event" + ++++ + +The obvious place to stay is the conference center itself. If you call the East Hotel conference center, they will probably say the hotel is fully booked. Luckily for you, we have allocated a number of rooms especially for the conference, but you need to specifically mention "devopsdays" conference name. + +But Hamburg is a big place, and you can also go other places. Here are some hotels that are located near the conference center (indicated with the green house/flag). +This list has been made for your convenience and contains hotels ranging prices from 25 Euro till 140 Euro or even beyond. We haven't checked them personally but googlemaps was our friend in creating this list. + +
View devopsdays Europe 2010 - Hamburg in a larger map diff --git a/content/events/2010-europe/program.md b/content/events/2010-europe/program.md index 627f0709e5b..d2fbaf10d6f 100644 --- a/content/events/2010-europe/program.md +++ b/content/events/2010-europe/program.md @@ -5,118 +5,121 @@ type = "event" +++ -
If you are new to the Open Space concept you may want to read some more details.
-
- - -

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
- - -
- - -
- +

Friday 15 October

+
+
09:00-09:30
+
Registration and Breakfast
+
09:30-09:45
+
Introduction
+
09:45-10:30
+
Devops for Business - Lessons Learned - Stephen Nelson-Smith [PDF]
+
10:30-11:15
+
Continuous Delivery - Jez Humble [PDF]
+
11:15-11:30
+
break
+
11:30-12:15
+
Kanban Fish Bowl Session - David Anderson
+
12:15-13:15
+
Lunch
+
13:15-15:00
+
Opening Open Space
+
15:00-16:00
+
Open Space Slot1
+
16:00-16:15
+
Break
+
16:15-17:15
+
Open Space Slot2
+
17:15-18:15
+
Open Space Slot 3
+
18:15-19:00
+
Venue Closing
+
20:00-...
+
Social Event
+ +
-

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
- - - -
+

Saturday 16 October

+ +
09:00-09:30
+
Registration and Breakfast
+
09:30-09:45
+
Kickoff Day 2
+
09:45-10:30
+
Squid Wrangling - Sam Newman and Chris Read [PDF]
+
10:30-11:15
+
Runtime changes are the weeds killing your crops - Spike Morelli [PDF|ODP]
+
11:15-11:30
+
break
+
11:30-12:15
+
Ignite talks +5 minutes of fame
+
12:15-13:15
+
Lunch
+
13:15-14:15
+
Re-Opening Open Space
+
14:15-15:00
+
Open Space Slot4
+
15:00-16:00
+
Open Space Slot5
+
16:00-16:15
+
Break
+
16:15-17:15
+
Open Space Slot 6
+
17:15-18:15
+
Open Space Slot 7
+
18:15-19:00
+
Open Space Closing
+ +
+

Devops for Business - Lessons Learned - Stephen Nelson-Smith

+Description + +I believe passionately in the relevance of agile and lean principles to system administration and other operations tasks. For the last four years I've been introducing and evangelizing what we now call Devops, concentrating on the message that this is good news for business. Over the last year one of our clients has been responsible for the development and management of a large UK Government Drupal site. I've been managing the technical infrastructure, live, staging, test and development environment, as well as introducing and running +an IT service desk. I've also overseen a major datacentre migration, and the building of a new architecture and infrastructure for a complete new web offering. Working with an operations team which historically had zero exposure to such approaches, and on projects which most naturally suit traditional management methodologies, I've learned a great deal about the right (and wrong) approach to introducing the Devops way, and Lean and Agile principles. This talk will serve as a field report, and explore some of my thoughts around best practices, and will discuss how (and if) Agile/Lean and ITIL/PRINCE2 methodologies can co-exist. + +
+

Continuous Delivery - Jez Humble

+continuous delivery, continuous deployment, deployment pipeline, agile testing, automation +Description + +Businesses rely on getting valuable new software into the hands of users as fast as possible, while making sure that they keep their production environments stable. Continuous Delivery is a revolutionary and scalable agile methodology that enables any team, including enterprise IT organizations, to achieve rapid, reliable releases through better collaboration between developers, testers, DBAs and operations, and automation of the build, deploy, test and release process. + +I'll start by discussing the value of CD to the business, inspired by the lean startup movement. I'll then present the principles and practices involved in continuous delivery, including value stream mapping, the deployment pipeline, acceptance test driven development, zero-downtime releases, and incremental development. I'll talk about how continuous delivery can co-exist with ITIL and compliance in an enterprise environment. Finally I'll cover how CD is enabled by an ecosystem including Devops, cloud computing, agile testing, and continuous deployment. + +
+

Kanban Fishbowl session - David Anderson

+Description + +Last year we had a presentation on Kanban for operations. Several people started out with trying this approach with various results. David Anderson introduced Kanban in software development and has started the WipSociety. After a brief introduction on Kanban we will have fishbowl session that allows the discussion of various results, problems and ideas. + +
+

Squid wrangling - Sam Newman and Chris Read

+Description: + +This talk outlines the development of a new version of one of Europe's biggest websites, handling up to 10 million unique users per month, with peaks of 35 million page impressions per day, and over 6,000 requests a second during the peak hour. Drawing on specific examples, we'll detail the evolution of the site's architecture and deployment topography, and try and draw out some general guidelines for anyone interested in scaling web applications. + +This talk details the development during 2009 of a new version of one of Europe’s highest-traffic websites. Giving a high-level overview of the reasons behind the initial reimplementation, we will then talk in detail regarding the challenges in scaling the application to handle the required load. + +Attendees will learn about: +
    +
  • Different types of caching strategies (e.g. reverse proxy vs application-level caching)
    • +
  • Our experiences comparing Squid and Varnish
    • +
  • Different types of Squid configuration
    • +
  • The importance of performance testing
    • +
  • Build & deployment techniques used
    • +
+We will talk specifics in terms of hardware & general deployment topographies, and try and draw out some general guidelines for anyone interested in scaling web applications. This talk is aimed at those people already building their own web sites, who have a basic grasp of the web and HTTP. Whilst it does detail a Java-based system, the lessons learned are equally applicable to other technology stacks. + +
+

Runtime changes are the weeds killing your crops - Spike Morelli

+Description: + +During my tenure at Linden Lab, creator of Second Life, significant changes had to be made to our systems infrastructure processes to allow our business to scale. These changes centered around consistency and repeatability in the deploy process, originating from the following postulate: given runtime changes to the filesystem, it is impossible to determine the state of the running system. We developed a toolchain - PGI, Programmatically Generated Images - around the concept of building complete system images that are not changed once built. The image then migrates through qa, staging, and into production. This was not free of challenges and problems, but consistently gave us more predictable deployment and a greater sense of confidence. It also helped bridge operations and development allowing for more efficient collaboration and awareness of the product on both sides. + +In this talk I will draw a parallel between farming practices and how as much attention is paid to the crops (your product) as to the soil (the infrastructure). Farming treats them as a unit and has developed techniques to fight bugs eating the crops (software bugs) alongside with ways to minimize external agents, like weeds, freely spawning in the soil and indirectly affecting the crops (unpredictable runtime state). + +To clarify, I'd like to focus on discussing best practices and reasoning behind certain choices rather than presenting a new toolchain as I find the problems more interesting than the implementation, for which there are already several possible solutions to build upon. diff --git a/content/events/2010-europe/propose.md b/content/events/2010-europe/propose.md deleted file mode 100644 index c246db3da08..00000000000 --- a/content/events/2010-europe/propose.md +++ /dev/null @@ -1,37 +0,0 @@ -+++ -date = "2016-05-02T12:42:53-05:00" -title = "propose" -type = "event" -+++ - {{< cfp_dates >}} - -
-There are three ways to propose a session: -
    -
  1. 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.
    2. -
  2. 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
    3. -
  3. 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 -
    -
  1. Proposal working title (can be changed later)
    2. -
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. -
  3. Description or abstract
    4. -
-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/2010-europe/reactions.md b/content/events/2010-europe/reactions.md new file mode 100644 index 00000000000..b0d3e657d49 --- /dev/null +++ b/content/events/2010-europe/reactions.md @@ -0,0 +1,43 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "reactions" +type = "event" + + ++++ + +This page will give you some idea of what happened at devopsdays Hamburg 2010. + +Send in yours! We'll add them to the page + +Images: + +Blogposts: + +Slides: + +Video: + + diff --git a/content/events/2010-europe/registration.md b/content/events/2010-europe/registration.md deleted file mode 100644 index 2f98b40e66e..00000000000 --- a/content/events/2010-europe/registration.md +++ /dev/null @@ -1,13 +0,0 @@ -+++ -date = "2016-05-02T12:42:53-05:00" -title = "registration" -type = "event" - - -+++ - -
- -Embed registration iframe/link/etc. -
- diff --git a/content/events/2010-europe/speakers.md b/content/events/2010-europe/speakers.md new file mode 100644 index 00000000000..01d557c642d --- /dev/null +++ b/content/events/2010-europe/speakers.md @@ -0,0 +1,52 @@ ++++ +date = "2016-05-02T12:42:53-05:00" +title = "contact" +type = "event" + + ++++ + + + + + + + + + + + + + + + + + + + + + +
Stephen Nelson Smith
Stephen Nelson-Smith

Stephen Nelson-Smith is the principle consultant at Atalanta Systems, an Agile Infrastructure consultancy, based in the South of England. He's an experienced technical manager and solutions architect, passionate about Devops making a real difference in business to provide a competitive advantage.


+Blog: http://agilesysadmin.net +Twitter: @lordcope +
Chris Read
Chris Read

Chris Read currently works at DRW as a DevOp where he helps developers and operations deliver more value faster. He used to work for ThoughtWorks as a Principal Technical Consultant and Infrastructure Specialist. This basically meant he helped developers understand the environments they are developing for, and helped our clients infrastructure people build better systems. His specialties are Unix (any flavor) and networking. He has done time as a Developer and as a Sys Admin, but now he is both…


+Blog: http://blog.chris-read.net/ +Twitter: @cread +
+Jez Humble
Jez Humble

Jez Humble is a Principal Consultant with ThoughtWorks, and author of Continuous Delivery, published in Martin Fowler's Signature Series (Addison Wesley, 2010). He has worked as a developer, system administrator, trainer, consultant, manager, and speaker. He has worked with a variety of platforms and technologies, consulting for non-profits, telecoms, financial services, and online retail companies.

His focus is on helping organizations deliver valuable, high-quality software frequently and reliably through implementing effective engineering practices in the field of Agile delivery.

+
+Blog: http://continuousdelivery.com/ +Twitter: @jezhumble +
+
Spike Morelli
Spike Morelli

He has done a bit of everything, from coding horrible things in languages who shall not be named, to security and a little bit of operations management. That said, most of his career has been revolving around systems engineering with primary focus on monitoring systems, automation and configuration management. In the last few years he has then picked up on the agile movement and enjoyed applying those practices to operations. Visualization is also another interest of his that he has been trying to bring to ops (think dashboards and BI for system metrics).


+Blog and Twitter: One day he will start twitting and writing on a blog again. +
+Sam Newman
Sam Newman

Sam Newman has been a technical consultant at ThoughtWorks for the last 5 years. He has written articles for O'Reilly, presented at conferences, and sporadically committed to open source projects. He is mainly a Java developer, but he also spends lots of time with Scala, Python, and Javascript.


+Blog: http://www.magpiebrain.com/ +Twitter: @samnewman +
+David Anderson
David Anderson

David J. Anderson, leads a management consulting firm focused on improving performance of technology companies. He has been in software development for 26 years and has managed teams in agile software development projects at Sprint, Motorola, Microsoft and Corbis. David is credited with the first implementation of a kanban process for software development in 2005.

David was a founder of the agile movement through his involvement in the creation of feature Driven Development. He was also a founder of the APLN, a founding signatory of the Declaration of Interdependence, and a founding member of the Lean Software and Systems Consortium.


+ +Blog: http://www.agilemanagement.net/ +Twitter: @agilemanager +
diff --git a/content/events/2010-europe/sponsor.md b/content/events/2010-europe/sponsor.md deleted file mode 100644 index cfeb27e40e4..00000000000 --- a/content/events/2010-europe/sponsor.md +++ /dev/null @@ -1,49 +0,0 @@ -+++ -date = "2016-05-02T12:42:53-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/2010-europe/welcome.md b/content/events/2010-europe/welcome.md index 324c6687a5e..b2197045138 100644 --- a/content/events/2010-europe/welcome.md +++ b/content/events/2010-europe/welcome.md @@ -6,47 +6,10 @@ aliases = ["/events/2010-europe"] +++ -## {{< event_start >}} - {{< event_end >}} +It's about one year since the first devopsdays 2009 took place in Belgium. Since then we have had successful conference in both Australia and the United States. Now we came back home to Europe. -DevOps Days is coming to {{< event_location >}}! +Location: East Hotel in Hamburg/Germany - +Date: Friday, 15th - Saturday 16th October 2010 - - - - - - - - - - - - - - - - - - - - -
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 >}} -
+ diff --git a/data/events/2010-europe.yml b/data/events/2010-europe.yml index 5b80cf4a524..21a21d81f45 100644 --- a/data/events/2010-europe.yml +++ b/data/events/2010-europe.yml @@ -8,8 +8,8 @@ status: "past" # Options are "past" or "current". Use "current" for upcoming. startdate: 2010-10-15 # The start date of your event. Leave blank if you don't have a venue reserved yet. enddate: 2010-10-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. +cfp_date_start: 2010-10-15 # start accepting talk proposals. +cfp_date_end: 2010-10-16 # close your call for proposals. cfp_date_announce: 2016-01-01 # inform proposers of status # Location @@ -20,14 +20,14 @@ location: "europe" # 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: propose -# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + - name: program + - name: lightning talks + url: events/2010-europe/lightning-talks # The url setting is optional, and only if you want the navigation to link off-site # - name: location # - name: registration - - name: sponsor + - name: speakers - name: contact - - name: conduct + - name: reactions # These are the same people you have on the mailing list and Slack channel. team: ["John Doe", "Jane Smith", "Sally Fields"] @@ -43,17 +43,32 @@ proposal_email: "proposals-europe-2010@devopsdays.org" # Put your proposal email # 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: xing-2010 level: gold - - id: arresteddevops - level: community + - id: nokia + level: gold + - id: thoughtworks-2010 + level: gold + - id: itgaile-2010 + level: gold + - id: codecentric-2010 + level: gold + - id: agilealliance-2010 + level: silver + - id: puppetlabs-2010 + level: silver + - id: opscode-2010 + level: silver + - id: urbancode-2010 + level: silver + - id: skillsmatter-2010 + level: media + - id: adminmagazine-2010 + level: media sponsor_levels: # In this section, list the level of sponsorships and the label to use. - id: gold label: Gold - id: silver - label: Silver - - id: bronze - label: Bronze - - id: community - label: Community + - id: media + label: Media From 09f5c4fbc3118ae6ff08967670a358d31afd5513 Mon Sep 17 00:00:00 2001 From: Matt Stratton Date: Mon, 2 May 2016 15:08:59 -0500 Subject: [PATCH 3/4] Add 2010 sydney --- content/events/2010-sydney/conduct.md | 36 ------ content/events/2010-sydney/contact.md | 17 --- content/events/2010-sydney/location.md | 10 -- content/events/2010-sydney/program.md | 122 --------------------- content/events/2010-sydney/propose.md | 37 ------- content/events/2010-sydney/registration.md | 13 --- content/events/2010-sydney/sponsor.md | 49 --------- content/events/2010-sydney/welcome.md | 45 +------- data/events/2010-sydney.yml | 18 ++- 9 files changed, 10 insertions(+), 337 deletions(-) delete mode 100644 content/events/2010-sydney/conduct.md delete mode 100644 content/events/2010-sydney/contact.md delete mode 100644 content/events/2010-sydney/location.md delete mode 100644 content/events/2010-sydney/program.md delete mode 100644 content/events/2010-sydney/propose.md delete mode 100644 content/events/2010-sydney/registration.md delete mode 100644 content/events/2010-sydney/sponsor.md diff --git a/content/events/2010-sydney/conduct.md b/content/events/2010-sydney/conduct.md deleted file mode 100644 index 3707c625d9f..00000000000 --- a/content/events/2010-sydney/conduct.md +++ /dev/null @@ -1,36 +0,0 @@ -+++ -date = "2016-05-02T12:42:19-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/2010-sydney/contact.md b/content/events/2010-sydney/contact.md deleted file mode 100644 index f94e779facd..00000000000 --- a/content/events/2010-sydney/contact.md +++ /dev/null @@ -1,17 +0,0 @@ -+++ -date = "2016-05-02T12:42:19-05: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 >}} diff --git a/content/events/2010-sydney/location.md b/content/events/2010-sydney/location.md deleted file mode 100644 index 721d5b4e93c..00000000000 --- a/content/events/2010-sydney/location.md +++ /dev/null @@ -1,10 +0,0 @@ -+++ -date = "2016-05-02T12:42:19-05:00" -title = "location" -type = "event" - -+++ - -Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. - - diff --git a/content/events/2010-sydney/program.md b/content/events/2010-sydney/program.md deleted file mode 100644 index 38446549b80..00000000000 --- a/content/events/2010-sydney/program.md +++ /dev/null @@ -1,122 +0,0 @@ -+++ -date = "2016-05-02T12:42:19-05:00" -title = "program" -type = "event" - -+++ - -
-
If you are new to the Open Space concept you may want to read some more details.
- -
- - -

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
- - -
- - -
- -
-

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
- - - -
diff --git a/content/events/2010-sydney/propose.md b/content/events/2010-sydney/propose.md deleted file mode 100644 index c3d3d9069e5..00000000000 --- a/content/events/2010-sydney/propose.md +++ /dev/null @@ -1,37 +0,0 @@ -+++ -date = "2016-05-02T12:42:19-05:00" -title = "propose" -type = "event" -+++ - {{< cfp_dates >}} - -
-There are three ways to propose a session: -
    -
  1. 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.
    2. -
  2. 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
    3. -
  3. 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 -
    -
  1. Proposal working title (can be changed later)
    2. -
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. -
  3. Description or abstract
    4. -
-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/2010-sydney/registration.md b/content/events/2010-sydney/registration.md deleted file mode 100644 index 6f2be2bb63e..00000000000 --- a/content/events/2010-sydney/registration.md +++ /dev/null @@ -1,13 +0,0 @@ -+++ -date = "2016-05-02T12:42:19-05:00" -title = "registration" -type = "event" - - -+++ - -
- -Embed registration iframe/link/etc. -
- diff --git a/content/events/2010-sydney/sponsor.md b/content/events/2010-sydney/sponsor.md deleted file mode 100644 index 1897600b1be..00000000000 --- a/content/events/2010-sydney/sponsor.md +++ /dev/null @@ -1,49 +0,0 @@ -+++ -date = "2016-05-02T12:42:19-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/2010-sydney/welcome.md b/content/events/2010-sydney/welcome.md index e0c7480ddee..3f6ded2b421 100644 --- a/content/events/2010-sydney/welcome.md +++ b/content/events/2010-sydney/welcome.md @@ -6,47 +6,6 @@ aliases = ["/events/2010-sydney"] +++ -## {{< event_start >}} - {{< event_end >}} +Lindsay Holmwood did a great job on organizing the devopsdays Sydney Australia 2010. -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 >}} -
+You can see the result at: http://devopsdownunder.org/ diff --git a/data/events/2010-sydney.yml b/data/events/2010-sydney.yml index f8fb8fbf076..1128373e4a6 100644 --- a/data/events/2010-sydney.yml +++ b/data/events/2010-sydney.yml @@ -45,15 +45,13 @@ proposal_email: "proposals-sydney-2010@devopsdays.org" # Put your proposal email sponsors: - id: samplesponsorname level: gold - - id: arresteddevops - level: community sponsor_levels: # In this section, list the level of sponsorships and the label to use. - - id: gold - label: Gold - - id: silver - label: Silver - - id: bronze - label: Bronze - - id: community - label: Community + # - id: gold + # label: Gold + # - id: silver + # label: Silver + # - id: bronze + # label: Bronze + # - id: community + # label: Community From 499081badbc20bdc61c24039f8d9f4c2706d6192 Mon Sep 17 00:00:00 2001 From: Matt Stratton Date: Mon, 2 May 2016 16:22:10 -0500 Subject: [PATCH 4/4] Add 2010 Mountain View --- content/events/2010-us/conduct.md | 36 --- content/events/2010-us/contact.md | 13 +- content/events/2010-us/lightning-talks.md | 25 ++ content/events/2010-us/location.md | 10 +- content/events/2010-us/program.md | 184 +++++-------- content/events/2010-us/propose.md | 37 --- content/events/2010-us/registration.md | 13 - content/events/2010-us/speakers.md | 304 ++++++++++++++++++++++ content/events/2010-us/sponsor.md | 49 ---- content/events/2010-us/welcome.md | 45 +--- data/events/2010-brazil.yml | 8 +- data/events/2010-europe.yml | 22 +- data/events/2010-us.yml | 51 ++-- 13 files changed, 462 insertions(+), 335 deletions(-) delete mode 100644 content/events/2010-us/conduct.md create mode 100644 content/events/2010-us/lightning-talks.md delete mode 100644 content/events/2010-us/propose.md delete mode 100644 content/events/2010-us/registration.md create mode 100644 content/events/2010-us/speakers.md delete mode 100644 content/events/2010-us/sponsor.md diff --git a/content/events/2010-us/conduct.md b/content/events/2010-us/conduct.md deleted file mode 100644 index 2350160a609..00000000000 --- a/content/events/2010-us/conduct.md +++ /dev/null @@ -1,36 +0,0 @@ -+++ -date = "2016-05-02T12:40:32-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/2010-us/contact.md b/content/events/2010-us/contact.md index 069d9b4c492..faea4a792d2 100644 --- a/content/events/2010-us/contact.md +++ b/content/events/2010-us/contact.md @@ -6,12 +6,11 @@ type = "event" +++ -If you'd like to contact us by email: {{< email_organizers >}} +If you want to contact us by email at organizers-us-2010@devopsdays.org -**Our local team** +the devopsdays US team -{{< list_organizers >}} - -**The core devopsdays organizer group** - -{{< list_core >}} +- Andrew Shafer +- Damon Edwards +- Gildas Lenadan +- Patrick Debois diff --git a/content/events/2010-us/lightning-talks.md b/content/events/2010-us/lightning-talks.md new file mode 100644 index 00000000000..3e5f4a02031 --- /dev/null +++ b/content/events/2010-us/lightning-talks.md @@ -0,0 +1,25 @@ ++++ +date = "2016-05-02T12:40:32-05:00" +title = "lightning talks" +type = "event" + + ++++ + + + +Below you will find the links to the lightning talks presented during devopsday USA 2010, in their order of appearance. + +- Adam Rosien - Kaching +- Alex Honor - devops toolchain +- Erica Brescia - History of Computing +- Clint Byrum - devops API contract +- Mark Lin - metrics simplified + + +- Brent Chapman - netomata +- Tim Lossen - Petascale storage DIY +- Rolf Russel - systems thinkin +- Paul Querna - libcloud +- John Willis - A simple story +- Erik Sowa - Feature Bits diff --git a/content/events/2010-us/location.md b/content/events/2010-us/location.md index ab8c50e823e..b18d57d16d3 100644 --- a/content/events/2010-us/location.md +++ b/content/events/2010-us/location.md @@ -5,6 +5,10 @@ type = "event" +++ -Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes. - - +The hosts for DevOps Day USA 2010 is the LinkedIn Corporation: +
2027 Stierlin Court
+
Mountain View, CA 94043
+
+
(Note: Look for the building address, LinkedIn has multiple buildings on the same street)
+
+
View Larger Map diff --git a/content/events/2010-us/program.md b/content/events/2010-us/program.md index d2025f5e17d..44303922eb7 100644 --- a/content/events/2010-us/program.md +++ b/content/events/2010-us/program.md @@ -5,118 +5,72 @@ type = "event" +++ -
-
If you are new to the Open Space concept you may want to read some more details.
- -
- - -

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
- - -
- - -
- -
-

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
- - - -
+DevOps Day US was a single-track conference organized around a series of panels where open discussion amongst all conference participants was encouraged. + +
    +
  1. Your mileage may vary: Experiences and lessons learned facing DevOps problems in the IT trenches (even if they weren't calling it DevOps!). The good, the bad, the surprises, and ideas for the future. +
      +
    • Stefan Apitz - LinkedIn
      • +
    • Ernest Muller - National Instruments
      • +
    • Dan Nemec - SilverPop
      • +
    • Burzin Engineer - Shopzilla
      • +
    • Kevin Rae - PowerReviews
      • +
    • moderator: Andrew Shafer
      • +
    +
    2. +
  2. Infrastructure as code: Automation is essential to DevOps. The infrastructure as code concept drives many of today's cutting edge automaton techniques. What is it all about? Where are its limitations? + +
    3. +
  3. Changing culture to enable DevOps: Changing tools is easy when compared to changing people and processes. How can we cultivate an organization's culture to identify and solve DevOps problems? +
      +
    • John Allspaw - Etsy
      • +
    • Lee Thompson - DTO Solutions
      • +
    • Israel Gat - The Agile Executive
      • +
    • Lloyd Taylor - Netelder Associates
      • +
    • moderator: Andrew Shafer
      • +
    +
    4. +
  4. Does the Cloud needs DevOps? Does DevOps need the Cloud?: Examining the role that cloud technologies can play in solving DevOps problems and the role that DevOps solutions can play in getting the most out of cloud technologies. +
      +
    • James Urquhart - Cisco
      • +
    • Adrian Cole - Jclouds
      • +
    • Justin Dean - Shopzilla
      • +
    • Joe Arnold - Cloudscaling
      • +
    • moderator: John Willis
      • +
    +
    5. +
  5. DevOps requires visibility: monitoring, testing, and performance : Examining the (often overlooked) role of monitoring and testing techniques in solving DevOps problems. + +
    6. +
  6. DevOps outside of Web Operations: Much of the public discussion about DevOps focuses on Web Operations. This panel is about taking the lessons of DevOps to other types of IT. + +
    7. +
  7. Making the business case: We know that solving DevOps problems improves your business operations and improves the bottom line, but how do you do you explain that to your CEO or CFO? How do you get the executives to buy in and invest in DevOps solutions? +
      +
    • Kurt Milne - IT Process Institute
      • +
    • Jay Lyman - The 451 Group
      • +
    • Rolf Andrew Russell - ThoughtWorks
      • +
    • Jody Mulkey - Shopzilla
      • +
    • moderator: Damon Edwards
      • +
    +
    8. +
diff --git a/content/events/2010-us/propose.md b/content/events/2010-us/propose.md deleted file mode 100644 index 09920c135ae..00000000000 --- a/content/events/2010-us/propose.md +++ /dev/null @@ -1,37 +0,0 @@ -+++ -date = "2016-05-02T12:40:32-05:00" -title = "propose" -type = "event" -+++ - {{< cfp_dates >}} - -
-There are three ways to propose a session: -
    -
  1. 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.
    2. -
  2. 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
    3. -
  3. 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 -
    -
  1. Proposal working title (can be changed later)
    2. -
  2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
    3. -
  3. Description or abstract
    4. -
-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/2010-us/registration.md b/content/events/2010-us/registration.md deleted file mode 100644 index 3afa0535d5d..00000000000 --- a/content/events/2010-us/registration.md +++ /dev/null @@ -1,13 +0,0 @@ -+++ -date = "2016-05-02T12:40:32-05:00" -title = "registration" -type = "event" - - -+++ - -
- -Embed registration iframe/link/etc. -
- diff --git a/content/events/2010-us/speakers.md b/content/events/2010-us/speakers.md new file mode 100644 index 00000000000..393cdde7c55 --- /dev/null +++ b/content/events/2010-us/speakers.md @@ -0,0 +1,304 @@ ++++ +date = "2016-05-02T12:40:32-05:00" +title = "speakers" +type = "event" + + ++++ + +
+
+
+ +Dan Nemec + +Dan Nemec, Engineering Solutions Architect at Silverpop, brings 12 years of operations and solution architecture experience with Software As A Service applications. + +Previously he was Senior Solution Architect at Harbinger/Inovis where he led the effort to improve the operational and deployment functionality of their custom built, hosted applications. + +He continues that effort at Silverpop, having been in Operations and currently in Development, by bridging both organizations and has led numerous, successful Devops efforts such as automated provisioning and deployment and configuration and environment standardization improving the agility of development and stability of operations. + +Nemec graduated from the University of Texas at Austin with a Bachelor of Science degree in Electrical Engineering. + +
+
+
+
+
+ +Burzin N. Engineer + +Burzin N. Engineer is Vice President of Infrastructure Technology at Shopzilla, Inc. Burzin has more than 18 years of experience in the IT industry. + +His experience ranges from system and database administration to network/storage design and architecture. His technology focal points revolve around solving today's largest IT problems such as server consolidation, virtualization, data mobility and ILM. + +At Shopzilla, Burzin is responsible for all facets of IT, including network, storage, systems and internal IT. He holds a Master of Science in Computer Science from the University of Southern California. He can be reached at bengineer at shopzilla dot com. + +
+
+
+
+
+ +Kevin Rae + +Kevin Rae wrote his first software on an Apple IIe and have been hooked ever since. + +After obtaining a BA in computer science from Claremont McKenna he traveled the US as a management consultant for Ernst & Young then spent the dot com bubble running systems for Fogdog Sports. + +After the bubble popped he managed systems administration and systems engineering teams for DST Output and during evenings and weekends earned an MBA from UC Davis. + +Kevin is currently employed as Director of IT at PowerReviews.Outside work he likes to spend time with his wife and 2 sons and also enjoys playing and recording music in his home studio. + +
+
+
+
+
+ +Theo Schlossnagle + +Theo Schlossnagle is a Founder and CEO at OmniTI where he designs and implements scalable solutions for highly trafficked sites and other clients in need of sound, scalable architectural engineering. + +In his role at OmniTI, he has founded several successful startups including Message Systems and Circonus. + +Theo is a participant in various open source communities including OpenSolaris, Reconnoiter, Apache, PostgreSQL, perl, and many others. + +He is a published author in the area of scalability and distributed systems as well as a veteran speaker in the open source conference circuit. + +
+
+
+
+
+ +Luke Kanies + +Luke is the founder and CEO of Puppet Labs and the founder of the Puppet project. + +Previously, he was a consultant, open source contributor, and article author. + +He has focused on tool development since 2001, developing and publishing multiple simple sysadmin tools and contributing to established products like Cfengine. + +He has presented on Puppet and other tools around the world, including at OSCON, LISA, Linux.Conf.au, and FOSS. + +
+
+
+
+
+ +Erik Troan + +Erik Troan is founder and CTO of rPath, Inc. + +Prior to founding rPath, Erik served in multiple roles at Red Hat including Vice President of Product Engineering for several years and chief developer for Red Hat Software. + +During his tenure with the company Erik was responsible for leading development for Red Hat Linux, RPM, and Anaconda. He managed a multimillion-dollar budget, participated in two public stock offerings and assisted in acquiring and integrating nine other companies. + +Erik has co-authored two editions of Linux Application Development. + +At rPath he is responsible for all aspects of product design and implementation and for the company's IT infrastructure. + +He holds BS degrees in Computer Science and Computer Engineering from North Carolina State University and a Masters degree in Economics from the University of Virginia. Erik also serves on the Board of Directors for Digium, Inc. + +
+
+
+
+
+ +John Allspaw + +John has worked in systems operations for over fourteen years in biotech, government and online media. + +He started out tuning parallel clusters running vehicle crash simulations for the U.S. government, and then moved on to the Internet in 1997. + +He built the backing infrastructures at Salon, InfoWorld, Friendster, and Flickr. He is now VP of Tech Operations at Etsy, and is the author of The Art of Capacity Planning and the upcoming Web Operations, published by O’Reilly. + +
+
+
+
+
+Lloyd Taylor + +Lloyd is an independent adviser, consultant, and investor who specializes in helping companies scale successfully. + +His professional work has included scaling LinkedIn's infrastructure to support it's rapid growth; Developing, implementing and operating an infinitely scalable global physical infrastructure for Google's server farms; Building out a worldwide performance measurement infrastructure for Keynote Systems; and Developing one of the first managed hosting architectures while at Digex. + +His pro bono work includes funding and advising a select group of non-profits working on zero-dependency methods for ending poverty throughout the world. http://www.linkedin.com/in/lloydtaylor + +
+
+
+
+
+ +James Urquhart + +James Urquhart manages cloud computing infrastructure strategy for the Server Provider Systems Unit of Cisco Systems. Named one of the ten most influential people in cloud computing by the MIT Technology Review, and author of the popular C|NET Blog Network blog, The Wisdom of Clouds (http://news.cnet.com/the-wisdom-of-clouds), Mr. Urquhart brings a deep understanding of these disruptive technologies and the business opportunities they afford. + +Mr. Urquhart is a seasoned field technologist with almost 20 years of experience in distributed systems development and deployment, focusing on service-oriented architectures, cloud computing, and virtualization. Prior to joining Cisco, Mr. Urquhart held leadership roles at Forte Software, Sun Microsystems, and utility computing infrastructure vendor Cassatt Corporation. + +Mr. Urquhart graduated from Macalester College with a Bachelor of Arts in Mathematics and Physics. + +
+
+
+
+
+ +Jyoti Bansal + +Jyoti founded AppDynamics in early 2008 with the vision of defining the next-generation of application performance management (APM) solutions for distributed applications running in cloud, virtual, and physical environments. + +Before founding AppDynamics, Jyoti led the design and architecture for several products at Wily Technology. + +Before Wily, Jyoti worked in senior engineering roles at Datasweep (acquired by Rockwell Automation) and netLens (acquired by Microsoft through FAST/Nextpage), where he built distributed application architectures for enterprise search and data mining. + +Jyoti received his BS in Computer Science from the Indian Institute of Technology, Delhi. + +He is the lead inventor on 14 US patent applications in the field of distributed applications management. + +His latest creation is a free product for troubleshooting java performance in production, available at www.appdynamics.com/free. + +
+
+
+
+
+ +Javier Soltero + +Javier Soltero is the CTO of Management Products at SpringSource division of VMware. + +Previously, Javier was the co-founder and CEO of Hyperic, the leader in multi-platform, open source IT management, which SpringSource acquired in May 2009. Prior to co-founding Hyperic, he was chief architect at Covalent Technologies, where he led the design and implementation of multiple enterprise products, including the configuration management product for Apache and the Covalent Application Manager (CAM)—now Hyperic's flagship product Hyperic HQ. + +Prior to Covalent, Soltero was a senior software engineer at Backflip, where he met Hyperic co-founders Charles Lee and Doug MacEachern. At Backflip, he was actively involved in the design, implementation, and operational aspects of the site. + +Soltero also held senior engineering positions at Netscape, where he participated in the design development of e-commerce and Internet infrastructure suites. Over the last 10 years, Soltero has been actively involved in various open source communities as both user and contributor to projects like JBoss and Apache Tomcat. + +Soltero is originally from San Juan, Puerto Rico and received his BS in Information Systems and Industrial Management from Carnegie Mellon University. + +
+
+
+
+
+ +Gareth Bowles + +Gareth Bowles has been working as a QA and technical operations manager at different West Coast startups since well before the dawn of the 21st century. + +He recently realized that I'd already been practicing quite a few devops concepts without putting a convenient name to them, especially trying to figure out the human factors and using the cloud for extra efficiency. + +Gareth is always looking for new ways to get the product built, tested and deployed faster while still getting a good night's sleep. + +
+
+
+
+
+ +Adam Fletcher + +Adam Fletcher is the Operations Architect for ITA Software's airline reservation system product, a mission critical, highly scalable, high performance, transaction processing system. + +He has over 10 years of systems operations and software development experience. Adam has been practicing devops without naming it for all of those years, firmly believing that automation and process control are critical to managing any infrastructure. + +Adam frequently writes on devops topics outside of web operations on his blog, http://www.thesimplelogic.com, and runs the Boston DevOps Meetups. + +
+
+
+
+
+ +Gene Kim + +Gene Kim is the CTO and co-founder of Tripwire, Inc. + +In 1992, he co-authored Tripwire while at Purdue University with Dr. Gene Spafford. + +Since 1999, he has been studying high performing IT operations and security organizations. + +In 2004, he co-wrote the Visible Ops Handbook, codifying how to successfully transform IT organizations from “good to great.” + +In 2008, he co-authored Security Visible Ops Handbook, a handbook describing how to link IT security and operational objectives in four practical steps by integrating security controls into IT operational, software development and project management processes. + +Gene is a huge fan of IT operations, and how developers can enable fast throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. + +He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. + +
+
+
+
+
+ +Michael Stahnke + +Michael Stahnke began working with Unix in the late 1990s. After getting a CS degree from Ball State in 2002, he quickly found his passion in Linux administration and automation. + +He has worked with Fortune 100 companies, and several open source projects. Michael has concentrated on Identity Management as well security integration into administration and automation processes. + +In 2005, Michael authored Pro OpenSSH for Apress Publishing. Michael also joined the Fedora project in that year. Today he (co)maintains about 30 packages, and is an active member on the Extra Packages for Enterprise Linux (EPEL) steering committee. + +He also contributes to the Spacewalk project, the Ruby special Interest Group, and several other facets of the Fedora Project. + +In 2008, Michael moved to a leadership position on his Unix and Virtualization +team at Caterpillar. Michael also works as an independent contractor for various technology organizations in Nashville, TN. + +
+
+
+
+
+ +James Turnbull + +James Turnbull is Director of Operations for Puppet Labs. He previously worked for the National Australia Bank as the manager of their Computer Emergency Response Team. + +James has also worked as an Executive Manager of IT Security at the Commonwealth Bank of Australia, the CIO of a medical research foundation doing Web-based clinical trials, managing the architecture group of an outsourcing company and in a number of IT roles in gaming, telecommunications and government. + +He is an experienced infrastructure architect with a background in Linux/Unix, AS/400, Windows, and storage systems. He has been involved in security consulting, infrastructure security design, SLA and service definition and has an abiding interest in security metrics and measurement. + +James is involved in the Free and Open Source Software community as a developer and contributor. He was the Treasurer and coordinated the mini-conference program at linux.conf.au 2008 in Melbourne, Australia and has been a member of the linux.conf.au papers committee since 2008. + +He is a member of Linux Australia, acting as President in 2010 and serving on the Council in 2008. + +In his spare time his interests include cooking, wine, political theory, photojournalism, philosophy, poetry, and cats. + +
+
+
+
+
+ +Kurt Milne + +Kurt Milne is the Managing Director of the IT Process Institute, and primary author of five major IT management research studies. + +He has 20 years of experience at leading technology companies including Hewlett Packard and BMC Software. + +His main areas of expertise include IT service management and IT controls, inventory and supply chain management, and computer integrated manufacturing. + +
+
+
+
+
+ +Rolf Russell + +Rolf Russell leads the DevOps/Build/Release practice at ThoughtWorks. + +He focuses on helping IT organizations become nimble and reactive in meeting their customers' needs through pragmatic improvements to the way software is build and taken into production. + +Rolf developed his passion for this space in the traditional way, through painful experience as poorly managed 'paths to production' endangered projects he was delivering. + +His experiences come through working with Fortune 1000 companies across an array of industries, including financial services, telecommunications, energy and media. + +
+
diff --git a/content/events/2010-us/sponsor.md b/content/events/2010-us/sponsor.md deleted file mode 100644 index 91c3365c9db..00000000000 --- a/content/events/2010-us/sponsor.md +++ /dev/null @@ -1,49 +0,0 @@ -+++ -date = "2016-05-02T12:40:32-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/2010-us/welcome.md b/content/events/2010-us/welcome.md index 01dbabe462a..21b3bca052b 100644 --- a/content/events/2010-us/welcome.md +++ b/content/events/2010-us/welcome.md @@ -6,47 +6,10 @@ aliases = ["/events/2010-us"] +++ -## {{< event_start >}} - {{< event_end >}} +DevOps Day USA 2010 was inspired by and a continuation of the conversation from Devopsdays Belgium 2009 and was held in Mountain View, California on Friday, June 25, 2010 just after Velocity. -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 >}} -
+ +You can get more information on the browse the program or browse the confirmed speakers bios. diff --git a/data/events/2010-brazil.yml b/data/events/2010-brazil.yml index 9c391c8a16f..a0f17d91af4 100644 --- a/data/events/2010-brazil.yml +++ b/data/events/2010-brazil.yml @@ -38,13 +38,13 @@ proposal_email: "proposals-brazil-2010@devopsdays.org" # Put your proposal email # 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: thoughtworks-2010 + - id: 2010-thoughtworks level: sponsor - - id: puppet-2010 + - id: 2010-puppetlabs level: sponsor - - id: opscode-2010 + - id: 2010-opscode level: sponsor - - id: locaweb-2010 + - id: 2010-locaweb level: sponsor sponsor_levels: # In this section, list the level of sponsorships and the label to use. diff --git a/data/events/2010-europe.yml b/data/events/2010-europe.yml index 21a21d81f45..8d266f8bed8 100644 --- a/data/events/2010-europe.yml +++ b/data/events/2010-europe.yml @@ -43,27 +43,27 @@ proposal_email: "proposals-europe-2010@devopsdays.org" # Put your proposal email # 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: xing-2010 + - id: 2010-xing level: gold - - id: nokia + - id: 2010-nokia level: gold - - id: thoughtworks-2010 + - id: 2010-thoughtworks level: gold - - id: itgaile-2010 + - id: 2010-itgaile level: gold - - id: codecentric-2010 + - id: 2010-codecentric level: gold - - id: agilealliance-2010 + - id: 2010-agilealliance level: silver - - id: puppetlabs-2010 + - id: 2010-puppetlabs level: silver - - id: opscode-2010 + - id: 2010-opscode level: silver - - id: urbancode-2010 + - id: 2010-urbancode level: silver - - id: skillsmatter-2010 + - id: 2010-skillsmatter level: media - - id: adminmagazine-2010 + - id: 2010-adminmagazine level: media sponsor_levels: # In this section, list the level of sponsorships and the label to use. diff --git a/data/events/2010-us.yml b/data/events/2010-us.yml index 5b733136e17..a8fddcc2cc8 100644 --- a/data/events/2010-us.yml +++ b/data/events/2010-us.yml @@ -20,14 +20,11 @@ location: "us" # 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: propose -# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site -# - name: location -# - name: registration - - name: sponsor + - name: program + - name: lightning talks + url: events/2010-us/lightning-talks + - name: speakers - 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"] @@ -43,17 +40,33 @@ proposal_email: "proposals-us-2010@devopsdays.org" # Put your proposal email add # 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 - level: gold - - id: arresteddevops - level: community + - id: 2010-linkedin + level: hosting + - id: 2010-appdynamics + level: Supporting + - id: 2010-bitnami + level: supporting + - id: 2010-cloudscaling + level: supporting + - id: 2010-dto + level: supporting + - id: 2010- newrelic + level: supporting + - id: 2010-opscode + level: supporting + - id: 2010-puppetlabs + level: supporting + - id: 2010-rpath + level: supporting + - id: 2010-thoughtworks + level: supporting + - id: 2010-zenoss + level: supporting + - id: 2010-vmware + level: supporting sponsor_levels: # In this section, list the level of sponsorships and the label to use. - - id: gold - label: Gold - - id: silver - label: Silver - - id: bronze - label: Bronze - - id: community - label: Community + - id: hosting + label: Hosting + - id: supporting + label: Supporting