Trask Stalnaker

Thanks, which specific opentelemetry dependency are you using that is getting flagged?

ah, if it's just an issue of 2.16 vs 2.17, can you open an issue over in https://github.com/open-telemetry/opentelemetry-java-instrumentation? that sounds like something we can probably address

> The issue is that if we approve this set of actions for your repo, then that would potentially approve any set of actions created for any repos under the...

hey @Brandon-Kimberly! in the [Java Instrumentation repository](https://github.com/open-telemetry/opentelemetry-java-instrumentation), we are currently using CircleCI's `xlarge` instances (8 cores, 16 GB). I tried super unsuccessfully a while back to fit into the CircleCI...

> we only needed your feedback I started converting Java Instrumentation repo to Github Actions. In Github Actions we need to parallelize across lots of jobs to get similar performance...

Hey @Brandon-Kimberly, can you add the Java Instrumentation repo to your table (not that it's green, but so we track it)? thx!

Does the attribution need to ship with the published artifact?

(uncontroversial) don't refer to generic users/contributors/etc using male pronouns, e.g. _user sets his own propagators_

don't use the terms whitelist and blacklist, instead use something more descriptive that doesn't rely on/imply white=good/allowed black=bad/denied, e.g. allowlist and denylist

> Tracing doesn't, but IIRC correctly there's a reason for that 🤔 that we've previously discussed. maybe to keep trace context propagation enabled even if no (local) exporting?