All, Thank you to everyone who provided valuable feedback on the proposed <https://github.com/mozilla/www.ccadb.org/pull/198> updates to the CCADB Policy and the Incident Reporting Guidelines (IRGs). Both artifacts have been enhanced thanks to the insightful recommendations and suggestions.
We want to reiterate the original objectives for this update: - Clarifying Root Store Operator expectations for CCADB disclosures. - Streamlining requirements across different root programs to reduce redundancy. - Enhancing the simplicity and readability of the policy. We plan to publish the updated CCADB Policy and IRGs later in June, with an effective date of July 1, 2025. We appreciate your continued collaboration in making the CCADB a more effective and transparent resource for the community. -Chris, on behalf of the CCADB Steering Committee On Fri, May 2, 2025 at 10:48 AM Chris Clements <[email protected]> wrote: > All, > > Following the community’s recent iteration > <https://groups.google.com/a/ccadb.org/g/public/c/GIBHz9FUjHY/m/XOOLNpOFCAAJ> > and improvement on the updated CCADB Incident Reporting Guidelines > <https://www.ccadb.org/cas/incident-report> (IRGs), the CCADB Steering > Committee has collaborated on an updated draft of the CCADB Policy. > > The set of proposed updates are available here > <https://github.com/mozilla/www.ccadb.org/pull/198>. > > Objectives for this update include: > > - Clarifying Root Store Operator expectations related to CCADB > disclosures. Some of these clarifications were motivated by public Incident > Reports filed to Bugzilla over the past year. > - Creating opportunities to (a) remove redundant/similar requirements > located across root program policies related to CCADB disclosures and (b) > encourage future simplicity. > - Promoting simplicity and improving readability through a > reorganization of normative and non-normative requirements. > > Additionally, minor updates are proposed to the IRGs (e.g., further > streamlining the incident reporting closure process). > > These proposals should not be considered “final”, but instead a “work > in-progress” that we hope to enhance through community contributions. We > welcome your feedback on these proposed updates and recommendations by *May > 23, 2025*. Please share your thoughts by replying to this email or, > *preferably*, by suggesting edits directly on GitHub. > > Thank you > -Chris, on behalf of the CCADB Steering Committee > -- You received this message because you are subscribed to the Google Groups "CCADB Public" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/ccadb.org/d/msgid/public/CAAbw9mAW4veJVtuEKg66X1FQyOODw6L8vMTUr%2B6vRQjdhwU78w%40mail.gmail.com.
