doc: add CPC meeting minutes for 2025-09-30

Author: tobie

meetings/2025/2025-09-30.md

@@ -0,0 +1,107 @@
+# OpenJS Foundation Cross Project Council Meeting 2025-09-30
+
+## Links
+
+* **Recording**:
+* **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/1663
+
+## Present
+
+* Claudio Wunder (@ovflowd)
+* Jordan Harband (@ljharb)
+* Ben Sternthal
+* Robin Ginn
+* Chris de Almeida (@ctcpip)
+* Tobie Langel (@tobie)
+* Adrian Estrada
+* Ulises Gascon
+* Wes Todd
+
+## Agenda
+
+1. One travel fund request
+
+### Announcements
+
+### Board Meeting Updates
+
+- https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-board
+- Next board meeting at JSConf
+
+### Staff Updates
+
+- https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-legal-info
+- https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-staff-update
+- https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-website-update
+
+_Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting._
+
+### openjs-foundation/cross-project-council
+
+* \[vis.gl\] Project Charter Approval [#1656](https://github.com/openjs-foundation/cross-project-council/issues/1656)
+    * It was agreed that Ben would ask the project to revert their merge so that the CPC would be able to comment. Additionally we would ask for a clearer description of the TSC composition (for example min/max size, how folks are elected).
+* 2025 OpenJS Foundation CPC Selections: Impact, At-Large, and Regular [#1655](https://github.com/openjs-foundation/cross-project-council/issues/1655)
+    * Impact project should not go through the form. The issue and form will be fixed to address this.
+* Create a Bundler (Tooling) Collaboration Space [#1630](https://github.com/openjs-foundation/cross-project-council/issues/1630)
+    * General agreement that this is a good idea, decision to move forward and to include deliverables/outcomes in the proposal.
+* Summit: Webpack Collaboration Summit [#1608](https://github.com/openjs-foundation/cross-project-council/issues/1608)
+    * Not addressed today as Claudio had dropped from the call.
+* clarifying charter requirements [#1607](https://github.com/openjs-foundation/cross-project-council/issues/1607)
+    * Issue #1656 discussed earlier is a great example why we need more clarity around what should be in project charters.
+    * General agreement that we don't want to formalize this by creating a policy. Instead, we want to lead by example by improving the charter template through better defaults and clearer instructions.
+    * Next steps would be a pull request that clarifies in the PROJECT_PROGRESSION file that the template is the source of truth for what belongs in the charter, and adds better defaults an guidance to the charter.
+    * This seems a good topic to move forward in the next working session.
+    * We also briefly discussed whether projects that had too much in the charter could remove sections that were requested without CPC approval. The CPC decided against this; if you're making changes to the charter, you need to run those changes to the CPC, unless those are strictly editorial.
+* Update website to match stage name changes [#1604](https://github.com/openjs-foundation/cross-project-council/issues/1604)
+    * Wait on outcome of [#1654](https://github.com/openjs-foundation/cross-project-council/pull/1654)
+* Rename "Complete" project stage to "Feature-complete", add new "Sunsetting" stage [#1654](https://github.com/openjs-foundation/cross-project-council/issues/1654)
+  * This was presented as a way to make it easier for maintainers to be transparent about their intentions wrt to the maturity of their project.
+  * In particular, this changes allows projects that are feature complete, but don't have an intention to sunset to say so, without suggesting that they are on a track for archiving their projects.
+* JavaScriptLandia Award Nominations [#1601](https://github.com/openjs-foundation/cross-project-council/issues/1601)
+    * Closed. Decisions announced at JS Conf (Oct. 16).
+* Audit github org owners [#1591](https://github.com/openjs-foundation/cross-project-council/issues/1591)
+* Move Dojo to at-large status [#1589](https://github.com/openjs-foundation/cross-project-council/issues/1589)
+    * Pending [1654](https://github.com/openjs-foundation/cross-project-council/pull/1654).
+* Clarify what information is collected about individuals as part of CoC incident handling [#1528](https://github.com/openjs-foundation/cross-project-council/issues/1528)
+* Project Website Footers [#1525](https://github.com/openjs-foundation/cross-project-council/issues/1525)
+* Possible GDPR Conflict Summary for Code of Conduct Report Privacy [#1522](https://github.com/openjs-foundation/cross-project-council/issues/1522)
+* Create an AI Collab Space [#1520](https://github.com/openjs-foundation/cross-project-council/issues/1520)
+* Is AI-assisted development allowed? [#1509](https://github.com/openjs-foundation/cross-project-council/issues/1509)
+* \[GeoDa - Onboarding\] Publish Project Charter on website or GitHub (see charter template) [#1496](https://github.com/openjs-foundation/cross-project-council/issues/1496)
+    * Needs to be finalized. Let's look at it during the working session next week.
+* Organize regular batched policy updates for foundation projects [#1486](https://github.com/openjs-foundation/cross-project-council/issues/1486)
+* Resources: GitHub's DevConnect Program [#1472](https://github.com/openjs-foundation/cross-project-council/issues/1472)
+    * Closing as program was sunset.
+* Code of Conduct Information sharing between a project and the foundation [#1470](https://github.com/openjs-foundation/cross-project-council/issues/1470)
+* Review NativeScript Charter for Approval [#1467](https://github.com/openjs-foundation/cross-project-council/issues/1467)
+    * Needs to be finalized. Let's look at it during the working session next week.
+* What version of the Contributor Covenant Code of Conduct should we use? [#1457](https://github.com/openjs-foundation/cross-project-council/issues/1457)
+* Proposal To Add A SERVICES.md or similar documentation to OpenJS Projects [#1425](https://github.com/openjs-foundation/cross-project-council/issues/1425)
+* Code of Conduct Plan of Action - Remaining Items [#1417](https://github.com/openjs-foundation/cross-project-council/issues/1417)
+* Update onboarding and post-graduation checklists to match new CoC policy [#1255](https://github.com/openjs-foundation/cross-project-council/issues/1255)
+
+### Next week's working session
+
+Are there any initiatives or agenda items that we should use a working session to further progress on?
+
+The working session will focus on improving the default charter template and charter reviews:
+- \[vis.gl\] Project Charter Approval [#1656](https://github.com/openjs-foundation/cross-project-council/issues/1656)
+- Review NativeScript Charter for Approval [#1467](https://github.com/openjs-foundation/cross-project-council/issues/1467)
+- \[GeoDa - Onboarding\] Publish Project Charter on website or GitHub (see charter template) [#1496](https://github.com/openjs-foundation/cross-project-council/issues/1496)
+- clarifying charter requirements [#1607](https://github.com/openjs-foundation/cross-project-council/issues/1607)
+
+### Regular reviews
+
+Please review regularly our list of dates and reminders, our quarterly review issues, and check the list of issues that can be closed:
+
+- https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md
+- https://github.com/openjs-foundation/cross-project-council/labels/cpc-quartely-review
+- https://github.com/openjs-foundation/cross-project-council/labels/cpc-can-issue-be-closed
+
+### Q&A, Other
+
+## Upcoming Meetings
+
+- **Calendar**: <https://calendar.openjsf.org>
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.