Skip to content

Commit 0100e0e

Browse files
bridgetkromhoutbridgetkromhout
committed
Merge pull request #275 from devopsdays/bridget-migration
Kansas City
2 parents 7902ca4 + 7f8d36a commit 0100e0e

File tree

9 files changed

+398
-0
lines changed

9 files changed

+398
-0
lines changed

‎content/events/2016-kansascity/conduct.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "conduct"
4+
type = "event"
5+
6+
+++
7+
8+
## ANTI-HARASSMENT POLICY
9+
10+
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.
11+
12+
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.
13+
14+
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.
15+
16+
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.
17+
18+
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.
19+
20+
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.
21+
22+
We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
23+
24+
## CODE OF CONDUCT
25+
26+
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.
27+
28+
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.
29+
30+
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.
31+
32+
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.
33+
34+
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.
35+
36+
VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.

‎content/events/2016-kansascity/contact.md

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "contact"
4+
type = "event"
5+
6+
7+
+++
8+
9+
If you'd like to contact us by email: {{< email_organizers >}}
10+
11+
**Our local team**
12+
13+
{{< list_organizers >}}
14+
15+
**The core devopsdays organizer group**
16+
17+
{{< list_core >}}

‎content/events/2016-kansascity/location.md

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "location"
4+
type = "event"
5+
6+
+++
7+
8+
Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
9+
10+
<!-- {{< event_map >}} -->

‎content/events/2016-kansascity/program.md

+122
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "program"
4+
type = "event"
5+
6+
+++
7+
8+
<hr>
9+
<div class="span-16 last ">If you are new to the Open Space concept you may <a href="/pages/open-space-format">want to read some more details</a>.</div>
10+
</center>
11+
<hr />
12+
13+
14+
<center><b><h2>The Schedule</h2></b></center>
15+
<div class="span-7 append-bottom border">
16+
17+
<div class="span-7 last">
18+
<h4>Day 1</h4>
19+
</div>
20+
21+
<div class="span-2">08:00-09:00</div><div class="span-4 box last">Registration, Breakfast, and Sponsor Booths Open</div>
22+
<div class="span-2">09:00-9:15</div><div class="span-4 box last"><strong></strong>Opening Welcome</div>
23+
<div class="span-2">09:15-09:45</div><div class="span-4 box last">
24+
<br />
25+
</div>
26+
<div class="span-2">09:45-09:55</div><div class="span-4 box last">
27+
Sponsors
28+
</div>
29+
<div class="span-2">09:55-10:25</div><div class="span-4 box last">
30+
<br />
31+
32+
</div>
33+
<div class="span-2">10:25-10:40</div><div class="span-4 box last">
34+
Break
35+
</div>
36+
37+
<div class="span-2">10:40-11:10</div><div class="span-4 box last">
38+
<br />
39+
</div>
40+
41+
<div class="span-2">11:10-11:20</div><div class="span-4 box last">
42+
Sponsors
43+
</div>
44+
45+
<div class="span-2">11:20-11:50</div><div class="span-4 box last">
46+
<br />
47+
</div>
48+
49+
<div class="span-2">11:50-13:00</div><div class="span-4 append-bottom last">Lunch (catered)</div>
50+
51+
<div class="span-2">13:00-13:30</div><div class="span-4 box last"><strong>Ignites</strong> <br />
52+
</div>
53+
54+
<div class="span-2">13:30-14:00</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space Opening</div>
55+
56+
<div class="span-2">14:00-14:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #1</div>
57+
58+
<div class="span-2">15:00-15:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #2</div>
59+
60+
<div class="span-2">16:00-16:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #3</div>
61+
62+
<div class="span-2">16:45-17:00</div><div class="span-4 box last"><strong></strong>Close Day & Logistics</div>
63+
64+
<div class="span-2">19:00-late</div><div class="span-4 box last"><strong>Evening Event</strong><br /></div>
65+
66+
67+
</div>
68+
69+
70+
<div class="span-7 append-bottom border">
71+
72+
<div class="span-7 last">
73+
<h4>Day 2</h4>
74+
</div>
75+
76+
<div class="span-2">08:00-09:00</div><div class="span-4 box last"> Registration, Breakfast, and Sponsor Booths Open</div>
77+
<div class="span-2">09:00-9:15</div><div class="span-4 box last"><strong></strong>Opening Welcome</div>
78+
<div class="span-2">09:15-09:45</div><div class="span-4 box last">
79+
<br />
80+
</div>
81+
<div class="span-2">09:45-09:55</div><div class="span-4 box last">
82+
Sponsors
83+
</div>
84+
<div class="span-2">09:55-10:25</div><div class="span-4 box last">
85+
<br />
86+
87+
</div>
88+
<div class="span-2">10:25-10:40</div><div class="span-4 box last">
89+
Break
90+
</div>
91+
92+
<div class="span-2">10:40-11:10</div><div class="span-4 box last" style="height:100px;">
93+
<br />
94+
</div>
95+
96+
<div class="span-2">11:10-11:20</div><div class="span-4 box last">
97+
Sponsors
98+
</div>
99+
100+
<div class="span-2">11:20-11:50</div><div class="span-4 box last">
101+
<br />
102+
</div>
103+
104+
<div class="span-2">11:50-13:00</div><div class="span-4 append-bottom last">Lunch (catered)</div>
105+
106+
<div class="span-2">13:00-13:30</div><div class="span-4 box last"><strong>Ignites</strong> <br />
107+
108+
</div>
109+
110+
<div class="span-2">13:30-14:00</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space Opening</div>
111+
112+
<div class="span-2">14:00-14:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #1</div>
113+
114+
<div class="span-2">15:00-15:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #2</div>
115+
116+
<div class="span-2">16:00-16:45</div><div class="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #3</div>
117+
118+
<div class="span-2">17:00</div><div class="span-4 box last"><strong></strong>Close Day & Farewell</div>
119+
120+
121+
122+
</div>

