-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REQUEST: Repository maintenance on opentelemetry.io -- end user WG gh team #1249
Comments
I created @open-telemetry/end-user-wg and added @reese-lee and @sharrmander. @musingvirtual please open a request to join the organization as a member so we can add you to the team as well (see https://github.com/open-telemetry/community/blob/main/community-membership.md#member). Thank you! |
@open-telemetry/end-user-wg does this mean the content in https://github.com/open-telemetry/community/tree/main/working-groups/end-user will be moved to https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en/community/end-user? |
Hi Armin, please find my membership request here.
#1189
…On Mon, Oct 10, 2022, 7:33 AM Armin Ruech ***@***.***> wrote:
@open-telemetry/end-user-wg
<https://github.com/orgs/open-telemetry/teams/end-user-wg> does this mean
the content in
https://github.com/open-telemetry/community/tree/main/working-groups/end-user
will be moved to
https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en/community/end-user
?
—
Reply to this email directly, view it on GitHub
<#1249 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMWYDFL63GDDW6TXEEEDD3WCQSLDANCNFSM6AAAAAARBBCRSI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I have this same question. I think it is important to make the end-user assets easily discoverable for new folks, which is why I originally put them under the /community repo. In my mind, putting them under the website repo doesn't seem an intuitive location. |
As @austinlparker et al. have pointed out before, we're generally wanting to move all/most OTel-related pages to the website. There are exceptions, of course -- like API reference documentation. For the language SIG docs, we've been using this issue to track progress: I'll let @austinlparker, @cartermp and @svrnm comment further, though maybe this issue isn't the place to hold this discussion. |
Yeah, I think what we've learned in general that the website gets a ton of traffic and it's where people go first to find things. I'm not opposed to also having things in the community repo, but in its current form it's for a lot more than hosting end-user WG stuff. |
Here would be my suggestion for a rule of thumb (exceptions will apply): official documents (like the Mission,Vision,Values or charters), that are owned by the GC,TC should live in this repo and we pull them in via a submodule eventually, but everything that's end-user or contributor-facing should ideally live with the website (as @cartermp said, for reach & findability). But yeah, we should have that discussion somewhere else |
the initial purpose of this issue is accomplished. |
Affected Repository
https://github.com/open-telemetry/opentelemetry.io
Requested changes
Create a github team for the end-user-working group, initial members: @reese-lee , @musingvirtual, @sharrmander
Purpose
Similar to the language SIGs for /instrumentation/ we want to have the end-user WG have ownership for /community/end-user (get asked & give approval for changes within that directory)
Expected Duration
permanently
Repository Maintainers
The text was updated successfully, but these errors were encountered: