-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
Add table of with status of SCS standards #29
Comments
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! |
I'd suggest to make an epic that contains each standard as a story. |
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 Questions: Also, I suppose we should keep these issues up to date, referencing any relevant documents, issues, discussions etc., so as to have a single |
There is also this issue within the docs-page repository with the aim of an interactive overview of available, I'm currently on: #60 (going back to this one: SovereignCloudStack/standards#86) |
@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.) |
Yes, you are correct. |
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 |
Will be covered via
|
* add cleanup step Signed-off-by: maxwolfs <[email protected]> * remove standards from docs Signed-off-by: maxwolfs <[email protected]> --------- Signed-off-by: maxwolfs <[email protected]>
As a user, I want to see the current status of SCS standards. Copy tables form slide 17 - 25 to docs repo.
The text was updated successfully, but these errors were encountered: