Cloud Native AI on Openshift blog article for Enable Architect
by Tom Coufal
Hello community,
I'm very excited to announce and share with you our 2 new articles
propagating Operate First and Cloud Native AI!
@Francesco Murdaca <fmurdaca(a)redhat.com>, @Václav (Vašek) Pavlín
<vasek(a)redhat.com> and I have recently authored 2 blog posts for the Enable
Architect blog by Red Hat. These posts are distilled from the experience
gained when preparing the Cloud Native AI workshop at DevConf.US 2021. It
is based on top of Operate First community cloud infrastructure, Open Data
Hub, project Meteor and much more.
https://www.redhat.com/architect/cloud-native-ai
https://www.redhat.com/architect/operate-first-open-data-hub
Many thanks to all of you who enabled us to work with the Operate First
platform and Open Data Hub. Thanks to you our workshops and blog posts are
cherries on top of the cake.
Thank you Francesco and Vasek, it's an honour!
Tom
2 years, 3 months
Workshop at SCaLE (Southern California Linux Expo)
by Karsten Wade
https://github.com/operate-first/community/issues/111
Summary if you haven't heard about this:
We have space to run a workshop / beta training / UX testing / cool demos /
etc. at SCaLE 19x in Pasadena, CA on either or both 03 & 04 March (Thu &
Fri).
This is a chance for us to start to reveal things we've been working on in
a friendly community environment where people are interested in new and
cool as much as polish and poise. SCaLE has a strong focus on accessibility
and inclusion, so it attracts a wide range of attendees and presentations
from across the Los Angeles area and beyond.
Currently, Red Hat and California are clearing people for attending events
of this size (under 5K) with vaccination+boosted requirements likely from
the event. (The details on their website are not updated to that, so I am
projecting my expectations of what will happen by March.)
https://github.com/operate-first/community/issues/111
I'm planning to attend and coordinate whatever we do; however many hands we
have there is who we have. If we're creative, can we:
* Run beta SRE training?
* Get people hands on experienced with GitOps?
* Show some cool demos? (Pre-recorded or live from remote or ...)
* Get people hands on with data science tools?
- Maybe a shared Open Data Hub workshop?
* What 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
2 years, 3 months
Governance for review
by Karsten Wade
Hi all,
This email contains a link to the proposed governance, steps for how to
comment, some further thoughts from me, and a proposed timeline for
ratifying this governance.
# Proposed governance
I have drafted a first governance for the Op1st community, ready for
reading and comments in this pull request:
https://github.com/operate-first/community/pull/107
You can make comments directly in the "Files changed" view in GitHub, line
by line. Every sentence within a paragraph has its own line, making it
easier to comment directly.
# How to comment
Instructions for this are in this comment in the pull request:
https://github.com/operate-first/community/pull/107#issuecomment-989183317
# Thoughts about the sections
One section I forgot to include in the pull request is also in there as a
comment from me, the one that initiates the Community SIG and the
Operations SIG as the two starting community groups.
One of the most important sections of governance for folks is the
membership section. I think we need to plan for a membership scenario going
forward based on where we are, and for us to essentially consider everyone
as a member to start.
So congrats, most of you are therefore members, and are encouraged to join
one or both SIGs, once things are finished and ratified.
# Timeline
My proposal is we decide on this governance by consensus, the model for
that is spelled out in the governance.
Because we have no other way to decide things at this point, we are going
to do the strange thing of adopting consensus as the model for this
decision. This means, if you disagree you can try to convince all of us to
use a different decision model. If you agree, you are free to +1 this
section of my email.
08 Dec -- Proposed governance raised
15 Dec -- First call for consensus is made, giving a chance for any
blockers (-1) to be raised
18 Dec -- If consensus is reached, governance is adopted. If there are
blockers, we continue to work through them.
21 Dec -- If we still have blockers and have not reached consensus, then we
hold over to January 2022.
11 Jan -- Second call for consensus is made, regardless of open blockers.
Call for consensus at this point includes if the community is going to
proceed regardless of blockers, or for us to identify which blockers we
want to resolve.
Weekly until closed -- We move through the blockers or decide every week by
consensus to no longer try to work through a blocker.
Ultimately, anyone making a block is saying they are willing to leave if
they don't feel their blocker is resolved. So each of these consensus
points is a chance for the community to say if we want to continue working
this out or if we have reached consensus without the blocking person
included.
--
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, 3 months
