Do not publish otelzerolog as it is not handling core functionality

[pellared]

This Issue originates from a SIG discussion around #5963 (comment) on 2024-08-01.

With otelzerolog bridge not being able transform fields into attribute nor handle context correlation (because of rs/zerolog#493), we do not see value in publishing (and even maintaining) otelzerolog.

Can we move this module to a separate repository until rs/zerolog#493 is solved?

CC @dmathieu @AkhigbeEromo

[dmathieu]

Seeing both those issues have been open for 2+ years, we can't expect a quick resolution.
So not having a zerolog bridge if we don't have those features makes sense.

I am a codeowner of that bridge because I helped @AkhigbeEromo set up the bridge. But I don't have any vested interest in that bridge, so I'm not particularly keen on owning that separate repository.
@AkhigbeEromo if you wish to take that, please feel free to do so.

[AkhigbeEromo]

I will like to take it

[pellared]

@AkhigbeEromo, I assigned it to you. Please create a PR that removes the otelzerolog and share with us where you are migrating it. After the migration you can add it to the OTel Registry. So far I created a PR to remove otelzerolog from OTel Registry: open-telemetry/opentelemetry.io#4932

[MrAlias]

@pellared is going to create a PR to just remove this. The clone of this can reference the history of the repository to make the copy.

[pellared]

@AkhigbeEromo I created #5996 as it is blocking the next release of OTel Go. Still, feel free to move the code to a fork and add it to the OTel Registry. Please make sure to keep the "license header" in the files to not violate the licensing.

[AkhigbeEromo]

Hello @pellared
How do I add the code to Otel registry

[pellared]

The reverse of open-telemetry/opentelemetry.io#4932

[AkhigbeEromo]

I have the code on a branch of my fork of the repo,
Just to clarify, when you say I should add the code to Otel registry
I should send in a PR doing the opposite of what you did to the Opentelemetry.io repo?

[pellared]

Calling it "fork" was not precise. I mean move this module to a separate repository e.g. https://github.com/AkhigbeEromo/otelzerolog.

After you move the code, (configure some build pipeline), and publish a release, you can add it to the registry by summitting a PR in https://github.com/open-telemetry/opentelemetry.io