Add table of with status of SCS standards

[anjastrunk]

As a user, I want to see the current status of SCS standards. Copy tables form slide 17 - 25 to docs repo.

[mbuechse]

Current development happens inside HedgeDoc.
The guide tells us where to place documentation. Still unsure where to put it. @garloff What do you think?

[garloff]

My suggestion would be to add an issues to the Standards repo to track each standardization line from the slides. Note that some already exist!
A master issue that links the others would be useful. (Use - [ ] syntax.)
Standards are Drafted as md docs in the standards repo.
The SCS docs page can include docs from various repos, including the standards.

[fkr]

A master issue that links the others would be useful. (Use - [ ] syntax.)

I'd suggest to make an epic that contains each standard as a story.
Definition of Done for the epic contains of that said list (that contains the stories).

[mbuechse]

So, if I understand your proposals correctly: both of you suggest to use one issue per row of the table; sometimes such an issue already exists, sometimes it needs to be created. Moreover, we might use (1) a master issue with tasks corresponding to these aforementioned issues or (2) an epic linking these issues. Now another option occurs to me: (3) tag the issues and use the board to track them -- in fact, one such board already seems to exist: https://github.com/orgs/SovereignCloudStack/projects/6/views/23?layout=board
edit one might also filter for the "standards" label instead of "SCS is standardized": https://github.com/orgs/SovereignCloudStack/projects/6/views/23?layout=board&filterQuery=label%3A%22standards%22
I'm not quite sure which is the correct one.
edit 2: there is a third label called "standardization": https://github.com/SovereignCloudStack/issues/labels/standardization
It seems to be used only three times, always in conjunction with one of the other two.

Questions:
How do you like this third option?
Is the board the right one, or would we use/create another one?

Also, I suppose we should keep these issues up to date, referencing any relevant documents, issues, discussions etc., so as to have a single source sink of truth?

[maxwolfs]

There is also this issue within the docs-page repository with the aim of an interactive overview of available, I'm currently on: #60
Feedback welcomed! :)

(going back to this one: SovereignCloudStack/standards#86)

[mbuechse]

@maxwolfs Thanks for pointing me to this issue. If I understand correctly, the aim is to convert the YAML file(s) into an interactive diagram, which I do like. I think the epic that @fkr suggested would be a good place for organizing the to-dos, whereas the diagram would mainly show what's already done, right?

BTW, I just noticed that the YAML claims that V2 of "SCS compatible" (a) has been stabilized on 2023-03-23 and (b) it contains the flavor naming standard. However, the latter standard hasn't been stabilized yet. @garloff Is that a contradiction, or are these different concepts of stabilization? (NB I don't mean to be nitpicking here; I'm still familiarizing myself with the topic, and as yet I can't tell with certainty what's problematic and what isn't.)

[maxwolfs]

@maxwolfs Thanks for pointing me to this issue. If I understand correctly, the aim is to convert the YAML file(s) into an interactive diagram, which I do like. I think the epic that @fkr suggested would be a good place for organizing the to-dos, whereas the diagram would mainly show what's already done, right?

Yes, you are correct.

[mbuechse]

I tried to start an epic, but all I can do at the moment is write plain issues; I can't assign labels or anything. The result so far is here: SovereignCloudStack/standards#285
This issue is about the IaaS track; I will add a corresponding issue for KaaS soon.
Existing standards would be tracked via #60
So I suppose this issue can indeed be closed now (I don't seem to be authorized to do so).

[mbuechse]

Will be covered via

• Add interactive overview for standards #60 regarding certification
• [EPIC] IaaS standards standards#285 regarding IaaS standards
• SCS K8s cluster standardization issues#181 regarding CaaS standards