This is a follow up to today's GC meeting: while talking about the proposal #3430 we got into a conversation about the fact, that we have not outlined how groups of people that share an interest in the wider ecosystem and community of OpenTelemetry can meet and organize. This is not about yet-another-process, this is about giving guidance how those groups can self-organize, that we are happy to have them and that we can provide a certain level of support to them.
The proposal is to create a document (e.g. in contributor guidelines) that outlines best practices(!) for such a group, i.e.:
- have a slack channel
#otel-<name> for your interest group (like #otel-industrial, #otel-collector-and-wasm, ...) and add the OpenTelemetry Admin account to it as channel manager.
- have them listed on the website or community README as inofficial, "not blessed but welcomed" OpenTelemetry User Groups for discovery
- suggest them to have their own github org like
otel-<name>
- suggest them to put their code if any under Apache-2.0 license to simplify potential later donations
- point them to the marketing and naming guidelines of OpenTelemetry and CNCF
- allow them to use OpenTelemetry Zoom Meetings if they want to meet on a regular basis
- recommend them to follow the CNCF Code Of Conduct (although this is mandatory for the channel+zoom)
- ...
I am happy to write down this guide, but wanted to collect feedback on this first. Again, this would not be a process or something we enforce, but a recommendation to communities that they can follow.
These communites can be the source of future SIGs or project proposals.
cc @open-telemetry/governance-committee
This is a follow up to today's GC meeting: while talking about the proposal #3430 we got into a conversation about the fact, that we have not outlined how groups of people that share an interest in the wider ecosystem and community of OpenTelemetry can meet and organize. This is not about yet-another-process, this is about giving guidance how those groups can self-organize, that we are happy to have them and that we can provide a certain level of support to them.
The proposal is to create a document (e.g. in contributor guidelines) that outlines best practices(!) for such a group, i.e.:
#otel-<name>for your interest group (like #otel-industrial, #otel-collector-and-wasm, ...) and add the OpenTelemetry Admin account to it as channel manager.otel-<name>I am happy to write down this guide, but wanted to collect feedback on this first. Again, this would not be a process or something we enforce, but a recommendation to communities that they can follow.
These communites can be the source of future SIGs or project proposals.
cc @open-telemetry/governance-committee