Rename "TracerSource" to "TracerProvider"

[toumorokoshi]

Updates

Here is the current living proposal:

• rename TracerSource to TraceProvier
• rename TraceOptions to TraceFlags

Original Post

From a naming standpoint, we currently deviate from the spec in two areas trace-related:

• our module name is "trace", the specification calls it tracing: https://github.com/open-telemetry/opentelemetry-specification
• we have a TracerSource, that is called TracerProvider: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/api-tracing.md#obtaining-a-tracer

I think it's important we ensure that naming is as consistent with the spec as possible, and best to do before we reach beta. Thoughts?

[lzchen]

I believe Java, JS and .NET are all named "trace", so there's also the factor of being consistent with the other languages. Also, if we rename "Trace" to "tracing" does that mean we should change the "non-speced" out classes in our code as well (e.g. TraceOptions)?

+1 for TracerProvider and MeterProvider

[toumorokoshi]

Ah interesting. Then ok, maybe it's ok to leave it as trace (seems like there'll be changes back to the spec instead there).

Regarding TraceOptions: looks like those are referred to as TraceFlags: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/api-tracing.md#spancontext. So probably another renaming opportunity there.