Video summary
The OpenJS Foundation Cross Project Council meeting held on July 21, 2026, began with announcements regarding upcoming community events and a brief review of administrative updates. The council highlighted the Node Interactive event at Render ATL in mid-August, which will feature dedicated sessions for Node.js contributors alongside its main conference proceedings. For attendees unable to travel to Atlanta or those interested in European opportunities, the meeting promoted NodeConfEU taking place in Bologna, Italy, later that September. Administratively, there were no specific board updates this week, though a board meeting was scheduled for Friday. The staff update section primarily addressed an ongoing issue regarding loopback, with plans to revisit governance and project funding topics in future sessions.
A significant portion of the discussion focused on refining the agenda structure and improving the annual project presentation process. Council members noted that previous presentations from projects like jQuery had been recorded but not consistently integrated into official documentation or schedules. To address this gap, they decided to update a specific document with links to recordings and established a protocol for scheduling future updates, aiming for concise 10-to-25-minute sessions led by project maintainers. Additionally, the council tackled the transition from "collaboration spaces" to formal working groups, noting that progress on renaming these entities had slowed but was expected to accelerate soon with calls for repository fixes and community involvement.
The meeting also covered updates from various specialized working groups, including AI, Bundler, OpenViz, and security initiatives. The AI working group reported success in booking guest speakers after overcoming initial staffing shortages, while the Bundler group discussed potential co-chairing arrangements to manage increased workload following a recent academic appointment of one of its members. Other groups like Ecosystem Reports were identified as inactive or merged with sustainability efforts, leading to decisions to remove them from official templates and meeting agendas. Furthermore, OpenViz shared news about new releases under the Cosmos project and an upcoming Collaborators Summit in Zurich, while security updates confirmed ongoing preparations for TC39 plenary meetings without immediate changes required.
In conclusion, the council agreed on several actionable items to streamline operations and enhance community engagement throughout the remainder of 2026. Key decisions included assigning specific tasks to update meeting templates by removing obsolete ecosystem reports and ensuring all future project presentations are properly documented with links to recordings. The group also resolved to dedicate time in their next working session specifically for advancing the governance document, acknowledging that Matteo's attendance was anticipated but secondary to moving forward on these critical topics. With administrative hurdles addressed and a clear path set for upcoming events like the Zurich summit and NodeConfEU, the council adjourned with plans to reconvene two weeks later or at the following week's working session depending on progress made on governance matters.
Read the full video transcript
All right. Hello everybody and welcome
to this 21st of July 2026
Open JS Foundation across project
council.
Do we have any announcements?
>> Well, Node Interactive at the Render ATL
conference is coming up. So
be sure to grab a ticket if you can.
It's
the middle of August. It's going to be a
lot of fun. We'll have our own dedicated
event within the event right on the main
floor by the expo hall. And we're also
going to have a coding workshop
sponsored by Harper. A code and learn
for Node.js. So if you want to learn how
to be a contributor to Node, that's a
great place to learn.
>> Very cool.
And where do people can get tickets
from?
>> Render Render ATL. So the Node
conference is included in that. So
>> All right. Any other announcements?
I'm glossing over this whole
Render ATL thing because I have FOMO,
right? Cuz I'm not making
>> going to be great. Well, for our
European friends if they can't or
anywhere else can't jump the the puddle,
you can go to Bologna, Italy in
September for NodeConfEU. That's going
to be super fun as well. So it'll be two
days of conference and one day for the
collab summit for maintainers. So
>> Also very cool.
>> Yeah, yep.
>> Any other announcements than those two?
Nope.
All right. So then the moving on
um to the next part of the agenda.
Um
>> No issues for board updates, um but we
do have a board meeting on Friday.
Um
so, if anybody has anything, uh
feel free to reach out.
Um and I just clicked through all the
staff update links. Uh and all that's in
there is the loopback
you know, uh one that's been lingering
for a long time.
>> Right.
Um so, no specific updates from the
board um
on this week, but um
in a couple of weeks.
Yes.
>> Yep.
>> All right, very cool.
Um
and so, we should go directly into the
um Oh, we should we should uh Wait, I'm
I'm looking at this. Um
we go through the working group updates
before um anything else?
>> Yeah, no, I the the this template has
gotten a little jumbled, I think. I was
going to ask Ben um you know, how I can
help maybe uh reorder some of the stuff.
Um but if we want, we can talk briefly
about I mean, I think next working
session we need to dig into the
governance
uh and and project funding stuff.
Um I know some some folks are uh
>> Yeah, the order is all weird.
>> Yeah, yeah.
>> This is why this is why I'm confused.
>> Yeah, yeah. Um you know, and maybe we
can even since the agenda's short, we
can maybe even jump into
uh the you know, working on the project
governance uh today uh in addition to
next week. That's that's what I would
maybe suggest.
Um and uh
so, so yeah, that's
that's what I'm thinking.
>> Okay, so that works. And then let's go
into the agenda, and then let's go back
up to the working group updates.
Um does that does that work?
Um the agenda is actually quite uh
small.
Um, there is 1759 which we just talked
about and which we can go in
um a bit um
more deeply in a few minutes.
Um, then there is the 1750 which is
scheduled the initial annual project
presentation and I think we had the
first one uh 2 weeks ago, correct?
That I that I missed.
Um, and so do uh what do we want to do
with issue 1750?
>> I I would love to hear, you know,
Robin's thoughts, but one quick thought
I had is um
I feel like there was a
a recording of the JQuery update that
was shared on Slack that we should maybe
drop into this uh issue as well.
I'll look for that. But what's uh what's
next on getting project presentations?
>> Um, I think it's booking the next one.
So,
I think we're wanting to start with
Impact. Michaela's that something you
all want to take on for Electron?
>> I'm so sorry. Something just came up
that I had to respond to. Um, I think I
missed that part of the agenda. Can you
just repeat that, please?
>> Oh, for the uh project presentations,
just we you know, we're starting here
from projects like to hear on a yearly
basis just what's new and cool going on
with the project and where you can use
our help. Uh JQuery did it a couple
weeks ago. I was actually on vacation,
too, but there's a recording. But it'd
be great just to have a few of your
maintainers come and just give an
update.
>> Okay, awesome. Yep, we can definitely
get that all arranged.
>> Okay.
>> Um,
>> feel free to grab any of the next CPC
meetings.
>> Great, sounds good. Yeah.
>> Okay, awesome.
That was easy.
>> Yep.
>> It was indeed.
Um
but what do we do with this issue? There
was also There was also um
a a document that's in project resources
um which has a presentation schedule um
which is not up-to-date.
Um do we
do we update it and put the links there?
Um
this is Sorry.
This is the doc.
And this is the issue.
Or should we update this?
>> We should.
>> Yeah, I mean, I think it's a good idea
when we know something's upcoming to put
it in here and then having this linked
to the recording.
I think it's a really good idea. I'm
happy It's It's a easy thing to do if
you want to assign to me.
>> All right. And so
What do we do?
Sorry, please.
>> I was going to say I dropped a comment
on the issue for the jQuery one. So uh
that's handy uh Ben if if uh that's
helpful.
>> Yeah, did you mention me by any chance?
>> Nope.
>> And I will.
>> Yep.
>> But I like the idea of having it on that
page just so folks, you know.
>> yeah?
>> Yeah, I think so, too.
>> Um so uh I'm just going to do I'm just
going to add this here. Um
Um and what do we do with the issue? Do
we keep keep this issue open
as a way to
um
>> us of this.
>> to remind us that there's this thing
going on?
Uh keep this issue open to remind us to
continue scheduling those.
Um, update the linked document
with the recording.
Um, that's it, right?
>> Uh, just to confirm, who should be
reached out to in order to actually
schedule the date?
>> Just uh,
me, Joe, and Toby. We'll just make sure
we dedicate time.
>> Okay, sounds good.
>> Thanks.
>> Or you can also just put a comment in in
in this issue actually. That works, too.
And I I I So, I haven't looked at the
video from the Jake Wearable one, but
how long was it? Like, what's the
expectation roughly?
10 15 minutes?
>> it. I was on vacation, too. I watched
it. I think it was like 20 25 minutes.
>> Okay, so aim for 10.
>> Okay, sounds good.
>> Yeah.
>> Sounds good.
>> This Yeah. All right, cool. Okay, well,
that's settled. And so, moving back to
Um, the next one Oh, and the next one is
just um, and Kate is still there. The
next one is just um, 1741.
Um, and this is um, all about um,
um, finishing the renaming of collapse
spaces into working groups. And I think
that's on Kate's plate.
>> Yes.
>> Um, and send it this is slow.
>> Yes, it's slowed down a little bit. Um,
but I'm going to work this week to try
and pick it back up a little and maybe
start um,
putting out some calls for people to uh,
fix their repos. Um, but we're getting
close.
>> All right, cool.
Okay.
Um, and so, now uh, let's move back to
uh, working group updates cuz that's a
good segue and then we can uh, spend a
bit of time on
um, 1759.
Um, and so working group updates there's
the AI working group.
Do we have any update on this topic
since the last update we had?
>> We have hosts who are reaching out to
guests to book. We've kind of done a We
have what three uh, three maintainers
who attend who are reaching out to one
or two guests each. So, those should
start getting booked. And then once we
know we have that greater pipeline, we
already have two in the hopper. Um, so
with you and uh,
and Matteo, so then we'll publish those
so we know that we're going to have
regular cadence.
We were running short on hosts for a
bit. People were busy. So.
>> Um,
Okay, that sounds that sounds perfect.
Um, and and I think Kate, you reached
out um, to was it Was it you that
reached out to ask whether or was it
Kelly? No, I'm I'm God, I'm this is
really bad. I'm [laughter]
I have so not back into this working
thing.
Um,
to see if like Matteo's and I were still
um,
>> Oh, relevant. I
I think Kylie reached out to you.
>> It was Kylie, yes.
>> But you are no longer relevant. Just
>> [laughter]
>> Sorry.
>> Matteo is still is like today clearly
I'm not and possibly.
>> [laughter]
>> Um, I don't know what answer we gave
her, well, we need to figure this out.
Okay.
Um,
Um, I know she was really happy with
both episodes and that we're using
StreamYard, which even pulls out little
video snippets for social media and it
just like nailed it right on the bat.
So,
>> All right, cool. In that case,
>> Yeah.
>> uh if she I mean, if she is happy, I'm
I'm
I'm happy.
All right. Uh Bundler
um working group, any updates?
>> Which working group? Oh, Bundler, yeah.
>> Yes, I haven't still had time for this,
to be very honest.
Uh there's some interaction with some
people in some issues and in the
community, which is great.
But again, I need to find time to
actually be able to start running this.
And I don't really know how.
Um
So, I don't know what to to do here
because it is a topic that actually a
lot of people are are excited about. But
that was a topic that someone
needs to have actual time to run this
and to be able to,
you know, give the attention it deserves
and I don't know what to do here.
>> Um is there anyone in the community that
could maybe help you co-chair it or
something like this?
>> I could try, yeah.
Um I showed in the next few months,
like the time when we are around there
have actual capacity to actually go and
visit this, circle this back. And maybe
even there might I might find someone,
you know, to help co-chair it.
Uh but these uh few two last few months
have been very busy.
Uh so,
you might have seen it, but I became a
professor at the Technical University of
Munich.
So,
uh
lots of important and that spend
very very hectic, but I'm very, very
happy.
And going to kidnap a few of you to be
guest lecturers to spread the love of
open source.
There. Yeah.
>> Yeah,
you don't have to be violent with me.
>> [laughter]
>> I'm happy to I'm happy to oblige without
the violence.
>> Absolutely.
>> Very cool. Okay, so in that case, we can
revisit this.
But yeah, I mean I think
finding a coach here sometimes can help
and really make things like smoother. I
think it works well with the CPC.
And
you know, maybe that's something that
like if there's someone else that could
you know, that's also wants to to help
you like pull this off that that could
be an issue
solution.
All right,
ecosystem report.
I I I thought we had chatted about this
and decided that it was
wasn't
I might be
Um
I thought this one was had like very
little activity. We had
considered
Yeah, the repository is archived.
>> That makes sense.
>> So is it still in the
Is it still in the read me?
Looking now.
It's not.
>> Yes.
It is.
The Cross Project Council read me.
>> Where?
>> Where it says OpenJS Collaboration
Spaces. Let me send you the link.
>> I'm there like right, but like the that
one isn't it.
>> Sustainability
>> one
I think that's a different one.
We should have renamed this one. By the
way, this is no longer collaboration
spaces.
>> I know.
>> Oh, is sustainability the same one? I'm
I'm I'm I'm
No, cuz we also have this one. No, um we
should remove ecosystem reports from me
here.
>> Oh, ecosystem
>> Um from the template.
>> Yeah, and I thought that was when the
sustainability those two were merged
from the beginning. But then the
sustainability has not been meeting
either, so
that may need to be
>> Right, but
at the very least we should remove this
one from the template. Um
Um there was so
Um there was reordering of the template
that's necessary in removing this. Like
where do we file issues for this?
>> So that would be I I linked to this
Um here. I'll copy it again. But it's
it's generated from the node js repo.
>> Oh, so it's here.
>> Mhm.
>> Um
All right, so let me grab
this URL and then file a new issue on
our side
to do this.
And
I don't update meeting template.
Um can we have reorder
um template
back to what it was before.
And the second thing is remove the um
ecosystem
working group.
Um
working group list.
Um
I don't believe that.
template
is
in this repo.
Um
>> [snorts]
>> and then
uh Joe, I'll I'll assign both of us to
do this.
>> Sure.
>> Um and
CPC
There we go.
All right. Okay, good.
Um
Oh.
This should be removed.
See.
And here it is what 1780 feet.
Okay.
Um Open Vis, do we have any updates on
Open Vis?
>> Uh they're
uh doing a lot of work on their
projects, releasing new uh
things. I think Cosmos just had uh
a big uh release that was posted There
was a blog that was posted on our site.
Uh SQL Rooms became a subproject
uh under Open Viz, and they are working
on their Collaborators Summit, which is
happening in Switzerland.
Which I believe I've got like dates in
my head. I have too many dates in my
head, but that's coming up this fall.
So, there's a registration link if you
go to openvisualization.org.
But, lots of good work happening there.
>> Collaborator meeting in Switzerland.
>> September 9th and 10th in Zurich.
>> September.
>> Oh.
>> Mhm.
>> I mean it.
Uh
okay, uh package metadata interop.
>> I've not had a meeting on that for a
while.
So, no update.
>> No update.
Uh package vulnerability, I think it's
the same issue.
Correct.
No update.
Um security, thanks for whoever added
the agenda notes here.
And standards,
uh I think um I saw a bunch of meetings
preparing
um meeting preparing uh on the TC39 uh
>> Yeah, that's happening right now.
>> Yeah, exactly. The plenary
>> this week.
>> Yeah.
>> Um and sustainability is also no update,
right?
All right.
Um,
well, we can as we wait for Matteo to
show up.
>> I don't know if he's didn't respond, so
I'm thinking his day job may have
consumed his
afternoon evening.
>> His evening?
>> Mhm.
>> Um, do we still spend some time on the
governance.md
uh, issue?
And do we uh,
>> I I think it'd be a good idea.
But where you where it was a suggestion
that Matteo should be here as well?
>> No, Matteo was supposed to be here as
well.
>> Oh, yeah. If we want to conclude this,
we can just kind of give folks an update
on the private session and then work on
the governance doc perhaps.
>> Yeah, yeah, on private. I think that's a
good idea.
>> Okay.
>> All right. So in that case, uh,
if there's no other uh,
businesses, then we should uh, conclude
this and
uh, we'll meet uh, some of you next week
for the working session, uh, which will
be on governance.md.
Um, and uh, if not, we'll see you in two
weeks here.
Thank you very much.
>> Great.
>> Um, we lost Claudio. I thought he would
be here for this.
I will message him.
>> Yeah, I'm going to um,
put in chat.
>> Tell me who is this is still being
recorded though can whoever is
>> Oh yeah.
>> the person stop recording.
>> Yeah.
>> All right, say goodbye again. I'm just
kidding.