open-telemetry / community

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

SIG documents should be owned by an OpenTelemetry account #1147

Open dyladan opened 2 years ago

dyladan commented 2 years ago

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.

dyladan commented 2 years ago

The following documents, unless checked off, are owned by contributors and not owned by the opentelemetry account:

If you own a SIG document, please transfer ownership to cncf-opentelemetry-governance@lists.cncf.io 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

  1. Click the share button
  2. Invite cncf-opentelemetry-governance at lists.cncf.io to be an editor
  3. Click the share button again
  4. Click on the arrow next to the governance committee email and select "Transfer Ownership"
  5. Click "Send Invitation"

Unanswered questions

tigrannajaryan commented 2 years ago

Unfortunately I get this: image

The solution is probably to copy it to cncf-opentelemetry-governance@lists.cncf.io (can be done by someone who is able to login using that account).

dyladan commented 2 years ago

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

dyladan commented 2 years ago

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

tigrannajaryan commented 2 years ago

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.

tigrannajaryan commented 2 years ago

@dyladan I have a similar problem with these docs. Can you please make copies of these 2 too?

dyladan commented 2 years ago

@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

dyladan commented 2 years ago

@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

trask commented 2 years ago

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.

SergeyKanzhelev commented 2 years ago

I sent transfer request for 4 documents I owned. lmk if I missed anything

sharrmander commented 2 years ago

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.

dyladan commented 2 years ago

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.

nachoBonafonte commented 1 year ago

I sent an ownership transfer for the Swift SIG meeting notes: https://docs.google.com/document/d/1LugL8r4bAkbTxZ1Gq_6j_8SDv1LuZaNeUdR-QLN4d48/edit#

bobstrecansky commented 1 year ago

Completely missed this notification, my apologies. Sent an ownership transfer request for the PHP documentation.

dyladan commented 9 months ago

Mainframe document ownership transferred

pjanotti commented 9 months ago

@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

trask commented 9 months ago

@pjanotti here's a new copy under the GC account: https://docs.google.com/document/d/1dYdwRQVE3zu0vlp_lqGctNm0dCQUkDo2LfScUJzpuT8/edit?usp=sharing

pjanotti commented 9 months ago

Thanks @trask

@dyladan you can mark .NET: Automatic Instrumentation Doc owned by @pjanotti as done.

mtwo commented 8 months ago

I've transferred the comms SIG notes and checked off the box above

mtwo commented 8 months ago

Also completed for client instrumentation. Thanks for tracking these and making the process so easy @dyladan!

mtwo commented 7 months ago

Fixed for Ruby