Skip to content

Commit 6913421

Browse files
authored
Merge pull request #15704 from rjw1/add-london-2026
[LDN-2026] Add London 2026
2 parents d16c881 + 3cda8ba commit 6913421

12 files changed

Lines changed: 482 additions & 1 deletion

File tree

assets/events/2026-london/logo.png

57.9 KB
Loading
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
+++
2+
Title = "Conduct"
3+
Type = "event"
4+
Description = "Code de conduite devopsdays London 2026"
5+
+++
6+
7+
Tous les participants, conférenciers, sponsors et volontaires à devopsdays London 2026 doivent accepter le code d'éthique et de déontologie, ou « code de conduite » suivant. Les organisateurs s’attacheront à faire respecter ce code durant l’événement. Nous attendons la coopération de chacun‧e pour assurer un environnement sain pour tous.
8+
9+
10+
### La Version Rapide
11+
12+
Notre conférence tient à être une expérience sans harcèlement pour tous, quel que soit votre sexe, votre identité sexuelle, votre âge, votre orientation sexuelle, votre handicap, votre apparence physique, votre poids, votre race, votre ethnie, votre religion (ou absence de religion), ou vos choix technologiques.
13+
14+
Nous ne tolérons aucun harcèlement des participant‧e‧s à la conférence, sous quelque forme que ce soit, quelles qu’en soient les circonstances. Les expressions et les images à connotation sexuelle ne sont pas appropriées lors de l'événement. Ceci inclut les conférences, les ateliers, les soirées, Twitter et les autres médias en ligne.
15+
16+
L'organisation s'engage à prendre des sanctions appropriées pour les personnes qui violent ces règles, jusqu'à l'exclusion sans remboursement et le recours légal.
17+
18+
19+
### La Version Moins Rapide
20+
21+
Le harcèlement comprend les commentaires à l'oral ou à l'écrit ainsi que les gestes offensants sur le sexe, l'identité sexuelle, l'âge, l'orientation sexuelle, le handicap, l'apparence physique, le poids, la race, l'ethnie, la religion, les choix technologiques, les images à connotation sexuelle dans des lieux publics, les intimidations délibérées, la traque, la poursuite, un harcèlement photographique ou vidéo, une suite d'interruptions des conférences et des autres sessions, un contact physique inapproprié et des avances sexuelles non désirées. sans son consentement ou à son insu.
22+
23+
Les participant‧e‧s à qui il sera demandé d'arrêter tout comportement de harcèlement doivent arrêter immédiatement.
24+
25+
Les sponsors sont aussi sujet à la politique anti-harcèlement. En particulier, les sponsors ne doivent pas utiliser d'images ou de supports à connotation sexuelle. Ils ne doivent pas non plus se livrer à des activités à connotation sexuelle. L'équipe du stand (y compris les bénévoles) ne doit pas utiliser de vêtements, uniformes ou costumes à connotation sexuelle. Ils ne doivent pas non plus créer un environnement sexualisé.
26+
27+
Face à un comportement de harcèlement, l'équipe d'organisation de la conférence peut prendre toute action qui lui semble adéquate. Cela va d'un simple avertissement à l'exclusion sans remboursement de la conférence.
28+
29+
Si vous vous sentez harcelé‧e, si vous pensez que quelqu'un se fait harceler, et plus généralement en cas de problème, merci de contacter immédiatement l’équipe d’organisation de l'événement.
30+
31+
Les membres de l'organisation sont facilement identifiables grâce à un badge "STAFF". Les membres de l'organisation seront ravi‧e‧s d'aider les participants à contacter la sécurité de l'événement, ou les forces de l'ordre ; à fournir une escorte ainsi qu'à aider de toute autre façon les personnes victimes de harcèlement, pour garantir leur sécurité pendant la durée de l'événement. Nous apprécions votre participation à l'événement.
32+
33+
Nous attendons de chacun‧e le respect de ces règles dans le bâtiment des conférences et des ateliers, ainsi que pendant les événements sociaux relatifs à la conférence.
34+
35+
36+
37+
Le code de conduite devopsdays London 2026 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
+++
2+
Title = "Conduta"
3+
Type = "event"
4+
Description = "Código de conduta do devopsdays London 2026"
5+
+++
6+
7+
8+
Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays London 2026 são requeridos a concordar com o seguinte código de conduta. A organização irá aplicar este código pelo evento. Nós esperamos cooperação de todas as pessoas participando para garantir um ambiente seguro para todas as pessoas.
9+
10+
### A versão rápida
11+
12+
Nossa conferência é dedicada a prover um uma experiência de conferência sem assédio para todos, independente de gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias. Nós não toleramos assédio de participantes da conferência de qualquer forma. Linguagem e imagens sexuais não são apropriadas em nenhum local, incluindo palestras, workshops, festas, Twitter e outras mídias online. Violações destas regras poderão causar expulsão da conferência, sem reembolso a critério da equipe organizadora.
13+
14+
### A versão não tão rápida
15+
16+
Assédio inclui comentários verbais ofensivos relacionados a gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias, imagens sexuais em espaços públicos, intimidação deliberada, stalking, perseguição, fotografias ou filmagens constrangedoras, interrupção contínua das apresentações ou outros eventos, contato físico inapropriado e atenção sexual indesejada. Participantes que receberem uma solicitação para interromper qualquer comportamento de assédio devem fazer isso imediatamente.
17+
18+
As políticas antiassédio também se aplicam a representantes de empresas patrocinadoras. Em particular, não devem usar imagens, atividades ou outro material de cunho sexual. As equipes de estandes e tendas (incluindo pessoas voluntárias) não devem utilizar roupas, uniformes ou trajes sexualizados ou criar um ambiente sexualizado de quaisquer formas.
19+
20+
Se alguém se envolver em comportamento de assédio, a equipe organizadora pode tomar qualquer ação que considerar apropriada, incluindo avisar a pessoa ofensora ou expulsá-la da conferência sem reembolso.
21+
22+
Se você estiver sofrendo assédio, notar que alguém está sofrendo assédio, ou tenha alguma dúvida, por favor contate alguém da organização imediatamente.
23+
24+
As pessoas da equipe da conferência podem ser identificadas por crachás distintos da organização. A organização estará disposta a contatar a segurança do hotel/local ou a polícia local, fornecer escolta ou ajudar pessoas que sofrerem assédio para que se sintam seguras durante a conferência. Nós valorizamos a sua participação.
25+
26+
Esperamos que todas as pessoas participantes sigam estas regras em salas de apresentação e workshops da conferência, além de eventos sociais relacionados.
27+
28+
_O código de conduta do devopsdays London 2026 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
+++
2+
Title = "Conduct"
3+
Type = "event"
4+
Description = "devopsdays London - Code Of Conduct"
5+
+++
6+
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.
9+
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.
13+
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.
17+
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:
20+
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.
26+
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.
28+
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;
32+
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.
39+
40+
Participants asked to stop any prohibited behaviour are expected to comply immediately.
41+
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:
45+
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.
52+
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
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
+++
2+
Title = "Contact"
3+
Type = "event"
4+
Description = "Contact information for devopsdays London 2026"
5+
+++
6+
7+
If you'd like to contact us by email: {{< email_organizers >}}
8+
9+
**Our local team**
10+
11+
{{< list_organizers >}}
12+
13+
14+
{{< list_core >}}
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
+++
2+
Title = "Location"
3+
Type = "event"
4+
Description = "Location for devopsdays London 2026"
5+
+++
6+
7+
Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details.
8+
9+
<!-- Uncomment this only if you have set the coordinates for your location in the config yaml. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html -->
10+
<!-- {{< event_map >}} -->
11+
12+
<!-- Edit and uncomment to let people know what accessibility features you have available -->
13+
<!--
14+
Example from Minneapolis 2020
15+
16+
We offer wheelchair-designated spaces, chairs, and standing options (with tall tables) in the mainstage session room; a quiet room; bathrooms labeled according to the facilities they contain; professional live captioning of mainstage sessions; ingredient labeling (based on data provided when registering); and private space (upon request) for those nursing. We'd also be happy to accommodate any other accessibility needs upon request: {{< email_organizers >}}
17+
-->
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
+++
2+
Title = "Propose"
3+
Type = "event"
4+
Description = "Propose a talk for devopsdays London 2026"
5+
+++
6+
{{< cfp_dates >}}
7+
8+
<hr>
9+
10+
There are three ways to propose a topic at devopsdays:
11+
<ol>
12+
<li><strong><em>A 30-minute talk</em></strong> presented during the conference, usually in the mornings.</li>
13+
<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>
14+
<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.
15+
</ol>
16+
17+
<hr>
18+
19+
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:
20+
21+
- _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.
22+
- _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.
23+
- _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.
24+
- _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.
25+
- _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.
26+
- _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.
27+
28+
<hr>
29+
30+
<strong>How to submit a proposal:</strong> Send an email to [{{< email_organizers >}}] with the following information
31+
<ol>
32+
<li>Type (presentation, panel discussion, ignite)</li>
33+
<li>Proposal Title (can be changed later)</li>
34+
<li>Description (several sentences explaining what attendees will learn)</li>
35+
</ol>
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
+++
2+
Title = "Registration"
3+
Type = "event"
4+
Description = "Registration for devopsdays London 2026"
5+
+++
6+
7+
<div style="width:100%; text-align:left;">
8+
9+
Embed registration iframe/link/etc.
10+
</div></div>
11+
</div>
Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
+++
2+
Title = "Sponsor"
3+
Type = "event"
4+
Description = "Sponsor devopsdays London 2026"
5+
+++
6+
7+
We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
8+
9+
<hr>
10+
11+
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.
12+
<p>
13+
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.
14+
<p>
15+
The best thing to do is send engineers to interact with the experts at devopsdays on their own terms.
16+
<p>
17+
18+
<!--
19+
<hr/>
20+
21+
<div style="width:590px">
22+
<table border=1 cellspacing=1>
23+
<tr>
24+
<th><i>packages</i></th>
25+
<th><center><b><u>Bronze<br />1000 usd</u></center></b></th>
26+
<th><center><b><u>Silver<br />3000 usd</u></center></b></th>
27+
<th><center><b><u>Gold<br />5000 usd</u></center></b></th>
28+
<th></th>
29+
</tr>
30+
<tr><td>2 included tickets</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
31+
<tr><td>logo on event website</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
32+
<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>
33+
<tr><td>logo on all email communication</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
34+
<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>
35+
<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>
36+
<tr><td>2 additional tickets (4 in total)</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td>&nbsp;</td></tr>
37+
<tr><td>4 additional tickets (6 in total)</td><td>&nbsp;</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
38+
<tr><td>shared table for swag</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td>&nbsp;</td></tr>
39+
<tr><td>booth/table space</td><td>&nbsp;</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
40+
</table>
41+
<hr/>
42+
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, send us an email.
43+
<br/>
44+
<br/>
45+
46+
<br>
47+
<br>
48+
<table border=1 cellspacing=1>
49+
<tr>
50+
<th><i>Sponsor FAQ</i></th>
51+
<th><center><b>Answers to questions frequently asked by sponsors&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</center></b></th>
52+
<th></th>
53+
</tr>
54+
<tr><td>What dates/times can we set up and tear down?</td><td></td></tr>
55+
<tr><td>How do we ship to the venue?</td><td></td></tr>
56+
<tr><td>How do we ship from the venue?</td><td></td></tr>
57+
<tr><td>Whom should we send?</td><td></td></tr>
58+
<tr><td>What should we expect regarding electricity? (how much, any fees, etc)</td><td></td></tr>
59+
<tr><td>What should we expect regarding WiFi? (how much, any fees, etc)</td><td></td></tr>
60+
<tr><td>How do we order additional A/V equipment?</td><td></td></tr>
61+
<tr><td>Additional important details</td><td></td></tr>
62+
</table>
63+
</div>
64+
65+
-->
66+
<hr/>

0 commit comments

Comments
 (0)