Having a first SIG Community call
by Karsten Wade
Are you interested in how we organize and run the Operate First project? Do
you want to participate in getting things done?
SIG Community has the charter to figure that out, one step at a time. Come
join us in all the work and fun!
Step one is having our first (virtual) meeting, see who is interested in
being involved, and decide on which subprojects and new SIGs those people
are interested in running.[1]
https://doodle.com/poll/phwviunxrerrkba2
The time windows I selected include NA/Western Europe-centric ones, but I
also put in a window that is more friendly for folks in Asia and around the
Pacific Rim.
My thinking is: when we have more SIGs, subprojects, and working groups, we
want to have folks participating from wherever they are. Let's be inclusive
from the start, and figure out accommodations that are needed to make it
work. Maybe we even have two meeting times, every other week?
See you there!
- Karsten
[1] This is the PR for the SIG Community charter, I anticipate it being
merged before next week. We can always make changes to it, but this gives
us a place to start the meeting from.
https://github.com/operate-first/community/pull/124
--
Karsten Wade [he/him/his] | Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen
The Open Source Way : https://theopensourceway.org
Operate First : https://operate-first.cloud
2 years, 9 months
Adding an automated publishing workflow for the training repo/content
by Stephanie Watson
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
2 years, 9 months
Onboarding RapiDAST
by Jeremy Choi
Hi all
RapiDAST is made public now at
https://github.com/RedHatProductSecurity/rapidast.
RapiDAST is currently providing a framework for automated dynamic scanning
against web API. The goal here in terms of OperateFirst is:
RapiDAST to be running as a service for the community hosted on operate
first clusters. Any service running on operate first and any other
community service can use RapiDAST to check for security risks in their API.
For onboarding, implementation of an operator and work to get it onboard is
yet to be done. Any guidance or references on processes, requirements or
implementation will be much appreciated.
Thanks
--
Jeremy Choi / Red Hat Product Security
2 years, 9 months