OpenJS Foundation Cross Project Council Meeting - September 15, 2026
Watch on YouTubeVideo summary
The OpenJS Foundation Cross Project Council meeting held on September 15, 2026, began with announcements regarding upcoming community events, including Node Comp EU in Bologna and the Node Collaborator Summit, alongside a recap of the recent Open Viz Collab Summit. The council also addressed administrative matters, noting that the next board meeting is scheduled for September 25th after skipping August due to the Render ATL event. A significant portion of the early agenda was dedicated to expediting an issue concerning ad network surplus content from Carbon Ads; following a successful email vote by the board to accelerate the process rather than waiting until the next formal meeting, the council agreed to proceed with implementation and planned a blog post similar to Mozilla's recent efforts to highlight the initiative.
The discussion then shifted to governance improvements and agenda planning, where members decided to close an older issue regarding ad network funding programs after agreeing that staff would provide regular updates on sustainability initiatives. The council also tackled the need to update meeting templates and refine project governance guidance, specifically addressing intellectual property documentation to ensure consistency between separate guides. Regarding future scheduling, the group determined that the originally proposed annual project presentation on September 29th would likely be canceled in favor of an alternative date around October 13th, which would also accommodate travel logistics for Node Comp EU. Additionally, the council identified a need for a general repository cleanup and a review of several aging issues labeled under "CPC working session," intending to address these before submitting them for a final pull request.
In their working group updates, the council reviewed the status of various collaborations, noting that the Bundler Collab Space had not yet launched due to sponsor priorities and deciding to pause active efforts there temporarily. The Ecosystem Working Group and Package V One Collab were identified as candidates for removal or consolidation, with a specific pull request submitted to supersede the Package Vault group under the Security Working Group before archiving its repository. The Security group reported positive developments, including new grants from Alpha Omega and the Sovereign Tech Fund, which are being used to staff initiatives and define success metrics, while also praising recent outreach efforts by Ulysus that provided early warnings to projects.
The meeting concluded with brief updates from the Standards and Sustainability groups, both of which reported no new items requiring immediate action or noted a lack of recent meetings respectively. With the agenda items covered and working group statuses clarified, the council agreed to wrap up the public session, allowing members to continue discussions after hours if necessary. The overall tone of the meeting was productive and forward-looking, balancing the administrative task of cleaning up legacy issues with the strategic goal of launching new initiatives and securing funding to support the foundation's growing ecosystem.
Read the full video transcript
All right,
we're uh getting this ball rolling.
Thanks for attending another episode of
the cross project council's or so sorry
the OpenJS Foundation's cross project
council meeting. Today is uh the 15th of
September 2026. Thanks everybody for
joining.
Um we can kind of get right into things.
Are there any announcements?
>> We have node comp EU happening in
Bolognia
uh in at the end of next week. It's
coming up quick. And then the node
project is having a node collaborator
summit. Um so that'll be great. That's
three days of Node. Uh this past week
we've had the open viz collab summit. So
you'll see videos and a recap blog
coming out of that.
Lots of great work.
>> Awesome.
Cool. Um, anything on the board side?
Board meeting updates.
>> Our next board meeting is September
25th.
I believe we took um August off because
it was render ATL.
>> Yeah. Okay.
Uh, great. So, if anybody has anything
that needs to be brought to the board,
um, please let us know. There's an issue
label, too, if that's uh the preferred
path.
Um,
so I think that this uh meeting uh
template is still a little bit uh off,
but I'm going to try to pop through here
really quickly. Uh the first looking at
the staff updates, the first one, the
legal info is still the loop back thing.
Um which I'm just going to not even
comment on because I don't think about
that anymore. Um, this label doesn't
even seem to exist anymore. Oh, no. No.
Okay, it was just a GitHub glitch. Um,
so yeah, nothing on either of those any
of those three staff update line items.
Um, let's maybe wait on figuring out
what the working session is to kind of
go through the rest of the things.
Um we we um have some elections coming
up uh that we will uh start to get into
in in the next um you know couple of
sessions. Um so uh I'm going to just
kind of move past some of that stuff.
I'm going to leave the working group
updates for the end um and just get
right into the CPC agenda.
So, the first item on the list is uh
1797, the um ad network stuff. Uh any
updates on this?
>> Yes, the uh we did actually do, speaking
of the board, we did an email vote uh to
expedite that instead of waiting till
September 25th because we had a lot of
great feedback uh from the CPC. Um I
know there are some project briefings as
well. Um, and I know the folks um at
Carbon Ads had uh they may have some
surplus
um ad content coming into the fourth
quarter that we did not want to miss.
So, we got that um passed. I updated the
issue yesterday, I believe. And uh now
I'll start working with the projects and
uh and just get that going. So, I'm
pretty excited. We'll announce we'll do
a blog as well. If you've seen, for
example, what Mozilla did, it was really
well done. So something in that spirit.
So
>> cool.
>> Very cool. Um just a quick question on
how do we handle this? Do we close this
issue? Um and do we um sort of organize
some kind of review um in um I don't
know like mid 27 something like this to
to discuss like what this looks like or
um how do you all think about this?
Wow. As awake as I am.
>> We do quarterly, you know, reports and
updates with our um ecosystem
sustainability partners. We haven't
quite reported that out, but it's, you
know, it's it's been working. We, you
know, we always want to do more, but,
you know, we've seen it. It took about
maybe a year before, you know, some of
our anticipated revenue started to go
up. Um, but
you know, we can do that. We can get
more into a rhythm with that.
>> I mean, I think that would be cool.
Like, you know, like like we're trying
to do with working groups and with
projects
>> of having like some updates to the CPC.
Yeah,
>> I think it would be nice to also
uh maybe have updates on these topics at
whatever cadence makes sense.
>> Yeah,
we can do that.
>> I think that would be great.
>> Yeah, because we have the content
already. Happy to share. Yeah.
>> Very cool.
>> All right.
>> I'm just gonna put a note also.
>> Yeah, I do think Toby that we can
probably close this issue. Right. It is
it is very specific to the discussion
and exploration and and that's all done.
>> Yeah. So, I'm just going to put a note
on this. Um,
it would be great to have a regular
update
on how these funding programs
of these sustainability programs are
going.
Okay, I'll just write this. Um,
I'm going and uh
Robin
and the staff and and staff offered to
do so on a regular basis
to do so on.
All right, cool.
I'll add it to the notes also
>> and I'm closing this.
>> Excellent. Thank you for all that.
Uh, moving along,
the next item is update the meeting
templates. And I have uh opened up the
repo and I'm going to do it
um as soon as we are done with this
meeting because I keep saying, "Oh yeah,
somebody should do that." And I know
what I would like to see happen. So, I'm
going to do it. Great. Um, next item on
the agenda is uh provide guidance on
governance for projects.
>> Yes, we had a good working session on
that last week um and have some
feedback. I've taken the action to clean
it up. I think I I need to add a little
bit more on um IP and I'm I think I'm
going to have our attorney take a quick
look as well. Um and then we should be
able to then probably throw it into a PR
for feedback. Awesome.
>> Um,
>> so I I didn't make it last week. Um, uh,
c can we just be, uh, mindful that
there's also guidance, IP guidance, um,
in a separate docu uh, and so that we
don't have um, overlap or that or that
we combine them together so that there's
at least like like consistency between
the two. Yeah.
Good point.
>> Yes. Yeah, good point.
>> Great.
Um, next item on the agenda is the um
annual project presentations.
Uh,
Nathan Walker suggests September 15th or
29th.
I'm guessing we can look at the 29th. um
>> node comp.
>> Oh yeah, yeah, yeah. So, um I think we
should maybe propose
>> the time after that. Um how does that
end up working out? Like will we like
have two
I'm guessing we'll we'll cancel
um the 29th.
>> That's a good idea. Um, in which case
the 6th would be a working session,
which I will be traveling that day. I
imagine Robin will be too.
>> And so we're looking at probably October
13th as perhaps a suggested uh
alternative.
I'm just going to quick drop a quick
note in there with Node Comp EU and uh
related travel.
would be best if it
scripts
presents on October 13th.
Oops. What the heck? How did I do that?
Sorry, I somehow selected all and
deleted my message. Uh, but I got it
back. Uh, please and thank you. All
right,
I'm going to put the comments on that
and uh hopefully work that out. Um
and then so the last item on the agenda
is the collab space stuff. Um uh Kate
isn't here. Uh so um but I assume that
um you know that's
progressing as it will progress and uh
you know we're getting there. Uh so
that's it for the agenda. Where's my
Zoom meeting? There it is. Um
anybody else have anything for the
agenda or should we talk about uh
working group stuff?
Cool. We'll jump into the working group
uh stuff or
I guess maybe let me ask do we what do
we want to do for working session next
week?
That's a good thing to just decide
before we get into the working groups.
Does it make sense to do more work on
um the guidance um uh right now or do we
want to Yeah. Okay.
>> Yeah.
>> Yeah. I was just wondering if there was
any review or something we wanted to do,
but yeah.
>> Oh, we could for a final, I guess, but I
think we need something else.
>> Okay. I'm looking to see what uh working
session
um labels we might have. Or is it CPC
working session? Oh, do we have like a
do we do we even have an issue that
collects them? I can't remember what our
tooling
>> No, but we have a label for it though.
>> Yeah, but I saw there's a label for Hang
on. Let me see what it says. Working Oh,
working CPC working session agenda.
>> That's another one. I don't know what
that is. There's like a CPC working
session.
>> Yeah. Yeah. I know. I feel like we were
we were there was an issue that was
being created. I don't know if it is
anymore, which is okay. We'll figure
that out. Not not important right now.
But if I look at that label, CPC working
session label, we've got uh governance
um um uh clarify CPC and TSC
responsibilities and limitations, which
was opened up uh a year ago. Uh clarify
charter requirements, which was opened
up over a year ago. And match
repositories. Oh, this one match
repository structure to readme process
and policy section. You remember? You
remember that thing we were working on?
Oh, that was fun.
>> I think we can just ask like Claude to
do that for us now.
>> Yeah. Right.
>> Yeah. Spring cleaning.
>> Exactly.
>> Yeah.
>> Organizing,
>> which isn't a bad idea. Yeah. And and
Ben shared um an an issue here for CBC
working session agenda from
last week,
which has those four things that I just
listed out. So,
>> I went fancy.
Sorry, what was that, Toby?
>> No, no, I'm I'm impressed.
>> Yeah, tooling.
Should we do cleanup,
some some governance review and cleanup
and and and um maybe even discuss these
other issues and whether they're even
issues, how we might want to um address
them, if they're still things that we
want to address.
>> Yep.
>> Okay.
>> Why don't we do just a repo cleanup in
general?
>> Yeah. Yeah. I think that maybe that's
what uh Robin meant by spring clean up.
I'm not sure.
>> I mean, unless you want because the
cleanup there that issue was like the
reading me stuff that Chris and I were
all busy doing and I don't think any of
us is in a mood to like look into this
for like next week.
>> Yeah. Yeah. All right. So next week um
uh repo cleanup
uh governance
uh
>> the governance my understanding was
Robin was suggesting that this needed
like a bit more time before putting it
back on the
working.
>> Yeah, we can do another quick another
quick review before we throw it into a
PR. Yeah.
>> Okay. So now
>> Oh, okay. So Oh, I I heard the opposite.
I heard like that needed a bit more like
maybe
>> I want to have I want to have our legal
counsel just take a quick glance to make
sure we're covered because I think
>> Right. And you think that will be done
by next week and or not?
>> Oh yeah.
>> Oh
well. I mean I know I know great
>> we have the most fast responsive legal
team. I'm telling you.
>> I mean that's not incorrect. Uh uh um um
but uh you know it it didn't feel
necessarily that it was either short or
like you know top off the pile kind of
problem. All right, cool. So in that
case Yeah. Okay. So in that case, okay,
I'm sorry for the misunderstanding and
uh
>> Oh,
great.
>> So in the notes I have next week repo
cleanup governance quick review before
final PR and discuss the issues that
have CPC working session label. There
are four and some are quite old.
Makes sense, right? Beautiful.
>> Excellent. All right. So, now into the
uh working group updates. I will just
get right into it. Anything from the AI
group?
No, I I don't uh I don't know if it's
been meeting lately. Uh things have been
busy and and whatnot. Uh bundler collab
space.
And let me actually look and see which
update this meeting uh thing. I just
want to see which ones we we want to
remove the ecosystem working group and
the package vone collab. Uh so
>> yeah and I'm not sure the bundler is
going to quite launch yet because the
our sponsor is kind of working on other
projects right now Cladio. So not quite
sure unless we have somebody to step up.
>> It hasn't quite launched I would say.
>> Okay. So we'll we'll leave that for now.
um ecosystem working group I think is
one of the ones that we are saying we
need to remove for now and do that ad
hoc uh open viz if anybody has anything
from them here
um
and then uh package metadata interop uh
anything from there which which was the
other one that we wanted to pull out oh
the package v collab space
um package vault. So you have a a PR uh
that you put in here, Chris.
>> Yeah, let's just merge that real quick.
It's just one saying that this group has
been uh superseded by the security
working group and then
merge that PR and then archive the repo.
>> Okay, great. I will approve it
as well.
Um,
this approved. I can just merge this. Do
we care about squash and merge? I do.
That's what I do.
>> There's only one commit, so there's
nothing to squash.
>> Oh, okay. Well, I still do it anyway.
Oh, invalid email for web commit. What?
It's
All right, somebody else merge it. I
don't know why it's giving me this
error.
I'm just going to ignore it because it's
Um, security. Anything in security? I
see agenda and notes from September 14th
call. Ben, you want to summarize? I saw
a nod there a little.
>> Yeah. Um, well, I have to summarize.
That's why I put the notes in here. Um,
if folks want to read it. Um, good shot.
Uh we have a new grant coming in from
Alpha Omega that we're um working on
staffing and and uh metrics for success
with the STA which has been really good.
Oh, Robin, you're muted.
>> And new grant coming in for Sovereign
Tech Fund. You said Alpha.
>> So Tech Fund. I forgot that they changed
their
>> Sovereign Tech Fund. Yeah.
>> Yes.
>> You said Alpha Omega. So
>> did I?
>> Too many grants.
>> Exactly.
>> Robin, I'm going to let you.
>> It's not a bad problem to have. Yeah,
>> I was going to say it's a good problem
to have.
>> It is. Yeah, I know.
>> Yeah.
>> Mhm.
>> Uh so that's great. Yeah, it's it's a
really healthy um group. Um we have
really good attendance which is really
nice and it's active and they're they're
working on interesting things. So it's
it's a real pleasure to to help them
with that.
>> Cool.
I like the CNA um month off. I think
that's great. Yeah.
And I just wanted to call it out here.
>> Yeah. And Ulysus has been reaching out
individually to projects, giving them
early heads up over the past month. So,
and um the blog that uh he wrote that's
posted on our blog is wonderfully done.
>> Um okay. Uh excellent. Moving on.
Anything from standards?
>> Um, I don't think there's anything new
to report.
>> Okay. Sustainability.
>> That's an ad hoc group. We haven't met
in some time.
>> Okay.
Um, great.
So, that is that list. Uh, and that is
kind of the whole uh thing here, right?
Yep. I bounced around, but scrolling
around, I don't see anything else we
need to review.
Um, so we can call this public uh
meeting to a close. We can give back
time or uh chat about anything else uh
after hours. So, um, anything else
before I close the session?
All right.
Thanks y'all.