The form is too long and discouraging me from adding telemetry probes about data-review

[Osmose]

note that these complaints are specifically about adding telemetry to Firefox, this looks like it could be used for other things as well

I've used this form multiple times for things like Shield studies and non-Telemetry data collection, and have found the questions useful for planning the collection, and relevant to the collection I was performing.

Maybe a telemetry-probe-specific form could alleviate some of these concerns? Assuming the maintenance burden of multiple forms is fine for the data stewards.

[chutten]

The simple technical limitation that it can't be done using artifact builds

Not strictly related to the conversation, but you may be interested to follow bug 1425909 where we hope to soon address this specific concern.

+1 to Osmose's plan for a "If you're extending the expiry of an existing Telemetry Histogram or Scalar, use this form (3 questions). If you're adding a new Telemetry Histogram, use this form (4 questions). If you're..."

The form as it stands seems to satisfy three distinct roles:

• Make sure the requester thinks about the collection.
• Surface details the reviewer will need to make a decision.
• Make sure the reviewer thinks about the collection.

That may contribute to some of the overlap from question to question.

[rjweiss]

The data stewards met last week. We all agreed that considering variants of requests and revising the process (similar to offering both exempt or non-exempt review in an IRB) is worth exploring. I've opened up #3 to track progress towards that objective.