💫 updates for 2026 launch

Author: alanderex

config.yml

@@ -19,51 +19,51 @@ copyright:
 
 # Event details
 event:
-  event_name: "PyCon DE & PyData 2025"
-  start_date: "23.04.2025"
-  end_date: "25.04.2025"
-  day_before: "22.04.2025"
+  event_name: "PyCon DE & PyData 2026"
+  start_date: "14.04.2026"
+  end_date: "16.04.2026"
+  day_before: "13.04.2026"
   month: "April"
-  year: "2025"
+  year: "2026"
   location: "Darmstadt, Germany"
   contact_email: "[email protected]"
   # program
-  cfp_open: "26.11.2024"
-  cfp_close: "06.01.2025"
-  review_deadline: "26.01.2025"
-  cfp_speakers_notifications: "05.02.2025"
-  cfp_link: "https://pretalx.com/pyconde-pydata-2025/cfp"
-  voting_url: "https://pretalx.com/pyconde-pydata-2025/p/voting/signup/"
-  voting_start: "09.01.2025 12:00 CET"
-  voting_end: "19.01.2025 23:59 CET"
-  contact_program: "[email protected]"
+  cfp_open: "19.11.2025"
+  cfp_close: "21.12.2025 23:59 CET"
+  review_deadline: "TBA"
+  cfp_speakers_notifications: "11.02.2026"
+  cfp_link: "TBA"
+  voting_url: "TBA"
+  voting_start: "TBA"
+  voting_end: "TBA"
+  contact_program: "TBA"
   # diversity
-  financial_aid_open: "06.12.2024"
-  financial_aid_close: "10.01.2025 23:59 CET"
-  financial_aid_notifications: "14.02.2025"
-  financial_aid_form: "https://forms.gle/u1qAPxQBcQYma9cq7"
+  financial_aid_open: "19.11.2025"
+  financial_aid_close: "21.12.2025 23:59 CET"
+  financial_aid_notifications: "TBA"
+  financial_aid_form: "TBA"
   financial_aid_regional_countries: "Albania, Algeria, Andorra, Armenia, Austria, Azerbaijan, Belarus, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Czech Republic/Czechia, Denmark, Egypt, Estonia, Finland, France, Georgia, Germany, Greece, Hungary, Iceland, Ireland, Israel, Italy, Jordan, Kosovo, Latvia, Lebanon, Libya, Liechtenstein, Lithuania, Luxembourg, Malta, Monaco, Montenegro, Moldova, Morocco, Netherlands, North Macedonia, Northern Cyprus, Norway, Palestine, Poland, Portugal, Republic of Cyprus, Romania, San Marino, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Syria, Tunisia, Turkey, Ukraine, United Kingdom, and Vatican City."
   # committees
-  call_for_committee_open: "22.10.2024"
-  call_for_committee_close: "01.11.2024"
-  apply_url_committees: "https://forms.gle/CwoS6z6BFxhjNBe4A"
+  call_for_committee_open: "09.10.2025"
+  call_for_committee_close: "31.10.2025"
+  apply_url_committees: "https://pioneershub.typeform.com/to/X4DSSKpG"
   # volunteers
-  call_for_volunteers_open: "01.03.2025"
-  call_for_volunteers_close: "15.03.2025"
+  call_for_volunteers_open: "01.03.2026"
+  call_for_volunteers_close: "15.03.2026"
   apply_url_volunteers: "/to-be-announced/"
   # tickets
-  ticket_sales_open: "15.01.2025"
-  ticket_sales_late_bird: "01.03.2025"
+  ticket_sales_open: "19.11.2025"
+  ticket_sales_late_bird: "11.02.2026"
 
   # Code of Conduct Team
   coc_email: [email protected]
   team_members: |
-    - Larissa Haas (Chair)
-    - Jonathon Olson
-    - Lev Dadashev
-    - Paula González Avalos
+    - To be announced
+    - To be announced
+    - To be announced
+    - To be announced
   backup_team_members: |
-    - Paloma Olivera
+    - To be announced
     - To be announced
 
 committees:
