Skip to content

Commit 6b6677b

Browse files
authored
Merge branch 'main' into ge-sponsor
2 parents b398ee3 + 6394c29 commit 6b6677b

7 files changed

Lines changed: 98 additions & 86 deletions

File tree

content/events/2025-london/conduct-fr.md

Lines changed: 0 additions & 37 deletions
This file was deleted.

content/events/2025-london/conduct-pt-br.md

Lines changed: 0 additions & 28 deletions
This file was deleted.
Lines changed: 40 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,56 @@
11
+++
22
Title = "Conduct"
33
Type = "event"
4-
Description = "Code of conduct for DevOpsDays London 2025"
4+
Description = "devopsdays London - Code Of Conduct"
55
+++
66

7+
### Purpose
8+
The organisers of devopsdays London are committed to enabling an event at which everyone can participate in an inclusive, respectful and safe environment. All participants are expected to behave with integrity and respect towards all participants attending or involved with devopsdays London.
79

8-
All attendees, speakers, sponsors, and volunteers at DevOpsDays London 2025 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody.
10+
### Scope / Applicability
11+
The Code of Conduct applies to all devopsdays London events which includes talks, open spaces, all interactions within the conference, social events and any other event organised by devopsdays London.
12+
The Code of Conduct applies to all participants at devopsdays London. Including attendees, speakers, sponsors, suppliers, volunteers, organisers and guests.
913

10-
### The Quick Version
14+
### Report contact details
15+
Our team members are identifiable by their purple devopsdays London t-shirts and can always be approached. We will always have someone available on the welcome desk and we also have a staffed phone and email address for reporting issues.
16+
Our team is available during all official events, including the speaker dinner and the social event(s), and our designated contacts stay sober throughout our events.
1117

12-
Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
18+
### Our standards & values
19+
Inclusiveness and respect for differences are core DevOps values, and we invite you to help us make this event a place that is welcoming and respectful to all participants. Examples of behaviour that contributes to a positive environment for our community include:
1320

14-
### The Less Quick Version
21+
- Demonstrating empathy and kindness toward other people;
22+
- Being respectful of differing opinions, viewpoints, and experiences;
23+
- Giving and gracefully accepting constructive feedback;
24+
- Accepting responsibility and apologising to those affected by our mistakes, and learning from the experience;
25+
- Focusing on what is best not just for us as individuals, but for the overall community.
1526

16-
Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, 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.
27+
Don’t judge and make assumptions just because someone is different whether in some visible way or in their lived experience. We ask everybody to treat each other with respect.
1728

18-
Sponsors are also subject to the anti-harassment policy. In particular, sponsors 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.
29+
### Prohibited conduct
30+
Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), technology choices, or the choice to wear a protective face mask. Examples of unacceptable behaviour include:
31+
The use of sexualized language, imagery, or clothing, and sexual attention or advances of any kind;
1932

20-
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.
33+
- Inappropriate touching, including pinching, patting, rubbing or purposefully brushing up against a person;
34+
- Rating a person’s appearance;
35+
- Trolling, insulting or derogatory comments, and personal or political attacks;
36+
- Sustained disruption of talks, sessions or other events;
37+
- Sharing others’ private information, such as a physical or email address, without their explicit permission;
38+
- Other conduct which could reasonably be considered inappropriate in a professional setting.
2139

22-
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.
40+
Participants asked to stop any prohibited behaviour are expected to comply immediately.
2341

24-
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.
42+
### Complaint process
43+
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of the conference staff immediately. Conference staff can be identified by distinct purple t-shirts. If a participant engages in prohibited behaviour, the conference organisers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
44+
Examples of appropriate action may include, but are not limited to:
2545

26-
We expect participants to follow these rules at conference and workshop venues and conference-related social events.
46+
- Undertaking a fact-finding exercise;
47+
- Requesting the offender to immediately stop the offending behaviour;
48+
- Suspending or terminating the offender’s access to the event;
49+
- Conveying the complaint to any investigative or disciplinary authority with jurisdiction over the person accused of harassment;
50+
- Contacting the offender’s employer for appropriate follow-up action.
51+
- Banning from future events.
2752

28-
_The DevOpsDays London 2025 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._
53+
We’re 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.
54+
55+
### Attribution
56+
The devopsdays London 2025 Code of Conduct is based on the Contributor Covenant, version 2.1, the UN Code of Conduct and the DevOpsDays Amsterdam 2024 Code of Conduct

content/events/2025-london/location.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,5 +4,6 @@ Type = "event"
44
Description = "Location for DevOpsDays London 2025"
55
+++
66

7-
Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details.
7+
The event will be held in the Sir Alexander Fleming building at Imperial College London.
88

9+
{{< event_map >}}

content/events/2025-london/propose.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,47 @@ Type = "event"
44
Description = "Propose a talk for DevOpsDays London 2025"
55
+++
66

7+
{{< cfp_dates >}}
8+
9+
<hr>
10+
11+
<center><h2>Our CFP is now open! Use <a href="https://docs.google.com/forms/d/e/1FAIpQLSfCx7yU_RInIncwU2dP48S790CY-LpNi9nenUsY82vRv0HKkQ/viewform">this form</a> to propose a talk.</h2></center>
12+
13+
<hr>
14+
15+
There are three ways to propose a topic at devopsdays:
16+
<ol>
17+
<li><strong><em>A 30-minute talk</em></strong> presented during the conference, usually in the mornings.</li>
18+
<li><strong><em>An Ignite talk</em></strong> presented during the <a href="/pages/ignite-talks-format">Ignite sessions</a> (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).</li>
19+
<li><strong><em>Open Space</em></strong>: If you'd like to lead a group discussion during the attendee-suggested <a href="/pages/open-space-format">Open Space</a> breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should <a href="../sponsor">sponsor the event</a> and demo it at your table.
20+
</ol>
21+
22+
<hr>
23+
24+
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:
25+
26+
- _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.
27+
- _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 area. We are happy to provide guidance/coaching for new speakers upon request.
28+
- _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.
29+
- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen.
30+
- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. 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.
31+
- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
32+
33+
<hr>
34+
As a speaker we will provide you with:
35+
36+
- a free ticket to the conference
37+
- free ticket for 1 other person and some discount codes
38+
<!-- - an invite to the speakers dinner the night before the conference starts -->
39+
40+
in addition, if you are personally funding your attendance we have some budget to cover reasonable travel and accommodation costs.
41+
42+
<hr>
43+
44+
### Help with your talk
45+
46+
If you are a first time speaker and/or from an under represented group in technology
47+
we would like to help you with your talk.
48+
49+
Several of the committee are veteran speakers and can provide help and suggestions
50+
to make your talk better should it be selected.

0 commit comments

Comments
 (0)