-
Notifications
You must be signed in to change notification settings - Fork 699
[DEN-2025] Fix Denver 2025 Event #14947
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 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
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
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
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
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
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 |
|---|---|---|
| @@ -1,43 +1,48 @@ | ||
| name: "2025-denver" # 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: "Denver" # The displayed city name of the event. Capitalize it. | ||
| event_twitter: "DevOpsDaysRox" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp | ||
| description: "Devopsdays is coming to Denver!" # Edit this to suit your preferences | ||
| description: "Devopsdays is returning to Denver for " # Edit this to suit your preferences | ||
| ga_tracking_id: "G-9SR9GD94E0" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" | ||
|
|
||
| # All dates are in unquoted 2025-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 2025-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: # The start date of your event. Leave blank if you don't have a venue reserved yet. | ||
| enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet. | ||
| startdate: 2025-09-15T08:00:59-06:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. | ||
| enddate: 2025-09-16T23:59:59-06:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. | ||
|
|
||
| # Leave CFP dates blank if you don't know yet, or set all three at once. | ||
| cfp_date_start: # start accepting talk proposals. | ||
| cfp_date_end: # close your call for proposals. | ||
| cfp_date_announce: # inform proposers of status | ||
| cfp_date_start: 2025-02-22T08:00:59-06:00 # start accepting talk proposals. | ||
| cfp_date_end: 2025-05-25T23:59:59-06:00 # close your call for proposals. | ||
| cfp_date_announce: 2025-06-15T08:00:59-06: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: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. | ||
| registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. | ||
| registration_date_start: 2025-02-22T08:00:59-06:00 # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. | ||
| registration_date_end: 2025-09-15T23:59:59-06:00 # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. | ||
|
|
||
| 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. | ||
|
|
||
| event_social_linkedin: "https://www.linkedin.com/company/devopsdaysrox/" | ||
| event_social_slack: "https://join.slack.com/t/denverdevops/shared_invite/zt-1vh386cqp-Y_YUcLvFTeuOXA1~zIHUPQ" | ||
| event_social_listserv: "https://lists.devopsdays.org/subscription?f=nPvKqspePofE0XidlymcAeU1dXc7633G7Gu0OOZmi7rYef45qeLCpMqcaXD4kQpNJ1xP21UP58763qC0763Sx3763zWJbw" | ||
| event_social_twitter: "DevOpsDaysRox" | ||
| event_social_youtube: "devopsdaysrockies" | ||
|
|
||
| # Location | ||
| # | ||
| # coordinates: "" # No longer used | ||
|
|
||
| location: "Denver" # Defaults to city, but you can make it the venue name. | ||
| location: "Downtown Denver" # Defaults to city, but you can make it the venue name. | ||
| # | ||
| location_address: "" #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! | ||
|
|
||
| nav_elements: # List of pages you want to show up in the navigation of your page. | ||
| # - name: propose | ||
| - name: propose | ||
| # - name: location | ||
| # - name: registration | ||
| - name: registration | ||
| # - name: program | ||
| # - name: speakers | ||
| - name: sponsor | ||
|
|
@@ -50,13 +55,6 @@ nav_elements: # List of pages you want to show up in the navigation of your page | |
|
|
||
| # 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: "Tavis Aitken" | ||
| twitter: "tavisto" | ||
| employer: "Splunk" | ||
| mastodon: "https://hachyderm.io/@tavisto" | ||
| - name: "Carla Murray" | ||
| employer: "Splunk" | ||
| twitter: "carlajmurray" | ||
| - name: "Keri Melich" | ||
| employer: "DuckDuckGo" | ||
| twitter: "themightymuppet" | ||
|
|
@@ -66,21 +64,13 @@ team_members: # Name is the only required field for team members. | |
| twitter: "peteroneilljr" | ||
| - name: "Mike Nabhan" | ||
| employer: "Akamai" | ||
| - name: "David Morse" | ||
| employer: "Parry Labs" | ||
| twitter: "ds_morse" | ||
| - name: "Matt Knox" | ||
| twitter: "mknox42" | ||
| - name: "Tavis Aitken" | ||
| twitter: "tavisto" | ||
| employer: "Splunk" | ||
| - name: "Beau Christensen" | ||
| twitter: "beauchristensen" | ||
| mastodon: "https://hachyderm.io/@e30m3" | ||
| employer: "Rivian" | ||
| - name: "Nick Huanca" | ||
| twitter: "NickHuanca" | ||
| - name: "Leigh Capili" | ||
| employer: "Flox" | ||
| twitter: "capileigh" | ||
| mastodon: "https://hachyderm.io/@tavisto" | ||
| - name: "Carla Murray" | ||
| employer: "Splunk" | ||
| twitter: "carlajmurray" | ||
| organizer_email: "[email protected]" | ||
|
|
||
| # List all of your sponsors here along with what level of sponsorship they have. | ||
|
|
||
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.
Organizers changes, please also email info @ to reflect these changes
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.
@toshywoshy I have already sent an email a few weeks ago with the organizer changes to [email protected] and i never got a reply. I just bumped it again for a second time - can you confirm if it was received? Maybe our message is going to spam?
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.
Changes completed; sorry that I missed it!