Organize regular batched policy updates for foundation projects

[tobie]

Each year a number of policies the CPC creates impacts foundation projects (e.g. updating the CoC, new security or continuity requirements, etc.).

This requires both changes to the onboarding checklist and outreach to update (and sometimes audit) current projects.

Rather than do this in an ad-hoc way, there was a discussion in the CPC today to organize this at a more regular cadence (once a year?) and batch all of these updates together.

This could also be tied to relevant CPC voting member elections and as a way to tighten the relationship between the CPC and projects.

A number of currently open issues would be good candidates for this batched update:

• Update onboarding and post-graduation checklists to match new CoC policy #1255
• Proposal To Add A SERVICES.md or similar documentation to OpenJS Projects #1425 and Create third-party-services-documentation-policy.md #1482
• continuity policy and package registries? #1355 and Create npm Continuity Policy #1483
• Project Website Footers #1525

[tobie]

Notes from July 8 CPC call:

• some progress made during last working session
• appetite for organizing something like this
• devil is in the details: how exactly do we do this so that it’s valuable and not too difficult/costly set up
• we have some project dashboards
• bringing those together is a priority
• 1 step would be to require every project to self-audit
• Let’s not block the sub-issues on this.
• let’s discuss an annual check separately

[tobie]

Notes from this week's CPC call:

• Covered in last working session. This would be great, but time intensive. Let’s continue moving forward on issues independent of figuring out batched updates so that progress is not blocked.
• Create an issue to work towards an end of year townhall/newsletter update (perhaps we can add in updates from projects, can a 2-way update increase participation)
• Suggest working session topic and that we spend the working session on one topic

[tobie]

What if we asked each project for the issue tracker where they would prefer we file an issue when there are things that need to be updated and we wrote a script to do so across all foundation projects?