-
Notifications
You must be signed in to change notification settings - Fork 690
[Rec-2025] Add Recife 2025 #15069
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
yagonobre
wants to merge
3
commits into
devopsdays:main
Choose a base branch
from
yagonobre:rec-2025
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[Rec-2025] Add Recife 2025 #15069
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
+++ | ||
Title = "Código de Conduta" | ||
Type = "event" | ||
Description = "Código de Conduta - DevOpsDays Recife 2025" | ||
+++ | ||
|
||
# Código de conduta | ||
<br> | ||
O DevOpsDays é um evento sem fins lucrativos cujo principal objetivo é promover a troca de experiências entre as pessoas sobre a cultura DevOps no Brasil. | ||
|
||
Este Código de Conduta será aplicado para todos enquanto participantes desse evento para proteger o público de danos e perigos morais. | ||
|
||
Nos dedicamos a promover um evento respeitoso e livre de assédio para todos. Não toleramos quaisquer formas de assédios ou intimidações de qualquer participante. | ||
|
||
Imagens, atividades ou materiais de conteúdo sexual, homofóbico, pejorativo e/ou discriminatório de qualquer natureza não são aceitos. | ||
|
||
Por assédio entende-se sem limitação: | ||
|
||
* Comentários ofensivos, verbais ou eletrônicos, relacionados a características pessoais, origem racial, orientação sexual, identidade de gênero, bem como comentários ou imagens sexuais, racistas, homofóbicas ou discriminatórias de qualquer natureza em espaços públicos ou digitais; | ||
* Intimidação deliberada; | ||
* Bullying; | ||
* Perseguição; | ||
* Encalço; | ||
* Fotografias ou gravações que gerem embaraço; | ||
* Interrupções reiteradas de palestras, bate-papos, reuniões eletrônicas, reuniões físicas ou outros eventos; | ||
* Contato físico inadequado ou atenção sexual indesejada. | ||
|
||
Espera-se que os participantes cumpram imediatamente solicitações para descontinuar qualquer assédio ou comportamento de bullying. Sejam gentis com os outros. Não insultem ou ofendam outros participantes. Lembrem-se de que piadas de assédio, sexismo, racismo ou exclusão não são aceitas pela sociedade, muito menos para nosso evento. | ||
|
||
Qualquer participante que violar tais regras pode ser convidado a se retirar, a critério exclusivo dos organizadores do evento. | ||
|
||
Se um participante se engajar em comportamento de assédio, os organizadores do evento podem tomar medidas que considerem adequadas, desde alertas ao infrator até a vedação de sua participação em demais eventos promovidos pelos membros da organização individual ou coletivamente. | ||
|
||
Se você for assediado, perceber que alguém está sendo assediado, ou tem outras preocupações, por favor aja para interceptar ou peça ajuda aos organizadores. Estamos certos de que essa política ajudará a fazer do DevOpsDays um espaço mais acolhedor, inclusivo, e integrador para todos. | ||
|
||
Prevenção à disseminação da Covid-19 é necessário para que tenhamos um bom evento, segue recomendações e o que iremos disponibilizar no evento: | ||
|
||
* Uso de mascara é recomendado durante o evento; | ||
* A entrada do evento só será liberada junto ao comprovante de vacinação; | ||
* Mascaras recomendadas pro evento são: Cirurgicas descartável ou PFF2 ou N95; | ||
* Teremos álcool em gel disponível em vários locais do evento; | ||
|
||
Este Código de Conduta foi adaptado a partir do código de conduta utilizado pelo DevOpsDays Porto Alegre 2016, que foi adaptado pela comunidade GTC - Grupo de Testes Carioca, que foi adaptado pelo evento LinguÁgil, que foi adaptado pelo evento Agile Trends, que foi adaptado a partir dos códigos de conduta utilizados pelo Ideias em Produção, adaptados a partir do Python Brasil 9, este por sua vez adaptados dos códigos de conduta utilizados pela Plone Foundation e pela PyCon US, e estão licenciados sob a Creative Commons Attribution-Share Alike 3.0 Unported. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
+++ | ||
Title = "Contato" | ||
Type = "event" | ||
Description = "Contato - DevOpsDays Recife 2025" | ||
+++ | ||
<br> | ||
<h4>Se você quiser entrar em contato conosco, basta enviar um e-mail para: {{< email_organizers >}}</h4> | ||
</br> | ||
|
||
<h4><strong>Organização:</strong></h4> | ||
|
||
{{< list_organizers >}} | ||
|
||
|
||
**{{< list_core >}}** |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
+++ | ||
Title = "Local" | ||
Type = "event" | ||
Description = "Local - Devopsdays Recife 2024" | ||
+++ | ||
|
||
<p></p> | ||
|
||
<h1>Local do evento</h1> | ||
<br> | ||
<h3><strong>Centro de Convençoes - Teatro Ribeira - Av. Prof. Andrade Bezerra, S/N, Olinda - PE</strong></h3> | ||
<a href="https://maps.app.goo.gl/eHqYG9qVDwnm12KcA">Map</a> | ||
|
||
|
||
{{< event_map >}} | ||
|
||
<p></p> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
+++ | ||
Title = "Program" | ||
Type = "program" | ||
Description = "Program for for devopsdays Recife 2024" | ||
+++ | ||
|
||
TBA |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
+++ | ||
Title = "Sponsor" | ||
Type = "event" | ||
Description = "Sponsor DevOpsDays Recife 2024" | ||
+++ | ||
|
||
We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. | ||
|
||
<hr> | ||
|
||
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. | ||
<p> | ||
The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. | ||
<p> | ||
<hr/> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,108 @@ | ||
+++ | ||
Title = "DevOpsDays Recife 2025" | ||
Type = "welcome" | ||
aliases = ["/events/2025-recife"] | ||
Description = "DevOpsDays Recife 2025" | ||
+++ | ||
|
||
|
||
<div style="padding: 10px;"> | ||
<div style="padding-bottom: 1em;"> | ||
<h2>DevOpsDays Recife 2025</h2> | ||
</div> | ||
<div style="padding-bottom: 1em;"> | ||
<div class = "row"> | ||
<div class = "col-md-2"> | ||
<strong>Datas</strong> | ||
</div> | ||
<div class = "col-md-8"> | ||
{{< event_start >}} | ||
</div> | ||
</div> | ||
<div class = "row"> | ||
<div class = "col-md-2"> | ||
<strong>Local</strong> | ||
</div> | ||
<div class = "col-md-8"> | ||
{{< event_link page="local" text="Centro de Convençoes - Teatro Ribeira" title="Local" >}} | ||
</div> | ||
</div> | ||
<div class = "row"> | ||
<div class = "col-md-2"> | ||
<strong>Contato</strong> | ||
</div> | ||
<div class = "col-md-6"> | ||
{{< event_link page="contact" text="Entre em contato com os organizadores" >}} | ||
</div> | ||
</div> | ||
<div class="row"> | ||
<div class="col-md-2"> | ||
<strong>CFP</strong> | ||
</div> | ||
<div class="col-md-6"> | ||
Em Breve! | ||
</div> | ||
</div> | ||
<div class="row"> | ||
<div class="col-md-2"> | ||
<strong>Ingresso</strong> | ||
</div> | ||
<div class="col-md-6"> | ||
Em Breve! | ||
</div> | ||
</div> | ||
</div> | ||
|
||
<div> | ||
<h4 style="padding-bottom: 1em;"> | ||
<strong>O DevOpsDays Recife retorna em 2025!</strong> | ||
</h4> | ||
<p> | ||
Em nossa quinta edição do DevOpsDays Recife, queremos que todos tenhamos mais uma excelente oportunidade de compartilhar conhecimento, contar histórias, socializar e fazer novos amigos! | ||
</p> | ||
<p> | ||
Queremos tornar a cultura DevOps cada vez mais presente, participe e venha contribuir para essa jornada! | ||
</p> | ||
<div> | ||
|
||
<div style="padding-top:1em; padding-bottom:1em;" class="d-flex flex-row"> | ||
<div> | ||
<h4> | ||
Informações: | ||
</h4> | ||
<div class="d-flex flex-row"> | ||
<div style="witdh: auto; padding-right: 1em;"> | ||
<a style="text-align:left;" class="btn btn-secondary btn-block" href="/events/2025-recife/contact"> <i class="fa fa-envelope-o fa-fw"></i> Entre em contato</a> | ||
</div> | ||
<div style="witdh: auto; padding-right: 1em; "> | ||
<a target="_blank" style="text-align:left;" class="disabled btn btn-secondary btn-block" href=""> <i class="fa fa-user-plus fa-fw"></i> Inscrições </a> | ||
</div> | ||
<div style="witdh: auto; padding-right: 1em;"> | ||
<a target="_blank" style="text-align:left;" class="disabled btn btn-secondary btn-block" href=""> <i class="fa fa-file-text-o fa-fw"></i> Call for Papers </a> | ||
</div> | ||
<div style="witdh: auto; padding-right: 1em;"> | ||
<a target="_blank" style="text-align:left;" class="btn btn-secondary btn-block" href="/events/2025-recife/local"> <i class="fa fa-map-marker fa-fw"></i> Local </a> | ||
</div> | ||
</div> | ||
</div> | ||
<div> | ||
<h4> | ||
Redes sociais: | ||
</h4> | ||
<div class="d-flex flex-row"> | ||
<div style="witdh: auto; padding-right: 1em;"> | ||
<a target="_blank" style="text-align:left;" class="btn btn-secondary btn-block" href="https://www.linkedin.com/company/devopsdaysrec/"><i class="fa fa-linkedin fa-fw"></i> LinkedIn</a> | ||
</div> | ||
<div style="witdh: auto; padding-right: 1em;"> | ||
<a target="_blank" style="text-align:left;" class="btn btn-secondary btn-block" href="https://twitter.com/devopsdaysrec/"><i class="fa fa-twitter fa-fw "></i> Twitter </a> | ||
</div> | ||
<div style="witdh: auto; padding-right: 1em;"> | ||
<a target="_blank" style="text-align:left;" class="btn btn-secondary btn-block" href="https://www.instagram.com/devopsdaysrec/"> <i class="fa fa-instagram fa-fw"></i> Instagram</a> | ||
</div> | ||
</div> | ||
</div> | ||
</div> | ||
<div style="text-align:center; width: auto;"> | ||
{{< event_logo >}} | ||
</div> | ||
</div> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,129 @@ | ||
name: "2025-recife" # The name of the event. Four digit year with the city name in lower-case, with no spaces. | ||
year: "2025" # The year of the event. Make sure it is in quotes. | ||
city: "Recife" # The displayed city name of the event. Capitalize it. | ||
event_twitter: "devopsdaysrec" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp | ||
description: "DevOpsDays Recife!" # Edit this to suit your preferences | ||
ga_tracking_id: "UA-36355678-5" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" | ||
event_logo: "logo.jpg" | ||
masthead_background: "background.jpg" | ||
|
||
# All dates are in unquoted YYYY-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 YYYY-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: 2025-12-13T00:10:00-03:00 | ||
enddate: 2025-12-13T18:00:00-03:00 | ||
|
||
# Leave CFP dates blank if you don't know yet, or set all three at once. | ||
cfp_date_start: "2025-04-15T00:00:00-03:00" #2019-09-17T00:09:00-03:00 # start accepting talk proposals. | ||
cfp_date_end: "2025-07-30T23:59:59-03:00" #2019-10-25T00:09:00-03:00 # close your call for proposals. | ||
cfp_date_announce: "2025-08-15T00:00:00-03:00" #2019-10-20T00:09:00-03:00 # inform proposers of status | ||
|
||
|
||
cfp_open: "false" | ||
cfp_link: "https://www.papercall.io/dodrec25" #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: "2025-04-15T00:09:00-03:00" #2022-10-01T00:09:00-03:00 # start accepting registration. Leave blank if registration is not open yet | ||
registration_date_end: "2025-12-10T00:09:00-03:00" #2022-10-31T00:09:00-03:00 # close registration. Leave blank if registration is not open yet. | ||
|
||
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 | ||
# | ||
coordinates: "" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html | ||
location: "Centro de Convençoes - Teatro Ribeira" # Defaults to city, but you can make it the venue name. | ||
location_address: "Av. Prof. Andrade Bezerra, S/N, Olinda - PE" #Optional - use the street address of your venue. This will show up on the welcome page if set. | ||
|
||
|
||
nav_elements: # List of pages you want to show up in the navigation of your page. | ||
# icon: "" deprecated - This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ | ||
- name: local | ||
url: /events/2025-recife/local | ||
- name: código de conduta | ||
url: /events/2025-recife/conduct | ||
- name: contato | ||
url: /events/2025-recife/contact | ||
- name: Programação | ||
url: /events/2025-recife/program | ||
|
||
# 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. | ||
toshywoshy marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
- name: "Henrique Cordeiro" | ||
employer: "Avantsoft" | ||
image: "henrique-cordeiro.png" | ||
bio: "" | ||
linkedin: "https://www.linkedin.com/in/henrique-cordeiro-pereira/" | ||
|
||
- name: "Lucas Assad" | ||
employer: "Ustore" | ||
image: "lucas-assad.jpg" | ||
bio: "" | ||
linkedin: "https://www.linkedin.com/in/lucas-assad/" | ||
|
||
- name: "Marília Angela" | ||
employer: "Bradesco" | ||
image: "marilia-angela.jpg" | ||
bio: "" | ||
linkedin: "https://www.linkedin.com/in/mariliaangela/" | ||
|
||
- name: "Shenia Andrade" | ||
employer: "Magazine Luiza" | ||
image: "shenia-andrade.jpg" | ||
bio: "" | ||
linkedin: "https://www.linkedin.com/in/shenia-tamires-andrade/" | ||
|
||
- name: "Yago Nobre" | ||
employer: "Nubank" | ||
image: "yago-nobre.jpg" | ||
twitter: "yagoyns" | ||
bio: "" | ||
linkedin: "https://www.linkedin.com/in/yagonobre" | ||
|
||
organizer_email: "[email protected]" # 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_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: platinum | ||
label: Platina | ||
max: 6 | ||
- id: gold | ||
label: Gold | ||
max: 5 | ||
- id: silver | ||
label: Silver | ||
max: 5 | ||
- id: community | ||
label: Comunidade | ||
|
||
sponsors: | ||
|
||
program: | ||
# - title: "Credenciamento" | ||
# type: custom | ||
# date: 2022-12-10T00:09:00-03:00 | ||
# start_time: "08:15" | ||
# end_time: "10:00" | ||
|
||
# - title: "marylia-gutierrez" | ||
# type: talk | ||
# date: 2022-12-10T00:09:00-03:00 | ||
# start_time: "09:00" | ||
# end_time: "09:30" | ||
|
||
# - title: "Open Spaces 💬 / Cofee Break ☕️" | ||
# type: open-space | ||
# date: 2022-12-10T00:09:00-03:00 | ||
# start_time: "15:00" | ||
# end_time: "15:30" | ||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link does not work yet, I know you have set the open date to 15 April, so this is more for myself a reminder and for you to see that the CFP opens correctly
You will need to change line 24 too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👋 Hi there! I just checked the Papercall now that it should be open, and it looks like I'm still getting a 404. Is this link correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed still 404 today also.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have confirmed that this link is still getting a 404. @yagonobre, we cannot merge this until the CFP is opened or you remove the CFP dates (commenting out is fine) if you intend to open it later.
--
(Tenga en cuenta que esto se tradujo con Google Translate; perdone cualquier error gramatical). He confirmado que este enlace todavía recibe un 404. @yagonobre, no podemos fusionar esto hasta que se abra el CFP o elimine las fechas del CFP (comentar está bien) si tiene la intención de abrirlo más tarde.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that I sent another email today to the mailing list.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gomex @camilla-m is there a better way to reach Recife that one of you knows of? I'd love to merge this PR, but the papercall is still inactive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay, I will update the pr on monday and postpone the cfp