-
Notifications
You must be signed in to change notification settings - Fork 667
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #232 from devopsdays/bridget-nashville
Corrections to initial Nashville site
- Loading branch information
Showing
8 changed files
with
72 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
+++ | ||
date = "2000-01-01T01:01:01-06: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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
+++ | ||
date = "2000-01-01T01:01:01-06: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 >}}]. | ||
|
||
<hr> | ||
|
||
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. | ||
<br> | ||
<br> | ||
The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms. | ||
<br> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
name: 2016-nashville # 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. | ||
name: "2016-nashville" # 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: "Nashville" # The city name of the event. Capitalize it. | ||
friendly: "2016-nashville" # Four digit year and the city name in lower-case. Don't forget the dash! | ||
status: "current" # Options are "past" or "current". | ||
|
@@ -10,8 +10,22 @@ cfp_date_end: 2016-08-31 | |
cfp_date_announce: 2016-09-15 | ||
coordinates: "36.160606, -86.7746752" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html | ||
location: "aVenue" # The name of your location | ||
navigationelements: ["welcome", "registration", "sponsor", "contact"] # List of pages you want to show up in the navigation of your page. Remove any that aren't relevent yet. | ||
team: ["James Fryman", "Jurnell Cockhren", "Eliza Marcum", "Chris Wage", "Nick Wallace"] | ||
|
||
nav_elements: # List of pages you want to show up in the navigation of your page. | ||
- name: welcome | ||
- name: registration | ||
url: https://www.eventbrite.com/e/devopsdays-nashville-2016-tickets-23942633060 | ||
- name: sponsor | ||
- name: contact | ||
- name: conduct | ||
|
||
# These are the same people you have on the mailing list and Slack channel. | ||
team_members: # Name is the only required field for team members. | ||
- name: "James Fryman" | ||
- name: "Jurnell Cockhren" | ||
- name: "Eliza Marcum" | ||
- name: "Chris Wage" | ||
- name: "Nick Wallace" | ||
organizer_email: "[email protected]" # Put your organizer email address here | ||
proposal_email: "[email protected]" # Put your proposal email address here | ||
sponsors: # List all of your sponsors here along with what level of sponsorship they have. | ||
|
File renamed without changes.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.