OpenJS Foundation Cross Project Council Meeting - August 18, 2026

[clears throat] >> Great. Thanks everybody for joining another episode of the Open JS Foundation's Cross Project Council meeting. Today is August 18th 2026. Um and we can get into things. Let's see. Do we have any announcements? >> I would just like to thank the Render ATL team for putting on an awesome event. They hosted us for Node Interactive last week. It was fun to see everyone. But Justin Samuels, thank you and the entire team. You're awesome to work with. And we really appreciated the space and bringing Node and JavaScript to the event. >> Yeah, it was great. It's a good time. >> Very cool. Any highlights to share for those that didn't make it? >> Are there highlights? >> Code and Learn I think um you know, went well and we learned a lot and you know, are already kind of thinking about what to do next. Some virtual sessions. You know, Ethan Arrowwood and and the team put in a lot of work. And yeah, Ben found a bug in Zed during the Code and Learn. Um But yeah, I think it was it was productive and I think was a great kind of restart of that whole effort and I think that folks really came away with some um improvements to it and and I think virtual should be fun and and so we're going to you know, look at doing more of that. So that was good. Um additionally, I thought the talks were all really great. It was really interesting because we were in the expo hall which of course is crazy loud. But there were a few areas in the expo hall where they had these sorts of other areas for you know, our space and and other uh spaces as well. And so what they did was you had a microphone for a speaker and then all the attendees had headphones on and they were tuned to that you know session and um so it was interesting but I think it kind of worked well because you could control the volume and you could hear the speaker and and I think it largely worked worked out all right. >> Yeah and I think it's nice for attendees to drop in as well you know so we got a lot of foot traffic um so yeah. It's very cool. >> Yeah I think Robin was saying the alternative was to be like upstairs and when I went up there it was like a ghost town up there so I think it was really great that we were in the expo hall yeah. So it's cool. >> Yeah and I always we also got to meet Matteo's family his daughter's probably the youngest attendee at five but it's always good reminder I know at Linux Foundation events we have free child care and I think it's really nice for kids to get exposed to that grow up with that so. >> Yeah. >> That's very cool. >> Yeah. And and I don't know what is there any expectations that we will work with them again next year in a similar fashion or what? >> Uh Justin in the hall said let's do it again next year I said absolutely of course if you all say yes but yeah that was my reaction. >> I think it was a render overall was an amazing event too and like just the diversity down there was really uh you know it was impressive it was just a great group of people uh it was a really really good event I was >> Yeah. And a nice way for us I mean I think it it was very web you know sort of it was very developer full stack developer focused so we probably got exposure to a lot of other JavaScript projects that we don't normally do, so I think that was great as well. >> Yeah. Cool. Moving on, any other announcements before we move on? Um no board meeting updates, there's no August meeting. Uh I think cuz cuz of the event and stuff. Um So nothing from there. Um and the next meeting isn't until next month, but uh let us know if there's anything we need to bring to the board or vice versa. >> [clears throat] >> I don't think there's anything on staff updates. Um I guess since the agenda is still um we need to reorder things, but since next working session is here, uh do we want to talk about what we want to work on next week? >> We are turning our next working session into the town hall uh for the advertising network, and that was sort of my bad. We updated the meeting request to say town hall with the link, but I will send out um uh an email with all of the context to all of our CPC private list and other maintainers who'd like to go, so that'll go out this week, and then hopefully we'll have a pretty good attendance on Tuesday next week. >> Okay. Cool. Um I want to jump down to the uh agenda and sort of just get that going, and then we can double back on on any of the other things that we need to. Um So first item on the agenda is the uh exploring the opt-in ad network. Um is there anything new here, Robin? >> No, I've just been I think I need to drop the date of the town hall, but I think I've been trying to keep everybody informed. So. >> Okay, great. Um next one is >> that oh that I know that some of the TCP SCs um are starting to socialize it within their group as well. Haven't had a lot of pushback or anything. So hopefully everyone will be excited about the opportunity. So. >> Yeah. Yeah, I haven't heard anything from folks yet, but I know it's being discussed as well. I don't know why this update meeting template is has the agenda on here, but we can just get that fixed and move that along. Provide guidance on governance is you know, still here and still I think being something we need to work on. Is that accurate? >> Yes, so maybe next working session or maybe a bit of time today depending on what else we want to discuss. >> Okay. Schedule initial annual project presentations. So we've had JQuery and Electron last time, which was great. And do we have anything booked for an upcoming session or anybody uh any projects being considered or considering? >> How about Express? Knocking out those impact projects. >> Yeah, I think that's a great idea. We can we can talk to folks. >> Chris is going off script. I know that meme. John. >> Yeah. I already planted a seed there. Folks can think about it and um we'll figure it out. >> When is the deadline? Sorry. >> Just whenever. I mean, you know, obviously sooner the better, but um it doesn't need to be in 2 weeks, but you know, uh if if >> That would be great though, wouldn't it? >> Yeah, 2 weeks would be perfect, but a month would be acceptable, too. Um so either the next session or the one after >> Chris nod. >> I think that was uh that was uh acceptance. >> Are you saying Chris is volunteering for that? >> Oh, Wes isn't here. We'll volunteer Wes. >> Yeah, yeah. >> That's a nod, [laughter] Chris, unquestionably. >> Yeah. Um cool. Uh we'll we'll we'll double back on that thought. Um last item on the agenda is the collapse space uh stuff. I assume that's probably just still in progress, uh Kate? >> Yeah, making good progress though. I made some changes on the CPC repo, so thanks to those who approved those PRs. >> Cool. Thank you. Appreciate it. >> [sighs and gasps] >> Uh great. That's the agenda. Um do we have any working group uh updates? Do we want to go through the list and check in? >> We should absolutely do that. >> Yeah, anything from the AI working group? I didn't attend uh the last meeting or two, so I don't have anything to share. No? >> No, but we had some great great sessions on AI at Render that um those we thought they would be recorded and they were not. So, we will still work with the folks who great gave great uh talks on on on a number of things and as Kylie says, it's the gift that keeps on giving, so we'll work on promoting their decks and their content. So. >> Sounds good. Uh next up, bundler. Anything on the Bundler group? >> No updates there yet. I mean after render, I'm going to do the things that we mentioned a few specific meetings ago. And to try to get things really up and running and people more active etc. etc. Just haven't had much time because all things are on my plate. >> Yeah. No worries. No update. Uh ecosystem report? >> That's not really an active working group anymore. >> Yes, that one of the ones that's on the list to pull off of here? >> Mhm. >> Okay. Uh >> Is it closed in the in the in the readme etc. or is it just in the template we need to remove it? Maybe, huh? >> I cannot recall but I can click right through this link and see what it says. This repository was archived. >> Right. And what does it say in the readme? Is it still um >> Nothing. Zilch. Probably wouldn't be a bad thing to update the readme to kind of talk a little bit more about what the effort was and what the outcomes were. >> No, I mean I was I was our readme. >> Oh. >> Which one is this? >> Uh ecosystem report. >> I think we Oh, yeah, I think we removed this already. From the readme. >> From our readme. Got it. I'm trying to find it. Okay, great. >> Yes. Ben did that in June. Thank you, Ben. But I had no idea you had done that in June. >> Sure. >> More than welcome. >> [laughter] >> I'll take credit. >> Yeah. >> Cool. Uh next up Open Viz. Any anyone here? >> They have a collab summit in September. So uh if you go to openvisualization.org, you'll read all about it and then they will post their talks as well. >> Cool. >> Yep. >> Uh package metadata interop. >> They have not met for some time. >> Is that another one that we're pulling off of this or no? Okay. >> Should probably check with them. Yeah. >> Uh package bone. No update? Security? Oh, you already got that in there. Uh Who added that? >> That was me. I just generally link to the the issue that has the agenda and the meeting notes from the previous call if folks are interested. It was also recorded. Um I don't know if if if anyone that attended the call wanted to pull out anything really interesting. Um you know, we we did get a um Steve from Capital One did share like a collection of cloud skills that Capital One had released that I haven't reviewed, but I was quite interested in that. Um called bone bone hunter. It's actually really hard to say. Um Yeah, that call is usually pretty good. >> Yeah, and I've submitted uh an uh application for the Sovereign Tech Fund at the Sovereign Tech Agency uh on a research project that the security working group's on on open vulnerability reporting and just trying to determine if it's better to be more transparent um on vulnerability reports, um, or continue in a coordinated fashion. You know, I think Linus Torvalds been quite vocal about saying, "Should all reports be confidential if everybody's discovering the same things on AI?" So, we're proposing a research project. So. >> And my gut reaction to that is that what you discover depends a lot on what how you prompt it and what models you're using. So, I'm not sure it's true that every AI-discovered vulnerability is automatically AI-discoverable by everyone else, but, uh, certainly worth researching. >> Yeah. >> It's going to be a topic at the, um, Node Collapse Summit as well. >> I always say please to my planter. Um, anyway, uh, standards? Going once? >> Uh, yeah. Uh, um, recently we were discussing W3C and W3C-related things. Um, which reminds me, Toby, have you made a decision? I don't know if we're past the deadline already or not. Um, >> The decision was considering >> Toby was considering running for the board, one of the boards, like there's too many boards of the W3C. Um, Toby, tell us about that. >> Uh, decision was made and I and I and I am running. Um, and Michael sent an email. Michael, who was the, um, primary AC rep, um, sent, um, sent it like literally an hour before this call. So, we'll see how that There's actually a good, um, a good set of people running this time, which is great cuz it wasn't the case at first. Um and we'll see where it goes. >> Did you say that's the executive board? >> Yes, and yes, I agree, Chris. There are too many boards in this organization. >> is running for the board the board of directors? >> Or the board board? >> Yeah. Um other than that, um I I probably keep repeating this, so if it sounds like broken record, that's fine. Um TC39 plenary meetings, in-person meetings next year. We've got two of them nailed down. Locations and dates we're still trying to get the third one um confirmed um and we'll announce everything all at once as we like to do. Um if the third one keeps dragging on uh or the planning for that keeps dragging on, then we may announce the other meetings in advance uh while we still try and pin that down, but I'm hopeful that um we'll we'll get that sorted out um in not too much more time. >> Cool. >> All right. >> Good luck. Uh sustainability. No update. Great. Um I think that's kind of everything. Dates and reminders. So, I guess the CPC uh community voting members, the nomination period for that is October 1st. The 1st and 2nd week, uh, I guess. But that's like a month or so. I just thought I'd check in here. Um, and then the chair uh, votes are in November. Okay, cool. Anything on the quarterly review? Nothing. >> Do do we have the COC team on that list? Because I I think I think we were supposed to review that on a regular basis and I think we have failed to do that seriously. >> I'll review the uh, membership of the uh, code of conduct panel. >> Yeah, I'm not sure what exactly we had decided, but I think we're um, past. I I I think we haven't done this in a while. I might be wrong though. I've been very wrong about many things over [laughter] the days, so this could be wrong. >> Well, I think it's important that we should have it we should have that dates uh, in >> in that same doc. Yes. >> Yeah. >> So, I don't think there's a defined cadence for the COC panel review. Doesn't mean there shouldn't be, but I don't think there is. Unless I just missed it. >> I think there is, but um, but I'm not >> It might be a nice thing to have as people time commitments may change, you know, so. >> One year term. >> One year? >> One year term. >> Okay. So, I'm going to open an issue just to like it I guess add dates to that doc. whatever [clears throat] we decide those dates are. >> And see when the last one was run, and I think it's more than a year ago, but I might be wrong. >> Okay. I'll just create an issue. Great. Anything else for the the meeting here, y'all? Do we want to end early or dig into something or what do we want to do? >> I think we can give back 3 minutes to people on 25. >> I think that sounds good to me. I'm not really prepared to dig into governance at the moment. Um so I think it would be the the other option. So cool. We'll call it a wrap. Thank you, everyone. Pleasure to see you all. Pleasure to make progress on the things that we do, and we'll talk to you soon. >> a lot of you last week, too. >> Yeah, it was great. >> Okay. >> Cool. Cheers. >> Bye, folks. >> See you all.