Skip to content

Commit ae4b8a7

Browse files
MrAliassvrnmpellared
authored
Apply suggestions from code review
Co-authored-by: Severin Neumann <[email protected]> Co-authored-by: Robert Pająk <[email protected]>
1 parent 820ca20 commit ae4b8a7

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

content/en/blog/2025/go-2025-goals.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ sig: SIG Go
99
cSpell:ignore: Yahn dashpole pellared otelhttp dmathieu otelhttp codeboten otellogr otellogrus otelslog otelzap otelzerolog
1010
---
1111

12-
As we kick off 2025, the OpenTelemetry Go team has come together to set a
12+
As we kick off 2025, the [OpenTelemetry Go](https://github.com/open-telemetry/opentelemetry-go) team has come together to set a
1313
roadmap for the year. Our focus is on driving the OpenTelemetry Go project
1414
forward while strengthening its integration with the broader OpenTelemetry
1515
ecosystem. Here's an overview of our goals, their expected timelines, and the
@@ -81,7 +81,7 @@ many bridges to popular logging packages:
8181

8282
The Go SIG plans to continue its effort in developing the upstream
8383
specification. Work to stabilize the OpenTelemetry Go implementation depends on
84-
this upstream development, including the development of the event signal.
84+
this upstream development, including the addition of Events.
8585

8686
### `otelhttp` Stabilization
8787

@@ -127,3 +127,5 @@ fruition!
127127
We want to hear from you! Let us know what is missing or what you would like to
128128
see prioritized by commenting on
129129
[our tracking GitHub issue](https://github.com/open-telemetry/opentelemetry-go/issues/6175).
130+
131+
If you'd like to participate in any of our efforts and become a contributor to the OpenTelemetry Go SIG, join our weekly SIG meetings on Thursday alternating between 09:00 PT and 10:00 PT and our channel [#otel-go](https://cloud-native.slack.com/archives/C01NPAXACKT) on [CNCF Slack](https://slack.cncf.io).

0 commit comments

Comments
 (0)