-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Rename "Working group" (WG) to SIG everywhere #2044
Comments
We also have some slack channels that are named "-wg": |
Note that this also means we need to rename
This needs to be done by an GitHub Org Admin, cc @open-telemetry/technical-committee @trask @austinlparker |
just went ahead and deleted this (see #2218) |
@open-telemetry/wg-prometheus is it ok for us to rename your team to something like also is it ok for us to rename your repo from https://github.com/open-telemetry/wg-prometheus to something like |
I would prefer that we archive the repository. We haven't used it in years, and it is probably misleading |
prometheus-interoperability works for me |
thanks! I've renamed and archived the repository and updated the team name to @open-telemetry/prometheus-interoperability I didn't find any uses of the old team name in code, but it did break past @mentions of the old team name, I don't think I realized that would happen (unlike repo renames where github handles the redirects), will be more clear beforehand on future team renames |
I'll open a Service Desk ticket to archive this channel. |
Done. |
Remaining
|
Thanks! Note, that if OpenTelemetry Admin is a channel manager we can also do it without a service ticket, although turnaround time was really quick so 🤷♂️ So all that is missing is removing the references in the document
and #2431 |
The distinction between working group and SIG has been confusing to everyone, and so the GC has decided to do away with the term "working group" (WG) and use only the term SIG.
The text was updated successfully, but these errors were encountered: