Skip to content

[PRAGUE-2026] adding the Prague 2026 event #15321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/events/2026-prague/organizers/z_vana.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
28 changes: 28 additions & 0 deletions content/events/2026-prague/conduct.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
+++
Title = "Conduct"
Type = "event"
Description = "Code of conduct for DevOpsDays Prague 2026"
+++


All attendees, speakers, sponsors, and volunteers at DevOpsDays Prague 2026 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.

### The Quick Version

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.

### The Less Quick Version

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.

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.

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 follow these rules at conference and workshop venues and conference-related social events.

_The DevOpsDays Prague 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._
14 changes: 14 additions & 0 deletions content/events/2026-prague/contact.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
+++
Title = "Contact"
Type = "event"
Description = "Contact information for DevOpsDays Prague 2026"
+++

If you'd like to contact us by email: {{< email_organizers >}}

**Our local team**

{{< list_organizers >}}


{{< list_core >}}
29 changes: 29 additions & 0 deletions content/events/2026-prague/location.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
+++
Title = "Location"
Type = "event"
Description = "Location for DevOpsDays Prague 2026"
+++

<br />
<p>The conference will take place at the Clarion Congress Hotel</p>
<p>Freyova 33<br />
190 00, Praha 9</p>

<p>
The venue is directly above a subway station (Vysocanska - yellow B line) so we recommend using public transport to get there.<br />
If you need to take a car you may use parking in Fenix Shoppng Center - first 3 hours for free, after that 50 CZK/hour. Alternatively you can use the streets around for 30 CZK/hour.
</p>

<p>
The venue is wheelchair accessible and we'd be happy to accommodate any other accessibility needs upon request: {{< email_organizers >}}.
</p>

<!-- 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 -->
<!-- {{< event_map >}} -->

<!-- Edit and uncomment to let people know what accessibility features you have available -->
<!--
Example from Minneapolis 2020

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 >}}
-->
18 changes: 18 additions & 0 deletions content/events/2026-prague/program.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
+++
Title = "Program"
Type = "program"
Description = "Program for devopsdays Prague 2026"
+++

<hr />
If Open Space is new to you, you may be interested in <a href="/pages/open-space-format">more details about Open Space</a>.
<hr />

<div>
<b>Color Keys:</b>
<div class="col-lg-2 col-md-2 program-element program-talk">Talk</div>
<div class="col-lg-2 col-md-2 program-element program-ignite">Ignite</div>
<div class="col-lg-2 col-md-2 program-element program-open-space">Open Space</div>
</div>

<hr />
10 changes: 10 additions & 0 deletions content/events/2026-prague/propose.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
+++
Title = "Propose"
Type = "event"
Description = "Propose a talk for DevOpsDays Prague 2026"
+++
{{< cfp_dates >}}

<hr>

