Skip to content

Add extra session for SIG Std/Cert on June 25, 2026 #437

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.

Sign up for GitHub

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
mbuechse merged 2 commits into from
Jun 9, 2026
Merged

Add extra session for SIG Std/Cert on June 25, 2026 #437

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a208447
Add two extra sessions for SIG Std/Cert in June 2026
mbuechse Jun 8, 2026
b0c1c01
Reduce to one extra session after deliberation
mbuechse Jun 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions teams/sig_standard_cert/onetimes.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,22 @@ events:
Jitsi server on https://conf.scs.koeln:8443/SCS-Tech
Dial-In: +49-221-292772-611
Coordinator: Matthias Büchse <matthias.buechse[at]cloudandheat.com>

- summary: "SIG Standardization/Certification: extra session"
begin: 2026-06-25 14:05:00
uid: sig-std-crt-2026-06-25@docs.scs.community
duration:
minutes: 50
description: |
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.

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.

This SIG is a joint effort by SCS and ALASCA.

Minutes: https://github.com/SovereignCloudStack/minutes/tree/main/sig-standardization
HedgeDoc: https://input.scs.community/2026-scs-sig-standardization
Jitsi server on https://conf.scs.koeln:8443/SCS-Tech
Dial-In: +49-221-292772-611
Coordinator: Matthias Büchse <matthias.buechse[at]alasca.cloud>
location: "https://conf.scs.koeln:8443/SCS-Tech"
Loading