diff --git a/assets/events/2026-krakow/logo-square.png b/assets/events/2026-krakow/logo-square.png new file mode 100644 index 0000000000..a6cdf0b93d Binary files /dev/null and b/assets/events/2026-krakow/logo-square.png differ diff --git a/assets/events/2026-krakow/logo.png b/assets/events/2026-krakow/logo.png new file mode 100644 index 0000000000..957abd3b46 Binary files /dev/null and b/assets/events/2026-krakow/logo.png differ diff --git a/assets/events/2026-krakow/organizers/barc_jakub.jpg b/assets/events/2026-krakow/organizers/barc_jakub.jpg new file mode 100755 index 0000000000..8a479148bd Binary files /dev/null and b/assets/events/2026-krakow/organizers/barc_jakub.jpg differ diff --git a/assets/events/2026-krakow/organizers/godowski_piotr.jpg b/assets/events/2026-krakow/organizers/godowski_piotr.jpg new file mode 100755 index 0000000000..52b1d03c26 Binary files /dev/null and b/assets/events/2026-krakow/organizers/godowski_piotr.jpg differ diff --git a/assets/events/2026-krakow/organizers/kamienski_janusz.jpg b/assets/events/2026-krakow/organizers/kamienski_janusz.jpg new file mode 100755 index 0000000000..f3031ca95e Binary files /dev/null and b/assets/events/2026-krakow/organizers/kamienski_janusz.jpg differ diff --git a/assets/events/2026-krakow/organizers/koltermann_przemyslaw.jpg b/assets/events/2026-krakow/organizers/koltermann_przemyslaw.jpg new file mode 100755 index 0000000000..91c2a3a9e5 Binary files /dev/null and b/assets/events/2026-krakow/organizers/koltermann_przemyslaw.jpg differ diff --git a/assets/events/2026-krakow/organizers/lewandowski_marcin.jpg b/assets/events/2026-krakow/organizers/lewandowski_marcin.jpg new file mode 100644 index 0000000000..aa64cde82b Binary files /dev/null and b/assets/events/2026-krakow/organizers/lewandowski_marcin.jpg differ diff --git a/assets/events/2026-krakow/organizers/piwosz_pawel.jpg b/assets/events/2026-krakow/organizers/piwosz_pawel.jpg new file mode 100755 index 0000000000..5b63b33f10 Binary files /dev/null and b/assets/events/2026-krakow/organizers/piwosz_pawel.jpg differ diff --git a/assets/events/2026-krakow/organizers/placeholder.jpg b/assets/events/2026-krakow/organizers/placeholder.jpg new file mode 100644 index 0000000000..3ff05d60a6 Binary files /dev/null and b/assets/events/2026-krakow/organizers/placeholder.jpg differ diff --git a/assets/events/2026-krakow/organizers/raimundo_pedro_ivo.jpg b/assets/events/2026-krakow/organizers/raimundo_pedro_ivo.jpg new file mode 100644 index 0000000000..0149a3a0e0 Binary files /dev/null and b/assets/events/2026-krakow/organizers/raimundo_pedro_ivo.jpg differ diff --git a/assets/events/2026-krakow/organizers/tomasiewicz_wojciech.jpg b/assets/events/2026-krakow/organizers/tomasiewicz_wojciech.jpg new file mode 100644 index 0000000000..14776a044f Binary files /dev/null and b/assets/events/2026-krakow/organizers/tomasiewicz_wojciech.jpg differ diff --git a/assets/events/2026-krakow/organizers/welian_agnieszka.jpg b/assets/events/2026-krakow/organizers/welian_agnieszka.jpg new file mode 100755 index 0000000000..1c0a61a722 Binary files /dev/null and b/assets/events/2026-krakow/organizers/welian_agnieszka.jpg differ diff --git a/content/events/2026-krakow/conduct-fr.md b/content/events/2026-krakow/conduct-fr.md new file mode 100644 index 0000000000..0287338a4e --- /dev/null +++ b/content/events/2026-krakow/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays Kraków 2026" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays Kraków 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. + + +### La Version Rapide + +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. + +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. + +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. + + +### La Version Moins Rapide + +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. + +Les participant‧e‧s à qui il sera demandé d'arrêter tout comportement de harcèlement doivent arrêter immédiatement. + +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é. + +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. + +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. + +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. + +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. + + + +Le code de conduite devopsdays Kraków 2026 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2026-krakow/conduct-pt-br.md b/content/events/2026-krakow/conduct-pt-br.md new file mode 100755 index 0000000000..32e3e7e425 --- /dev/null +++ b/content/events/2026-krakow/conduct-pt-br.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do devopsdays Kraków 2026" ++++ + + +Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays Kraków 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. + +### A versão rápida + +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. + +### A versão não tão rápida + +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. + +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. + +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. + +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. + +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. + +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. + +_O código de conduta do devopsdays Kraków 2026 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._ diff --git a/content/events/2026-krakow/conduct.md b/content/events/2026-krakow/conduct.md new file mode 100644 index 0000000000..be8523ba07 --- /dev/null +++ b/content/events/2026-krakow/conduct.md @@ -0,0 +1,74 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Kraków 2026" ++++ + + +
+ +All attendees, speakers, sponsors, and volunteers at devopsdays Kraków 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 Kraków 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ +
\ No newline at end of file diff --git a/content/events/2026-krakow/contact.md b/content/events/2026-krakow/contact.md new file mode 100644 index 0000000000..14b6a6eaae --- /dev/null +++ b/content/events/2026-krakow/contact.md @@ -0,0 +1,58 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Kraków 2026" ++++ + + +
+ +If you'd like to contact drop an email to: {{< email_organizers >}} + +## Our local team + +
+ +{{< list_organizers >}} + +{{< list_core >}} + +
\ No newline at end of file diff --git a/content/events/2026-krakow/location.md b/content/events/2026-krakow/location.md new file mode 100644 index 0000000000..6aa68ea866 --- /dev/null +++ b/content/events/2026-krakow/location.md @@ -0,0 +1,17 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays Kraków 2026" ++++ + +Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details. + + + + + + diff --git a/content/events/2026-krakow/propose.md b/content/events/2026-krakow/propose.md new file mode 100644 index 0000000000..ed49438e24 --- /dev/null +++ b/content/events/2026-krakow/propose.md @@ -0,0 +1,78 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Kraków 2026" ++++ + + + +
+ {{< cfp_dates >}} +
+ +
+ +
+ +There are three ways to propose a topic at devopsdays: + +1. A 30-minute talk presented during the conference, usually in the mornings. +2. A Lightning Talk presented during the Lightning Talks session (scheduling varies). These are up to 5 minutes slots. +3. Experience Exchange: If you'd like to lead a group discussion during the attendee-suggested Experience Exchange (aka Open Space) 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 sponsor the event and demo it at your table. + +
+ +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: + +- _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. +- _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. +- _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. +- _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. +- _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. +- _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. + +
+ +**How to submit a proposal:** Send an email to [{{< email_organizers >}}] with the following information + +1. Type (presentation, lightning talk) +2. Proposal Title (can be changed later) +3. Description (several sentences explaining what attendees will learn) + +SEND A PROPOSAL +
diff --git a/content/events/2026-krakow/registration.md b/content/events/2026-krakow/registration.md new file mode 100644 index 0000000000..94a8a7461e --- /dev/null +++ b/content/events/2026-krakow/registration.md @@ -0,0 +1,10 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Kraków 2026" ++++ + +
+ +Registration will open soon! +
diff --git a/content/events/2026-krakow/sponsor.md b/content/events/2026-krakow/sponsor.md new file mode 100644 index 0000000000..e8d1c150b2 --- /dev/null +++ b/content/events/2026-krakow/sponsor.md @@ -0,0 +1,60 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Kraków 2026" ++++ + + +
+ +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. + +
+ +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 Experience Exchange session. + +**All attendees are welcome to propose any subject** they want during the Experience Exchange sessions, 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. + +CONTACT US +
+ +
diff --git a/content/events/2026-krakow/welcome.md b/content/events/2026-krakow/welcome.md new file mode 100644 index 0000000000..3e0c6f2794 --- /dev/null +++ b/content/events/2026-krakow/welcome.md @@ -0,0 +1,93 @@ ++++ +Title = "devopsdays Kraków 2026" +Type = "welcome" +aliases = ["/events/2026-krakow/"] +Description = "devopsdays Kraków 2026" ++++ + + + +
+ {{< event_logo >}} +
+ +
+
+ +## DevOpsDays Kraków 2026 + +Join us for the next edition of DevOpsDays Kraków, a renowned event, in Kraków on June 6th at ECHO Miasta Kraków. Experience insightful lectures on the latest developments in the DevOps field and network with like-minded individuals. + +## What is DevOpsDays Kraków? + +DevOpsDays Kraków is a part of the international DevOpsDays series, designed for developers, IT operations, management, CEO's, security, and sys admins. The conference covers topics of all DevOps pillars: organizational culture and cultural shift, lean processes, automation, monitoring, shared knowledge and responsibility, and security. If you're into DevOps practices and culture, this conference is for you! + +## Why is it worth to join us? + +Our participants come from various backgrounds, including software development, system administration, QA, product and engineering management, business analytics, and security. This diverse group of practitioners will share their knowledge and experiences on delivering technology projects with the latest trends. Come and join us to learn and share the latest IT solutions and cultural experiences in the tech community. +
+ +
+ PROPOSE A TALK + SPONSOR + CONTACT +
+ +
diff --git a/data/events/2026/krakow/main.yml b/data/events/2026/krakow/main.yml new file mode 100644 index 0000000000..168720a984 --- /dev/null +++ b/data/events/2026/krakow/main.yml @@ -0,0 +1,128 @@ +name: "2026-krakow" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2026" # The year of the event. Make sure it is in quotes. +city: "Kraków" # The displayed city name of the event. Capitalize it. +event_twitter: "dodkrk" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +masthead_background: "krakow-banner-masthead.png" +description: "Devopsdays is coming to Kraków!" # Edit this to suit your preferences +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" + +# All dates are in unquoted 2026-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2019-01-04T00:00:00+02:00 +# variable: 2019-01-05T23:59:59+02:00 +# Note: we allow 2026-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) + +startdate: 2026-06-06T09:00:00+02:00 +enddate: 2026-06-06T16:59:59+02:00 + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: 2026-03-14T00:00:00+02:00 +cfp_date_end: 2026-04-19T23:59:59+02:00 +cfp_date_announce: 2026-05-04T00:00:00+02:00 # inform proposers of status + +# cfp_link: "" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. + +registration_date_start: 2026-03-15T00:00:00+02:00 +registration_date_end: 2026-06-06T17:00:00+02:00 + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location +location: "Kraków" # Defaults to city, but you can make it the venue name. +location_address: "ECHO Miasta, ul. Kapelanka 56" #Optional - use the street address of your venue. This will show up on the welcome page if set. Also used by the event_map shortcode! + +# Optional - Social badges +# These can be used in the body of any page via matching shortcodes. See sample: https://devopsdays.org/events/2025-denver/welcome/ +event_social_linkedin: "https://www.linkedin.com/company/devopsdays-krak%C3%B3w" # Change this to the url to your Linkedin group, company, or page. +event_social_slack: "" # Change this to your slack invite link. +event_social_listserv: "" # Change this to your mailing list subscription form url. +event_social_twitter: "dodkrk" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +event_social_mastodon: "" # Change this to url to your mastodon page +event_social_bsky: "" # Change this to url to your bluesky page +event_social_youtube: "" # Change this to the youtube channel handle for your event such as devopsdaysrox + + +# Social Share Buttons +# Optional: Specify which social share buttons to display on event pages. +# If not specified, defaults to all: ["email", "twitter", "facebook", "linkedin"] +# Valid values: "email", "twitter", "facebook", "linkedin" +# Example: social_shares: ["email", "linkedin"] # Only show email and LinkedIn share buttons +social_shares: # ["email", "twitter", "facebook", "linkedin"] + +nav_elements: # List of pages you want to show up in the navigation of your page. + - name: propose + # - name: location + # - name: registration + # - name: program + # - name: speakers + - name: sponsor + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + + +# 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: "Kuba Barć" + image: "barc_jakub.jpg" + - name: "Piotr Godowski" + image: "godowski_piotr.jpg" + employer: "IBM" + linkedin: "https://www.linkedin.com/in/piotr-godowski-4274091/" + bio: "Piotr is a seasoned software architect working at IBM, currently focused on Hybrid Clouds management and software licensing in the containerized world. Passionate of IT technologies, including AI, cyber security, BI, IoT and distributed systems. Member of ISO/IEC Polish National Body, owner of several software patents." + - name: "Janusz Kamieński" + linkedin: "https://www.linkedin.com/in/jakamienski/" + employer: "Splunk - a Cisco company" + image: "kamienski_janusz.jpg" + bio: "Developer, journalist, tabletop RPG Game Master and milkoholic. Active participant of dev communities, co-organizer of meetups and DevOps conferences in Poland. Applies DevOps pattern on tech and business side in all projects he touches. For a dozen of years worked in web technologies. Full-stack developer since 2008. Gains experience and new levels in everyday work at Splunk. Loves to train Acro Yoga and ride a bike in his spare time." + - name: "Przemysław Koltermann" + image: "koltermann_przemyslaw.jpg" + bio: "Docker Certified Associate and Docker Community Leader in Warsaw. Senior Software Engineer at GOG.com. Team DevOps, active everywhere where developers and IT meet, like development environment, deploy pipelines or Kubernetes. Master of Science in Computer Networking. Active Docker and Kubernetes advocate, performing lectures and trainings." + - name: "Marcin Lewandowski" + employer: "IBM" + image: "lewandowski_marcin.jpg" + bio: "Marcin is a Senior Software Engineer at IBM Lab in Kraków. He usually works across the stack, including designing and implementing DevOps processes for microservices he and his team owns. Interested in everything that helps do more with less and a huge fan of automating everything. If you talk Kubernetes, Ansible or Gradle Kotlin DSL, we'll find a common topic, or two." + - name: "Paweł Piwosz" + employer: "Tameshi" + image: "piwosz_pawel.jpg" + bio: "DevOps Institute Ambassador. CD.Foundation Ambassador. AWS Community Builder. Engineer, leader, mentor, speaker. My focus is on CALMS. I am building better understanding of DevOps as driver for the organization. I am devoted to Serverless and CI/CD. I authored the framework for design the CI/CD - www.cicd.run. Host of Last Week In IT and DevOps In Agile Way podcasts." + - name: "Pedro Ivo Raimundo" + image: "raimundo_pedro_ivo.jpg" + bio: "Olá, tudo bem? My name is Pedro and I'm a Cloud Engineering Manager at Pegasystems. I've worked for companies like IBM, Luxoft, Eaton, and now Pega. These days, my focus is on Cloud, SaaS, DevOps and mostly, leadership. When I'm not catching up with my Steam games backlog, I love participating in conferences, hackathons, learning new things and meeting new people. See you around!" + - name: "Tojciech Tomasiewicz" + employer: "Pegasystems" + image: "tomasiewicz_wojciech.jpg" + bio: "Cloud engineer at Pegasystems, passionate about leadership, soft skills, and the human side of technology. Having worked on three continents, I'm obsessed with culture and collaboration. Outside work, I run marathons, read books, listen to podcasts, and enjoy random trivia." + - name: "Agnieszka Welian" + employer: "Pegasystems" + image: "welian_agnieszka.jpg" + linkedin: "https://www.linkedin.com/in/agnieszka-welian/" + bio: "Agnieszka is a dedicated engineer specializing in cloud solutions, with expertise in cutting-edge technologies such as Kubernetes and Terraform. She also brings valuable insights from her experience in testing activities. Agnieszka is passionate about enhancing people’s wellbeing and promoting a healthy work-life balance. Outside of her professional endeavors, she is a sports freak, board game lover and owner of two adorable cats." + + + +organizer_email: "krakow@devopsdays.org" # Put your organizer email address here + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +sponsors: + +sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link + +# In this section, list the level of sponsorships and the label to use. +# You may optionally include a "max" attribute to limit the number of sponsors per level. For +# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all +# sponsorship for a specific level, it is best to remove the level. +sponsor_levels: + - id: gold + label: Gold +# max: 10 + - id: silver + label: Silver + max: 0 # This is the same as omitting the max limit. + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/static/_redirects b/static/_redirects index 65a2ca14c2..e5071cd057 100644 --- a/static/_redirects +++ b/static/_redirects @@ -60,7 +60,7 @@ /kansas-city/* /events/2026-kansas-city/:splat 302 /kazan/* /events/2018-kazan/:splat 302 /kiel/* /events/2018-kiel/:splat 302 -/krakow/* /events/2024-krakow/:splat 302 +/krakow/* /events/2026-krakow/:splat 302 /kiev/* /events/2025-kyiv/:splat 302 /kyiv/* /events/2025-kyiv/:splat 302 /ljubljana/* /events/2025-ljubljana/:splat 302 diff --git a/static/events/2026-krakow/krakow-banner-masthead.png b/static/events/2026-krakow/krakow-banner-masthead.png new file mode 100644 index 0000000000..38b0977bf9 Binary files /dev/null and b/static/events/2026-krakow/krakow-banner-masthead.png differ diff --git a/utilities/README.md b/utilities/README.md index 50d26371c7..8f5691f500 100644 --- a/utilities/README.md +++ b/utilities/README.md @@ -114,7 +114,7 @@ All logos will be resized at release time, to 200px wide. Versions for high-dens ## Local Organizers -See the example local organizer team members listed in the generated data file found in `data/events/201?-yourcity.yml`. To generate the `team_members: ` section you can use [add_organizers.sh](add_organizers.sh). +See the example local organizer team members listed in the generated data file found in `data/events/YYYY-yourcity.yml`. To generate the `team_members: ` section you can use [add_organizers.sh](add_organizers.sh). The organizer photo must be in JPG format, and should be a minimum 300px x 300px, but optimally 600px x 600px. These images should be placed in the `assets/events/yyyy-city/organizers` directory (which the `add_organizers.sh` script will do).