Training content & courses: Repo or repos or branches or all the above
by Karsten Wade
All:
The team working on SRE training are ready to setup their repositories, and
Stephanie created this issue for opening the first repository:
https://github.com/operate-first/common/issues/39
We had a meeting today with the team who is going to be working in GitHub,
and we're not sure what is the best model to follow for repositories.
Please join us there to discuss what we want the repo(s) to look like. We
particularly need help from people with experience around automation
amongst multiple repositories.
Background
=========
Stephanie and anyone else, please fix any incorrect GitHub and modularity
thinking here, thanks.
As a community, we are creating a knowledge pool of modular course
materials. Modular here means, creating discrete pieces of content, each
explaining what, how, and why for a task. The learner might be a
contributor learning or reminding how to do the task; or the learner might
be a user taking a full SRE course. The same content can be used in both
cases, but placed into a context specific for the different learner type.
This content therefore is more than a Markdown file, it has inline or
metadata (labels, etc.) that means it can be organized to appear in
multiple learning pathways.
These multiple learning pathways currently are: SRE Learners, Open Source
Developers, Project Contributors, and Data Scientists and Data Engineers.
So if combining the pool with the number of learning path options, it could
be four separate learning paths with e.g. twelve modules per path. Those
modules would comprise existing modular content, combined with content
specific to the module that shapes the relationship to the learner persona.
An example of a single module might be, "How to use GitOps to make changes
to a live production cloud." It could have the how-to and sparse-why
content (useful for Project Contributors and Open Source Developers) from
one location (a repo?), which can be combined with the full what/how/why of
a beginner's viewpoint into a single ready-to-teach module.
That's already 48 unique combinations to cover four pathways, and within
those modules it might be 3x to 5x more when combining pieces to form a
specific module.
Is this a repos problem? A branching problem? A nesting folders problem?
Or something else?
Kind regards,
- Karsten
--
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
3 years
SCaLE 19x CFP closes 30 Nov
by Karsten Wade
Hi all
If you haven't attended or heard of SCaLE, let me introduce you to one
of the best open source ecosystem and community shows on the planet:
https://www.socallinuxexpo.org/scale/19x
We're planning a first-day workshop, something that can highlight the
work we're leading toward landing for KubeCon and Red Hat Summit later
in the year. Details are still being discussed, join in if you are
interested.
https://github.com/AICoE/content-pipeline/issues/20
For anyone interested in submitting talks, let's coordinate in that
issue as well. We can improve CFPs, co-present around complementary
topics, and generally increase chances of acceptance.
SCaLE is very friendly to new speakers and contributors, is volunteer
run, and is consistently the most diverse open source-related event year
over year. Held now in lovely Pasadena, CA at the Pasadena Convention
Center.
Kind regards,
- Karsten
--
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
3 years
Join the Operate First Data Science Community!
by Aakanksha Duggal
Hello All,
Join us for the initial Operate First Data Science Community Meetup on
Tuesday, November 16th at 11:00 ET. There you will learn about the existing
open data science platform managed by the Operate First team and how you
can get started with setting up your very own cloud native data science
environment.
Subscribe to our calendar
<https://calendar.google.com/calendar/u/2?cid=N3QyMm1ydm92amNmdTZqZm5ucDRu...>
for event details.
Our long term goal for this ongoing event is to embrace the
multidisciplinary nature of the current state of AI operations and cloud
infrastructure by discussing technical topics relevant to data scientists,
software engineers, DevOps professionals, statisticians and the
intersection of their work, all in an open and public forum. We welcome new
speakers and Data Science enthusiasts to submit proposals for future talks.
If you are interested, get started by creating an issue in our GitHub
repository
<https://github.com/aicoe-aiops/cloud-first-data-science-community/issues/...>
.
To learn more about the Operate First Data Science Community, visit our
website
<https://www.operate-first.cloud/data-science/operate-first-data-science-c...>
and find the agenda for the upcoming meetups here
<https://www.operate-first.cloud/data-science/operate-first-data-science-c...>
.
We look forward to seeing you at the Meetup!
Best,
The Operate First Data Science Team
Links
1. Calendar Invite:
https://calendar.google.com/calendar/u/2?cid=N3QyMm1ydm92amNmdTZqZm5ucDRu...
2. Topic suggestion:
https://github.com/aicoe-aiops/cloud-first-data-science-community/issues/...
3. Website:
https://www.operate-first.cloud/data-science/operate-first-data-science-c...
4. Agenda:
https://www.operate-first.cloud/data-science/operate-first-data-science-c...
5. Slack:
https://join.slack.com/t/operatefirst/shared_invite/zt-o2gn4wn8-O39g7sthT...
6. Mailing List:
https://lists.operate-first.cloud/admin/lists/community.lists.operate-fir...
Thanks and Regards,
Aakanksha Duggal
She/Her
Software Engineer
Red Hat Boston <https://www.redhat.com/>
AI Center of Excellence
Office of the CTO
aduggal(a)redhat.com
<https://www.redhat.com/>
3 years, 1 month
Strategy and Roadmap for Docs, Handbooks, Guides, etc.
by Humair Khan
Hello everyone, lately there's been some discussion about how we ought to
handle our documentation, guides, handbooks and such going forward. Our
intention is to have them be as community/contributor friendly as possible
-- and that doesn't seem to be the case currently.
I've created GitHub thread to discuss existing issues, which can be found
here <https://github.com/operate-first/SRE/issues/424>. We are hoping to
address some of these in the coming weeks, and would also welcome insight
from the broader community. If you have any suggestions/thoughts/concerns,
we welcome your input so that we may incorporate them in our roadmap. Thank
you!
Regards,
Humair Khan
3 years, 1 month
Fwd: SREcon22 Americas Call for Participation Now Available
by Karsten Wade
Let's coordinate some talks, and see if we can do so with some
organizational diversity too, i.e., two speakers for each talk from
different organizations.
---------- Forwarded message ---------
From: Liz Markel <liz.markel(a)usenix.org>
Date: Wed, Oct 20, 2021 at 10:00 AM
Subject: SREcon22 Americas Call for Participation Now Available
To: Veronica Cooley-Perry <vcooley(a)redhat.com>
Submissions are due November 17.
[image: USENIX SREcon22 Americas]
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct0_...>
Dear Veronica:
SREcon22 Americas is scheduled to take place on March 14–16, 2022, in San
Francisco, CA, USA. *The Call for Participation
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct1_...>
is now open!*
SREcon22 Americas
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct2_...>
is the first of three global events in 2022, when we will finally have the
chance to gather again in person in several regions worldwide. Our goal is
to use this opportunity to come together and reflect on how scalable and
reliable systems sustained our lives these past two years. Join us in
showcasing how scaling expertise has paid off for teleconferencing,
education, streaming entertainment, delivery services, telemedicine, and
other unexpected demands.
Talk topics of interest include, but are not limited to:
- Scaling with low or no physical presence
- Telemedicine implementation, especially regulatory compliance
- Remote education, especially around infrastructure
- How changes in spending affected your ability to build out and
maintain your systems
- Impact on supply-chain systems
View the Call for Participation
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct1_...>
Submit a proposal for 15-minute talks, 30-minute talks, or panels by*
Wednesday, November 17.*
Please join us in creating an excellent program for SREcon22 Americas! We
welcome and encourage participation from all individuals in any country,
including people who are underrepresented in, or excluded from, technology,
including but not limited to: people of all colors, women, LGBTQ people,
people with disabilities, neurodiverse participants, students, veterans,
and others with unique characteristics. Similarly, we welcome participants
from diverse professional roles and a wide variety of backgrounds: if you
are a technologist who faces unique challenges and shares our areas of
interest, we encourage you to be a part of SREcon22 Americas.
In addition to making your own submission for this CFP, please pass along
this opportunity to colleagues who have interesting experiences and
valuable knowledge to share, and encourage them to submit a proposal! The
SREcon community has a strong commitment to inclusion of diverse ideas, and
is built on a foundation of respectful collaboration amongst all
participants through critical thought, deep technical insights, continuous
improvement, and innovation.
The program co-chairs—Mohit Suley (Microsoft) and Heidi Waterhouse
(LaunchDarkly)—look forward to receiving your proposals!
[image: Liz Markel headshot]
Cheers,
*Liz Markel*
Community Engagement Manager
USENIX Association
*Follow the @SREcon
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct3_...>
Twitter feed and USENIX's LinkedIn
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct4_...>
and Facebook
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct5_...>
pages to stay up to date on what's happening in the SREcon community.*
About this mailing list:
USENIX
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct6_...>
never shares, sells, rents, or exchanges email addresses of its members,
conference attendees, and other constituents. Review our privacy policy
<https://s.usenix.org/acton/ct/2452/s-03de-2110/Bct/l-1998/l-1998:cd1/ct7_...>
.
We would like to continue sending you occasional email announcements like
this one. However, if you no longer want to receive emails from USENIX,
please click here
<http://s.usenix.org/acton/rif/2452/s-03de-2110/-/l-1998:cd1/l-1998/zout?s...>
to opt out.
If you have any questions about the mailing list, please email
info(a)usenix.org <info(a)usenix.org?subj=mailing%20list%20question>. We may
also be reached via postal mail:
USENIX Association
2443 Fillmore St, #380-25600, San Francisco, CA 94115-1814, USA
--
Veronica Cooley-Perry, PMP
She, Her, Hers
Associate Manager, Global Event Strategy
Red Hat <https://www.redhat.com/>
100 E. Davie Street
Raleigh, NC 27601
vcooley(a)redhat.com
M:+1 7742581064
<https://red.ht/sig>
--
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
3 years, 1 month
Bringing SRE training into the Operate First community
by Stephanie Watson
Hi, everyone!
I'm working with some groups who are developing some self-paced training
experiences for site reliability engineers. That training will live within
the Operate First community space and will be open to community
contributions over time.
We're excited about bringing this feature to the community!
What kind of SRE topics would you like to see covered in training here in
the community space?
-Stephanie
--
Stephanie Watson, RHCE
she/her/hers | Program Manager, PnT Associate Experience
swatson(a)redhat.com
3 years, 1 month