‎content/events/2016-kansascity/propose.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "propose"
4+
type = "event"
5+
+++
6+
{{< cfp_dates >}}
7+
8+
<hr>
9+
There are three ways to propose a session:
10+
<ol>
11+
<li><strong><em>A proposal for a talk/panel</em></strong> 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.</li>
12+
<li><strong><em>An Ignite talk</em></strong> that will be presented during the<a href="/pages/ignite-talks-format"> Ignite sessions</a>. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room</li>
13+
<li><strong><em>Open Space session</em></strong> : 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 <a href="/pages/open-space-format">Open Space explanation</a> for more information.
14+
</ol>
15+
16+
### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
17+
18+
Our main criteria to make it to the top selection are:
19+
20+
- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
21+
- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
22+
- _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.
23+
24+
<strong>How to submit a proposal:</strong> Send an email to [{{< email_proposals >}}] with the following information
25+
<ol>
26+
<li>Proposal working title (can be changed later)</li>
27+
<li>Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)</li>
28+
<li>Description or abstract</li>
29+
</ol>
30+
<strong>Rules:</strong>
31+
<ul>
32+
<li>Be specific... we aren't mind readers (a description of about 20 lines is about right)</li>
33+
<li>Detail is good... but not as important as explaining why your proposal would be interesting</li>
34+
<li>Propose your own talk; don't have someone else do it for you.</li>
35+
<li>Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!</li>
36+
<li>Multiple proposals welcome... just follow the other rules</li>
37+
</ul>

‎content/events/2016-kansascity/registration.md

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "registration"
4+
type = "event"
5+
6+
7+
+++
8+
9+
<div style="width:100%; text-align:left;">
10+
11+
Embed registration iframe/link/etc.
12+
</div></div>
13+
</div>

‎content/events/2016-kansascity/sponsor.md

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "sponsor"
4+
type = "event"
5+
6+
7+
+++
8+
9+
We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
10+
11+
<hr>
12+
13+
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.
14+
<br>
15+
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.
16+
<br>
17+
The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
18+
<br>
19+
<hr/>
20+
21+
<!--
22+
23+
<div style="width:590px">
24+
<table border=1 cellspacing=1>
25+
<tr>
26+
<th><i>packages</i></th>
27+
<th><center><b><u>Bronze<br />1000 usd</u></center></b></th>
28+
<th><center><b><u>Silver<br />3000 usd</u></center></b></th>
29+
<th><center><b><u>Gold<br />5000 usd</u></center></b></th>
30+
<th></th>
31+
</tr>
32+
<tr><td>2 included tickets</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
33+
<tr><td>logo on event website</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
34+
<tr><td>logo on shared slide, rotating during breaks</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
35+
<tr><td>logo on all email communication</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
36+
<tr><td>logo on its own slide, rotating during breaks</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
37+
<tr><td>1 minute pitch to full audience (including streaming audience)</td><td>&nbsp;</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr></tr>
38+
<tr><td>2 additional tickets (4 in total)</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td>&nbsp;</td></tr>
39+
<tr><td>4 additional tickets (6 in total)</td><td>&nbsp;</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
40+
<tr><td>shared table for swag</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td>&nbsp;</td></tr>
41+
<tr><td>booth/table space</td><td>&nbsp;</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
42+
</table>
43+
<hr/>
44+
There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, <a href="mailto:<%= render(:partial => "/#{@eventhome}/_email_organizers") %>?subject=Sponsor devopsdays <%= @eventid %>">send us an email</a>.
45+
<br/>
46+
<br/>
47+
</div>
48+
-->
49+
<hr/>

‎content/events/2016-kansascity/welcome.md

+52
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
+++
2+
date = "2016-05-07T09:30:25-05:00"
3+
title = "welcome"
4+
type = "event"
5+
aliases = ["/events/2016-kansascity"]
6+
7+
+++
8+
9+
## {{< event_start >}} - {{< event_end >}}
10+
11+
DevOps Days is coming to {{< event_location >}}!
12+
13+
<!-- <div style="text-align:center;">
14+
{{< event_logo >}}
15+
</div> -->
16+
17+
<table>
18+
<tr>
19+
<td><b>Dates</b></td>
20+
<td>{{< event_start >}} - {{< event_end >}}
21+
</tr>
22+
<!-- <tr>
23+
<td><b>Location</b></td>
24+
<td>{{< event_location >}}</td>
25+
</tr> -->
26+
<!-- <tr>
27+
<td><b>Propose</b></td>
28+
<td>{{< event_link page="propose" text="Propose a talk!" >}}</td>
29+
</tr> -->
30+
<!-- <tr>
31+
<td><b>Register</b></td>
32+
<td>{{< event_link page="registration" text="Register to attend the event!" >}}</td>
33+
</tr> -->
34+
<!-- <tr>
35+
<td><b>Speakers</b></td>
36+
<td>View the {{< event_link page="program" text="program" >}}.</td>
37+
</tr> -->
38+
<tr>
39+
<td><b>Sponsors</b></td>
40+
<td>{{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.</td>
41+
</tr>
42+
<tr>
43+
<td><b>Contact</b></td>
44+
<td>{{< event_link page="contact" text="Get in touch with the Organizers" >}}</td>
45+
</tr>
46+
<tr>
47+
<td></td>
48+
<td>
49+
{{< event_twitter devopsdayskc >}}
50+
</td>
51+
</tr>
52+
</table>

0 commit comments

Comments
 (0)