Skip to content

Commit 4d5b4d7

Browse files
fkrmbuechse
andauthored
Feat/continue meetings in 2026 (#405)
* add Lean Coffee and SCS Community meeting for 2026 Signed-off-by: Felix Kronlage-Dammers <[email protected]> * extend sig std/crt into 2026 Signed-off-by: Felix Kronlage-Dammers <[email protected]> * extend PB into 2026 Signed-off-by: Felix Kronlage-Dammers <[email protected]> * Update etherpad url for 2026 Signed-off-by: Matthias Büchse <[email protected]> --------- Signed-off-by: Felix Kronlage-Dammers <[email protected]> Signed-off-by: Matthias Büchse <[email protected]> Co-authored-by: Matthias Büchse <[email protected]>
1 parent 4906404 commit 4d5b4d7

File tree

3 files changed

+66
-0
lines changed

3 files changed

+66
-0
lines changed

other.yml

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -149,3 +149,31 @@ events:
149149
- 2025-10-03 11:05:00 # Public Holiday in Germany
150150
- 2025-10-31 11:05:00 # Public Holiday in parts of Germany
151151
- 2025-11-28 11:05:00 # Moved to December
152+
- summary: "SCS Community Meeting"
153+
begin: 2026-01-23 11:05:00
154+
duration:
155+
minutes: 50
156+
description: |
157+
The monthly meeting for the broader SCS community. Everyone is welcome - bring your questions, stories, ideas!
158+
Jitsi server on https://conf.scs.koeln:8443/SCS-Tech
159+
Dial-In: +49-221-292772-611
160+
Coordinator: The SCS Project Board - <project-board[at]lists.scs.community>
161+
location: "https://conf.scs.koeln:8443/SCS-Tech"
162+
repeat:
163+
interval:
164+
weeks: 4
165+
until: 2026-12-18 # required
166+
- summary: "Lean SCS Operator Coffee"
167+
begin: 2026-01-08 10:05:00
168+
duration:
169+
minutes: 50
170+
description: |
171+
This format offers a place where SCS operators can meet and discuss operating SCS with the various topics around that.
172+
Jitsi server on https://conf.scs.koeln:8443/SCS-Tech
173+
Dial-In: +49-221-292772-611
174+
Coordinator: Felix Kronlage-Dammers <fkr[at]osb-alliance.com>
175+
location: "https://conf.scs.koeln:8443/SCS-Tech"
176+
repeat:
177+
interval:
178+
weeks: 4
179+
until: 2026-12-18 # required

team_meetings.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,3 +52,20 @@ events:
5252
- 2025-07-07 14:05:00 # Moved to 12:05:00 same day
5353
- 2025-09-08 14:05:00 # Too many ppl are out
5454
- 2025-10-13 14:05:00 # No topics
55+
- summary: "SCS Project Board"
56+
begin: 2026-01-12 14:05:00
57+
duration:
58+
minutes: 50
59+
description: |
60+
The SCS Project Board as described in SCS-0005. The SCS Project Board governs the SCS Open Source Project.
61+
62+
Minutes: https://github.com/SovereignCloudStack/minutes/tree/main/project-board
63+
Etherpad: https://input.scs.community/2025-scs-project-board
64+
Jitsi server on https://conf.scs.koeln:8443/SCS-Tech
65+
Dial-In: +49-221-292772-611
66+
Coordinator: The SCS Project Board
67+
location: "https://conf.scs.koeln:8443/SCS-Tech"
68+
repeat:
69+
interval:
70+
weeks: 1
71+
until: 2026-12-18

teams/sig_standard_cert/team_meetings.yml

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -113,3 +113,24 @@ events:
113113
except_on:
114114
- 2025-10-28 10:05:00 # too many people won't make it
115115
- 2025-11-04 10:05:00 # ALASCA Summit 2025
116+
- summary: "SIG Standardization/Certification"
117+
begin: 2026-01-15 14:05:00
118+
duration:
119+
minutes: 50
120+
description: |
121+
In this Special Interest Group, we discuss and align our activities and approach to standardization and certification. That is to say, we devise and refine the relevant concepts and processes; we work on a roadmap for new certificate versions; and we align on which standards are desireable for each certificate subject. We then work with the teams to align on existing or new standards.
122+
123+
Besides aspects of openness and sovereignty, the main goal of our standards is interoperability. We should take the user perspective: As a member of a DevOps team developing a service (think SaaS or PaaS) for SCS, I need XYZ. Every standard should be abstract enough to work regardless of the SCS reference implementation.
124+
125+
This SIG is a joint effort by SCS and ALASCA.
126+
127+
Minutes: https://github.com/SovereignCloudStack/minutes/tree/main/sig-standardization
128+
Etherpad: https://input.scs.community/2026-scs-sig-standardization
129+
Jitsi server on https://conf.scs.koeln:8443/SCS-Tech
130+
Dial-In: +49-221-292772-611
131+
Coordinator: Matthias Büchse <matthias.buechse[at]alasca.cloud>
132+
location: "https://conf.scs.koeln:8443/SCS-Tech"
133+
repeat:
134+
interval:
135+
weeks: 1
136+
until: 2026-12-18

0 commit comments

Comments
 (0)