diff --git a/assets/events/2026-melbourne/organizers/fabian_iannarella.jpg b/assets/events/2026-melbourne/organizers/fabian_iannarella.jpg new file mode 100644 index 0000000000..61394d5663 Binary files /dev/null and b/assets/events/2026-melbourne/organizers/fabian_iannarella.jpg differ diff --git a/assets/events/2026-melbourne/organizers/jordan_kueh.png b/assets/events/2026-melbourne/organizers/jordan_kueh.png new file mode 100644 index 0000000000..68eb158252 Binary files /dev/null and b/assets/events/2026-melbourne/organizers/jordan_kueh.png differ diff --git a/assets/events/2026-melbourne/organizers/matthew_jones.png b/assets/events/2026-melbourne/organizers/matthew_jones.png new file mode 100644 index 0000000000..cf499043ca Binary files /dev/null and b/assets/events/2026-melbourne/organizers/matthew_jones.png differ diff --git a/assets/events/2026-melbourne/organizers/mel_kaulfuss.jpg b/assets/events/2026-melbourne/organizers/mel_kaulfuss.jpg new file mode 100644 index 0000000000..65d321b659 Binary files /dev/null and b/assets/events/2026-melbourne/organizers/mel_kaulfuss.jpg differ diff --git a/assets/events/2026-melbourne/organizers/peter_hall.jpeg b/assets/events/2026-melbourne/organizers/peter_hall.jpeg new file mode 100644 index 0000000000..0aeaf0c982 Binary files /dev/null and b/assets/events/2026-melbourne/organizers/peter_hall.jpeg differ diff --git a/assets/events/2026-melbourne/organizers/simon_richards.jpeg b/assets/events/2026-melbourne/organizers/simon_richards.jpeg new file mode 100644 index 0000000000..ec42590c20 Binary files /dev/null and b/assets/events/2026-melbourne/organizers/simon_richards.jpeg differ diff --git a/assets/events/2026-melbourne/organizers/vero_farias.png b/assets/events/2026-melbourne/organizers/vero_farias.png new file mode 100644 index 0000000000..2cd804913d Binary files /dev/null and b/assets/events/2026-melbourne/organizers/vero_farias.png differ diff --git a/assets/events/2026-melbourne/organizers/wendy_ha.jpg b/assets/events/2026-melbourne/organizers/wendy_ha.jpg new file mode 100644 index 0000000000..89d6677c3b Binary files /dev/null and b/assets/events/2026-melbourne/organizers/wendy_ha.jpg differ diff --git a/content/events/2026-melbourne/conduct.md b/content/events/2026-melbourne/conduct.md new file mode 100644 index 0000000000..a08d5eba4c --- /dev/null +++ b/content/events/2026-melbourne/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Melbourne 2026" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Melbourne 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 Melbourne 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-melbourne/contact.md b/content/events/2026-melbourne/contact.md new file mode 100644 index 0000000000..deb8a009e4 --- /dev/null +++ b/content/events/2026-melbourne/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Melbourne 2026" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2026-melbourne/location.md b/content/events/2026-melbourne/location.md new file mode 100644 index 0000000000..84031096dc --- /dev/null +++ b/content/events/2026-melbourne/location.md @@ -0,0 +1,17 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays Melbourne 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-melbourne/propose.md b/content/events/2026-melbourne/propose.md new file mode 100644 index 0000000000..8672be7687 --- /dev/null +++ b/content/events/2026-melbourne/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Melbourne 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. +
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. 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_organizers >}}] with the following information +
    +
  1. Type (presentation, panel discussion, ignite)
    2. +
  2. Proposal Title (can be changed later)
    3. +
  3. Description (several sentences explaining what attendees will learn)
    4. +
diff --git a/content/events/2026-melbourne/registration.md b/content/events/2026-melbourne/registration.md new file mode 100644 index 0000000000..bca8772f36 --- /dev/null +++ b/content/events/2026-melbourne/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Melbourne 2026" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2026-melbourne/sponsor.md b/content/events/2026-melbourne/sponsor.md new file mode 100644 index 0000000000..8d4bcc848f --- /dev/null +++ b/content/events/2026-melbourne/sponsor.md @@ -0,0 +1,66 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Melbourne 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 open space session. +

+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, 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. +

+ + +

