census err I mean telemetry (java) and zipkin

[Adrian Cole]

I noticed the opentelemetry java repo is pending a jaeger exporter.

For those who dont know opentelemetry is mostly copy pasting from census and with the disadvantage of losing history of what happened in census which is a partial view of what should have happened. while we have had less problems about census doing things wrong than OT, this combined project represents a mapping risk. even in census some mappings were done wrong and not fixed because bogdan didn't agree.

rather than repeat this problem of being on defensive I wonder if it makes sense to spike an opentelemetry zipkin exporter before someone else raises a bad one that results in mapping changes and dead issues to fix them.

anyone interested? I suspect this goes for all repos.

-A

[Brian Devins-Suresh]

I'm feeling in the same boat, it seems like engaging is the safest way to ensure things do go completely sideways. I'd volunteer but I think my time needs to be spent on wrapping up work-in-progress in zipkin first

--
You received this message because you are subscribed to the Google Groups "zipkin-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zipkin-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/zipkin-dev/CAHzwyDs9ipbiw-g%3DHU-y4yHYy5SzhXgZZTNEJ4DS7oWf4SApZg%40mail.gmail.com.

[Adrian Cole]

fyi it looks like the current approach is to port the OC one. While
that has problems, I'm getting that no-one has cycles so we can't
really complain too much. Anyway, good that they are going to include
zipkin in the original release
https://github.com/open-telemetry/opentelemetry-java/issues/534

> To view this discussion on the web visit https://groups.google.com/d/msgid/zipkin-dev/CAO3-Ny4zH%2BHLsNwZ8HbDJRXiuGyYN5DTkXKYduujsosy7t0bzg%40mail.gmail.com.