sebright2

See https://github.com/census-instrumentation/opencensus-java/pull/1141#issuecomment-388479392. When ~~google-java-format~~ google-java-format-gradle-plugin fails, it lists the files with incorrect formatting, but it doesn't describe the error. We could provide more information about the failure by running "./gradlew...

We should provide classes that can be used to test code that is instrumented with opencensus-java tracing. #410 implements this feature but isn't complete.

Consider providing Java annotations to automatically add tags or start a child span.

3

Several people have mentioned this idea, so I wanted to open an issue. We could provide method-level Java annotations to conveniently modify the current context when a method is called....

Move current Span logic from the API to the implementation.

3

#643 makes a similar change to tagging. If it is merged, we should make the tracing package consistent, so that all current context logic is in the implementation library.

Consider testing the code examples contained in Javadocs.

4

We should test these examples to at least ensure that they compile. I'm not sure what we should use, though. I did a quick search and found one implementation of...

Provide a way to determine whether tags, stats, or trace classes are no-op implementations.

7

The no-op implementations can often be used to avoid unnecessary if statements, but it is important to be able to check whether they are no-op when necessary. See https://github.com/census-instrumentation/opencensus-java/issues/215#issuecomment-296304442

Consider changing the Javadoc policy to allow omitting unnecessary param and return tags.

1

This is related to the discussion in https://github.com/census-instrumentation/opencensus-java/pull/485#discussion_r130210392. Javadocs written with the current style (https://github.com/census-instrumentation/opencensus-java/blob/master/CONTRIBUTING.md#javadoc) can sometimes clutter the documentation and hide the most relevant points.

See https://github.com/census-instrumentation/opencensus-java/pull/446#discussion_r126848618.

Consider requiring a feature to be implemented in a few libraries before making the spec final

1

See https://github.com/census-instrumentation/opencensus-specs/issues/195#issuecomment-430091302. We could update https://github.com/census-instrumentation/opencensus-specs/blob/a6ad82f4ee21038c33d5282ebb4979d08808e6b5/Process.md#step-3-specs-pull-request to require each new feature to be merged with a "draft" label. Then, after the feature has been implemented in a few libraries and...