Joshua MacDonald

The technical committee discussed the risks and benefits of adopting self-hosted runners. Here are some of the points discussed: - If possible, benchmarking using CPU performance counters can overcome the...

I support!

It sounds like the EasyCLA check is not actually running. I wonder if there's a way to create the branches manually and then use PRs to review the deprecation changes...

I do not support non-numeric gauge points. There is an existing convention for "info" metrics from OpenMetrics which are 1-valued, where you may put all sorts of values as attributes.

I would prefer to not burden SDKs with UTF-8 correctness. See the comment here: https://github.com/open-telemetry/opentelemetry-specification/issues/3421

> truncation can create invalid utf8 in some languages Byte-level truncation can create invalid utf8, period -- it's just that (we've noticed) protobuf libraries are not consistent, so this is...

@jsuereth see https://github.com/open-telemetry/opentelemetry-specification/issues/3421

Could we agree on a transformation to turn invalid UTF-8 into valid UTF-8? Should we reject those strings?

I believe there's a question of what we actually want to have, here. The term `character` is reasonably well defined in relation to utf-8, [but it's not the same as...

> We now have open issues in the spec to handle this in the API/SDK. Please link any spec issues, for the readers following this issue?