CFCA: Repeated unexplained delays in providing timely status updates

This case concerns CFCA’s repeated unexplained delays in providing timely updates on incidents, referenced as occurring in Bug 1524733, Bug 1532113, and Bug 1532559. Ryan Sleevi requested that CFCA provide an incident report describing what it was doing to ensure the Mozilla Community receives timely updates on all incidents going forward, citing Mozilla’s “Keeping Us Informed” expectations. Oliver Bi (s**********l@126.com) responded that there may have been a misunderstanding, explaining that he did not provide timely updates because he planned to update status and submit a final report after a system was officially used, and he described a timeline for automated ordering system development and deployment. After the system was used on March 2, Oliver Bi asked whether the question had been explained clearly and whether the bug could be closed. Ryan Sleevi clarified that his question was specifically about ensuring weekly (timely) updates, and Oliver Bi stated that he understood the weekly update expectation and would provide next update timing and update status before the “Next Update” time if remediation takes longer than a week. A Fastly representative (w**********r@fastly.com) stated that all questions had been answered and remediation was complete. The bug is marked RESOLVED with resolution FIXED.

1. 2019-07-13 CFCA started development of an automated ordering system.
2. 2019-09-10 CFCA developed the first version of the automated ordering system.
3. 2019-09-27 CFCA deployed a test system for the automated ordering system.
4. 2019-12-09 CFCA began production system deployment for the automated ordering system.
5. 2020-02-01 CFCA planned for the system to be officially used (after Spring Festival).
6. 2020-03-02 CFCA reported that the system had been used.
7. 2020-04-01 A participant stated remediation was complete and the questions were answered.

1. 2020-02-05 Community commenter — Ryan Sleevi cited prior CFCA incident-update delays and requested an incident report ensuring timely updates going forward per Mozilla’s “Keeping Us Informed” guidance.
2. 2020-02-06 Community commenter — Oliver Bi replied that he believed there was a misunderstanding and explained delays were due to planned status/final reporting after a system was officially used, providing a development/deployment timeline.
3. 2020-03-09 Community commenter — Oliver Bi said the system had been used on March 2 and asked whether the issue was explained clearly and whether the bug could be closed.
4. 2020-03-30 Community commenter — Ryan Sleevi clarified that his question was about ensuring bugs receive timely (weekly) updates, which he said Comment #1 did not address.
5. 2020-03-31 Community commenter — Oliver Bi acknowledged the weekly update expectation and said that if remediation takes longer than a week, he would state the next update time, get confirmation, and update status before the “Next Update” time.
6. 2020-04-01 Fastly representative — w**********r@fastly.com stated that all questions were answered and remediation was complete.