Skip to content
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

Blog article on joint SCS standardization w/ ALASCA. #790

Closed
wants to merge 2 commits into from

Conversation

garloff
Copy link
Member

@garloff garloff commented Nov 23, 2023

Once merged, the article will go live within ~10 minutes.
ToDo:

  • Review layout (on staging)
  • Proofread English translation
  • Align publication time with ALASCA

@garloff garloff added Community Issues or pull requests relevant for SIG Community standards Issues / ADR / pull requests relevant for standardization & certification labels Nov 23, 2023
@garloff
Copy link
Member Author

garloff commented Nov 23, 2023

Should we move this from the Blog section into the Own announcements section?

Signed-off-by: Kurt Garloff <[email protected]>
@garloff
Copy link
Member Author

garloff commented Nov 23, 2023

Ignore this, we have PR #789 which I overlooked.
Probably we can use the english translation from this one though.

langfristige Kontinuität der SCS-Standardisierungsaktivitäten. Die Special
Interest Group ist offen für alle Cloud Provider und Integratoren, die
entsprechend SCS-konforme Angebote im Markt machen und zu den Standards
beitragen wollen.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds potentially a little exclusive. It could be misundastood, that only firms, which already utilize the standards may join. Is this, what we aim for as participation criteria?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I depends on how you read the "und" -- IT folks may read it as boolean and where both conditions need to be fulfilled, people with less math background probably see it as inclusive. We are open to everyone that wants to contribute, though I think I would consider input from people that consume SCS standards or that provide services according to SCS standards a lot more relevant than arbitrary musings from people whose interest is unclear ...

Copy link
Contributor

@alexander-diab alexander-diab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very well formulated. Two thoughts:

  1. Overall it sounds like there is collaboration and intended to be used on both sides. If the decision is finalized, it could be expressed stronger and clearer.
  2. For people like us, who are familiar with the topics, that text may be easy to consume. It may be considered to do a reality check with a person, which has less background.

and coordintated by Dr. Matthias Büchse from Cloud & Heat technologies.
Building on top of already existing standards, the goal is to achieve a
broader adoption of SCS standards by more close collaboration with ALASCA
and also cover the ALASCA technology stack with the cloud lifecycle management
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
and also cover the ALASCA technology stack with the cloud lifecycle management
and also cover the ALASCA technology stack with the cloud-lifecycle management

(weil cloud sich auf lifecycle und nicht auf management tool bezieht)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disagree

@mbuechse
Copy link
Contributor

I think this is a duplicate of #789.

@mbuechse mbuechse closed this Nov 23, 2023
@fkr fkr deleted the feat/announce-std-with-alasca branch February 16, 2024 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community Issues or pull requests relevant for SIG Community standards Issues / ADR / pull requests relevant for standardization & certification
Projects
Status: Published
Development

Successfully merging this pull request may close these issues.

3 participants