search

open-telemetry / community

OpenTelemetry community content
https://opentelemetry.io
Apache License 2.0
752 stars 229 forks source link

Rename SIG "meetings" with "office hours" #1805

Open jpkrohling opened 10 months ago

jpkrohling commented 10 months ago

During KubeCon (Contribfest?), someone (@mtwo? @dyladan? sorry, a lot happened that week) mentioned that we might consider renaming our SIG "meetings" to "office hours", or a more welcoming term. The reasoning is that "meetings" may imply that this is a closed group of people, and we want to more explicitly encourage people to join those calls.

mtwo commented 10 months ago

Definitely wasn't me, I wanted to attend contribfest but my talk was at the same time :(

Regardless, I don't have a strong opinion. Each session usually has a mix of scheduled topics and Q&A time, perhaps we could call them "Meeting + Office Hours"?

cijothomas commented 9 months ago

Agree to call it something more easy to understand.. "Office Hours" sounds better than "SIG meeting"

In OTel Rust group, we received similar feedback, and we tweaked the wording to be more welcoming: "The meeting is open for all to join. We invite everyone to join our meeting, regardless of your experience level. Whether you're a seasoned OpenTelemetry developer, just starting your journey, or simply curious about the work we do, you're more than welcome to participate!" https://github.com/open-telemetry/opentelemetry-rust#contributing

arminru commented 9 months ago

How about SIG/WG/... "public meeting"?

"Office hours" sounds to me as if there was no agenda with items to discuss together, but interested folks show up and ask questions to the maintainers waiting there.

carlosalberto commented 9 months ago

+1 for "Public meeting".

jpkrohling commented 8 months ago

How do we proceed from here? Should I just go ahead and start renaming the docs and the community readme file?

tedsuo commented 6 months ago

If we're just changing "meeting" to "public meeting," I would say yes just go ahead and rename the references in the community repo, then make a request in the maintainers meeting and maintainers slack channel for repo maintainers to update their readme's.