[LIMA-2025] Add location and update date event#14984
[LIMA-2025] Add location and update date event#14984edanpiro wants to merge 1 commit intodevopsdays:mainfrom
Conversation
✅ Deploy Preview for devopsdays-web ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
edanpiro
force-pushed
the
feature/events-lima
branch
from
3d02c49 to
382fe58
Compare
| +++ | ||
|
|
||
| If you'd like to contact us by email: {{< email_organizers >}} | ||
| If you'd like to contact us by email: contacto@devopsdays.pe |
There was a problem hiding this comment.
Changing the contact email requires core approval, please email info @ to confirm this change
There was a problem hiding this comment.
No, Core will not allow this email change. In the documentation (paragraph six, emphasis mine):
We’ll set up the cityname@devopsdays.org mail alias for your team. This will let you have a standard email listed as a public-facing organizer point of contact. All organizers on your team need to be on this alias individually, and the global core team is also on this email alias. It’s fine to use other email lists, chat programs, and other tools for your internal coordination and outgoing announcements, but we require that your event’s published organizer_email: field be set to this for consistency and problem prevention.
| +++ | ||
|
|
||
| Valoramos mucho a los patrocinadores para este evento comunitario. Si estás interesado en patrocinar, por favor envíanos un correo electrónico a [{{< email_organizers >}}]. | ||
| Valoramos mucho a los patrocinadores para este evento comunitario. Si estás interesado en patrocinar, por favor envíanos un correo electrónico a sponsors@devopsdays.pe. |
There was a problem hiding this comment.
Changing the contact email requires core approval, please email info @ to confirm this change
There was a problem hiding this comment.
Please leave the {{< email_organizers >}} tags as they are.
In the documentation (paragraph six, emphasis mine):
We’ll set up the cityname@devopsdays.org mail alias for your team. This will let you have a standard email listed as a public-facing organizer point of contact. All organizers on your team need to be on this alias individually, and the global core team is also on this email alias. It’s fine to use other email lists, chat programs, and other tools for your internal coordination and outgoing announcements, but we require that your event’s published organizer_email: field be set to this for consistency and problem prevention.
| +++ | ||
|
|
||
| If you'd like to contact us by email: {{< email_organizers >}} | ||
| If you'd like to contact us by email: contacto@devopsdays.pe |
There was a problem hiding this comment.
No, Core will not allow this email change. In the documentation (paragraph six, emphasis mine):
We’ll set up the cityname@devopsdays.org mail alias for your team. This will let you have a standard email listed as a public-facing organizer point of contact. All organizers on your team need to be on this alias individually, and the global core team is also on this email alias. It’s fine to use other email lists, chat programs, and other tools for your internal coordination and outgoing announcements, but we require that your event’s published organizer_email: field be set to this for consistency and problem prevention.
3 participants
This pull request includes several updates to the event details for DevOpsDays Lima 2025. The changes primarily involve updating contact information, location details, and event dates.
Updates to event details:
content/events/2025-lima/contact.md: Updated the contact email address tocontacto@devopsdays.pe.content/events/2025-lima/location.md: Changed the title and description to Spanish, added detailed location information, and included images of the venue.content/events/2025-lima/sponsor.md: Updated the sponsor contact email address tosponsors@devopsdays.pe.data/events/2025/lima/main.yml: Adjusted the event start and end dates to August 21, 2025, and added the venue address. [1] [2]