-
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
Documentation of the SCS Hardware Landscape #277
Conversation
Signed-off-by: Marc Schöchlin <[email protected]>
Signed-off-by: Marc Schöchlin <[email protected]>
Signed-off-by: Marc Schöchlin <[email protected]>
Signed-off-by: Max Wolfs <[email protected]>
Signed-off-by: Max Wolfs <[email protected]>
Signed-off-by: Marc Schöchlin <[email protected]>
…ocs into hardware-landscape
…ocs into hardware-landscape
Signed-off-by: Marc Schöchlin <[email protected]>
From 1 January 2025, the environment will be operated by [forum SCS-Standards](https://scs.community/2024/10/23/osba-forum-scs-standards/) | ||
and the participating companies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really sure why this needs to be part of the documentation. This is content better suited for a blogpost.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the comment that I made to the one item within the document applies to the whole document. |
Co-authored-by: Felix Kronlage-Dammers <[email protected]> Signed-off-by: Marc Schöchlin <[email protected]>
Why does it make sense to describe the Hardware Landscape as part of the documentation?
In principle, however, it also makes sense to create at least a short blog article pointing out that the environment and its documentation exist. |
Add some documentation which provides a high-level overview.