OpenJS Foundation Cross Project Council Meeting 2025-05-13  ## Metadata - Author: [[OpenJS Foundation]] - Full Title: OpenJS Foundation Cross Project Council Meeting 2025-05-13 - Category: #articles - Document Note: --- tags: [#openjs, #cpc, #governance, #working-groups, #code-of-conduct, #open-source, #community] - #openjs - #cpc - #governance Author: [OpenJS Foundation Cross Project Council Meeting Participants] Source: [YouTube: OpenJS Foundation Cross Project Council Meeting 2025-05-13](https://www.youtube.com/watch?v=VAX72EAUPfE) Reference: [YouTube Transcript](https://www.youtube.com/watch?v=VAX72EAUPfE) date created: 2025-05-15 18:40 --- # Title: 🏛️ OpenJS Foundation Cross Project Council Meeting 2025-05-13 — Governance, Working Groups, and Community Updates ## Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) --- ## 📝 Summary This Cross Project Council (CPC) meeting of the OpenJS Foundation (May 13, 2025) featured updates on new working groups (Performance, Security, TypeScript) within Express, progress on code of conduct refinements, partnership and funding process questions, governance clarifications, and expanded travel support for contributors. The council discussed ongoing compliance, onboarding improvements, upcoming board meetings, collaboration spaces (notably for data visualization), and stressed the need for documented frameworks around partnerships and financial decisions. Membership processes have been further streamlined, and the council emphasized inclusive, transparent community practices. --- ## 📖 Main Content The OpenJS Foundation’s Cross Project Council met to cover pressing issues and community needs: - **Working Groups & Community Growth**: Express project leads are spinning up new working groups—Performance, Security, and TypeScript—signaling investment in project stability and forward-looking development. These are in early stages, with open invitations for participation. - **Event & Conference Logistics**: Announcements included the upcoming JS Comp, ticket sales, discount codes for maintainers, and closing of the Call for Proposals. The council highlighted opportunities for funding travel through Express’ own surplus and the community-wide CPC fund. - **Collaboration & Visualization**: A new open visualization collaboration space was discussed (with website shared: [openvisualization.org](https://openvisualization.org)), inviting broader community participation and demoing works in progress from diverse contributors. - **Governance & Board Operations**: Regular updates, invitation to propose agenda items for board meetings, and reminders of the fourth-Friday schedule. Plans to share board meeting slides and open feedback loops. - **Code of Conduct & Compliance**: Substantial progress on codifying decision-making in the Code of Conduct (CoC) team charter, including multiple pull requests, checklists, and review of Contributor Covenant versions. Continued effort to inventory and audit compliance across projects, with a plan to communicate and enforce standards. - **Onboarding & Documentation**: The council is reviewing onboarding processes and documentation checklists, aiming for clearer, more actionable policies across projects—especially around post-graduation checklists, privacy footers, and security requirements. - **Strategic Partnerships & Legal Process**: Express project surfaced gaps in documented frameworks for handling strategic partnerships (esp. those involving funding, infrastructure, or co-marketing). Council members recommended developing legal/contractual frameworks akin to other major open source initiatives. - **Membership Process Improvements**: Regular membership is now easier—via form submission rather than PR—lowering friction for new joiners and making governance more accessible. Regular members can join private sessions and participate in decisions. - **Funding Distribution & Security Programs**: Discussion covered how surplus funds (such as those from the GitHub security program) can be distributed for community benefit, reiterating the importance of transparent, agreed-upon processes for allocation. --- ### 🗒️ Notes #### [00:18](https://www.youtube.com/watch?v=VAX72EAUPfE&t=18) — Announcements & Events - JS Comp tickets available; discounts for maintainers. - CFPs closed; program committee reviewing proposals. - Board meeting schedule and openness for agenda contributions. #### [01:16](https://www.youtube.com/watch?v=VAX72EAUPfE&t=76) — Express Working Groups - Launching new Performance, Security, and (planned) TypeScript working groups. - Participation process and coordination hurdles with OpenJS calendar/portal. #### [02:27](https://www.youtube.com/watch?v=VAX72EAUPfE&t=147) — Visualization Collaboration - Community collaboration in open visualization. - Demo projects (openvisualization.org); open to new contributors. #### [04:47](https://www.youtube.com/watch?v=VAX72EAUPfE&t=287) — Board & Governance Updates - Board meetings: fourth Fridays, open session/private session split. - Plan to publish slides for greater transparency. #### [05:01](https://www.youtube.com/watch?v=VAX72EAUPfE&t=301) — Code of Conduct (CoC) Progress - PR to clarify decision-making in CoC team charter (PR #1463). - Approvals and ongoing feedback requested; Contributor Covenant version 3 pending. - Ongoing work to update, document, and migrate CoC to the correct repositories. #### [09:46](https://www.youtube.com/watch?v=VAX72EAUPfE&t=586) — Compliance & Inventory - Inventory of project compliance with CoC requirements. - Plan to clean up issues, communicate status, and ensure all projects adhere to updated standards. #### [12:08](https://www.youtube.com/watch?v=VAX72EAUPfE&t=728) — Onboarding & Policy Audits - Improving onboarding/post-graduation checklists, focusing on privacy, documentation, and security. - Open items for future CPC working sessions: COC audits, project outreach, and privacy compliance. #### [14:54](https://www.youtube.com/watch?v=VAX72EAUPfE&t=894) — Security & Governance Requirements - Considering additional security requirements for projects joining OpenJS. - Current recommendations include open governance, documented CoC, privacy footers. - Discussion about tiering requirements and CPC decision-making authority. #### [17:26](https://www.youtube.com/watch?v=VAX72EAUPfE&t=1046) — Partnerships & Legal Frameworks - Express partnership inquiry; unclear on process for strategic/financial partnerships. - Council identifies documentation gap; need for legal review of deals involving money/infrastructure. - Plans to model future partner programs on established projects (e.g., Hyperledger). #### [19:31](https://www.youtube.com/watch?v=VAX72EAUPfE&t=1171) — Security Funding & Project Distribution - Allocating GitHub security program funds: plans and challenges. - Importance of clarity and community input in distribution processes. #### [21:16](https://www.youtube.com/watch?v=VAX72EAUPfE&t=1276) — Community Travel Support - Express to use surplus funds for contributor travel, following CPC fund processes. - Two travel funds now exist: CPC community fund and event-specific scholarships. #### [23:15](https://www.youtube.com/watch?v=VAX72EAUPfE&t=1395) — Membership & Participation - Membership now form-based, easier than PRs. - Regular members participate in private sessions and key decisions. --- ## 📖 References - [OpenJS Foundation YouTube](https://www.youtube.com/channel/UCQ9JcRE4lY8OeIZYJ8CO2lw) - [openvisualization.org](https://openvisualization.org) - [OpenJS Foundation Governance Docs](https://openjsf.org/about/governance/) - [OpenJS Cross Project Council GitHub](https://github.com/openjs-foundation/cross-project-council) --- ## 🗣️ Paraphrase 1. **Original:** “We’ve got a few new working groups on Express… performance, security, hopefully a TypeScript working group. If anyone’s interested, reach out—we can get you links, even if they’re not all on the calendar yet.” **Paraphrased:** The Express project is launching several working groups, including Performance, Security, and one focused on TypeScript. Anyone interested can contact the team for participation details, even as the calendar listings are still being finalized. 2. **Original:** “The partnership proposal was…‘Hey, we have some neat things, we have a partnership with MDN, are you interested?’…We were unclear on what to do. I just wanted to throw that out there—maybe there’s a gap there.” **Paraphrased:** A group approached the Express team with a partnership opportunity (similar to their MDN collaboration), but it was unclear how to proceed due to a lack of documented guidance on such strategic partnerships, highlighting a need for clear process documentation. --- ## 📰 Newsletter 📰 **OpenJS Foundation CPC Update: Fresh Working Groups, Policy Overhauls, and More!** It’s been a busy week for the OpenJS Cross Project Council: new working groups are kicking off in Express (Performance, Security, TypeScript—bring your ideas!), JS Comp is coming soon (discounts for maintainers!), and a vibrant open visualization collaboration space just launched ([openvisualization.org](https://openvisualization.org)). Behind the scenes, governance is getting a tune-up—expect better onboarding, code of conduct clarity, and streamlined project audits. Plus, partnerships and travel funding just got easier, with Express supporting travel for contributors and membership now a form, not a PR. 🔗 [Meeting replay & resources](https://www.youtube.com/watch?v=VAX72EAUPfE) --- ## ✅ Action Items - **Contributor Onboarding:** Review onboarding processes and checklists for clarity and inclusivity; ensure privacy and CoC documentation are up-to-date. - **Governance Advocacy:** Promote transparent frameworks for strategic partnerships and project funding, especially around legal/contractual processes. - **Community Engagement:** Share working group invitations widely and support distributed team collaboration (e.g., open visualization spaces). - **Funding & Recognition:** Leverage surplus and travel funds to lower barriers for contributor participation, mirroring Express/CPC approaches. - **OSPO Director Alignment:** Use OpenJS’s transparency, onboarding, and DEIB focus as benchmarks for developing open, inclusive programs in the WordPress and broader open source ecosystem. --- ## 🧪 Hypotheses - Improved onboarding, checklists, and policy documentation increase new contributor retention and project sustainability. - Clearly defined legal and governance frameworks for partnerships reduce risk and increase community trust. - Expanding travel funds leads to greater diversity and community participation at key events. - Proactive code of conduct compliance fosters healthier, more inclusive open source communities. ### 📊 Methodology - **Surveys** of new contributors about onboarding experiences pre/post documentation updates. - **Case studies** of partnership management before and after implementing legal frameworks. - **Diversity analysis** of travel fund recipients over time. - **Compliance audits** across projects regarding CoC and governance requirements. - **Engagement metrics** from working group and visualization space participation. ### ❓ Questions - How does onboarding clarity impact contributor retention and project quality? - What legal or operational pitfalls have other open source projects encountered with partnerships? - What percentage of projects fully comply with updated CoC and privacy policies? - How can travel funding best support underrepresented contributors? - How are project governance models evolving across the foundation? ### 🔮 Future Research - Longitudinal study of contributor diversity and participation as governance evolves. - Comparative analysis of partnership management strategies across open source foundations. - Impact assessment of expanded travel funding on community engagement. - Ongoing audit of CoC adherence and its effects on project health. ### 💡 Implications - Transparent governance and onboarding may become industry standards, shaping policy for other open source organizations. - Better partnership frameworks can safeguard projects from legal and operational risk. - Increased travel and event support drives broader community growth and sustainability. - Continuous CoC evaluation ensures resilience against exclusion and misconduct. --- ## 🧠 Learning Styles Assessment - **Readability**: Conversational, informal, ~10th–11th grade level. - **Visual Learners**: *Present*: Video format, references to visual projects (openvisualization.org). *Improve*: More visuals in minutes and documentation. - **Aural Learners**: *Present*: Meeting is live-streamed, archive available. *Improve*: Audio summaries or podcast versions. - **Verbal Learners**: *Present*: Detailed discussion, minutes, written policy docs. *Improve*: Storytelling elements in onboarding material. - **Physical Learners**: *Present*: Not explicit. *Improve*: Hands-on workshops, real-world scenarios in onboarding. - **Logical Learners**: *Present*: Checklist processes, audits, and policy breakdowns. *Improve*: More flowcharts, decision trees for governance. - **Social Learners**: *Present*: Open invitations, community discussions, working groups. *Improve*: Peer mentoring and collaborative working sessions. - **Solitary Learners**: *Present*: Self-paced membership process, access to docs. *Improve*: Reflection prompts, personal onboarding goals. - **Naturalistic Learners**: *Present*: Not explicit. *Improve*: Connect community health to sustainability, environment in events. --- ## 📊 Accessibility Assessment - **Screen Reader Compatibility**: *Present*: YouTube transcript is accessible, but linked resources may vary. *Improve*: Semantic HTML, alt text in documentation. - **Keyboard Navigation**: Not addressed. *Improve*: Ensure all membership forms and resources are keyboard accessible. - **Contrast and Readability**: Not discussed. *Improve*: Use high-contrast, accessible design in docs and project websites. - **Text Resizing**: Not covered. *Improve*: Responsive, scalable text in all web resources. --- ## 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment - **Cultural Relevance**: *Present*: Diverse project and contributor mentions; focus on inclusive working groups. *Improve*: Share more global perspectives, project success stories. - **Inclusive Language**: *Present*: Welcoming, accessible, avoids jargon. *Improve*: Add language options or translations. - **Neurodiversity Support**: *Present*: Bullet points, process focus. *Improve*: Shorter, more visual guides, summaries for accessibility. - **Representation**: *Present*: Varied community and project leaders mentioned. *Improve*: Showcase a broader array of identities and roles. - **Psychological Safety**: *Present*: Encouraging, supportive tone, open for questions. *Improve*: Explicit DEIB statements in onboarding and governance docs. --- ## ✅ Logical validity **Strengths**: - *Causal Reasoning*: Clear links between actions (e.g., new onboarding policies) and intended outcomes (retention, compliance). - *Appeal to Evidence*: Discussion based on current issues, PRs, and concrete project examples. - *Logical Flow*: Sequential agenda, items build on one another. - *Balanced View*: Openly acknowledges gaps (e.g., lack of partnership frameworks), proposes solutions. **Weaknesses/Fallacies**: - No major logical fallacies detected. Tone is transparent and process-oriented. - Mild *Appeal to Authority* in referencing “what other open source projects do,” but well-justified and not used to short-circuit reasoning. **Tone**: Open, welcoming, collaborative, sometimes informal, often pragmatic. --- ## 🔍 DARVO Analysis - **Deny**: None observed; open acknowledgment of both progress and gaps. - **Attack**: None; respectful collaboration, even when surfacing issues. - **Reverse Victim/Offender**: None; group focuses on shared improvement, not blame. - **Tone/Emotion**: Supportive, practical, sometimes self-deprecating humor (“I’ve had a lot of coffee…”). No manipulation detected. --- ## 🔍 SEO Evaluation 1. **Keywords**: OpenJS, Cross Project Council, governance, working groups, code of conduct, onboarding, community, Express. 2. **Meta Description**: Add summary such as “OpenJS Foundation’s Cross Project Council tackles working group launches, governance improvements, onboarding, funding, and community engagement.” 3. **Title Tag**: Use “OpenJS Foundation CPC Meeting May 2025: Governance, Working Groups, Community Updates.” 4. **Headers**: Minutes would benefit from clear subheadings. 5. **Content Length**: Meeting minutes and transcript are long; summaries should highlight actionable content. 6. **Internal/External Links**: Links to OpenJS resources and project websites included; could add more for deep dives. 7. **URL Structure**: Use /openjs-cpc-meeting-may-2025. 8. **Image Optimization**: Not relevant unless recap post includes photos. 9. **Mobile Optimization**: YouTube and docs generally mobile-friendly; confirm for all linked resources. 10. **User Engagement**: Calls for participation, form-based membership; opportunity for comments in recap blog post. 11. **Schema Markup**: Add Article/FAQ schema to recaps for rich search snippets. 12. **Social Sharing**: Recaps should add sharing buttons and Open Graph tags. --- ## 🎯 Conclusion This CPC meeting showcases OpenJS Foundation’s commitment to iterative governance, open participation, and real-world impact. Through new working groups, transparent funding, and constant process refinement, the foundation leads by example—lowering barriers to participation, clarifying policy, and welcoming diverse contributors. The council’s openness about its own gaps (especially around partnerships and legal structure) demonstrates humility and growth-mindset leadership. The move to simpler membership and expanded community funding shows practical steps toward a more inclusive, sustainable open-source future. - Document Tags: [[openjs]] - Summary: To learn more about critical open source JavaScript projects like Appium, Dojo, jQuery, Node.js, and webpack, and 27 more checkout The OpenJS Foundation: https://openjsf.org/ - URL: https://www.youtube.com/watch?v=VAX72EAUPfE Starting. Okay, we arelive on YouTube. Excellent. Uh, thankseveryone for joining another episode ofthe OpenJS Foundation's Cross ProjectCouncil meeting. Um, oh, thanks Ben. Yousent me the code there. Great.Uh, today is May 13th and um let's getthings started. Do we have anyannouncements?Other than uh JS Comp's going to be alot of fun. Buy your tickets now. Ifyou're an active OpenJS maintainer, hitus up. We'll be having maintainerdiscount codes coming at you again. Um,CFPs closed on Sunday, the day beforeyesterday. So, lots of great CFPs thathave come through. Uh, we have a programmeeting tomorrow, but our programcommittee will be reviewing those and welook to announce it. I can'tremember what the schedule is, um,probably in a month on the schedule.Great. Wes, you got an announcement? Yeah. Um, we’ve got a few newworking groups on Express that I justwanted to call out in case folks wereinterested. Um, one of them has gotits first meeting tomorrow. So, um, theperformance working group is the onethat's starting up tomorrow, but we alsoWe have a security working group. Uh, we'regoing to be starting up a hopefully aTypeScript working group. And I'mmissing one more. Uh, so if anybody'sinterested in that kind of work,feel free to reach out and we can getyou links. They’re not all showingup on the OpenJS calendar just yet. We've got to work that out. I think becausewe made them in the portal, theyhave to be made under the OpenJSproject. I don’t know what it is. Um,but since they weren’t showing up there,I just wanted to mention them hereso that folks knew they existed. Yeah,that's really exciting. I’m glad tosee all the progress that's beenhappening there, all the movement. It’sreally great. Excellent. Um, Robin, do youmentioned something before we startedstreaming? I don’t know if you want tohighlight the recent data viz demo oranything like that. Uh, you knowshare more about that to get folksinterested. Well, maybe just about thecollaboration space. We have an openvisualization collaboration space. Uh,yeah, someone demoed a project that waskind of... I would say it’s more than aWork in progress. It's not a project yet,but that’s on ourpublic calendar. We have folks from theOpen Viz, Spankita from Cosmos, and Juliafrom Geoda University of Chicago. Um, butif you’re interested in openvisualization, we even have a website forthat collaboration space,openvvisisualization.org. You can seethose projects— a lot of cool things. AndI think it looks, um, I think it's moreaccessible from a technology perspectivethan it looks. So, great. Yeah. And, uh, I don’t think thestream would have the chat, so I’ll justhighlight that. I think the demo is A5,the letter A, the number five, andthengo.org. So, uh, check that out andjoin the collaboration space ifthat’s of interest toyou. Great. Any other announcementsbefore we get into the agenda?If not, then I will take a look at wherewe're at.Excuse me. Uh, okay. Uh, next onthe list here is any board meetingupdates. I guess I’m on the board, so Ishould be able to answer that, but II don't know of any updates to share. Um,yeah, our board meetings are the fourthFridays of the month. So, if you havesomething you want discussed, I know ourCPC reps, Joe, Toby, and Matteo, willbring things to the private sessionin the public session. So, and thenwe'll report out. Yeah. And I thinkwe're going to try to start sharingthe slides. Yep. Yeah. So, all right. Look for more next ina coupleweeks. Excuse me. Uh, I'm going tobounce through the staff updateslists of things here. Um, the first oneis loop back, which is on my plate. Idon't know, but yeah, I don't haveanything to say about that. Um, I willtry to get progress on that at somepoint. Uh, but the other three labelsdon't have any open issues, it lookslike. So, that'sgood. Excuse me. So, I will move onto the agenda. Uh, the first item here issomething that came out of our workingsession last week. Um, basically, this isa pull request to document the decision-makingprocess just a little bitmore here in the code of conduct team charter. Uh, this is pull request 1463, andum, looks like we have a bunch ofapprovals here,um, and some work on it, which is great.Um, so I guess, if folkshave time, they should take a look andput your thumb on there or add anycomments, and we will keep that movingforward. We've been making great progress onthe code of conduct work.Um, let's see. Next on the list here iswhat version of the contributor covenantshould we use? Um, yes, I'm goingto check the timeline of whenversion three will be out of thecontributors' covenants code ofconduct, which is what we use and alot of other open source projects use. Uh, we did have a meeting last week tokind of discuss some of the thoughtsthat we had when we reviewed it in thelast meeting. The team wasvery receptive. We had a reallygood conversation. Michael Dawson andChris Almeida were both inthe call as well, andyeah, it was a good conversation. Um,they were taking someinput from us, and so I think youI know they'd incorporate that. It seemed like we're not too far from, um,you know, that being done, uh, but I'll tryto check back with the team and get atimeline on that. Uh, feel free to chime in if you have any questions or comments; otherwise,I will keep moving on. Uh, the next itemis 1425. Um, a proposal to add a services.mmdor similar documentation to OpenJSprojects. Uh, I feel like this has beentalked about some, and Ben, I see you havea comment on this issue from six minutesago. So I will give you the mic. Yeah, Iwanted to capture this. Um, we didtalk about it in the security working groupthe week before last, and so we're justwaiting on a written recommendation fromRUD that we'll, um, bring back to thisgroup. So hopefully that will be next week. Great. That'll behelpful. Excellent. Then I will continuemoving on. Um, the next item is the umissue that, uh, Michaela, uh, very helpfullyput together around, uh, the code ofconduct, remaining items, and our plan ofaction. Um, I think that the really, youknow, updating the contributorcovenant is a part of this, which isBasically, we're on hold until thenew one is released. There’s anotheritem here: the third item is to move thecode of conduct to the GitHub repo, whichwe actually advise in our code ofconduct guidance. So that'ssomething I think we shoulddefinitely do and figure out what the changes would be and any issues alongwith that. But the main thing is thefirst item, which is issue1255. This is all aroundthe need to go through thelist of projects that are in thedescription of this issue and makesure they abide by thechecklist that exists. So, my last comment from aweek ago has summarized theessentially rolling it out to theprojects. The delegation andI had an older inventory. Kate has beenworking very diligently on aninventory as well. So, we willdevelop a plan to help communicate that. And cascade it to the projects once wefigure out where it lands. Okay, great.Great. Okay. I almost wonder if weshould have just a new issue for that, um,and kind of clean up. Probably a goodidea. Yeah. Yeah. And we can clean upsome of these, um, lingering code ofconduct process issues. I feel like I'lljust summarize by saying that, uh, we'vebeen working on, uh, code of conductrelated, uh, aspects for a long time. Um,and I feel like we're really at thefinal stages here of just kind ofcleaning up and some kind ofremaining items, and then making surethat, um, you know, the projects and everything are all kind of abiding byuh, how we've laid things out. So,really close. Uh, I think we couldprobably clean up some of the issuesthat we have here and make them moreconcise and clear, and know wherewe're going, but I think we're at thefinal stages of that, uh, really longongoing effort. So that'll begood. Um, anybody have any questions orcomments on any of that stuff, thecode of conduct relatedactivities? Uh, if not, I will keepmoving on. The next item is the 1387. The issue is the health check on the NativeScript TSC charter. Um, I feel like Toby spoke tothem, but I can't remember whatcame out of that. And let me see,there might have been another NativeScriptissue. Yeah, there's anotherNativeScript issue here. So, let mesee if that one wasupdated. Nope. Um, okay. So, we may bewaiting on um, I'll prod Toby todrop a comment in either of these ifhe has any updates. Uh otherwise, wewill try to make progress on those inthe interim. Um, so those are the next two items on theagenda, and the one after that is1355.Um, this is the continuity policy andpackageregistries. Um, this is also waiting onRUD. I see Ben, you dropped thatcomment inthere. Okay, good enough. Uh, we lookforward tomore guidance and suggestions fromRudd, who is a very helpful contributorto the work that we do. And then, oh, so this is the last itemon the agenda here is the issue that Iwas referencing before about updatingOnboarding and postgraduation checklistsfor a number of projects for the codeof conduct, you know, guidance andpolicies. Um, so I've had a lot of coffeethis morning and we kind of justblazed right through theagenda, which I think is never a badthing.Um, the last thing that we would need todo here is talk about what we wantto do for the next CPC workingsession.Um, does anybody have anything that theythink should be worked on? And while Iwait for any responses, I know we have a label forthis topic. Where isWorking CPC working session?Uh, filter by label. So, code ofconduct, migrate project status repo.Let me drop the link to this, um, whathang, drop a link to this list ofissues.Um, the match repository structure toreadme process and policy section.Um, this is, I think, you know, we did abunch of work on the readme for the CPCthat kind of stalled. That's anotherThe thing that we could work on. Um, I think a couple of these we maywant to revisit and potentiallyclose to the two old ones maybe.Um, soyeah, anything people want to work onnext week?I mean, I hate to keep doing this. Sorry, Ben,were you going to say something? Yeah.I mean, um, I wonder, Kate, if it would makesense to review the COC policy auditthat you've done and if there are nextsteps there to kind of use theworking group to figure those out. Sure. Idea. Sorry. Go ahead, Kate. Oh,no. Just seconding that idea. Yeah.Yeah. One of the other things I wasthinking about too coming out of thesecurity collaboration space, is thereanything that’s going to be requiredbecause if we’re going to do the sort ofsweeping outreach to the projects, youknow, I’ve been sort of tracking who’smissing their privacy footers, butI don’t know if we’ve quite in oursecurity cloud space determined what’sgoing to bemandatory or not. But, okay.So, is that something that would beanother thing that RUD would need? Do we need to provide or just kind ofreview where things are? Probably RUD isdefinitely an input to that, but I thinkit would probably be the CPC who makesthe final decision because essentiallywhat you would be doing is addingrequirements for projects joining OpenJS,security requirements. So I thinkit's a group exercise. Probably we'vetiered them, as you know, from therecommendations. So right now therecommendations are open governance,documented code of conduct, privacy,footer, things like that, but it's pretty minimal. So, the question is, doesthis group want to add any otherrequirements?Okay. I mean, I suppose that's somethingwe could discuss then or even now ifwe wanted to.Um, I think it wouldn't be bad too if wewere going to look at, you know, likeBennett said,review the projects in terms of thecode of conduct.Adherence could also take some time andjust kind of clean up some of theremaining issues around that and reallymake the final tasks more clear.Get that all sorted as well. Folks who are new to what we doand this meeting, we've kind of set it up so that wealternate a regular meeting like this,where we go through the agenda,and then the opposite week we have aworking session. We try to pick a topicand really dig in and make someprogress, which I think hasgenerally been working prettywell. Um, so okay, well I guess wehave a handful of things there. We’lllook at project reviewin terms of code ofconduct adherence, as well as anysecurity items, and thenwe can potentially clean things up as we gotoo. Um, great. One thing that comesto mind since we have time,is there anything that anyone wants to talk aboutor work on rightnow? Um,Wes, we had two random things that cameup in Express over the past few weeks.One is a partnership opportunity.I’ve been looking around in theCPC docs to see if there’s anything thatI should have read or known about thatUm, would you tell us what to do orthat kind of thing? So, I just DM'dRobin and Ben about it, but Irealized there might be a gap there. So, this partnership proposal wassomebody who came to the project andsaid, "Hey, we've got some neatthings. We have an example partnershipwith MDN. Are you interested?" Andwe had a meeting with them, and we wereunclear about what we would need to do toparticipate in. So, I just wanted tothrow that out there and see if there wassomething that we missed. What kind of partnership is it? Is itfinancial? Is it infrastructure? Yeah,that's where we probablyhave a gap for any sort of strategicpartnership. I know we have it onthe vendor services, but anything thathas a kind of larger co-marketingrevenue share really needs to comethrough us. We’re also going to belaunching a partner program sortof modeled after what the Hyperledgeror Trusted in IP project has, and NCFas well. But again, whenever thereis money involved or even co-marketing, weneed to have legal frameworks in place. For that. So yeah, and I thinkinfrastructure as well too because, um,totally. Yeah, we had, um, yeah, for folkswho are new, our infrastructure, we hadan archaeological dig of 15 years, 18years of handshake deals with people, um,and it’d be a revolving door and we’d bescrambling. So we like to document thoseand, yeah, get contracts in place.Awesome. So it sounds like we did the rightthing by just, okay, cool, totally open. Yeah, loop me in. I’d love to talk tohim. Yeah. And then there was one otherone that I think Ulyses, maybe, I feellike we talked about yesterday on ourCPC call. There was something we had tofollow up on. Or is Chris here too? Maybe.Sorry, the list goes off my screennow. Um, I think it was maybe to do withthe GitHubsecurity program membershipstuff. I was hoping to lean on them.I know we had a follow-up that wasI think there we had a follow-upquestion on Monday. Um, and Raphael gavesome of his experiences on the GitHubsecurity, you know, that they wereasking for two people. I think that wasto delegate for training and whatnot,but the money goes to the project for. You to distribute as you see fit amongsthowever many you see fit. That juststruck my memory and reminded me of whatI wanted to ask about. Okay. Um, so oneof the things we discussed was whatwe would do with that, you know, moneyand we don't really have a good plan. Sowe thought we’d ask. Oh, Chris, I'mgoing to interject only in the interestof time. I actually talked about thiswith Robin earlier. Um, I can fill youguys in about that. So we’re goodwith the plan that we talked about. So let's just catch up on it later so wecan move the CPC stuff along. Not thatwe don't want to rope in the CBC, butI think there was other stuff on theagenda. Maybe. If not, I'm happy to gointo it. Sorry. Well, there wasn't. Thatwas why I brought it up.I waited until Joe literally was like,"Anybody got anything you want to talkabout?" Oh, okay. Uh, well, now I feelembarrassed for interrupting. Um, pretendI never said anything. No, no, no, no.You... It sounds like you already startedtalking. I didn't know that happened, soI'm, I'm, I'm... Yeah. Yeah. Okay. So, tofill everybody else in. All right. So, letme take a step back. The fortunate position of having alittle bit of cash sitting around, butit's sitting around doing nothing. Um,which is not good. Uh, it should be doingsome good. Um, one of the things that theproject has agreed to use thefunds for is travel. Uh, so very similarto the same reason, the same thing thatthe CPC or OpenJS Foundation has acommunity fund for travel requests. Um,that is also a permissible use of theexpress funds. Um, but we like the CPCtravel fund process and would like tojust use that even if we are funding thetravel. Um, so the intent there is that ifwe have somebody from Express who couldbe contributors, maintainers, or TC members,whoever is going to apply for some fundingthrough for travel, and if we can foot the bill, that would besomething we would like to do, and thenit doesn't have to come out of theOpenJS coffers. Um, and then they wouldstill follow the normal, you know,CPC travel fund approval process. Um,but of course you would get the thumbsup from the Express folks on therequests. Um, and we would note that we would be able to pay forThat. And so I talked to Robin aboutthat earlier, and that seemed like thatwas totally fine for us to do. Um, Idon't know if there's any other commentsfrom Robin, or if Wes, you had—if that'ssomething I'm forgetting or leaving out,or, yeah. And we'll figure out the bestway with Kate and Ben on how to make iteasy for everybody. Awesome. See, Chris, I knew I was—like, Ineeded to lean on somebody here. We hada topic to ask about, and you had alreadydone. So, and then just to talk aboutbecause I had another question offline. So, for JS Comp, we have two buckets oftravel funds. You have the CPC communityfund where you all decide. Um, and thenwe have a scholarship fund set asidefor folks who need it through thefoundation, and there's an applicationand a link on the event website as well. So, there are two optionsdepending on where you sit, right?Um, one thing I’ll drop in the chatthere is, um, Nathan did—uh, Nathanfrom the NativeScript project. Hang on,where'd it go? Uh, NathanWalker from, uh, NativeScript, didopen an issue two hours ago toReview the Native Script charter. Um, soI dropped the link to that issue inthe chat. So if folks want to take alook at that, please do so. Anything else we want to discussbefore we go into a private session? No. Maybe for new folks, it's important to remind themhow they can join private sessions or becomeregular members. Yeah. Please,if you are not a regular member, it's very easy to become oneas long as you're active in the projector in the OpenJS work. Uh we now havea form that you can submit. We used todo it through pull requests, butnow there's a form and you can find itin our documentation. It's not toohard to find. Like if I go to theREADME and look for regular members,it says anyone who has been activein the foundation or one of its memberprojects, as described in the CPCgovernance with a link to it, canbecome a regular member. You can request to become aregular member, and then is this thelink? Nope, that's a link to thegovernance. Okay, let me just dropthat in here. So anyway, there is a formin that link on how to apply to become aAs a regular member, you just basicallyfill out the form, and as long as nobodysays that’s crazy, you can join andbe a part of some of the private decisionsthat happen. So when a project applies,we have the CPC members review that;we review travel fund requests. You know,there's not a lot that you need to be aregular member for, but it's good tojoin, and then we won't have to kickyou out when we go to a privatesession. The more, the merrier. Great. Okay, with that, I will bid you all a fondado, and hopefully see you next time.Thanks for joining, folks onthe stream. Thanks for watching, andwe'll call it a wrap and jump to aprivate session. Thanks. Thank you., OpenJS Foundation Cross Project Council Meeting 2025-05-13, OpenJS Foundation, 01jvasb7f8t4aaxpz326ndkyj2.