community
community copied to clipboard
open-telemetry
SIG documents should be owned by an OpenTelemetry account
Related #1146
All SIG meeting note documents should be owned by an OpenTelemetry or CNCF google account. This will prevent access issues like we have seen before in the related issue. This has also happened in the past when OTel members have changed employers.
There should also be a defined ownership/administrative permission structure in order to handle instances of abuse, spam, or other issues with the docs. For example, it would be desirable for maintainers to have sufficient permission to change a document to a read-only state or to roll back to a previous history version.
The following documents, unless checked off, are owned by contributors and not owned by the opentelemetry account:
- [x] Specification SIG doc owned by @carlosalberto
- [x] Log SIG doc owned by @tigrannajaryan
- [ ] Sampling SIG doc owned by @tedsuo
- [ ] Instrumentation SIG doc owned by @tedsuo
- [x] Maintainers meeting doc owned by @carlosalberto
- [ ] Collector Doc owned by @flands
- [ ] C/C++: SDK Doc owned by @reyang
- [x] .NET: Automatic Instrumentation Doc owned by @pjanotti
- [x] .NET: SDK Doc owned by @SergeyKanzhelev
- [ ] Erlang/Elixir: SDK Doc owned by UNKNOWN
- [x] GoLang: SDK Doc
- [x] Java Doc owned by @bhs
- [x] JavaScript: SDK Doc
- [ ] PHP: SDK Doc owned by @bobstrecansky
- [ ] Python: SDK Doc owned by [email protected]
- [x] Ruby: SDK Doc owned by @fbogsany
- [ ] Rust: SDK Doc owned by midori at lightstep dot com
- [x] Swift: SDK Doc owned by UNKNOWN
- [x] Communications (Website, etc.) Doc owned by @mtwo
- [x] End-User WG Doc owned by @sharrmander
- [x] eBPF Doc owned by @tigrannajaryan
- [x] Agent Management WG Doc owned by @tigrannajaryan
- [ ] Client Instrumentation Doc owned by @mtwo
- [ ] Kubernetes Operator Doc owned by UNKNOWN (unused doc?)
- [x] Community Demo Application Doc
- [x] GC document @SergeyKanzhelev
- [x] TC document @SergeyKanzhelev
- [x] .NET archived document @SergeyKanzhelev
- [x] archived java + instrumentation @trask
- [ ] Prometheus Workgroup @alolita
- [ ] FAAS WG @alolita
If you own a SIG document, please transfer ownership to [email protected] and make a comment here so that your transfer can be accepted by a governance member. Until your transfer is accepted YOU STILL OWN THE DOCUMENT. Once your transfer is accepted, the line item will be checked off.
Process to transfer ownership
- Click the share button
- Invite cncf-opentelemetry-governance at lists.cncf.io to be an editor
- Click the share button again
- Click on the arrow next to the governance committee email and select "Transfer Ownership"
- Click "Send Invitation"
Unanswered questions
- Who owns Erlang doc?
- Who controls [email protected]
- Why is midori at lightstep dot com not an otel member and who are they? They are not mentioned here so may miss this issue.
- Swift document is not public. Why is it not public and who owns it? Is it in use?
- Why is Sharr not an otel member? They are not mentioned here so may miss this issue.
- Kubernetes SIG doc is empty and has an unknown owner. How is the k8s SIG communicating?
Unfortunately I get this:
The solution is probably to copy it to [email protected] (can be done by someone who is able to login using that account).
I am able to log into that account. The meeting notes link will change though. I suspect this will happen with many documents owned by organization accounts and not personal accounts
Created a new log sig doc at https://docs.google.com/document/d/1P_wkLEomswd0M0eNNnxSOe6U-EOpCZaMIIxKuM4frw8
@tigrannajaryan can you confirm that it looks correct? I'll make a PR and will update the calendar when it gets merged
Created a new log sig doc at https://docs.google.com/document/d/1P_wkLEomswd0M0eNNnxSOe6U-EOpCZaMIIxKuM4frw8
@tigrannajaryan can you confirm that it looks correct? I'll make a PR and will update the calendar when it gets merged
@dyladan yes, looks good, thank you.
- [ ] eBPF Doc owned by @tigrannajaryan
- [ ] Agent Management WG Doc owned by @tigrannajaryan
@dyladan I have a similar problem with these docs. Can you please make copies of these 2 too?
- [ ] eBPF Doc owned by @tigrannajaryan
- [ ] Agent Management WG Doc owned by @tigrannajaryan
@dyladan I have a similar problem with these docs. Can you please make copies of these 2 too?
On it
eBPF: https://docs.google.com/document/d/13GK915hdDQ9sUYzUIWi4pOfJK68EE935ugutUgL3yOw Agent Management: https://docs.google.com/document/d/19WA5-ex8rNFIBIyVb5VqMXfWNmUQwppGhN8zBeNG0f4
@tigrannajaryan see above PRs. I have not yet updated the calendars because I think we should do that when the PR merges so everything is consistent
I just sent a transfer request for the Archived Java meeting notes doc, which I owned b/c we made a copy when rolling over due to size, in order to preserve the original doc links.
I sent transfer request for 4 documents I owned. lmk if I missed anything
I sent an ownership transfer request for the End User Workgroup Notes. Thanks!
I missed this issue; for unrelated reasons I recently copied the SIG notes to a new location and am waiting for my PR with the new updated link to get merged. RE: #1191
For reference the prior End User WG notes are here and the new document is here.
I sent an ownership transfer request for the End User Workgroup Notes. Thanks!
I missed this issue; for unrelated reasons I recently copied the SIG notes to a new location and am waiting for my PR with the new updated link to get merged. RE: #1191
For reference the prior End User WG notes are here and the new document is here.
Thanks Sharr. I'm sure you missed the issue because I didn't tag you as I didn't know your github username. Thanks for following up.
I sent an ownership transfer for the Swift SIG meeting notes: https://docs.google.com/document/d/1LugL8r4bAkbTxZ1Gq_6j_8SDv1LuZaNeUdR-QLN4d48/edit#
Completely missed this notification, my apologies. Sent an ownership transfer request for the PHP documentation.
@dyladan I completely missed the initial notification for this issue. I hitting the same issue reported by Tigran - I guess it needs the creation of a new document. Could you please take care of that?
This is for this doc: https://docs.google.com/document/d/1XedN2D8_PH4YLej-maT8sp4RKogfuhFpccRi3QpUcoI/edit?usp=sharing
@pjanotti here's a new copy under the GC account: https://docs.google.com/document/d/1dYdwRQVE3zu0vlp_lqGctNm0dCQUkDo2LfScUJzpuT8/edit?usp=sharing
Also completed for client instrumentation. Thanks for tracking these and making the process so easy @dyladan!