@@ -98,5 +97,4 @@ Description = "devopsdays Goiânia 2019"
-{{< event_twitter >}}
-
+{{< event_twitter >}}
\ No newline at end of file
diff --git a/content/events/2019-indianapolis/location.md b/content/events/2019-indianapolis/location.md
index 22d757f48be..99622c4072b 100644
--- a/content/events/2019-indianapolis/location.md
+++ b/content/events/2019-indianapolis/location.md
@@ -10,3 +10,18 @@ Description = "DevOpsDays Indianapolis at the Marriott Downtown Indianapolis"
350 W Maryland St, Indianapolis, IN 46225
{{< event_map >}}
+
+
+
+
+
+ +### After party will be held at Indiana City Brewing Co. on Thursday at 18:00 + +
+
+Join us at Indiana City Brewing Company
+after the conference on July 25th at 6pm. We will have appetizers, beer
+and the famous Ignite Karaoke!
+
+The address is 24 Shelby Street, Indianapolis, IN 46202.
diff --git a/content/events/2019-istanbul/speakers/leonardo-di-donato.md b/content/events/2019-istanbul/speakers/leonardo-di-donato.md
index 4de25644179..3c208721a59 100644
--- a/content/events/2019-istanbul/speakers/leonardo-di-donato.md
+++ b/content/events/2019-istanbul/speakers/leonardo-di-donato.md
@@ -7,7 +7,10 @@ linktitle = "leonardo-di-donato"
+++
-Leonardo is an Open Source Software Engineer at InfluxData where he maintains the infrastructure and API layers for InfluxCloud.
-His interests range from theoretical aspects of computer science to machine learning to distributed systems.
-He is the creator of influxdata/go-syslog, a blazingly fast Golang parser for syslog message and transport.
-He is also involved in the Linux Foundation's eBPF project (IO Visor) as a maintainer of kubectl-trace project.
\ No newline at end of file
+Open Source Software Engineer @Sysdig
+
+Leonardo is an Open Source Software Engineer at Sysdig in the Office of the CTO.
+He is in charge of the Open Source methodologies and projects of Sysdig.
+At the same time he mainly takes care of Falco, a Container Native Runtime security project sandboxed by the CNCF.
+He is also involved in the Linux Foundation's eBPF project (IO Visor) as a maintainer of kubectl-trace project.
+He's also the creator of go-syslog, a blazingly fast Golang parser for syslog messages and transports, and of kubectl-dig, a tool to have deep visibility into Kubernetes directly from the kubectl.
\ No newline at end of file
diff --git a/content/events/2019-montevideo/welcome.md b/content/events/2019-montevideo/welcome.md
index 6483924ff1d..6f489b762be 100644
--- a/content/events/2019-montevideo/welcome.md
+++ b/content/events/2019-montevideo/welcome.md
@@ -5,19 +5,38 @@ aliases = ["/events/2019-montevideo/"]
Description = "DevOpsDays Montevideo 2019"
+++
-***DevOpsDays Montevideo, Uruguay: Southernmost DevOpsDays on earth!***
+
-
-
-{{< event_twitter >}}
-
-----------
-
-
-Nuestro logo surgió de un concurso abierto; [ver detalles aquí](/events/2019-montevideo/logo/). +
-+
+
+
+ +### After party will be held at Indiana City Brewing Co. on Thursday at 18:00 + +
+
+Join us at Indiana City Brewing Company
+after the conference on July 25th at 6pm. We will have appetizers, beer
+and the famous Ignite Karaoke!
+
+The address is 24 Shelby Street, Indianapolis, IN 46202.
diff --git a/content/events/2019-istanbul/speakers/leonardo-di-donato.md b/content/events/2019-istanbul/speakers/leonardo-di-donato.md
index 4de25644179..3c208721a59 100644
--- a/content/events/2019-istanbul/speakers/leonardo-di-donato.md
+++ b/content/events/2019-istanbul/speakers/leonardo-di-donato.md
@@ -7,7 +7,10 @@ linktitle = "leonardo-di-donato"
+++
-Leonardo is an Open Source Software Engineer at InfluxData where he maintains the infrastructure and API layers for InfluxCloud.
-His interests range from theoretical aspects of computer science to machine learning to distributed systems.
-He is the creator of influxdata/go-syslog, a blazingly fast Golang parser for syslog message and transport.
-He is also involved in the Linux Foundation's eBPF project (IO Visor) as a maintainer of kubectl-trace project.
\ No newline at end of file
+Open Source Software Engineer @Sysdig
+
+Leonardo is an Open Source Software Engineer at Sysdig in the Office of the CTO.
+He is in charge of the Open Source methodologies and projects of Sysdig.
+At the same time he mainly takes care of Falco, a Container Native Runtime security project sandboxed by the CNCF.
+He is also involved in the Linux Foundation's eBPF project (IO Visor) as a maintainer of kubectl-trace project.
+He's also the creator of go-syslog, a blazingly fast Golang parser for syslog messages and transports, and of kubectl-dig, a tool to have deep visibility into Kubernetes directly from the kubectl.
\ No newline at end of file
diff --git a/content/events/2019-montevideo/welcome.md b/content/events/2019-montevideo/welcome.md
index 6483924ff1d..6f489b762be 100644
--- a/content/events/2019-montevideo/welcome.md
+++ b/content/events/2019-montevideo/welcome.md
@@ -5,19 +5,38 @@ aliases = ["/events/2019-montevideo/"]
Description = "DevOpsDays Montevideo 2019"
+++
-***DevOpsDays Montevideo, Uruguay: Southernmost DevOpsDays on earth!***
+DevOpsDays Montevideo, Uruguay: El evento DevOpsDays más al sur del planeta!
Our event pages are in Spanish, but don't worry [Google translator is your friend!](https://translate.google.com.uy/translate?sl=es&tl=en&u=https%3A%2F%2Fwww.devopsdays.org%2Fevents%2F2019-montevideo%2Fwelcome%2F) ----------- - -Llega a Uruguay la primera edición de DevOpsDays; una oportunidad única de compartir experiencias en dos días de conferencias, charlas y talleres. - -DevOpsDays es una serie de conferencias técnicas que se desarrollan a lo largo del mundo, cubriendo temas de desarrollo de software, Infraestructura de TI, Operaciones de TI, y la intersección entre ellas. El primer DevopsDay se realizó en Ghent, Bélgica, en 2009. A partir de ahí, los eventos se han multiplicado. - -Cada evento es llevado a cabo por [voluntarios locales](/events/2019-montevideo/contact). La mayoría de los eventos presentan una combinación de charlas seleccionadas y espacios abiertos. - ----------- +
+
+ 
+
+
+
+
+Sobre el evento
+DevOpsDays es una serie de conferencias técnicas que se desarrollan a lo largo del mundo, cubriendo temas de Desarrollo de Software, Infraestructura y Operaciones de TI, y la intersección entre ellos. El primer DevopsDay se realizó en Ghent, Bélgica, en 2009. A partir de ahí, los eventos se han multiplicado y expandido globalmente.
+Ahora llega a Uruguay la primera edición de DevOpsDays! Una oportunidad única de compartir experiencias en dos días de charlas, presentaciones, paneles expertos y networking con practitioners de Uruguay y el mundo.
+Cada evento es llevado a cabo por voluntarios de la comunidad local, en beneficio de la propia comunidad. No es una conferencia comercial, sino que apuntamos a fortalecer y extender la comunidad DevOps local, en un evento que cree una experiencia única para asistentes y sponsors.
+El evento se desarrollara en un único track de charlas de 30 minutos con expositores locales e internacionales. También se incluye una sesión de charlas Ignite (5 minutos por presentación, slides automáticas) para los speakers más osados.
+Nuestro logo surgió de un concurso abierto; ver detalles aquí.
+¿Quiénes deberían asistir?
+-
+
- + Practicantes de DevOps que quieran compartir sobre los desafíos, historias de guerra, problemas y soluciones que surjan de su experiencia. + +
- + Desarrolladores, Operadores de IT, Testers, Técnicos de Seguridad o cualquier otro profesional de TI que quiera conocer más sobre las prácticas DevOps y como incluirlas en su día a día. + +
- + Tomadores de decisión que tengan interés en conocer más sobre la cultura y en cómo adoptar DevOps en sus empresas para acelerar la entrega de valor a sus clientes. + +
- + Estudiantes que quieran integrarse a una comunidad dinámica, en constante crecimiento y en la vanguardia tecnológica. + +
@@ -91,15 +110,11 @@ Cada evento es llevado a cabo por [voluntarios locales](/events/2019-montevideo/
- {{< event_logo >}}
-
-
--Nuestro logo surgió de un concurso abierto; [ver detalles aquí](/events/2019-montevideo/logo/). +
+
\ No newline at end of file
diff --git a/content/events/2019-portugal/speakers/manuel-pais.md b/content/events/2019-portugal/speakers/manuel-pais.md
index 6ae8cf31230..28ef6275df5 100644
--- a/content/events/2019-portugal/speakers/manuel-pais.md
+++ b/content/events/2019-portugal/speakers/manuel-pais.md
@@ -9,4 +9,40 @@ linktitle = "manuel-pais"
#### Speaker
-Manuel Pais is an independent DevOps and Continuous Delivery Consultant, focused on team design, practices and flow. He helps organizations define and adopt DevOps and Continuous Delivery (both from technical and human perspectives) via strategic assessments, practical workshops and coaching. Also InfoQ lead editor. Co-curator of DevOpsTopologies.com. Co-author of the books “Team Guide to Software Releasability” (Conflux Digital, 2018) and “Team Topologies” (IT Revolution Press, 2019). Answers by @manupaisable at Twitter and Medium.
\ No newline at end of file
+Manuel Pais is an independent DevOps and Continuous Delivery Consultant, focused on team design, practices and flow. He helps organizations define and adopt DevOps and Continuous Delivery (both from technical and human perspectives) via strategic assessments, practical workshops and coaching. Also InfoQ lead editor. Co-curator of DevOpsTopologies.com. Co-author of the books “Team Guide to Software Releasability” (Conflux Digital, 2018) and “Team Topologies” (IT Revolution Press, 2019). Answers by @manupaisable at Twitter and Medium.
+
+***
+
+### Quick Q&A With Manuel Pais
+
+> *We had a chance to catch up with Manuel and ask him a few questions about teams and his editorial work.*
+
+**[Miguel Alho](/events/2019-portugal/contact/): Hi Manuel! You have created a pretty large body of work related to the team aspect of our work, whether through the [devopstopologies.com](http://devopstopologies.com) website or through your upcoming book Team Topologies… How did you come to focus on this aspect?**
+
+**Maunel Pais**: Hi! That’s a great question. Well, in the last 5 years I took part in several consulting engagements where clients wanted to adopt DevOps and Continuous Delivery. Often they expected new technology and practices would solve their problems but their effectiveness was limited by the way teams interacted (or not) or unclear team responsibilities. For example, if you adopt infrastructure-as-code but only the infrastructure team can make modifications and provision new resources, they will remain a bottleneck that decreases the flow of work.
+
+On the other hand, back in 2015 I found out about Matthew Skelton’s [DevOps Topologies](http://devopstopologies.com) which resonated to me and many other people as a great visualization of common patterns and anti-patterns in team structures and interactions. As I worked with Matthew at different clients worldwide, we further identified behavior patterns and associated context that led to a faster flow without compromising quality (in fact, usually improving it).
+
+In short, I know from experience that we need to start with team interactions and flow of work to make substantial improvements in the way organizations build and run modern software.
+
+**MA: Do you see in your work a lot of companies misapplying these patterns? Why does that tend to happen?**
+
+**MP**: I wouldn’t say misapplying but rather many companies are still not thinking about these issues. It’s hard when we’re talking about changing behaviors and getting people out of their comfort zone, including at the management level. There’s often no space for organizational learning, i.e. finding out iteratively what are the right teams and responsibilities to go faster. It’s hard when you’re in a constant whirlwind of market and technology changes. But that’s the very reason why it’s necessary to think harder about team design and clarify responsibilities and expectations.
+
+The advice I would give is to start with the [DevOps Topologies](http://devopstopologies.com) to kickstart conversations in and around teams on how they see themselves in the spectrum of patterns presented. Just raising awareness can be super valuable. Management support is critical to make more sweeping changes (again, this should be learning-driven, not big bang re-org) but even without it teams can start by clarifying what are their responsibilities and prefered ways of working and communicating (kind of a “Team API”) with other teams.
+
+On the other hand, we start to see more and more companies that have bought into the model of autonomous product teams but are not seeing the value yet because these teams are expected to learn and become high performing teams without any supporting structures in place. That is extremely complicated in any organization beyond 30-40 people.
+
+That’s why I’m talking about why “Product Teams Need a Family Too” at DevOpsDays Portugal on June 3, meaning they need a support system that really allows the kind of speed and reliability organizations are striving for today. Tip: it doesn’t come true just by saying we have autonomous teams now. This talk is based on the [Team Topologies](http://teamtopologies.com) book that me and Matthew Skelton have written for Gene Kim’s [IT Revolution Press](https://itrevolution.com/book/team-topologies/), but only starts shipping in September, so this will be an early look into these ideas :)
+
+**MA: Your editing for InfoQ must give you great visibility on the trends. Where do you see moving towards?**
+
+**MP**: I’ve been the DevOps lead editor at InfoQ for several years now, and it’s amazing how much has changed, from infrastructure-as-code to Docker and Kubernetes, or the rise of microservices architectures.
+
+We actually put out a [“DevOps and Cloud Trends Report”](https://www.infoq.com/articles/devops-cloud-trends-2019/) on a regular basis at [InfoQ](https://www.infoq.com) where we discuss trends and place technologies and practices on the adoption hype cycle. We see adoption of DevOps, containers and infrastructure-as-code as having established their value, so organizations lagging behind need to look into how to make use of them right now (again, with a learning mentality, not big bang). Then you have technologies like Kubernetes and approaches like self-service platforms, DevEx (caring about the developer experience), ChatOps becoming more widespread. On the “innovator” side are those things we tend to associate only with the Netflixes and Googles, like chaos engineering or AIOps.
+
+Of course, as the saying goes “your mileage may vary”. There’s such a wide spectrum of maturity levels across organizations, it’s hard to make predictions. I believe forward-thinking organizations are moving towards resiliency of both live systems and their development toolchains, via easy-to-use internal platforms but which make strong use of external cloud and other service providers. Kubernetes is a hot topic of course, but the learning curve and ops skills required to run in-house are still high, making the case for adoption difficult for companies with low engineering and/or organizational maturity.
+
+**MA: Awesome work there, and best of luck with the book!"**
+
+***
\ No newline at end of file
diff --git a/content/events/2019-portugal/welcome.md b/content/events/2019-portugal/welcome.md
index 51c97e476c7..148e85503ca 100644
--- a/content/events/2019-portugal/welcome.md
+++ b/content/events/2019-portugal/welcome.md
@@ -86,14 +86,107 @@ Description = "devopsdays portugal 2019"
+
+
+
+ {{< event_twitter >}}
+
+
-
-
+ +There are three ways to propose a topic at devopsdays: +
+ +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_proposals >}}] with the following information +
+DevOpsDays Portugal 2019 is powered by the DevOps Lisbon & DevOps Porto, the two main meetup groups dedicated to DevOps in Portugal.
- -This will be the first DevOpsDays organized in Portugal; we have chosen Lisbon as the first city to host the event, and hope to alternate with Porto (and other cities) each year.
- -The conference this year will focus on real world experience reports from diverse organizations in Portugal and abroad. Covered topics will include Culture, Automation, Lean, Measurement, and Sharing (CALMS), and others.
- - {{< event_logo >}} - +
+
diff --git a/content/events/2019-sydney/conduct.md b/content/events/2019-sydney/conduct.md
new file mode 100644
index 00000000000..a602ad90fc9
--- /dev/null
+++ b/content/events/2019-sydney/conduct.md
@@ -0,0 +1,35 @@
++++
+Title = "Conduct"
+Type = "event"
+Description = "Code of conduct for devopsdays sydney 2019"
++++
+
+## 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.
diff --git a/content/events/2019-sydney/contact.md b/content/events/2019-sydney/contact.md
new file mode 100644
index 00000000000..33f85bd8f97
--- /dev/null
+++ b/content/events/2019-sydney/contact.md
@@ -0,0 +1,15 @@
++++
+Title = "Contact"
+Type = "event"
+Description = "Contact information for devopsdays sydney 2019"
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/content/events/2019-sydney/location.md b/content/events/2019-sydney/location.md
new file mode 100644
index 00000000000..321e6d11f6a
--- /dev/null
+++ b/content/events/2019-sydney/location.md
@@ -0,0 +1,10 @@
++++
+Title = "Location"
+Type = "event"
+Description = "Location for devopsdays sydney 2019"
++++
+
+Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details.
+
+
+
diff --git a/content/events/2019-sydney/propose.md b/content/events/2019-sydney/propose.md
new file mode 100644
index 00000000000..96ac38aa67a
--- /dev/null
+++ b/content/events/2019-sydney/propose.md
@@ -0,0 +1,35 @@
++++
+Title = "Propose"
+Type = "event"
+Description = "Propose a talk for devopsdays sydney 2019"
++++
+ {{< cfp_dates >}}
+
+
+
+
+
+
+
+
+
+
+ DevOpsDays Portugal 2019 is powered by the DevOps Lisbon & DevOps Porto, the two main meetup groups dedicated to DevOps in Portugal.
+ +This will be the first DevOpsDays organized in Portugal; we have chosen Lisbon as the first city to host the event, and hope to alternate with Porto (and other cities) each year.
+ +The conference this year will focus on real world experience reports from diverse organizations in Portugal and abroad. Covered topics will include Culture, Automation, Lean, Measurement, and Sharing (CALMS), and others.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 
+
+
+ + +There are three ways to propose a topic at devopsdays: +
-
+
- A 30-minute talk presented during the conference, usually in the mornings. +
- An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total). +
- Open Space: If you'd like to lead a group discussion during the attendee-suggested 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_proposals >}}] with the following information +
-
+
- Type (presentation, panel discussion, ignite) +
- Proposal Title (can be changed later) +
- Description (several sentences explaining what attendees will learn) +
+
+Embed registration iframe/link/etc.
+