We want to track when add-ons become damaged either by submitting information to AMO or through FHR.

Not sure what you needinfo'ed me for here, maybe because this bug is very poorly defined? I don't really know what we want and I don't really have any time to work on this. Unless you have a better idea than me we should just close this bug.

Sorry, I'm not sure either, but the main question we had was: what does damaged mean in this context? I think a report to FHR of the number of addons that: * cannot be enabled because they do are not signed at all * cannot be enabled because they do are signed incorrectly Would be useful for us detecting problems in signing. If damage means something else, let us know. Wasn't implying that its for you to work on either.

(In reply to Andy McKay [:andym] from comment #2) > Sorry, I'm not sure either, but the main question we had was: what does > damaged mean in this context? I think a report to FHR of the number of > addons that: > * cannot be enabled because they do are not signed at all > * cannot be enabled because they do are signed incorrectly > > Would be useful for us detecting problems in signing. If damage means > something else, let us know. Wasn't implying that its for you to work on > either. I can't really remember, I'm guessing it was signed add-ons that later got detected as broken during the periodic check but it could be anything we want it to be at this point.

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.