Closed goern closed 2 years ago
What do you mean compatible? Is there a reference document on how to create compatible tutorial for redhat-scholars? @goern
all their tutorials are based on https://github.com/redhat-scholars/courseware-template maybe it is something we can adopt and reuse for op1st? @durandom
absolutely. https://github.com/operate-first/support/issues/113 <-- the workshop in there is also based on this framework. Let's investigate how to turn it into a nice self-hosted page
In the past, the FDE used https://github.com/sophwats/reproducible-workshops as a reproducible workshops template (can see an implementation here. There is definitely room to update it and add some CI/CD elements to customize for op1st :)
In the past, the FDE used https://github.com/sophwats/reproducible-workshops as a reproducible workshops template (can see an implementation here. There is definitely room to update it and add some CI/CD elements to customize for op1st :)
We might consider also https://github.com/aicoe-aiops/project-template (used in this repo as well), that mixes devops and ml requirements :)
I'd like to see something that looks good, is maintained and used by a larger community.
@blues-man @rcarrata @acidonper is the redhat-scholars template something used widely at RH consulting / SA?
Well the goal is to create content usable by an "extended developer advocacy" team in Red Hat from all departments :) It is used by both DAs and and SSAs at the moment, waiting for more contributions!
@durandom, we are using this template but it is not a standard or used widely.
I think that it will probably be used intensively in the future but it is not a fact. From my side, I have 4 workshops published with this template and I pretend to continue to use it...
/kind documentation /priority backlog
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
@mayaCostantini havent you worked on this?
@mayaCostantini havent you worked on this?
Yes indeed, see the Managing Vulnerabilities with Thoth Tutorial and the corresponding repository
/remove lifecycle-rotten /close See comment above
/close
@goern: Closing this issue.
SSIA ;)