You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/events/2016-philadelphia/propose.md
+36-23
Original file line number
Diff line number
Diff line change
@@ -8,33 +8,46 @@ type = "event"
8
8
+++
9
9
{{< cfp_dates >}}
10
10
11
+
<center>
12
+
<b>Call for proposals closes Thursday June 30th.</b><br>
13
+
Selected proposals will be announced within a few weeks of the closing date.
14
+
</center>
15
+
11
16
<hr>
12
-
There are three ways to propose a session:
13
-
<ol>
14
-
<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>
15
-
<li><strong><em>An Ignite talk</em></strong> that will be presented during the<ahref="/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>
16
-
<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 <ahref="/pages/open-space-format">Open Space explanation</a> for more information.
<ahref="http://bit.ly/devopsdaysphl16cfp">Submit a Session Proposal</a>
19
+
</div>
20
+
<hr>
21
+
22
+
Devopsdays Philadelphia is a single track, two day event. The format will include main track presentations, <ahref="/pages/ignite-talks-format">Ignite talks</a>, and <ahref="pages/open-space-format">Open Spaces sessions</a>. We're soliciting proposals for 30 minute presentations and Ignite style lightning talks.
18
23
19
-
### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
24
+
A selection committee will review all proposed talks. Submitters will receive an email update before the program is announced. All proposals must be received by Thursday June 30th. Selected proposals will be announced within a few weeks of the closing date.
20
25
21
-
Our main criteria to make it to the top selection are:
26
+
Are you new to public speaking? We can provide guidance/coaching for new speakers upon request.
22
27
23
-
-_original content_: content not yet presented at other conferences, or a new angle to an existing problem
24
-
-_new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
25
-
-_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.
28
+
There are three types of sessions that you can propose. This call for proposals covers types 1 and 2.
26
29
27
-
<strong>How to submit a proposal:</strong> Send an email to [{{< email_proposals >}}] with the following information
28
30
<ol>
29
-
<li>Proposal working title (can be changed later)</li>
30
-
<li>Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)</li>
31
-
<li>Description or abstract</li>
31
+
<li><strong><em>Talk/panel</em></strong> for the conference main track. These are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.</li>
32
+
<li><strong><em>Ignite talk</em></strong> that will be presented during the <ahref="/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>
33
+
<li><strong><em>Open Space session</em></strong>. We welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the <ahref="/pages/open-space-format">Open Space explanation</a> for more information.</li>
32
34
</ol>
33
-
<strong>Rules:</strong>
34
-
<ul>
35
-
<li>Be specific... we aren't mind readers (a description of about 20 lines is about right)</li>
36
-
<li>Detail is good... but not as important as explaining why your proposal would be interesting</li>
37
-
<li>Propose your own talk; don't have someone else do it for you.</li>
38
-
<li>Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!</li>
39
-
<li>Multiple proposals welcome... just follow the other rules</li>
40
-
</ul>
35
+
36
+
### Selection Guidelines
37
+
38
+
Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
39
+
40
+
* Broad appeal: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
41
+
* New local presenters: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local Philadelphia area communities.
42
+
* Under-represented voices: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
43
+
* Original content: We prefer talks not already presented at another event, especially another one in the local area or one available in recorded form.
44
+
* No third-party submissions: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
45
+
* No vendor pitches: We value vendors and sponsors, however we cannot accept a talk that appears to be a pitch for your product. If you'd like to demo your product or service, please consider sponsoring the event to secure your company a table.
46
+
47
+
### Code of Conduct
48
+
49
+
Please review the event <ahref="http://www.devopsdays.org/events/2016-philadelphia/conduct/">code of conduct</a>.
50
+
51
+
### Travel Expenses
52
+
53
+
If your employer does not cover travel expenses you incur as a speaker at Devopsdays Philadelphia the conference will help. Speakers receive free conference tickets and should not incur out-of-pocket travel expenses in order to participate.
Copy file name to clipboardExpand all lines: content/events/2016-philadelphia/sponsor.md
+34-27
Original file line number
Diff line number
Diff line change
@@ -7,44 +7,51 @@ type = "event"
7
7
8
8
+++
9
9
10
-
We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
10
+
We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}. Gold, Silver, and Bronze sponsorship packages are detailed in our <ahref="events/2016-philadelphia/sponsor/devopsdaysPHL2016-prospectus.pdf">prospectus</a>.
11
11
12
-
<hr>
12
+
Additional à la carte sponsorships are also possible:
13
13
14
-
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.
15
-
<br>
16
-
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.
17
-
<br>
18
-
The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
19
-
<br>
20
-
<hr/>
14
+
<ul>
15
+
<li>coffee - signage by the coffee displays with your logo throughout the day
16
+
<li>breakfast - signage by the breakfast tables and in the eating area with your logo in the morning before sessions
17
+
<li>snacks - signage by the snack area with your logo during the afternoon when snacks are available
18
+
<li>lunch - signage by the lunch tables and in the eating area with your logo during lunch
19
+
<li>evening reception - signage at the evening happy hour
20
+
<li>lanyards
21
+
<li>room and session sponsorships
22
+
<li>logo and t-shirt design
23
+
</ul>
21
24
22
-
<!--
25
+
These may be purchased in addition to (or in lieu of) the sponsorships in the prospectus.
26
+
27
+
Please email us at {{< email_organizers >}} for more information.
<tr><td>2 included tickets</td><tdbgcolor="gold"> </td><tdbgcolor="gold"> </td><tdbgcolor="gold"> </td></tr>
34
-
<tr><td>logo on event website</td><td bgcolor="gold"> </td><td bgcolor="gold"> </td><td bgcolor="gold"> </td></tr>
35
-
<tr><td>logo on shared slide, rotating during breaks</td><td bgcolor="gold"> </td><td bgcolor="gold"> </td><td bgcolor="gold"> </td></tr>
36
-
<tr><td>logo on all email communication</td><td> </td><td bgcolor="gold"> </td><td bgcolor="gold"> </td></tr>
37
-
<tr><td>logo on its own slide, rotating during breaks</td><td> </td><td bgcolor="gold"> </td><td bgcolor="gold"> </td></tr>
38
-
<tr><td>1 minute pitch to full audience (including streaming audience)</td><td> </td><td> </td><td bgcolor="gold"> </td></tr></tr>
39
-
<tr><td>2 additional tickets (4 in total)</td><td> </td><td bgcolor="gold"> </td><td> </td></tr>
40
-
<tr><td>4 additional tickets (6 in total)</td><td> </td><td> </td><td bgcolor="gold"> </td></tr>
41
-
<tr><td>shared table for swag</td><td> </td><td bgcolor="gold"> </td><td> </td></tr>
<tr><td>Logo on DevOpsDays Philadelphia website and on event signage.</td><tdbgcolor="gold"> </td><tdbgcolor="gold"> </td><tdbgcolor="gold"> </td></tr>
46
+
<tr><td>Logo on all attendee email.</td><td> </td><tdbgcolor="gold"> </td><tdbgcolor="gold"> </td></tr>
47
+
<tr><td>1 minute pitch to all attendees</td><td> </td><td> </td><tdbgcolor="gold"> </td></tr>
43
48
</table>
44
-
<hr/>
45
-
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>.
46
-
<br/>
47
-
<br/>
48
49
</div>
49
-
-->
50
+
51
+
DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee 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.
52
+
53
+
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.
54
+
55
+
The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
Copy file name to clipboardExpand all lines: data/events/2016-philadelphia.yml
+21-8
Original file line number
Diff line number
Diff line change
@@ -9,18 +9,33 @@ cfp_date_start: 2016-04-01
9
9
cfp_date_end: 2016-06-01
10
10
cfp_date_announce: 2016-07-01
11
11
coordinates: "39.9500, -75.1667"# The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
12
-
location: "location"# The name of your location
13
-
navigationelements: ["welcome", "contact", "location", "program", "propose", "proposals", "registration", "conduct", "sponsor"] # List of pages you want to show up in the navigation of your page. Remove any that aren't relevent yet.
14
-
team: ["John Doe", "Jane Smith", "Sally Fields"]
12
+
location: "Chemical Heritage Foundation"# The name of your location
13
+
navigationelements:
14
+
- "welcome"
15
+
- "contact"
16
+
- "location"
17
+
- "propose"
18
+
- "registration"
19
+
- "conduct"
20
+
- "sponsor"# List of pages you want to show up in the navigation of your page. Remove any that aren't relevent yet.
21
+
team:
22
+
- "Peter Shannon"
23
+
- "Dave Konopka"
24
+
- "Sarah Gray"
25
+
- "Yash Prabhu"
26
+
- "Mike Tyler"
27
+
- "Clinton Wolfe"
15
28
organizer_email: "[email protected]"# Put your organizer email address here
16
29
proposal_email: "[email protected]"# Put your proposal email address here
17
30
sponsors: # List all of your sponsors here along with what level of sponsorship they have.
18
31
- id: chef
19
32
level: gold
20
-
- id: datadog
33
+
- id: dramafever
21
34
level: gold
22
-
- id: arresteddevops
23
-
level: community
35
+
- id: pivotal
36
+
level: gold
37
+
- id: victorops
38
+
level: silver
24
39
25
40
sponsor_levels: # In this section, list the level of sponsorships and the label to use.
26
41
- id: gold
@@ -29,5 +44,3 @@ sponsor_levels: # In this section, list the level of sponsorships and the label
0 commit comments