Head to [the CFP](https://www.papercall.io/dodprague) for more information.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this page isn't linked, the url here does not work

11 changes: 11 additions & 0 deletions content/events/2026-prague/registration.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
+++
Title = "Registration"
Type = "event"
Description = "Registration for DevOpsDays Prague 2026"
+++

<div style="width:100%; text-align:left;">

{{< tix city="prague" year="2026" >}}

</div>
5 changes: 5 additions & 0 deletions content/events/2026-prague/speakers.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
+++
Title = "Speakers"
Type = "speakers"
Description = "Speakers for Devopsdays Prague 2026"
+++
213 changes: 213 additions & 0 deletions content/events/2026-prague/sponsor.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,213 @@
+++
Title = "Sponsor"
Type = "event"
Description = "Sponsor DevOpsDays Prague 2026"
+++

We greatly value sponsors for this open event. If you are interested in sponsoring, please <a href="mailto:[email protected]?subject=Interested%20in%20Sponsoring%20DevOpsDays%20Prague%202026">send us an email</a>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This includes a off mailing list email
@nimbinatus is this ok?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching that, @toshywoshy! @alllomancer, one of the few rules we enforce is around published mailing lists being an *@devopsdays.org mailing list. This allows global core to ensure that we can help if there's anything that goes wrong with your event, as well as ensuring future organizers have access to the same mailing list should someone try to reach a future event using a past email. I'm more than happy to make you a prague-sponsors@ mailing list and put your internal one listed here as the only subscriber, though, so you can continue to work with the tools you have. Mind sending me an email at [email protected] so I can facilitate that for you?


<a class="btn btn-primary btn-block" style = "width: 200px; margin-top: 10px; margin-bottom: 10px; background-color: #96bfe6; border-color: #96bfe6;" href="https://assets.devopsdays.org/events/2025/prague/DevOpsDays-Prague-2025-prospectus.pdf" target="_blank">Download Sponsoring Kit!</a>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You still have 2025 listed here, you should update to a 2026 version


<hr>

DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not provide speaker slots nor distribute attendee contact lists as part of any sponsorship. 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.
<p>
Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. All attendees are welcome to propose any subject they want during the open spaces, including product demos, 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. The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
<p>
Gold sponsors get a big table and Silver sponsors a small table where they can interact with those interested to come visit during breaks and any sponsor is free to collect attendee information with mutual consensus.
<p>

<hr/>

<center><h3>Sponsor Packages</h3></center>

<div align="center">
<table border=1 cellspacing=1 cellpadding=10>
<tr>
<th></th>
<th bgcolor="#1A83A9"><center><font color=white><b>Community<br/></font></center></b></th>
<th bgcolor="#FFC000"><center><font color=white><b>Gold<br/></font></center></b></th>
<th bgcolor="#C0C0C0"><center><font color=white><b>Silver<br/></font></center></b></th>
<th bgcolor="#CD7F32"><center><font color=white><b>Bronze<br/></font></center></b></th>
<th bgcolor="#0D9850"><center><font color=white><b>Lanyard<br/></font></center></b></th>
<th bgcolor="#0D9850"><center><font color=white><b>T-Shirt<br/></font></center></b></th>
</tr>
<tr>
<td>Price</td>
<td><center>FREE</center></td>
<td><center>4000&nbsp;EUR</center></td>
<td><center>2500&nbsp;EUR</center></td>
<td><center>1200&nbsp;EUR</center></td>
<td><center>3000&nbsp;EUR</center></td>
<td><center>6000&nbsp;EUR</center></td>
</tr>
<tr>
<td>Number available</td>
<td bgcolor="#d9ead3">∞</td>
<td bgcolor="#d9ead3">SOLD OUT</td>
<td bgcolor="#d9ead3">5</td>
<td bgcolor="#d9ead3">∞</td>
<td bgcolor="#d9ead3">SOLD OUT</td>
<td bgcolor="#d9ead3">SOLD OUT</td>
</tr>
<tr>
<td>Tickets included</td>
<td bgcolor="#d9ead3">1</td>
<td bgcolor="#d9ead3">6</td>
<td bgcolor="#d9ead3">4</td>
<td bgcolor="#d9ead3">2</td>
<td bgcolor="#d9ead3">4</td>
<td bgcolor="#d9ead3">8</td>
</tr>
<tr>
<td>Discount for additional tickets</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
</tr>
<tr>
<td>Booth</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">large</td>
<td bgcolor="#d9ead3">small</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">large</td>
</tr>
<tr>
<td>Banner/roll-up on the main stage</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">1</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">1</td>
<td>&nbsp;</td>
</tr>
<tr>
<td>On stage pitch</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">1min</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">1min</td>
</tr>
<tr>
<td>Logo on a dedicated slide during breaks</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
</tr>
<tr>
<td>Logo on a shared slide during breaks</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td>Special perk</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">Logo on Lanyard</td>
<td bgcolor="#d9ead3">Logo on T-shirts</td>
</tr>
<tr>
<td>Logo in newsletters</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
</tr>
<tr>
<td>Placement of company logo on social media</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
</tr>
<tr>
<td>Logo on the event page</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
</tr>
<tr>
<td>Swags bag insert</td>
<td>&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
<td bgcolor="#d9ead3">&nbsp;</td>
</tr>
</table>
</div>
<hr/>

<!--


<div style="width:590px">
<table border=1 cellspacing=1>
<tr>
<th><i>packages</i></th>
<th><center><b><u>Bronze<br />1000 usd</u></center></b></th>
<th><center><b><u>Silver<br />3000 usd</u></center></b></th>
<th><center><b><u>Gold<br />5000 usd</u></center></b></th>
<th></th>
</tr>
<tr><td>2 included tickets</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
<tr><td>logo on event website</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
<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>
<tr><td>logo on all email communication</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
<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>
<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>
<tr><td>2 additional tickets (4 in total)</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>4 additional tickets (6 in total)</td><td>&nbsp;</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
<tr><td>shared table for swag</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>booth/table space</td><td>&nbsp;</td><td>&nbsp;</td><td bgcolor="gold">&nbsp;</td></tr>
</table>
<hr/>
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.
<br/>
<br/>

<br>
<br>
<table border=1 cellspacing=1>
<tr>
<th><i>Sponsor FAQ</i></th>
<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>
<th></th>
</tr>
<tr><td>What dates/times can we set up and tear down?</td><td></td></tr>
<tr><td>How do we ship to the venue?</td><td></td></tr>
<tr><td>How do we ship from the venue?</td><td></td></tr>
<tr><td>Whom should we send?</td><td></td></tr>
<tr><td>What should we expect regarding electricity? (how much, any fees, etc)</td><td></td></tr>
<tr><td>What should we expect regarding WiFi? (how much, any fees, etc)</td><td></td></tr>
<tr><td>How do we order additional A/V equipment?</td><td></td></tr>
<tr><td>Additional important details</td><td></td></tr>
</table>
</div>

-->
<hr/>
Loading