There have been recent suggestions about moving the repo to a big/prominent repo, such as OpenTelemetry contrib. Some users perceive depending on a repo owned by a single person as a risk (https://github.com/Vunovati/pino-opentelemetry-transport/issues/158), so I should probably do something about this as I want to avoid the situation where there are multiple implementations of the Pino transport.
There have been recent suggestions about moving the repo to a big/prominent repo, such as OpenTelemetry contrib. Some users perceive depending on a repo owned by a single person as a risk (https://github.com/Vunovati/pino-opentelemetry-transport/issues/158), so I should probably do something about this as I want to avoid the situation where there are multiple implementations of the Pino transport.
pino-opentelemetry-transport was created to solve an issue in Pino (https://github.com/pinojs/pino/issues/1292) and with the intention of being included in the Pino org. I made sure that we are in line with @pinojs code conventions in the initial PR(https://github.com/Vunovati/pino-opentelemetry-transport/pull/1) that was reviewed by @pinojs maintainers.
Since pino-opentelemetry-transport is an implementation of a Pino transport interface it makes the most sense to group it with the other Pino transports and packages from its ecosystem.
If the transform comes from the same org as Pino, it should address distrustful users' concerns in the future.
I will move the ownership of the repo to @pinojs and will continue maintaining it the same way.