Update End User Resources (#4286)

.htmltest.yml

@@ -35,6 +35,8 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
   - ^https://x.com
   # OTel Google calendar - curl returns 200, but the link checker gets a 401:
   - ^https://calendar.google.com/calendar/embed\?src=google.com_b79e3e90j7bbsa2n2p5an5lf60%40group.calendar.google.com
+  # YouTube playlists sometimes give a 404, although they give a 200 when accessed via browser:
+  - ^https://www.youtube.com/playlist\?list=
 
   # Ignore Docsy-generated GitHub links for now
   - ^https?://github\.com/.*?/.*?/(new|edit)/ # view-page, edit-source etc

content/en/community/end-user/_index.md

@@ -1,24 +1,33 @@
 ---
-title: End-user Resources
-linkTitle: End User
-description: Vendor-agnostic resources for users of OpenTelemetry
+title: End-user resources
+linkTitle: End user
+description: Vendor-agnostic resources for OpenTelemetry users
 ---
 
-The [OpenTelemetry End User Working Group][] has heard feedback from users who
-desire a vendor-agnostic space to discuss adopting OpenTelemetry, so we provide
-multiple ways for you to connect with other users of the project and share best
-practices:
-
-- [A synchronous monthly discussion group](discussion-group/)
-- [A private slack channel](slack-channel/)
-- [Talks about OTel in practice](otel-in-practice/)
-- [Direct interview/feedback sessions](interviews-feedback/)
-
-These forums will bring together operations and development engineers from
+Looking to connect with other OpenTelemetry end users in a vendor-agnostic
+space, or to learn more about OpenTelemetry? Perhaps you have some feedback
+about your implementation or adoption that you'd like to share with project
+contributors, or you want to help prioritize project issues. You've come to the
+right place!
+
+- To connect with other end users and learn about upcoming events:
+  - Join the [Slack channel](slack-channel/)
+  - Join the [APAC end user discussion group](discussion-group/)
+- To learn about OpenTelemetry, check out:
+  - [OTel in practice](otel-in-practice/)
+  - Curated content on the
+    [OpenTelemetry YouTube channel](https://www.youtube.com/@otel-official)
+- To provide feedback and help prioritize issues:
+  - Participate in a [direct interview/feedback session](interviews-feedback/)
+  - Take a [survey](/community/end-user/feedback-survey/)
+  - Join a panel discussion (more info coming soon!)
+  - Vote on issues (more info coming soon!)
+
+These forums aim to bring together operations and development engineers from
 different organizations to discuss challenges and solutions to achieving
-ubiquitous observability. Share successes and failures, discover best practices,
-and meet others who are also on a journey to implement observability powered by
-OpenTelemetry.
+ubiquitous observability. We encourage you to share your successes and failures,
+discover best practices, and meet others who are also on a journey to implement
+observability powered by OpenTelemetry.
 
 ### Topics
 
@@ -37,15 +46,13 @@ But here are some of the kinds of things we expect will be on the table:
 
 **Is this group only for OpenTelemetry end users?**
 
-No! Anyone is welcome to join and discuss their journey to observability. This
-group is hosted by the OpenTelemetry Community End-User Working Group, so we
-expect most participants will be from organizations that are evaluating or using
+Everybody is welcome to join and discuss their journey to observability. This
+group is hosted by the OpenTelemetry Community End-User SIG, so we expect most
+participants will be from organizations that are evaluating or using
 OpenTelemetry.
 
 **I have questions about this, who can I reach out to?**
 
-You can find members of the End User Working Group in
-[#otel-user-research](https://cloud-native.slack.com/archives/C01RT3MSWGZ).
-
-[opentelemetry end user working group]:
-  https://github.com/open-telemetry/community/tree/main/working-groups/end-user
+You can find members of the
+[OpenTelemetry End User SIG](https://github.com/open-telemetry/community/tree/main/working-groups/end-user)
+in [#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ).

content/en/community/end-user/discussion-group.md

@@ -5,6 +5,9 @@ description: Monthly OpenTelemetry usage discussions, all are welcome!
 weight: 20
 ---
 
+**As of April 2024, AMER and EMEA sessions are discontinued in favor of
+discussion panels with a more targeted focus.**
+
 Interested in learning how other end users are implementing OpenTelemetry in
 their organizations? Come talk shop with other OpenTelemetry end users! This is
 a vendor-neutral space to discuss best practices, ask questions, and meet other
@@ -16,7 +19,6 @@ and changes to the project.
 
 ## About
 
-- Sessions are available for all regions!
 - Search the blog for "End-User Discussions" to find summaries of past
   discussions.
 - A project maintainer and/or a Governance Committee member will be in
@@ -29,21 +31,11 @@ and changes to the project.
 Here are upcoming sessions, or you can view them on the
 [OpenTelemetry calendar](https://github.com/open-telemetry/community#calendar):
 
-- **EMEA (Europe, Middle East, and Africa)**: every third Tuesday of the month
-  at 11AM GMT ([Zoom link](https://us06web.zoom.us/j/85691064809?pwd=c0VCejh))
-  - February 20
-  - March 19
-  - April 16
 - **APAC (Asia Pacific)**: every third Wednesday of the month at 11AM India ST
   (GMT +5.5), [register](https://lu.ma/1w129wgu) to get the Zoom link
-  - February 21
-  - March 20
   - April 17
-- **AMER (Americas)**: every third Thursday of the month at 9AM PT (GMT -8),
-  ([Zoom link](https://us06web.zoom.us/j/87037874951?pwd=WGo3eUZpeWFZTlhJQXhJeXZhQmwvUT09))
-  - February 15
-  - March 21
-  - April 18
+  - May 15
+  - June 19
 
 Past topics/questions have included:
 

content/en/community/end-user/interviews-feedback.md

@@ -4,10 +4,10 @@ description: Help improve OpenTelemetry - share your feedback directly with us!
 weight: 10
 ---
 
-One of the core functions of the OpenTelemetry End User Working Group is to
-improve the project by gathering feedback from end users and sharing them with
-the appropriate SIGs to help drive prioritization of improvements and changes to
-the project.
+One of the core functions of the OpenTelemetry End User SIG is to improve the
+project by gathering feedback from end users and sharing them with the
+appropriate SIGs to help drive prioritization of improvements and changes to the
+project.
 
 Direct interview or feedback sessions between an organization and the
 OpenTelemetry Community is one such resource. In these hour-long sessions, we
@@ -24,8 +24,8 @@ We will then take the feedback you shared and turn them into actionable tasks
 for the relevant SIGs, as well as provide context and insight for you during the
 session as appropriate.
 
-We schedule these sessions once a month, usually during one of the end-user
-working group's meetings (alternating Thursdays at 10AM Pacific Time), but can
+We try to schedule these sessions once a month, usually during one of the
+end-user SIG's meetings (alternating Thursdays at 10AM Pacific Time), but can
 set up a different time if that does not work for you. The sessions are
 typically attended by a few project maintainers and/or Governance Committee
 members, as well as some curious general members of the Community.
@@ -40,13 +40,16 @@ Things to keep in mind:
   concerns.
 - These are open to the public, so other users may come and ask you questions.
 
-To schedule a session, reach out to us in
-[CNCF Community Slack](https://communityinviter.com/apps/cloud-native/cncf):
+You can view
+[past recordings](https://www.youtube.com/playlist?list=PLVYDBkQ1TdywIl9xKEo5_u7zlwY38dW43)
+on the OpenTelemetry YouTube channel.
+
+To schedule a session, reach out to us via
+[CNCF's Community Slack](https://communityinviter.com/apps/cloud-native/cncf):
 
 - In the
-  [#otel-user-research](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
+  [#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
   channel
 - Via direct message: ping
-  [Reese Lee](https://cloud-native.slack.com/team/U03UARAJ405),
-  [Adriana Villela](https://cloud-native.slack.com/team/U02EUCBFK8A), or
-  [Rynn Mancuso](https://cloud-native.slack.com/team/U03FU45JA1M)
+  [Reese Lee](https://cloud-native.slack.com/team/U03UARAJ405) or
+  [Adriana Villela](https://cloud-native.slack.com/team/U02EUCBFK8A)

content/en/community/end-user/otel-in-practice.md

@@ -1,9 +1,9 @@
 ---
-title: OpenTelemetry In Practice
+title: OTel In Practice
 linkTitle: OTel in Practice
 description: >-
-  _OpenTelemetry in Practice_ is a _series_ of talks initiated by some members
-  of the End User Working Group.
+  _OTel in Practice_ is a _series_ of talks initiated by some members of the End
+  User SIG.
 weight: 30
 ---
 
@@ -14,13 +14,16 @@ We’re aiming to:
 - Build stronger connections with developers focused on specific languages
 - Improve the experience of implementing OpenTelemetry in production
 
-Each OpenTelemetry in Practice session will include a half hour of lightning
-talks and a half hour of open conversation about the topic. We are looking for
-people to join the OpenTelemetry in Practice team and people to give talks at
-future events. So if you’re interested in shaping these conversations, reach out
-in the
-[#otel-user-research channel](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
-of the [CNCF Slack](https://slack.cncf.io).
+Each OTel in Practice session typically includes one or more talks by end users
+or project contributors, with space for discussion. We welcome speakers from all
+backgrounds! If you're interested in sharing what you've learned in a 15-minute
+lightning talk or a longer 30-minute session, reach out in the
+[#otel-sig-end-user channel](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
+on the [CNCF's Slack](https://slack.cncf.io).
+
+You can view
+[past sessions](https://www.youtube.com/playlist?list=PLVYDBkQ1TdyxKgdGE4ThYLkNRCuLLYy9x)
+on the OpenTelemetry YouTube channel.
 
 Join the
 [OpenTelemetry in Practice Meetup Group](https://www.meetup.com/opentelemetry-in-practice-meetup-group/)

content/en/community/end-user/slack-channel.md

@@ -2,19 +2,28 @@
 title: Slack Channel
 linkTitle: Slack
 description: >-
-  Join a private slack channel to discuss OpenTelemetry with other end users.
+  Join a Slack channel to discuss OpenTelemetry with other end users.
 weight: 40
 ---
 
-- Confirm your agreement with channel [Code of Conduct][] and reach out to Reese
-  Lee, Rynn Mancuso, or Adriana Villela on CNCF slack for an invite to
-  `#otel-endusers`.
+Previously, we had a private channel to provide a space for end users to discuss
+adoption and implementation issues while allowing them to maintain a layer of
+privacy and to meet compliance concerns. Now that the project and community have
+grown, and with the transition of the End User WG to End User SIG, we believe
+that this private channel is no longer needed.
+
+As of April 2024, we will begin shifting all of our communications to the
+[#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
+channel (previously named the #otel-user-research channel), and will be
+archiving the private channel by April 30, 2024.
+
+We encourage you to join us over at #otel-sig-end-user to learn about our new
+charter, what you can expect from us as an end user, and more. Note the
+following:
+
 - Troubleshooting or tactical SDK specific questions are still best directed to
   individual SIG channels or the
   [#opentelemetry](https://cloud-native.slack.com/archives/CJFCJHG4Q) channel.
 - Vendor specific questions are still best directed to vendor channels, or if it
-  doesn’t exist
+  doesn’t exist,
   [#otel-vendor](https://cloud-native.slack.com/archives/C031SAMGV2A)
-
-[code of conduct]:
-  https://github.com/open-telemetry/community/blob/main/working-groups/end-user/discussion-group-code-of-conduct.md

static/refcache.json

@@ -8883,6 +8883,10 @@
     "StatusCode": 200,
     "LastSeen": "2024-01-30T16:34:02.591185-05:00"
   },
+  "https://www.youtube.com/@otel-official": {
+    "StatusCode": 200,
+    "LastSeen": "2024-04-15T11:38:45.271323+02:00"
+  },
   "https://www.youtube.com/embed/coPrhP_7lVU": {
     "StatusCode": 200,
     "LastSeen": "2024-01-30T16:15:42.688406-05:00"