@@ -74,9 +74,16 @@ committees:
       attend_conference: true
     workload:
       average: "Usually not much to do, but be prepared for reports. If reports come in immediate action is required."
-      start: "15.11.2024"
+      start: "15.11.2025"
       peak: "During the conference, it depends on reports coming in"
       end: "Until all reports have been resolved"
+  "community_support":
+    attend_conference: true
+    workload:
+      average: "1-2 hours per week"
+      start: "15.11.2024"
+      peak: "4 weeks before the conference, during the conference"
+      end: "2 weeks afters the conference"
   "communication":
     attend_conference: true
     workload:
@@ -88,7 +95,7 @@ committees:
     attend_conference: true
     workload:
       average: "1-2 hours per week"
-      start: "10.11.2024"
+      start: "01.11.2025"
       peak: "During the selection and notification process. Four months before the conference 4-5 hours per week for 2 weeks"
       end: "Four weeks after the conference until report and reimbursements are made"
   "experience":
@@ -102,7 +109,7 @@ committees:
     attend_conference: true
     workload:
       average: "1-2 hours per week"
-      start: "15.11.2025"
+      start: "01.11.2025"
       peak: "2 weeks before the conference, during the conference if something breaks"
       end: "conference end"
   "on_site_operations":

docs/committees/community-support.md

@@ -0,0 +1,93 @@
+---
+title: Community Support Committee
+icon: fontawesome/solid/users-line
+---
+
+# Community Support Committee
+
+## Mission
+
+The Community Support Committee ensures that every participant feels welcomed, supported, and included throughout the conference
+experience.  
+Its mission is to foster a positive, respectful, and enjoyable environment for attendees, speakers, and volunteers — from first contact to
+follow-up after the event.  
+This committee serves as the friendly and reliable point of contact for the community, helping to address concerns, guide attendees, and
+ensure that everyone can fully participate.
+
+## Committee Structure
+
+### Chair
+
+The Chair(s) of the Community Support Committee lead and coordinate the team’s efforts to ensure smooth and empathetic attendee
+interaction.  
+They organize the volunteer shifts, maintain clear communication with other committees, and oversee community well-being before, during, and
+after the event.  
+The Chair(s) will attend virtual planning meetings and be on-site at the conference to manage support operations.
+
+### Members
+
+A team of committee members who serve as the community’s go-to support network.  
+They help answer questions, provide guidance, ensure inclusivity, and assist in handling any interpersonal or practical issues that arise
+during the conference.
+
+## Requirements
+
+- Empathy, patience, and strong interpersonal skills
+- Ability to stay calm and solution-oriented in stressful situations
+- Experience in community moderation or event support (preferred but not required)
+- Familiarity with the conference’s Code of Conduct and diversity goals
+- Willingness to collaborate closely with the Diversity, Communication, and Volunteer Committees
+- Commitment to maintaining confidentiality and discretion when needed
+
+## Responsibilities
+
+- **Provide Attendee Support:**  
+  Act as the first point of contact for attendees with questions or concerns before and during the conference, ensuring everyone feels heard
+  and supported.
+
+- **Coordinate On-Site Helpdesk and Information Points:**  
+  Manage or staff information desks and digital support channels (e.g., Discord, email) to offer guidance and updates.
+
+- **Support Code of Conduct Enforcement:**  
+  Collaborate with the Code of Conduct team to ensure that all participants experience a safe and welcoming environment.
+
+- **Assist with Accessibility and Inclusion:**  
+  Work with the Diversity Committee to respond to accessibility requests and ensure that all attendees can participate comfortably.
+
+- **Volunteer Support:**  
+  Help coordinate volunteers, making sure they have clear instructions, know their responsibilities, and feel part of the team.
+
+- **Community Well-Being:**  
+  Foster a friendly atmosphere, mediate small issues if they arise, and make sure attendees know where to turn for help.
+
+### Responsibilities for Chair(s)
+
+* Chair virtual meetings with the community support committee members
+* Coordinate volunteer and attendee support logistics
+* Be in attendance on-site at {{config.extra.event.event_name}} to oversee community well-being
+
+### Workload
+
+The workload for the Community Support Committee varies throughout the year, with most activity happening closer to and during the
+conference.  
+In early stages, the committee focuses on preparation and coordination with other teams. As the conference approaches, the workload
+intensifies due to volunteer organization, attendee communication, and live support.
+
+* **Preparations:** A few hours per week setting up support channels and guidelines.
+* **Before Conference:** Up to 4–6 hours per week organizing volunteers and ensuring information flow between committees.
+* **During Conference:** Full on-site presence or active remote shifts, providing real-time support to attendees and volunteers.
+* **After Conference:** Gathering feedback and documenting improvements for next year.
+
+### Timeline
+
+:fontawesome-solid-gauge:  **average:** {{config.extra.committees.community_support.workload.average}}
+
+:fontawesome-regular-calendar:  **start:** {{config.extra.committees.community_support.workload.start}}
+
+:fontawesome-solid-heart-pulse: **peak** {{config.extra.committees.community_support.workload.peak}}
+
+:fontawesome-solid-ranking-star: **finish** {{config.extra.committees.community_support.workload.end}}
+
+---
+
+[Apply here]({{config.extra.event.apply_url_committees}}){:target="_blank" .md-button .md-button--primary }

docs/committees/diversity.md

@@ -61,6 +61,9 @@ A team of four committee members from diverse backgrounds and experiences.
   Help collect receipts from grantees to facilitate the reimbursement process
   with [Finance](../office/finance-budget.md).
 
+- **Support Accessibility Needs:**  
+  Respond to participants who reach out with accessibility requirements and work with the organizing team to ensure they have a welcoming, inclusive, and accessible conference experience.
+
 - **Collaborate with Other Communities:**  
   Work with community partners like [PyLadies](https://pyladies.org) and reach out to other communities to ensure
   diverse participation.

docs/committees/experience.md

@@ -82,6 +82,6 @@ The workload for the Experience Committee will vary depending on the proximity t
 :fontawesome-solid-ranking-star: **finish** {{config.extra.committees.experience.workload.end}}
 
 ---
-[Apply here]({{config.extra.event.apply_url_committees}}){:target="_blank" .md-button .md-button--primary }
+[This Committee is set up already and currently not accepting applications](#){:target="_blank" .md-button .md-button--primary }
 
 ---

docs/committees/index.md

@@ -1,6 +1,7 @@
 ---
 icon: fontawesome/solid/people-group
 ---
+
 # Volunteer Committees
 
 The committees are the driving force behind the conference, responsible for shaping its many facets. We’re seeking
@@ -14,17 +15,15 @@ field or eager to learn and grow with us, there’s a place for you on our team.
 ## The Committees
 
 - :fontawesome-solid-shield: [Code of Conduct](code-of-conduct.md)
-- :fontawesome-solid-paper-plane: [Communication](communication.md)
+- :fontawesome-solid-users-line: [Community Support](community-support.md)
 - :fontawesome-solid-universal-access: [Diversity](diversity.md)
 - :fontawesome-solid-face-smile: [Experience](experience.md)
 - :fontawesome-solid-people-group: [On-Site Operations](on-site-ops.md)
 - :fontawesome-solid-chalkboard: [Program](program.md)
 - :fontawesome-solid-compass: [Steering](steering.md)
-- :fontawesome-solid-shirt: [Swag](swag.md)
 - :fontawesome-solid-video:  [Video](video.md)
 
 ---
-
 ## Committee Descriptions
 
 Please review the committee descriptions to find the one that best fits your interests and skills.
@@ -34,16 +33,45 @@ The conference is realized by [volunteer organizers](index.md) and the [conferen
 While the volunteers are responsible for the conference content, authenticity and attendees' experience,
 the backoffice is responsible for the organization (sponsoring, finances, budget, contracts, etc.).
 
-[Applications are closed for 2025](#){:target="_blank" .md-button .md-button--secondary }
+[Apply to Volunteer Here]({{config.extra.event.apply_url_committees}}){:target="_blank" .md-button .md-button--primary }
+
+---
+## How Committees Are Formed
 
+* We first invite experienced members from last year to return and share their know-how.
+* Existing roles are confirmed, and we fill only the open spots.
+* We always bring in fresh faces to keep ideas and energy flowing.
 
+---
 ## Application Process
 
 * Please review the committee descriptions
 * Choose one or multiple committee you’re interested in contributing to
 * Fill out the application form
 * The Steering Committee will review the applications and get back to you
 
-[Applications are closed for 2025](#){:target="_blank" .md-button .md-button--secondary }
+[Apply to Volunteer Here]({{config.extra.event.apply_url_committees}}){:target="_blank" .md-button .md-button--primary }
+
+---
+
+## Committee Team Health
+
+A healthy, motivated team is the foundation of our success. We value openness, fairness, and reliability in how we work together.  
+Joining a committee means being part of a hands-on team where everyone contributes and supports one another.
+
+- **Active Contribution:**  
+  Joining a committee means taking responsibility for a clear and manageable task — and following through. Just joining meetings is not enough.
+
+- **Shared Responsibility:**  
+  We aim for a fair distribution of work so that everyone contributes meaningfully and no one carries the load alone.
+
+- **Respectful Accountability:**  
+  If someone consistently cannot contribute, we’ll kindly ask them to step back — no hard feelings, but we want to keep our teams focused and balanced.
+
+- **Supportive Culture:**  
+  We encourage open communication, offer help when someone feels stuck, and celebrate each other’s progress.
+
+- **Positive Collaboration:**  
+  We believe in constructive feedback, shared learning, and creating an environment where everyone feels valued and inspired to do their best work.
 
 ---

docs/committees/operational-model.md

@@ -6,7 +6,7 @@ hide:
 ---
 
 
-!!! tip "Pycon DE & PyData 2025 works 'Distributed & Asynchronous'"
+!!! tip "{{config.extra.event.event_name}} works 'Distributed & Asynchronous'"
     We are a large team and we have made excellent experience in the past working this way.
 
 # Operational Models

docs/committees/program.md

@@ -31,6 +31,14 @@ conference.
   fields
 * Newcomers are welcome
 
+* We’re looking for Program Committee members who are:
+
+  * Hands-on – an engineer at heart; you write code, do development, and enjoy building tools or automating workflows.
+  * Organized & proactive – skilled at managing processes, coordinating reviewers, and keeping timelines on track.
+  * Communicative – comfortable writing and speaking with keynote speakers, sponsors, and the community.
+
+
+
 ## Responsibilities
 
 - **Update Submission Guidelines**  

docs/committees/steering.md

@@ -67,6 +67,6 @@ the formation of committees, providing guidance, and ensuring initial milestones
 
 ---
 
-[Apply here]({{config.extra.event.apply_url_committees}}){:target="_blank" .md-button .md-button--primary }
+[Steering is recruited from experienced organizers and invite-only](#){:target="_blank" .md-button .md-button--primary }
 
 ---

docs/committees/team-communication.md

@@ -11,7 +11,7 @@ helps us work more efficiently and ensures no important details get lost. 🚀
 
 ## Inner-Committee Communication
 
-We use Discord as our primary platform for internal communication. When you join, the Admins will invite you to your
+We use **Discord** as our primary platform for internal communication. When you join, the Admins will invite you to your
 committee’s channel to get started smoothly.
 
 ## Cross-Committee Communication

docs/mission.md

@@ -29,9 +29,10 @@ We hold ourselves to high standards in everything we do, from organizing the eve
 We need enthusiastic volunteers like you! You don't need to be an expert – just bring your:
 
 - Excitement about creating an awesome experience for everyone
-- Willingness to lend a hand wherever it's needed
+- Sense of responsibility to take on a clear task, see it through, and deliver reliably
 - Passion for including people from all walks of life
 - Team spirit and openness to new ideas and people
+- Willingness to lend a hand wherever it's needed
 - Eagerness to learn and grow while helping others do the same
 
 Check out the volunteer committees you can join: