From 7de1a8c4163dface5f7928c1465a18c2bb52e291 Mon Sep 17 00:00:00 2001
From: Yuri Shkuro <github@ysh.us>
Date: Sat, 29 Apr 2023 19:49:23 -0400
Subject: [PATCH] Propose Jaeger project for LFX Mentorship '23 Term 02 June -
 August

Signed-off-by: Yuri Shkuro <github@ysh.us>
---
 .../2023/02-Jun-Aug/project_ideas.md             | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/programs/lfx-mentorship/2023/02-Jun-Aug/project_ideas.md b/programs/lfx-mentorship/2023/02-Jun-Aug/project_ideas.md
index 5e00018e..6cafe4b5 100644
--- a/programs/lfx-mentorship/2023/02-Jun-Aug/project_ideas.md
+++ b/programs/lfx-mentorship/2023/02-Jun-Aug/project_ideas.md
@@ -17,4 +17,20 @@
 
 ## Proposed Project ideas
 
+### Jaeger
+
+#### Upgrade Jaeger's internal telemtery to OpenTelemetry
+
+- Description: historically, the Jaeger backend used the OpenTracing API, with Jaeger's own Go SDK `jaeger-client-go`, for instrumenting its own internals for distributed tracing. Since Jaeger's SDKs have been deprecated, we want to upgrade the Jaeger backend to use the OpenTelemetry tracing API and SDK directly.
+- Expected Outcome:
+  - Replace the use of OpenTracing API with OpenTelemetry
+  - Remove `jaeger-client-go` and `jaeger-lib` as dependencies
+  - Remove `opentracing-go` and `opentracing-contrib/*` as dependencies
+  - Switch to standard instrumentation libraries where available (e.g. for HTTP, gRPC)
+  - Rethink/rework `crossdock` integration tests to test end-to-end flow with OpenTelemetry data
+  - Publish a blog post on medium.com/jaegertracing documenting the experience
+- Recommended Skills: Go
+- Mentor(s): Yuri Shkuro (@yurishkuro, github@ysh.us)
+- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/3381
+
 ---