How about a Community Handbook? [RFC]
by Karsten Wade
While we're busy thinking about and working for what our users need, as an
open source project we have to keep an equal attention on the needs of
contributors. Ourselves!
Here's a great idea I learned about, which we started up a few months back:
https://github.com/operate-first/community-handbook
The idea is, *everything* a contributor needs to know should be in the
Operate First Community Handbook.
If a sought-after part is missing, then it is the responsibility of the
original seeker to bring back what they find out to put in the Community
Handbook, as an issue or draft write-up.
What do you think?
Will you participate as a contributor and user of the Community Handbook?
For this to work, we need all contributors to participate. It is an
anti-pattern to have a small set of people working on the Community
Handbook. For it to be effective, it needs to be the go-to location for all
answers, so that handing out a link to the Handbook is always the best
thing to do. (Called "link first culture" in some circles.)
Read on for more details.
Ideally, the Community Handbook is autopublished here:
https://www.operate-first.cloud/community-handbook
Then all of the existing guides in parts of the project, such as the
Hitchhiker's Guide, can be pulled into the Community Handbook
automatically. As we have SRE learner pathways, some of those can be tagged
as how-to tutorials auto-included in the Handbook, and so forth
In fact, we will want to automate a lot of this handbook. For example,
imagine a new SRE contributor who wants to find how something is done. The
section in the Community Handbook automatically pulls in the documentation
from the repo as well as the actual runbooks or other files. When those
files are updated in the course of doing work, the Community Handbook is
automatically updated with that information.
The Community Handbook is currently written using the same concept as the
rest of the website, to make it easy to collaborate. We can discuss other
tooling methods such as GitBook or JupyterBook, but we need to be aware of
keeping the barrier to writing and editing the Community Handbook to be as
low as possible.
Although a relatively new idea beyond certain projects, you can see a few
active examples here:
https://handbook.chaoss.community/community-handbook/
https://about.gitlab.com/handbook
If this whole thing intrigues you beyond Operate First, you are welcome to
join us in the IEEE SAOpen group where I'm working with some of the folx
behind those two handbooks for defining a toolkit and process anyone can
adopt:
https://opensource.ieee.org/community-advisory-group/documentation-curati...
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, 3 months
OpenTelemetry onboarding
by Karsten Wade
Hello all Op1st,
Let me open this thread by welcoming Sally O'Malley, who is interested in
bringing OpenTelemetry to the Operate First community cloud.
Welcome, Sally! Great to have you here. This forum/mailing list is the new
central communication hub for community discussions, as the open access and
archives counterpart to the discussions happening around artifacts in the
git repositories and in unstructured chat
Speaking of which, here is the issue I opened on the Community Board
<https://github.com/orgs/operate-first/projects/16> to help keep track of
all the steps and movement involved:
https://github.com/operate-first/community/issues/83
I haven't been involved in onboarding a project yet, so I'm excited to work
with Sally on my first one. Sally and I have mostly worked together around
DevConf.US, where Sally is event Co-Chair and a great leader to follow. I'm
confident inviting her to jump right in and start engaging with everyone,
and I'll follow around and keep notes.
For simplicity of keeping all aware of the conversation, let's use this
thread and start discussing what and how to bring OpenTelemetry
experimental features to Operate First users, and how to begin delivering
Op1st environment value back to OTel as an environment user/contributor.
I'll reply to this message to take a part of the thread into the "what does
this look like for everyone" discussion.
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, 3 months
Community Metrics
by Hema Veeradhi
Hi all,
Reaching out to the group to spark some discussions/ideas around outlining
metrics we would like to track for measuring the growth, size, health and
impact of the Operate First community. For example, some of the metrics
that can help measure the size and growth of the community would include
number of users, number of contributors, number of issues submitted over
time, number of PRs merged over time etc.
We have started listing out these potential metrics in this gdoc
<https://docs.google.com/document/d/12JjCKzYzRBihR1cn6L0htp1yHQqZzKDEiQZCO...>
(as
well as a markdown here
<https://github.com/operate-first/community/blob/main/metrics/README.md>)
and would love to have your feedback/suggestions around it.
+Shrey Anand <shanand(a)redhat.com> and I have also created an
initial notebook
<https://github.com/operate-first/community/blob/main/metrics/community_me...>
that explores some of the operate first GitHub community metrics that are
being collected and stored by Augur <https://github.com/chaoss/augur>,
which we were able to set up with +Cali Dolfi <cdolfi(a)redhat.com>'s help.
Augur is a software suite for collecting and measuring structured data
about free and open-source software communities. It is developed and
maintained by the CHAOSS community <https://chaoss.community/>. The notebook
<https://github.com/operate-first/community/blob/main/metrics/community_me...>
visualizes some of these metrics and as a next step we would like to
include more metrics and visualize them in interactive dashboards using
some of the existing operate first tooling such as Superset
<https://www.operate-first.cloud/users/support/docs/trino_superset_user_gu...>,
and have them be publicly available for others to view.
It would be great to hear from others what they think are useful community
metrics and if there's interest we can also set up some time for a working
group to brainstorm ideas and have discussions around how we would like to
gauge the Operate First community. You can also leave your
suggestions/comments to this issue
<https://github.com/operate-first/community/issues/22> and please feel free
to add anyone else who might be interested to this thread!
--
Thanks and Regards,
Hema Veeradhi
She/Her
Software Engineer | AI COE - CTO OFFICE
Red Hat | Boston <https://www.redhat.com/>
hveeradh(a)redhat.com
<https://www.redhat.com/>
3 years, 3 months
Fwd: 🍂 Get Ready for Hacktoberfest 2021 (#8)! 🍂
by Marcel Hild
We should take this as a marketing opportunity. Let's label enough issues
as `hacktoberfest`
Anybody willing to sift through the current ones or create new exciting
ones?
---------- Forwarded message ---------
From: Team DigitalOcean <hacktoberfest(a)news.digitalocean.com>
Date: Thu, Sep 9, 2021 at 4:34 PM
Subject: 🍂 Get Ready for Hacktoberfest 2021 (#8)! 🍂
To: <mhild(a)redhat.com>
Hacktoberfest is coming! (#8, it’s great!)
[image: Hacktoberfest hero image]
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjN4CWv5k1oyf4Js_n_...>
[ Hacktoberfest hero image ] [[https://hacktoberfest.digitalocean.com/]]
Hey there,
Get ready because Hacktoberfest
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjN4CWv5k1oyf4Js_n_...>is
coming! (#8, it’s great!)
In the 8th year of Hacktoberfest, we’re more committed than ever to
celebrating the open-source community and all that it does. Thanks to your
feedback, we’re excited to be adding new features to this year’s
Hacktoberfest to show our appreciation for open-source maintainers.
Additionally, we’ve provided even more ways the community can get involved,
ranging from submitting quality pull requests in Gitlab to project
donations. Read on for more details about this year’s Hacktoberfest!
*What’s new for 2021?*
- You can now have PRs submitted via Gitlab count towards your
Hacktoberfest goal!
- We’re encouraging participants to show appreciation to their favorite
projects by donating directly to their repos.
*What’s staying the same?*
- We’re keeping all of the maintainer-friendly opt-in and pull request
review changes that were put in place last year. Check out all of the rules
here
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjK6mk41Gio4LAjdy74...>
.
- When it comes to events, have it your way! From office hours to Twitch
streams, we’re counting all Hacktoberfest-related virtual gatherings as an
official event.
- Want to give back to open source and the environment? Plant a tree
instead of receiving a tee.
There’s plenty more in store, so make sure to check out the Hacktoberfest
website
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjN4CWv5k1oyf4Js_n_...>
for all the ways you can get involved this year. See you in Hacktober!
Hacktoberfest, here we come!
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjN4CWv5k1oyf4Js_n_...>
Hacktoberfest, here we come! [[https://hacktoberfest.digitalocean.com/]]
[image: Footer Banner]
[ Hacktoberfest footer ]
[image: Twitter]
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjAA1DNfYSkr3KzD7Yq...>
[image: Facebook]
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjJSOosb3ZhwwRGj3Q2...>
[image: YouTube]
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjHLEVE-Iy5TgYA3SqV...>
[image: Instagram]
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjOJ6s516RJf_KX5Wnb...>
[image: Linkedin]
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjB5L9qc5UNb0DcpjB6...>
Give $100, get $25. Refer a friend.
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjL78k_se14jVdYuLXh...>
*Trouble seeing this email? View it as a web page.
<https://waves.digitalocean.com/MTEzLURUTi0yNjYAAAF_ae9pjIlaA_mqtFmrlgm-dw...>*
Copyright DigitalOcean. All right reserved.
Floor 10, 101 Avenue of the Americas, New York, NY 10013
[image: DigitalOcean logo (footer section)]
[ DigitalOcean logo (footer section) ]
This email was sent to mhild(a)redhat.com. You can update your email
subscription preferences
<https://waves.digitalocean.com/u/MTEzLURUTi0yNjYAAAF_ae9pjA1PwwVsMi225uX4...>
at any time.
3 years, 3 months