@@ -6,7 +6,7 @@ information on this and other language SIGs.
6
6
7
7
See the [ public meeting notes] ( https://docs.google.com/document/d/1CIMGoIOZ-c3-igzbd6_Pnxx1SjAkjwqoYSUWxPY8XIs/edit )
8
8
for a summary description of past meetings. To request edit access, join the
9
- meeting or get in touch on [ Gitter ] ( https://gitter.im/open-telemetry/opentelemetry-python ) .
9
+ meeting or get in touch on [ Slack ] ( https://cloud-native.slack.com/archives/C01PD4HUVBL ) .
10
10
11
11
See to the [ community membership document] ( https://github.com/open-telemetry/community/blob/main/community-membership.md )
12
12
on how to become a [ ** Member** ] ( https://github.com/open-telemetry/community/blob/main/community-membership.md#member ) ,
@@ -20,7 +20,7 @@ Please take a look at this list first, your contributions may belong in one of t
20
20
21
21
1 . [ OpenTelemetry Contrib] ( https://github.com/open-telemetry/opentelemetry-python-contrib ) : Instrumentations for third-party
22
22
libraries and frameworks. There is an ongoing effort to migrate into the Opentelemetry Contrib repo some of the existing
23
- programmatic instrumentations that are now in the ` ext ` directory in the main OpenTelemetry repo. Please ask in the Gitter
23
+ programmatic instrumentations that are now in the ` ext ` directory in the main OpenTelemetry repo. Please ask in the Slack
24
24
channel (see below) for guidance if you want to contribute with these instrumentations.
25
25
26
26
# Find the right branch
@@ -30,12 +30,15 @@ The default branch for this repo is `main`. Changes that pertain to `metrics` go
30
30
## Find a Buddy and get Started Quickly!
31
31
32
32
If you are looking for someone to help you find a starting point and be a resource for your first contribution, join our
33
- Gitter and find a buddy!
33
+ Slack and find a buddy!
34
34
35
- 1 . Join [ Gitter.im ] ( https://gitter.im ) and join our [ chat room ] ( https://gitter.im/open-telemetry/opentelemetry-python ) .
35
+ 1 . Join [ Slack ] ( https://slack.cncf.io/ ) and join our [ channel ] ( https://cloud-native.slack.com/archives/C01PD4HUVBL ) .
36
36
2 . Post in the room with an introduction to yourself, what area you are interested in (check issues marked "Help Wanted"),
37
37
and say you are looking for a buddy. We will match you with someone who has experience in that area.
38
38
39
+ The Slack channel will be used for introductions and an entry point for external people to be triaged and redirected. For
40
+ discussions, please open up an issue or a Github [ Discussion] ( https://github.com/open-telemetry/opentelemetry-python/discussions ) .
41
+
39
42
Your OpenTelemetry buddy is your resource to talk to directly on all aspects of contributing to OpenTelemetry: providing
40
43
context, reviewing PRs, and helping those get merged. Buddies will not be available 24/7, but is committed to responding
41
44
during their normal contribution hours.
0 commit comments