From f7de75724b32f840815e53093ef41445df74a0eb Mon Sep 17 00:00:00 2001 From: anarwal1 Date: Thu, 20 Aug 2026 17:59:27 -0400 Subject: [PATCH 1/7] adding script for otel intro --- scripts/script1.md | 134 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 scripts/script1.md diff --git a/scripts/script1.md b/scripts/script1.md new file mode 100644 index 0000000..e4f1f8d --- /dev/null +++ b/scripts/script1.md @@ -0,0 +1,134 @@ +# OpenTelemetry New Contributor Walkthrough — Draft Video Script + +**Target length:** 4–6 minutes +**Audience:** Someone interested in contributing to OpenTelemetry but unsure where to begin. + +## 1. Welcome — Starting at OpenTelemetry.io (~30 sec) + +**On screen:** Open `opentelemetry.io`. + +**Narration:** + +Welcome! If you're interested in contributing to OpenTelemetry but aren't sure where to start, this video will walk you through the main community resources. + +We'll start from the OpenTelemetry website and find our way to the contributor documentation, GitHub community, Special Interest Groups, CNCF Slack, and finally some issues you can use to make your first contribution. + +You don't need to already be an OpenTelemetry expert to get involved. Plenty of contributors start with documentation fixes or issue triage. + +--- + +## 2. Finding the Contribution Guide (~45 sec) + +**On screen:** Navigate from `opentelemetry.io` to the community/contribution resources and open the contributor documentation. + +**Narration:** + +From the OpenTelemetry website, navigate to the community and contribution resources. That takes you to the OpenTelemetry community repository on GitHub. + +Start with the New Contributor Guide. + +Before contributing code, you'll want to review a few prerequisites, including creating a GitHub account, signing the Contributor License Agreement, and reading the Code of Conduct. + +The contributor guide also explains how the community works and where to find more detailed contribution instructions. + +--- + +## 3. Finding the OpenTelemetry GitHub Community (~45 sec) + +**On screen:** Open the `open-telemetry/community` repository. Scroll through the README and highlight **Get Involved**. + +**Narration:** + +This is the OpenTelemetry community repository. It's where the project keeps its governance docs, its SIG list, and its meeting calendar. + +The "Get Involved" section lists three next steps: + +First, read the contributor guide. + +Second, join Slack and community meetings. + +And third, if you already know which part of OpenTelemetry interests you, find its Special Interest Group, or SIG. + +Almost everything in the project is organized by SIG, so that's next. + +--- + +## 4. What Is a SIG? (~60 sec) + +**On screen:** Navigate to the OpenTelemetry SIG list in `community/sigs.md`. Scroll through several SIGs and show the columns for meetings, Slack channels, and repositories. + +**Narration:** + +SIG stands for **Special Interest Group**. + +OpenTelemetry is a large project, so the community is organized into SIGs focused on different parts of the project. + +There are SIGs for specific implementations and languages, as well as cross-cutting areas such as security, documentation, contributor experience, and developer experience. + +For each group, the SIG list gives you the meeting schedule, meeting notes, Slack channel, repositories, and who to contact. + +SIG meetings are open to the community, so sitting in on a meeting or its Slack channel lets you see what a group is working on before you pick something up. + +Choose the SIG that most closely matches the area where you'd like to contribute. + +--- + +## 5. Joining Slack (~60 sec) + +**On screen:** Return to the community README → Slack section. Show the CNCF Slack signup link and the listed OpenTelemetry channels. + +**Narration:** + +OpenTelemetry doesn't run its own Slack workspace. It uses the **CNCF** Slack — the Cloud Native Computing Foundation's shared workspace. + +If you aren't already a member, follow the signup link from the OpenTelemetry community page to create your CNCF Slack account. + +Once you're there, start in `#opentelemetry-new-contributors`. It's the channel set up specifically for people making their first contribution. There's also a general `#opentelemetry` channel. + +Most SIGs have their own Slack channel as well. You can find the appropriate channel directly from the SIG list we looked at earlier. + +These channels are where you can ask questions and reach the people maintaining the area you're interested in. + +--- + +## 6. Finding a Good First Issue (~60 sec) + +**On screen:** Open an OpenTelemetry GitHub repository. Navigate to **Contribute** and/or **Issues**. Show issues carrying the `good first issue` label. + +**Narration:** + +Once you've picked an area, open its repository and go to the **Contribute** tab or the issue list. + +Many repositories tag beginner-friendly work with the `good first issue` label, and GitHub's Contribute tab collects those in one place. Not every repository uses it, so if the tab is empty, check the issue list directly. + +Before starting work, read the repository's `CONTRIBUTING.md` because contribution processes can differ between repositories. + +Also read the issue discussion and check whether someone is already working on it. + +If you're unsure whether an issue is a good fit, reach out through the relevant SIG or Slack channel before you start. + +--- + +## 7. Wrap-Up (~30 sec) + +**On screen:** Briefly revisit the community repository or show a simple path: + +`opentelemetry.io → Contributor Guide → SIG → Slack → GitHub Issue` + +**Narration:** + +That's the basic path for getting started: + +Start at OpenTelemetry.io. + +Read the contributor guide. + +Find a SIG related to your interests. + +Join the CNCF Slack community and the relevant SIG channel. + +Then find a good first issue and connect with the community before you start working on it. + +And remember: contributing doesn't only mean writing code. Documentation, issue triage, community work, reviews, and other contributions all help OpenTelemetry grow. + +Welcome to the OpenTelemetry community. We hope to see you contributing. From 42edd348026ace3172f8d52ac531bf7264e07b69 Mon Sep 17 00:00:00 2001 From: anarwal Date: Thu, 20 Aug 2026 18:07:58 -0400 Subject: [PATCH 2/7] update file name --- scripts/{script1.md => 01-intro.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename scripts/{script1.md => 01-intro.md} (100%) diff --git a/scripts/script1.md b/scripts/01-intro.md similarity index 100% rename from scripts/script1.md rename to scripts/01-intro.md From da6704c57caa1bdb29e00d9312f7da1bfaca4e3b Mon Sep 17 00:00:00 2001 From: anarwal Date: Fri, 21 Aug 2026 13:53:32 -0400 Subject: [PATCH 3/7] update as per feedback --- scripts/01-intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/01-intro.md b/scripts/01-intro.md index e4f1f8d..c93e64d 100644 --- a/scripts/01-intro.md +++ b/scripts/01-intro.md @@ -67,7 +67,7 @@ There are SIGs for specific implementations and languages, as well as cross-cutt For each group, the SIG list gives you the meeting schedule, meeting notes, Slack channel, repositories, and who to contact. -SIG meetings are open to the community, so sitting in on a meeting or its Slack channel lets you see what a group is working on before you pick something up. +SIG meetings are open to anyone, so sitting in on a meeting or its Slack channel lets you see what a group is working on before you pick something up. Choose the SIG that most closely matches the area where you'd like to contribute. From a56b06477be8ebe0dd1045dd27d2df3b1ba2b399 Mon Sep 17 00:00:00 2001 From: Abhimanyu Date: Fri, 21 Aug 2026 15:45:58 -0400 Subject: [PATCH 4/7] Update scripts/01-intro.md Co-authored-by: Marylia Gutierrez --- scripts/01-intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/01-intro.md b/scripts/01-intro.md index c93e64d..559f6a5 100644 --- a/scripts/01-intro.md +++ b/scripts/01-intro.md @@ -39,7 +39,7 @@ The contributor guide also explains how the community works and where to find mo **Narration:** -This is the OpenTelemetry community repository. It's where the project keeps its governance docs, its SIG list, and its meeting calendar. +This is the OpenTelemetry community repository. It's where the project keeps its governance docs, its Special Interest Groups list, and its meeting calendar. The "Get Involved" section lists three next steps: From f174fe3bea71f8bd97117f12ae9e3157d8732f82 Mon Sep 17 00:00:00 2001 From: Abhimanyu Date: Tue, 25 Aug 2026 10:48:58 -0400 Subject: [PATCH 5/7] Update scripts/01-intro.md Co-authored-by: Kayla Reopelle <87386821+kaylareopelle@users.noreply.github.com> --- scripts/01-intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/01-intro.md b/scripts/01-intro.md index 559f6a5..32baad3 100644 --- a/scripts/01-intro.md +++ b/scripts/01-intro.md @@ -11,7 +11,7 @@ Welcome! If you're interested in contributing to OpenTelemetry but aren't sure where to start, this video will walk you through the main community resources. -We'll start from the OpenTelemetry website and find our way to the contributor documentation, GitHub community, Special Interest Groups, CNCF Slack, and finally some issues you can use to make your first contribution. +We'll start from the OpenTelemetry website and find our way to the contributor documentation, GitHub community, Special Interest Groups, CNCF Slack, and finally how to find issues you can use to make your first contribution. You don't need to already be an OpenTelemetry expert to get involved. Plenty of contributors start with documentation fixes or issue triage. From f12ce455d168913c4895f243f59aa364a10ad471 Mon Sep 17 00:00:00 2001 From: Abhimanyu Date: Tue, 25 Aug 2026 10:49:47 -0400 Subject: [PATCH 6/7] Update scripts/01-intro.md Co-authored-by: Kayla Reopelle <87386821+kaylareopelle@users.noreply.github.com> --- scripts/01-intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/01-intro.md b/scripts/01-intro.md index 32baad3..5df6b55 100644 --- a/scripts/01-intro.md +++ b/scripts/01-intro.md @@ -129,6 +129,6 @@ Join the CNCF Slack community and the relevant SIG channel. Then find a good first issue and connect with the community before you start working on it. -And remember: contributing doesn't only mean writing code. Documentation, issue triage, community work, reviews, and other contributions all help OpenTelemetry grow. +And remember: contributing doesn't only mean writing code. Documentation, issue triage, community work, pull request reviews, and other contributions all help OpenTelemetry grow. Welcome to the OpenTelemetry community. We hope to see you contributing. From e3b0f8af96993076790c7f8327ba1278c8084430 Mon Sep 17 00:00:00 2001 From: anarwal Date: Thu, 27 Aug 2026 15:29:32 -0400 Subject: [PATCH 7/7] updating as per feedback --- scripts/01-intro.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/scripts/01-intro.md b/scripts/01-intro.md index 5df6b55..ef504ed 100644 --- a/scripts/01-intro.md +++ b/scripts/01-intro.md @@ -93,19 +93,23 @@ These channels are where you can ask questions and reach the people maintaining ## 6. Finding a Good First Issue (~60 sec) -**On screen:** Open an OpenTelemetry GitHub repository. Navigate to **Contribute** and/or **Issues**. Show issues carrying the `good first issue` label. +**On screen:** Open an OpenTelemetry Collector Contrib GitHub repository. Go to **Issues** and filter by the `good first issue` label. Then open the repository's `CONTRIBUTING.md`. **Narration:** -Once you've picked an area, open its repository and go to the **Contribute** tab or the issue list. +Once you've picked an area, open its repository and go to the **Issues** tab. -Many repositories tag beginner-friendly work with the `good first issue` label, and GitHub's Contribute tab collects those in one place. Not every repository uses it, so if the tab is empty, check the issue list directly. +Many repositories tag beginner-friendly work with the `good first issue` label. Filter the issue list by that label to see what's open. -Before starting work, read the repository's `CONTRIBUTING.md` because contribution processes can differ between repositories. +Not every repository uses the label, and the ones that do can run out of tagged issues. If the filtered list is empty, ask in the SIG's Slack channel — someone there will know what needs picking up. + +Most repositories also have a `CONTRIBUTING.md`. That's where the guidelines live: how to set up the project locally, how the review process works, and anything specific to that codebase. Read it before you start, since the process differs between repositories. Also read the issue discussion and check whether someone is already working on it. -If you're unsure whether an issue is a good fit, reach out through the relevant SIG or Slack channel before you start. +If it looks unclaimed, leave a comment saying you'd like to take it. That tells maintainers and other contributors the issue is being picked up, and it's the right place to ask a clarifying question — the answer stays attached to the issue for whoever reads it next. + +If you don't get a reply, or you're not sure the issue is a good fit for a first contribution, ask in the SIG's Slack channel. ---