Nikita Salnikov-Tarnovski

> This is a periodic reminder that OTel is still in complete churn mode Otel aims to have a GA for Trace API by the end of September.

My current proposal as to how we can move forward with this issue is [documented here](https://docs.google.com/document/d/1YNRCg9fdjJgZRs56vvf7rfFPk06mhp781sWHYypOaAk/edit#heading=h.xdwfdouv37cn)

@carlosalberto can we now close this issue as we have accepted OTEP https://github.com/open-telemetry/oteps/blob/main/text/0155-external-modules.md?

> Should not be an issue from the billing standpoint, but let me double-check if there are any technical limitations on the GHA side. Any news on this, @idvoretskyi ?

Not any immediate problems, but I am thinking if it is a good idea to bring a massively parallel job to Java instrumentation repo.

@Brandon-Kimberly, can you open the similar "Proposal: Use GitHub Actions for CI/CD" issue in https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation repo? Or alternatively can I copy-paste the text of your issues and do it myself?...

> @Brandon-Kimberly, can you open the similar "Proposal: Use GitHub Actions for CI/CD" issue in https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation repo? Or alternatively can I copy-paste the text of your issues and do it...

@caniszczyk We don't include source code. We repackage compiled classfiles into our own jar file. Where should we put that attribution?

@open-telemetry/governance-committee Any advice?

> which entity/who is accepting the EULA and publishing to container registry? That's going to be the sticking point, as you can't actually bind the opentelemetry project to the EULA......