From a5fa4d28721454641568e326be35610ea147e563 Mon Sep 17 00:00:00 2001 From: kolbl Date: Tue, 13 Jan 2026 20:21:33 +0100 Subject: [PATCH] adding initial info for devopsdays graz 2026 --- content/events/2026-graz/conduct.md | 28 +++++++ content/events/2026-graz/contact.md | 14 ++++ content/events/2026-graz/location.md | 63 ++++++++++++++ content/events/2026-graz/sponsor.md | 78 ++++++++++++++++++ content/events/2026-graz/welcome.md | 85 +++++++++++++++++++ data/events/2026/graz/main.yml | 118 +++++++++++++++++++++++++++ 6 files changed, 386 insertions(+) create mode 100644 content/events/2026-graz/conduct.md create mode 100644 content/events/2026-graz/contact.md create mode 100644 content/events/2026-graz/location.md create mode 100644 content/events/2026-graz/sponsor.md create mode 100644 content/events/2026-graz/welcome.md create mode 100644 data/events/2026/graz/main.yml diff --git a/content/events/2026-graz/conduct.md b/content/events/2026-graz/conduct.md new file mode 100644 index 0000000000..db6084c560 --- /dev/null +++ b/content/events/2026-graz/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Graz 2026" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Graz 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 Graz 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-graz/contact.md b/content/events/2026-graz/contact.md new file mode 100644 index 0000000000..6be93317bd --- /dev/null +++ b/content/events/2026-graz/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Graz 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-graz/location.md b/content/events/2026-graz/location.md new file mode 100644 index 0000000000..fd779348bb --- /dev/null +++ b/content/events/2026-graz/location.md @@ -0,0 +1,63 @@ + ++++ +Title = "Location" +Type = "event" +Description = "Location for DevOpsDays Graz 2026" ++++ + +
+

Conference Venue

+

The conference will take place at the WIFI & FH Campus 02.

+ +

Friday – Workshops

+

+ The workshops on Friday will be held in the lecture halls of FH Campus 02:
+ Körblergasse 126
8010 Graz +

+ +

Saturday – Conference

+

+ The conference on Saturday will take place in the "Europasaal" at WIFI Graz:
+ Körblergasse 111/113
8010 Graz +

+
+ +
+

Arriving by Public Transport

+

Bus stops on the premises and in the vicinity of WIFI Graz:

+ +
+ +
+

Arriving by Car

+

+ A limited number of paid parking spaces are available directly at the WKO parking lot.
+ You can pay using the easypark app – Zone 10100. +

+

+ Alternatively, park for free at the P&R lot on AVL premises:
+ Babenbergerstraße 86, 8020 Graz
+ Then take the free bus to WIFI Graz (Line 62, stop at Zollgasse (Bahnhofgürtel) or Kalvariengürtel – direction WKO-WIFI/tim). +

+

+ You may also park in the Green Zone around the WKO premises. +

+
+ +
+

Accessibility

+

+ The venues are wheelchair accesible. diff --git a/content/events/2026-graz/sponsor.md b/content/events/2026-graz/sponsor.md new file mode 100644 index 0000000000..e9240a72fa --- /dev/null +++ b/content/events/2026-graz/sponsor.md @@ -0,0 +1,78 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Graz 2026" ++++ + +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email and we'll promptly provide you with all the necessary details. If you have any questions or need further clarification, feel free to reach out to us. We offer some flexibility in our sponsorship packages +and are happy to tailor a solution that suits your budget and requirements. + + + +Check out the sponsoring section on our website! + + + +We are grateful for any efforts to create your swag bag items sustainably, helping to reduce the carbon footprint of our conference and contribute to a more +sustainable future. + +

+ + +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-graz/welcome.md b/content/events/2026-graz/welcome.md new file mode 100644 index 0000000000..86d9a1db14 --- /dev/null +++ b/content/events/2026-graz/welcome.md @@ -0,0 +1,85 @@ ++++ +Title = "devopsdays Graz 2026" +Type = "welcome" +aliases = ["/events/2026-graz/"] +Description = "devopsdays Graz 2026" ++++ + +
+
+
+ {{< event_logo >}} +
+
+
+
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+
+
+ Location +
+
+ {{< event_location >}} +
+
+
+
+ Program +
+
+ View the program on our website DevOpsDays Graz. +
+
+ + +
+
+ Get a ticket +
+
+ + DevOpsDays Graz Tickets + +
+
+
+
+ Propose +
+ +
+ Our call for speakers is already closed. +
+
+
+
+ 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/graz/main.yml b/data/events/2026/graz/main.yml new file mode 100644 index 0000000000..d0f500c591 --- /dev/null +++ b/data/events/2026/graz/main.yml @@ -0,0 +1,118 @@ +name: "2026-graz" # 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: "Graz" # The displayed city name of the event. Capitalize it. +event_twitter: "devopsdays" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Join the second edition of the Devopsdays in Graz!" # 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: 2026-09-04 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2026-09-05 # 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: #2026-03-31 # 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: "https://www.devopsdays.at/events/devopsdays-graz-2026" # 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: "Graz" # Defaults to city, but you can make it the venue name. +# +location_address: "WIFI & Campus02, Graz" #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/2026-denver/welcome/ +event_social_linkedin: "https://www.linkedin.com/company/devopsdaysgraz" # Change this to the url to your Linkedin group, company, or page. +event_social_instagram: "https://www.instagram.com/devopsdaysgraz" # Change this to the url to your Linkedin group, company, or page. +event_social_facebook: "https://www.facebook.com/devopsdaysgraz" # Change this to the url to your Linkedin group, company, or page. +event_social_bsky: "https://bsky.app/profile/devopsdaysgraz.bsky.social" # Change this to url to your bluesky page + +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: "Patrick Koch" + employer: "AVL List GmbH" + - name: "Sandra Niederl" + employer: "Guid.New" + - name: "Bernd Hirschmann" + employer: "EG Austria" + - name: "Linda Kolb" + employer: "AVL List GmbH" + - name: "Alexandra Torrico Perez" + employer: "ilvi GmbH" + - name: "Claudia Schlacher" + employer: "Guid.New" +# employer: "Acme Anvil Co." +# github: "devopsdays" +# facebook: "https://www.facebook.com/sally.fields" +# linkedin: "https://www.linkedin.com/in/sallyfields" +# website: "https://mattstratton.com" + # image: "sally-fields.jpg" + +organizer_email: "graz@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: FH Campus02 + level: location +# - id: AVL List GmbH +# level: gold +# # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. +# - id: BearingPoint GmbH +# level: gold +# - id: Guid.New +# level: gold +# - id: NTS NETZWERK TELEKOM SERVICE AG +# level: silver +# - id: EBCONT +# level: silver +# - id: DENOVO GmbH +# level: swag bag + +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 + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: lanyard + label: Lanyard + - id: swag bag + label: Swag Bag + - id: location + label: Location \ No newline at end of file