Changes

Jump to: navigation, search

CA/Responding To An Incident

451 bytes added, 11:35, 18 August 2017
More tweaks
= Incident Report =
Each incident should result in an incident report, written as soon as the problem is fully diagnosed and (temporary or permanent) measures have been put in place to make sure it will not re-occur. If the permanent fix is going to take significant time to implement, you should not wait until this is done before issuing the report. We expect to see incident reports as soon as possible, and certainly within two weeks of the initial issue report. While remediation work may still be ongoing, a satisfactory incident report will serve to resolve the issue from a Mozilla perspective.  The incident report may well repeat things which have been said previously in discussions or bug comments. This is entirely expected. The report should be a summary of previous findings. The existence of data in discussions or bug comments does not excuse a CA from the task of compiling a proper incident report.
The incident report should cover at least the following topics:
Accountapprovers, antispam, confirm, emeritus
4,925
edits

Navigation menu