-
Notifications
You must be signed in to change notification settings - Fork 8
Onboarding SCS Hardware Landscape #341
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
base: main
Are you sure you want to change the base?
Conversation
|
As suggested by @fkr, the Project Board should take responsibility for the access to the HW Lab in the future. Hence the request for review by the Project Board here :) |
fkr
left a comment
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.
LGTM!
|
Imho we should also document, what the PB needs to do with those PRs (since the access mgmt setup is then handled by B1, who currently do the OPS for the HW Lab.) |
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
dde01e9 to
7e02fdb
Compare
Good point. However, someone from the Project Board should document it in this PR. I don't want to tell the Board what to do 😅 |
While here, write one sentence on what the PB does with the mail. Signed-off-by: Felix Kronlage-Dammers <fkr@hazardous.org>
I've added couple sentences with a042a32. |
Co-authored-by: Kurt Garloff <kurt@garloff.de> Signed-off-by: Felix Kronlage-Dammers <fkr@hazardous.org>
This PR adds instructions on how to get access to the SCS Hardware Landscape.
Closes #322