Igor Morozov

Is golang-migrate abandoned?..

Should be `cargo bench` included? Or only `cargo fmt`, `cargo clippy --all` and `cargo test --all`?

I'm looking at `test.sh`. There commands for testing opentelemetry, opentelemetry-contrib, opentelemetry-jaeger and opentelemetry-zipkin crates. Should other crates be added?

What do you think about [cargo-make](https://sagiegurari.github.io/cargo-make/)? Is it worth trying?

@diceride there are two types of exporters: push-based and pull-based. Push-based use a client to send data, and pull-based use a server to expose data. Prometheus normally is pull-based, thus...

@Flowneee spec explicitly [specifies](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md#prometheus-exporter) which port prometheus exporter should listen on. So opentelemetry-js creates a separate server for this. But the exporter itself is in the separate package.

+1 I think there should be a compatibility matrix or at least a list of unsupported features. Probably code coverage is also a useful metric for maturity

Is it possible to use some temporary workaround? For example witx? (especially after #2659 has been merged) I want to experiment with the implementation of the plugin system using wasm,...

Also, I get `does not validate as email` error when use gmail-style emails with plus sign (e.g. `[email protected]`)

Well, it should be breaking. However, using reflection to detect nil here looks a bit strange... It's like embedding workaround right into codebase instead of fixing)