diff --git a/content/events/2026-melbourne/welcome.md b/content/events/2026-melbourne/welcome.md new file mode 100644 index 0000000000..7f5a170dbf --- /dev/null +++ b/content/events/2026-melbourne/welcome.md @@ -0,0 +1,87 @@ ++++ +Title = "devopsdays Melbourne 2026" +Type = "welcome" +aliases = ["/events/2026-melbourne/"] +Description = "devopsdays Melbourne 2026" ++++ + + + +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ + + + + + + + + + + +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ + + diff --git a/data/events/2026/melbourne/main.yml b/data/events/2026/melbourne/main.yml new file mode 100644 index 0000000000..f03dc922e8 --- /dev/null +++ b/data/events/2026/melbourne/main.yml @@ -0,0 +1,123 @@ +name: "2026-melbourne" # 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: "Melbourne" # The displayed city name of the event. Capitalize it. +event_twitter: "devopsdownunder" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Devopsdays is coming to Melbourne!" # 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: # 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. + +# 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_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_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: "" # No longer used + +location: "Melbourne" # 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! + +# 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://linkedin.com/company/devopsdownunder" # Change this to the url to your Linkedin group, company, or page. +event_social_slack: "https://join.slack.com/t/devopsdownunder/custom_shared_invite_url" # Change this to your slack invite link. +event_social_listserv: "https://lists.devopsdays.org/subscription?custom_listserv_invite_url" # Change this to your mailing list subscription form url. +event_social_twitter: "devopsdownunder" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +event_social_mastodon: "https://mastodon.social/@devopsdownunder" # Change this to url to your mastodon page +event_social_bsky: "https://bsky.app/profile/devopsdownunder.bsky.social" # Change this to url to your bluesky page +event_social_youtube: "devopsdownunder" # Change this to the youtube channel handle for your event such as devopsdaysrox + +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: "Vero Farias" + bio: "Vero is a Computer Scientist with nineteen years of experience, who’s worn a few hats over the years: DevOps, SRE, and Software engineering. A passionate advocate for women and kids in tech, she works to make technology inclusive and accessible for everyone. Outside of work, she thrives as a mom and enjoys laser-cutting projects, cooking, soccer, table tennis, cycling, and participating in tech and non-tech community events." + image: "vero_farias.png" + - name: "Wendy Ha" + employer: "Seek, CNCF Ambassador" + bio: "Wendy is an Software Engineer with passion across Platform Engineering, Site Reliability and Observability. She is a proud advocate for Women in Tech, the Deaf and Hard of Hearing community, and Women-led Entrepreneurship. When she’s not coding or contributing to the community, you’ll find her enjoying a cup of coffee or exploring Melbourne's Dandenong trails. " + twitter: "wendy_ha18" + image: "wendy_ha.jpg" + - name: "Peter Hall" + employer: "ANZ bank" + bio: "Peter has a long background in all things cloud, security and development and is now working as an SRE engineering manager with ANZ bank. He is a big supporter of the DevOps and SRE communities in Melbourne and was involved in the organization of both the 2015 and 2023 DevOpDays conferences in Melbourne. He is also one of the co-organizers of the Melbourne Infracoders meetup." + twitter: "peterkh" + image: "peter_hall.jpeg" + - name: "Fabian Iannarella" + twitter: "fiannarella" + image: "fabian_iannarella.jpg" + - name: "Matthew Jones" + employer: "Read Guava" + twitter: "geekle" + image: "matthew_jones.png" + - name: "Mel Kaulfuss" + employer: "Stile" + bio: "Mel has been building software, and technical communities for over a decade now. DevOps principles are central to her work at the intersection of technology, product and people, she loves to bring people together to deliver value in safe inclusive spaces. She watches too much k-drama, and has two cheeky border terriers." + image: "mel_kaulfuss.jpg" + - name: "Jordan Kueh" + employer: "Culture Amp" + image: "jordan_kueh.png" + - name: "Simon Richards" + employer: "Mantel Group" + bio: "Simon is passionate about driving business outcomes by strategically leveraging best of breed methodologies and tooling to deliver quantifiable and impactful value. With a keen focus on guiding teams to build scalable, reliable platforms that champion engineering excellence while driving significant improvements in business performance and achieving positive change." + image: "simon_richards.jpeg" + + + + +organizer_email: "melbourne@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: +# - id: samplesponsorname +# level: gold +# url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. + +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 aa7183c585..e700857ed5 100644 --- a/static/_redirects +++ b/static/_redirects @@ -169,7 +169,7 @@ /miami/* /events/2020-miami/:splat 302 /luanda/* /events/2020-luanda/:splat 302 /criciuma/* /events/2020-criciuma/:splat 302 -/melbourne/* /events/2023-melbourne/:splat 302 +/melbourne/* /events/2026-melbourne/:splat 302 /ankara/* /events/2020-ankara/:splat 302 /lima/* /events/2025-lima/:splat 302 /rosario/* /events/2020-rosario/:splat 302