Over in 1271457 comment 6, Benjamin asked me to file a bug to make it so that use counters can expire and can be opt-in/opt-out like other telemetry probes.

My suggestion is to make use a yaml file, modeled after scalars.yaml, and be able to specify all of the 'normal' things we expect: expiration, opt-in/opt-out, responsible people, bug#. Description might be optional here if we can autogenerate that from the interface.

If we make use of the Scalars.yaml model, lets base this on parse_scalars.yaml (and extend it to handle usecounters). That way we can have validation & parsing code shared.

Hello, I'm asking your help with an experiment with making decisions on bugs. You've been needinfo'ed on this bug. I'd like you to take one action to help this bug make progress toward a decision. The things you can do include: * If you know or have a good guess of which product and component this bug belongs to, change the product and component of the bug * If you know of the right person to ask about this bug, redirect the needinfo to them * If you cannot reproduce the bug, close it All we need you to do is one thing that will help us make a decision on the bug or resolve it. Thank you for your help with this. If you have questions, please contact emma@mozilla.com.