Juraci Paixão Kröhling

Either @bogdandrutu or @jpkrohling should work on this.

Either @bogdandrutu or @jpkrohling should work on this.

Either @bogdandrutu or @jpkrohling should work on this, perhaps with guidance from @lizthegrey, who did this last year.

Either @bogdandrutu or @jpkrohling should work on this, perhaps with guidance from @lizthegrey, who did this last year.

Use go workspaces to simplify dependency versioning

8

During the SIG meeting on August 10, we agreed that we'd do a proof-of-concept of Go Workspaces to simplify the management of versions (especially replaces statements) in the Go modules...

Use go workspaces to simplify intermodule deps

6

I was able to positively confirm that all modules had some effect when added to the go.work. For instance: ``` $ make install-tools cd ./internal/tools && go install github.com/client9/misspell/cmd/misspell cd...

Split components into their own modules

2

Depends on #5991. On August 10, during the SIG meeting, we agreed on splitting components into modules, such as the OTLP Exporter and Receiver. This should be done after the...

Remove configuration for otelcorecol

2

Verify that the default config file matches the one we use for otelcorecol. If so, remove the config from the repository to rely on the default one. _Originally posted by...

[builder] Remove setting of the Go executable from Validate()

2

Context: https://github.com/open-telemetry/opentelemetry-collector/pull/6026/files#r963914627 The Validate function currently sets the path to the Go executable, when the function's name does not imply this behavior at all.