1:53 p.m.
Hi Stephanie,
Welcome! We do actually have multiple SRE training efforts underway for
Operate First at the moment, so we should try to coordinate this better as
a first step. Sarah Coghlan has been coordinating training for new SREs
from the student community. There have also been some Operate First
workshops, although those are not exactly training.
I am not sure that we have critical mass to form a separate training SIG
yet, so I think discussing it in SIG-Community makes sense, at least to
start. Both efforts have the objective of bringing more people to Operate
First and making it easier for them to contribute.
On Tue, Feb 15, 2022 at 2:22 PM Stephanie Watson <swatson(a)redhat.com> wrote:
Hello, community!
My team is currently focused on creating self-paced training content aimed
at enabling current and prospective SREs for their job roles. Most of our
content is going to internal Red Hat associates first (it's the group we
serve). But we have a goal to work with other Red Hatters committed to
pushing that content out into the community space. We also have two
training modules (units of training) currently in development that are
going directly into the community space: "The Operate First Mindset" and
"Getting Involved with Open Source."
To make this possible, I've worked on setting up our Operate First
"training" repo <https://github.com/stefwrite/training> [1] with a
README.md, directory structure, and the placeholders for the Operate First
and Open Source courses in Jupyter Book form. Our current plan is to
develop each training module as a Jupyter Book within that directory
structure.
We're now at the stage of needing help from the rest of the community to:
- Get feedback/suggestions about our plan to use Jupyter Book in this
way
- Engage someone who can create some PR-triggered automation that will
build the books and publish them to a training space at
operate-first.org
- Take any suggestions on how we could organize the content in the
repo better to facilitate that automation
I am working off building Jupyter Books into HTML, then publishing the
HTML. But perhaps there's an alternative I haven't considered. I'm welcome
to anything that will make the process easier for contributors and
maintainers alike!
Once we can establish a flow of create+publish+maintain, we can all start
to build out that content.
What should my next step be?
Also, Is this within the realm of the community SIG? Or should we form a
"training SIG" for this? Or maybe a general "knowledge SIG"
that's focused
on both docs and training?
[1] https://github.com/stefwrite/training
--
Stephanie Watson
she/her | Program Manager, PnT Experience
swatson(a)redhat.com | M: 919-333-5050
_______________________________________________
Community mailing list -- community(a)lists.operate-first.cloud
To unsubscribe send an email to community-leave(a)lists.operate-first.cloud