OpenJS Foundation Cross Project Council Meeting - August 4, 2026

All right, great. Thanks everybody for joining another episode of the OpenJS Foundation's Cross Project Council meeting. Today is the 4th of August in the year 2026. Um, and we can kind of get into things. Uh, first of all, do we have any announcements? render ATL is next week where we're having the node interactive uh summit. They have summits across the board and so we're really thankful that they're providing us that opportunity. Um really excited about the code and learn if you want to learn how to contribute to an open source project. Uh Harper is sponsoring that and there's been a lot of folks working so >> yeah. >> Yep. >> Wonderful. [sighs] Cool. Um, any board meeting updates? >> Think of any. >> Yeah, I can't think of any. I don't know if uh Rob >> the only board update is is opened in an issue that we'll talk about after the electron presentation. So, >> yeah, makes sense. >> Yeah. >> Um, so yeah, I mean um Uh should we I don't know what the plan was, but should we jump into that first uh the presentation and then we can kind of run through the the somewhat light agenda and go from there? >> Yep. >> All right, cool. Well, um I'm happy to uh welcome folks from Electron. We had a jQuery presentation a few weeks ago which was really great. We're trying to do this regular project presentations to the CPC which of course is uh published as well to the larger community. So, uh, welcome, uh, Eric and Michaela. >> Hey. Um, yeah, I could do the presentation for us. Uh, so, uh, Ma told me I have 10 minutes, so I'll try to keep it on time. Um, and I have some slides to share, so give me a sec. Um, all right, cool. Um I think it's sharing now. So uh all right from here Electron um what what have we done in the past year? Um what are we doing now? What are we planning on doing in the future? Um I guess just as a uh background, Electron um you build desktop apps with JavaScript, HTML, and CSS. Uh it's kind of a Frankenstein of Node.js JS and Chromium kind of embedded together. Um so you kind of have access to um the power of node but also um the rendering of uh of a modern browser engine. So um going to start with 2025 what we were doing. Um uh we did a lot uh we're a relatively small team of maybe like somewhere between a dozen and two dozen maintainers depending on how um you count everyone's time. Um uh we release with every other Chromium major version a new major version of Electron um that keeps us up to date with uh security uh and uh new platform features. Um so we had six new major versions in 2025. Uh and one of the things that we have to do inheriting from all this Chrome infrastructure is also um use what they use to build. Um, so we actually had to uh re revamp all of our build tooling uh from what Chrome meme uses um or used to use called Ninja and now there's a new thing called CISO. So there was a big u there's a big recall there. Um we redid our releases page uh which is nice. It it has a lot more uh functionality in it now and it's built on modern technology. Um goodbye handlebars. Uh and then uh what else? Oh yeah, RFC's um we started a new RFC system um um about 2 years ago and we've gotten a bunch of uh good RFC's both from um maintainers and occasionally from uh people outside of the uh the maintainer community and we get comments from people and um I can talk a little bit more about those uh in depth later. Uh we did Google Summer code last year that was really fun. I was a mentor on two projects. Uh we did one for um saving and restoring uh the browser windows uh uh like a new API and another one for uh some developer tooling like a chrome extension uh kind of thing that we wrote. Um there was a whole thing hubbub uh last year about shyoon and uh package supply chain security and the npm ecosystem. Uh we had to do a lot of stuff there to make sure that uh we're secure. Now everything is uh based on OIDC uh trusted publishing. Um we kind of implemented that as soon as uh GitHub actions kind of started supporting those things and uh we got a bunch of new maintainers which is really cool. Um so 26 so far would have what are we doing this year? Um so yeah so one of the RFC's that we got implemented was a summer of code project from last year that was uh to save and restore windows state um just based on the C++ layer. Uh and another one was a lazy uh lazy electron downloads which is to uh remove the post install script from the electron mpm package which is you know tying back to the supply chain security stuff. Um, we have a lot of weekly downloads. Maybe not as much as uh popular JavaScript packages because, you know, it's a very uh niche uh uh space and there aren't really like transitive dependencies um where Electron's like, you know, five layers down the tree. Um we did a a lot of work. We got a new maintainer from one password and he's helped a lot with um Linux improvements. He's very uh passionate about that. So um like our whin support's gotten way better uh and which is important as Ubuntu has been kind of moving towards um way as default I think as of 24 maybe uh I'm not sure the specifics um we had a huge push on improving startup speeds uh via profile guide optimization in electron um which is if you've opened anything that uses electron 43 that's been pretty huge um and um couple things that are kind of still going on um there is the uh prompt API that just landed that uses the new Windows window.ai global method um that Chrome exposed, but now we're kind of just exposing as plumbing in Electron. Uh and also uh making our clipboard API more modern uh for um to align with web standards. Um what's next? Oh yes, uh downloads our app. I think that's this is the case across the entire ecosystem, but at least it shows that we're keeping up with everyone else. Um I feel like downloads have kind of exploded everywhere. Um that's good. Um so Electron's governance is organized in a bunch of our different working groups. Um here are some of the stuff that we've done for a couple of them. So uh for releases we did major releases this year four out of um I'm not sure how many we usually have but they've been on time. Um in in the ecosystem side, we have uh decreased our npm dependencies across the chain um just to reduce the amount of one bundle size for all our all of our um build tooling but also to remove the risk of uh supply chain security attacks. Um on the API side, we've approved 49 new [clears throat] features. Um, as the API working group, we kind of just review API PRs and uh see see what we want to actually add to our API surface cuz it's kind of big and overwhelming. Uh, we've kept up to date with uh Chromium and Node.js upgrades and um security has been really overwhelming. I don't know if you guys have looked at uh Chrome's new like stable release blog posts, but there are a lot of uh CVs uh now and we're we're we're trying our best to keep up and I think we've been doing a good job. Um, here are all a list of packages that we've uh we've published uh this year. Uh, I mean, we're just keeping up to date with uh security, new features, bug fixes, and whatnot. Um, it's been a weird time in open source, I think, uh, with uh, AI and everything. We're kind of figuring everything out, but I think we're in a good rhythm to um, keep uh, maintaining all these packages. So, 2026 and beyond on the horizon. Um, we have a couple of approved RSC's. um they the repo is electron RFC's uh um where uh we haven't really gotten the um the the bandwidth or time to um to uh to like implement them yet. But hey, we're still working on stuff. Um we've had security improvements to the ASR integrity functionality, which kind of does an integrity check of your app bundle uh on startup. Um we are dropping 32-bit support for Windows and Linux which is kind of exciting for people who don't want to maintain um software for legacy platforms and uh we are releasing a new major version of our build tooling called Electron Forge. Um those are kind of things that are going on right now. Uh and I feel like maybe I'm really entrenched in the context of maintaining this project. So um happy to field any questions as well. Um that was the last slide. Cool. So, unfortunately, I missed um JQ Corey's presentation a couple of weeks ago. So, this is the first one that I see. And this is so awesome. Uh thank you for showing up. Um thank you for providing this context to everyone. Mhm. >> Um and uh yeah, we should have been doing this for a very long time because it is just like so great to hear from u excited maintainers working on their projects. Um and so that's like thank you so much. Um I um hear you of course and I think everyone sort of feels the pain um of the security um um u state or uh whatever you want to call it. Um do you feel like um this is an area or there are other related or unrelated areas where you you feel uh that collectively uh we could do more together or that you would need help or that uh uh there's specific questions that you have uh or like it feels like everyone has these issues and um are we doing enough or what should we be doing uh as a group of projects um or was potentially outside support to improve the situation there? Um I think at first it was really overwhelming but also at some point package manager started adding the like minimal age gates. Um we we've been disabling post install scripts and whatnot. So I think that definitely uh reduces some of the blast radius. um for uh how like a new vulnerability can affect us. Um I think top of mind like this is maybe not something for a collection of projects other than Node.js, but I do think like there are a lot of packages that exist that maybe should you know live in you know the standard library or whatever of uh of the language. But I feel like we've been making strides on that I feel in the node space cuz I've seen stuff like um I'm trying to remember all the all the new APIs that have landed in the last couple major versions but stuff like globbing um like style style text or whatever like helps you get [clears throat] rid of like a couple packages that like you know have tens of millions of downloads every week but also have maybe been owned in the past um through these kinds of worms. So, I don't know. This is kind of I think we're in an okay state, but it always feels like we're on the brink of something uh new that might, you know, show up and ruin everyone's day. Um since we have cursed here um I mean it's really interesting to see some of this stuff move to um node um would it make sense I mean what is TC39 thinking about in terms of of language and um like increasing what's going on in in the language language to deal to sort of uh reduce the supply chain the the the dependency tree sorry do you know there conversations on this topic or is this something that's been discussed >> um it's kind of outside of the mandate of TC39 um the uh I do uh in the I will share the um TG3 three, which is the security task group um scope and program of work to kind of see what would be in scope for TC39. Um but they generally will be they really have to do with just what's in the language itself and uh impacts of uh proposed changes to the language that would impact security. Um so most recently things like shadow realm compartments um and anytime you are uh dealing with uh like things that cross boundaries. Um so when you talk about the supply chain and dependencies and components um that's really something uh that we would you far more suited for like the OpenJS Foundation security working group the open SSF uh there's a couple of working groups in the open source security foundation that that would be more relevant to um uh so >> sorry Chris I I think I I didn't speak clearly Um Eric was just uh saying that uh a number of sort of standard lib things u moved into node um and that helped them sort of have a better security story for um electron that's sitting on top of it. Um, and my question wasn't uh so much like what is TC39 doing in terms of like ecosystem security because I agree it's out of scope, but in terms of like has this conversation of moving um um essentially increasing the scope of the the API that are shipped um that happened at the language level been discussed and maybe this is a silly question that we don't need to spend a ton of time on No, no, I mean I think your question is relevant, but I think we it's important to draw the distinction of like what where the language ends and where other things begin. A lot of what people associate with JavaScript aren't actually part of the language. They're part of the host environment. Um so for example, JavaScript the language itself has no IO, right? Um IO is a big uh vector for where you will have a tax service. Um so that stuff is part of um web web platform specifications whether that's DOM or URL or HTML. Um so uh the standard lib things that uh we're talking about that node have added uh I I I guess I' I'd need to know which ones in particular we're talking about but most of the security surface area um tends to be on that side of like the host environment uh the runtime. So, you know, web platform or server side runtimes like node and it and and it and it doesn't get down to the language level things. >> Yeah, I know it makes sense. I think I'm I'm I was thinking about this with the sort of like low dash perspective uh which is very much uh uh not IO but like more related to um but I I but I think you're both the No, thank you. I think like this is a great explanation. >> Um, question Eric and Michaela, how did you get your new contributors? Was that through the Google Summer of Code? Did they show up? Was the through referrals? Because what' you get five new out of what 12 to 24? That's pretty good. >> Uh, yeah. I I think some of them were basically active users in like our issue tracker or like submitting a lot of PRs and then we're like, "Hey, do you want to come, you know, attend a meeting or something to uh if like for example, they're presenting an RFC or if they um they have like PRs that we thought were good and they would probably benefit from being inside like our our Slack workspace." um summer of code we we did get like a lot of interest from uh or like in the past from like the students they they were always like okay you know it'd be nice to stay but then also sometimes they go back to school and like they don't have time for it. So um we we definitely have less expectations of like converting some of our code um contributors to full-time maintainers. Um >> yeah. >> Okay. Uh and oh I I think maybe also one thing is that a lot of companies use Electron and some of the maintainers that we've gotten are specifically that we've invited to our maintainer summit uh in the past and u been like hey do you want to join a working group it'll give you this this this kind of like um extra privilege permission access to the project and I think uh it's like a nice trade-off of like a little bit of their time and um in exchange for being part of the group. Yeah. >> Cool. Great. >> Yeah. I don't know if you want to add more to that. Yeah, sorry I've been adding things to the comments of >> not the best. Um, so I think um in general a lot of people um recently with specific um subject areas that they've been interested in and support areas. Um I think off the top of my head um the individual uh particularly interested in Linux uh really came in and started adding a number of Linux PRs. Um and then we reached out to sort of get more uh feedback from them and that sort of grew it uh naturally in that way. Um another individual uh started helping out really in uh the uh issue tracker and um wanting to provide aid um to people. So then similarly naturally brought them into the fold um in that process. So a lot of people have just um been taking initiative in specific subject areas and then we've then as Eric said reached out to them um and sort of naturally formed that process. >> Awesome. Yeah, you proactively reaching out I think is a lesson for all of us. Right. So, >> I was going to say congrats to both these six major releases in a year. That is uh amazing. You know, I I was curious on the LLM package. Is that something you all see that could have more cross, you know, project use? Um I was looking at the API just on the MPM package. It looked potentially like something that we might be able to use. um in Navcript for example on the desktop. What what's your experience so far in that? I know it's a new new realm it looks like. >> Um I think we had that kind of as a spike initially when people started um being like hey what can we do with LMS in the desktop space? Um I think um Michaela correct me if I'm wrong, but that David um who's also at Microsoft um was working specifically on potentially refactoring that package to support the new prompt API stuff that we were trying to integrate uh natively. I don't know if that's uh taken taken off yet, but I remember that being part of the plan. So I don't know. It's kind of so that initial uh sorry internet that sort of initial is what the electron LLM package um was uh to try to satiate um and basically give people a taste of what Electron um in the LM space could look like. But as Eric mentioned uh David uh that Electron prompt API um RFC response. Um and so at this point we're sort of trying to see where people um might be interested in incorporating uh that functionality. say if that is something that you think uh could be potential interest to you all definitely reach out um and we can see about um sort of what that but at this point it's sort of like a a response to um a lot of electron um LLM asks uh that both of those uh came into being. >> Makes sense. Yeah, it's interesting because I know it mentioned Llama. It'll be interesting with Apple Foundation models as well going through there. Yeah, thanks. I was just curious. >> Of course. >> Um just for those of us who haven't followed um this this builds on um Chromium um APIs. >> Yes. >> Uh the the AI thing specifically. Yes. Uh let me try to find that. Um >> it's like not a stand like a web standard or anything. Um, but I do think let me Yeah. Uh, let's see. So, here's the RFC uh link that I'm just throwing into the chat for more information. Um, I also again, sorry, um, internet has been in the chat. Um, we also have >> that has been underlined here and I can send out uh the presentation later uh so that people can access those links. >> Okay. Yeah. actually. Thanks, M. I think that helps a lot. >> So, it uh links the uh Chromium built-in API um or sorry, built-in AI link there as any other questions, folks? If not, uh, thank you. It's a really great presentation and, um, you know, number two in in this great series. So, I'm, uh, excited that we've move forward on this. Yeah. Thanks, Eric. Appreciate it. >> Thank you. >> Cool. >> Um, shall [clears throat] we jump right into the agenda because, uh, item number one is something we should talk about. Uh so um and there's an issue open to reorder this agenda the the the meeting um layout here uh to kind of put that stuff at top. But regardless uh the first item on the agenda is CPC discussions explore optin ad network and revenue sharing for projects. Uh Robin would you like to um tell the group about this? >> Yeah sure. Um yeah, I met with the folks at Carbon who have been running the advertising for the Mozilla Developer Network. They uh basically sell and serve the ads in a privacycentric way. They're curated um in partnership with their customer which is MDN. And so they proposed a model uh similar for us. Um I really sort of love this idea. We do do sell sponsorships, for example, for events and we have logos on our event pages. Um, it's a little different than membership, but I thought this might be a nice way to continue to diversify our revenue stream and and do a revenue share back to the projects. Um, we h have proposed kind of a different split this time, 50/50, because this is something that's more um that has more responsibilities for the foundation to help with that. It would be implemented through the project websites. Again, the projects still have control on where that runs. Um, and if you look at MDN, I want you there's two different types of ads. They're the ones if like you click on the CSS or HTML, you'll see ads along the side. Those are the kind of the traditional ads. Um, and then the ads on the homepage are sold separately and so the project can decide whether or not they want to do that because those are quite um those are more prominent but they are uh they do sell at a higher rate. Um they have mentioned that you know eyeballs are going down with AI but they're increasing the prices and that hasn't seem to be a problem. Um they're working with other open source projects. they uh their some of their customers are like Google and IBM and Sentry and you know all those brands that we know and love um and serve developers. So I think that's sort of it in a nutshell. I try to capture as much of that in the issue. Uh we did have a board discussion about it and they were quite supportive but again this is uh very much project uh optin. So, um, we definitely want the CPC to form an opinion and advise what the board should be, uh, thinking about and voting on in our next meeting. Questions, comments, additional contexts, Joe from the board. You know, I think the the kind of um response that you would expect from people who want to be thoughtful about this sort of thing, you know, just um making sure we're taking the right steps and the right sort of ads and and things like that. Um if I remember correctly, there were some questions about the revenue sharing, but uh I don't remember exactly. And I know sometimes when people propose partnerships to us, sometimes we'll analyze, is it worth the the legal and the staff and the project time to get something up? Is there enough of an ROI for the foundation? Um the folks at Carbon put together a very professional presentation, looked at uh web traffic of our projects, and then they they put together an estimate and then they cut that in half to be very conservative. um in even cutting that in half was you [clears throat] know quite significant. You know they were saying up to 800,000 for the first year which would be quite significant. Again I would even cut that in half again based on our experience on how long it took to ramp up our like our hero devs and node source and other programs through our ESP. Toby. >> Yeah. First of all, um I mean I know people have a different relationship to advertisement in general. Um and I get that. Um but I think um the um economical reality of open source and open source foundations um and um sustainability and security of projects um um it has um created a an environment uh where um it would be risky uh for the foundation to rely only on membership going forward. Um and and that anything um that we can do to diversify revenue stream for the projects and for the foundation uh we should seriously consider um and try whenever um there are whenever it sounds reasonable. Um, and I think the CPC's role here is to make sure that um this is done in a way that um it works with the projects that want to opt in and um doesn't create issues for the projects that don't. Um so so I think that's a that's something very important to to keep in mind as we you know discuss this moving forward. Um I I do want to say again Robin thank you for doing the that the work of like trying to seek these different uh funding strategies. Um you know the ESP is a thing that I quote um mention on a very regular basis because I think it's a it's a novel um program and it is trying to solve a problem. I think this is another one um and it's been discussed for a very long time as a as a way to uh sustain open source projects. So so I think that's great. Um for me there are also sort of you know if the CPC sort of moves in the direction of approving this um there are specific things that I think we want to think about um up front. uh one is make I mean quite clearly if this is curated it means someone will do the curation um uh and I'm I'm expecting that's essentially going to be um the the the yeah the the advertiser the advertiser um but if you know if there are specific requirements that projects have um that we um bake this into a policy upfront um rather than reactively uh down the road like what happens if like one project one doesn't want specific ads from uh let's say um you know maybe uh something that could be a competitor of that project as an example right like I think we need to be upfront with this and and sort of like have um a minimal but like um clear upfront way of dealing with uh that um and that um the CPC should come up with something Um, and um, I think I had another point, but uh, I think I lost it. Uh, so yeah, just I think it's great that we do this. I think um, that we consider this. Um, I think that if there's, you know, um, if there aren't objections, we should move forward with it. Um, and, uh, Oh, yeah. No, that we should be preemptive about policy. um and that we should be and you mentioned this careful about what it actually means in terms of u financials um so that we don't um very much underdeliver on the outcomes u because I think we went through this um with ESP and I don't think it's good to go through this another time. I think there's general agreement here but I just want to make sure that we're careful with this too. >> Yeah. On the flip side, we've had discussions with our attorneys and our board. If we were to end up making too much money, then we would have to look at some different structures. We we do withhold tax on the ESP program because if we do reach a certain thresh threshold, if it's over x% of our budget and the attorneys aren't quite sure, that could trigger us paying taxes. So, we have been uh planning for that and setting aside tax dollars. So, we would do the same with this project. I think that makes sense, right? >> It's an optimist speaking. Yeah, >> exactly. I was going to say it's a nice problem to have. I mean, we over taxes on profit is a nice is a nice problem to have. >> I know. We definitely overestimated our first year with the ESP and we had a reforcast when we voted on our second half of the year budget. So, yeah, message, >> right? >> Yeah. >> Yeah. But I think it also speaks to like the communication between the projects and sort of like so having a better understanding of what exactly is requested. Uh you know so that projects understand like you know if I just put an ad in this corner will that work or do I actually need to plaster the whole website or you know like these questions like the more we have these questions answered uh upfront the better it is and sort of like the the less tension disappointment there is. >> Yes. Yes. If you hide the ad, it's not going to be Yeah, it's not going to work. >> The numbers are not gonna right. I mean, it's Yes. It's just like um so that I mean, I think it's easier to get a sense of this with advertisement. Um so, I'm I'm expecting less surprises here, but still so that there's um you know, a a common um Yeah. that there's no bad surprises or no disappointment. >> Good point. Good point. Yeah. I I want to I want to second the appreciation huge effort on this Robin for sure. I mean it >> we have something we can share here because we we did actually work with Bitter Brains on the banner that's on the Navcript website at the moment. This actually answers one key point that we've been trying to resolve with this is that all the money that comes in through that advertisement goes back into Open Collective and the sponsors. But it'd be great if we could change that direction to go to the foundation and maybe the insight from that banner helps resolve some side of the question in terms of, you know, the impression and where that lives, you know, it's just a banner on the top, you know, and it's across both sides of homepage. Obviously the the exposure of that project is probably a a small fraction of of other projects that are in the foundation but at least it provides some insight. Um but however we can facilitate >> transferring that bitter brains um direction to the foundation and maybe it can be a start into >> collecting some ad revenue from something that's already hooked up there >> and it could be um I've talked with Carbon about bringing on additional partners that they collaborate with to help scale through the partners and through their own sales network as well. So, you know, that's always an option. But yeah, we're definitely feeling, as Toby mentioned, the the pinch with corporate members as new AI foundations are spun up. I'm sure you all are when you're sitting in your companies trying to advocate why OpenJS over XYZ Foundation. So, um, diversifying I think is a way to go and, um, you all and we all own these trademarks and I think this is a, you know, not, you know, people again may be uncomfortable with ads, but we do promote our sponsors all of the time. So, I didn't think it was too much of a stretch. No, >> I mean as long as it remains optin for projects, um I don't see why we should not do it. I think I mean I don't know what the terms of the the agreements are. Um but we want to make sure that like there's uh enough interest from projects for it to make sense, right? So um um you know if like no project wants to do it then like it like it's let's it's not spend like resources doing that. So I'm not sure how you plan how you're thinking about this and I think that might be useful to to consider or discuss. >> Yeah. I'll come back to Chris. I think we had 11 projects almost immediately opt into the ESP program. So So that's that's if that's any indication. So >> I don't know if it is. I >> don't know if it is. It is a little different but you know I think in the financial incentives I think and the money going back to the maintainers is definitely it's been nice to see the maintainers use that money for documentation infra infrastructure support events. Uh Chris, >> um yeah, I just wanted to mention some of the projects websites receive uh a huge amount of traffic. Um, and depending on where they're hosted for free, there may be like terms associated that they're for non-commercial and putting ads up may uh come into conflict with some of that or or may be subject to some um I don't know stipulation. So um obviously that's a sort of more of an implementation detail uh rather than hey do we want to do this? or projects interested in this, but >> it should something we should look into. >> Yeah. And to be clear, like depending on the website traffic, that traffic that goes, for example, through Electron, that revenue would be split with Electron. It's just not all in one big bucket. So, >> have you talked to any projects yet and got any? >> Not yet. I think what we did with the ESP is we did a town hall and got their feedback. I think that that would be a nice next step. >> Great. >> Yeah, I think that makes sense. Um, it's the next step. I mean I I don't know if you want to like how you know if you move forward with the agreement and the board approval first um or um and then you bring the project to uh a town hall or if you do the town hall and and then I mean that that's sort of like operation operational and up to you really up to you and the board. So >> we're not having a board meeting in August because of the the event so it'll be September. So, I think doing things in tandem is fine. And then I can have the attorneys in tandem start to think through the agreement. Okay, >> cool. All right. I'm glad we talked about that. >> Good. Speaking of projects, there's one I don't think there's one thing that it's not on our issue. Nathan, are you ready to share your app, your OpenJS app? Um I don't have anything on screen but um certainly we can chat about it. You know obviously you all do a ton for open source and all these projects including including us and it's really an appreciation uh for the foundation if everyone finds it valuable. I think our hope is that you know it could become an open- source project you know others can sort of make it what they will um anything that's useful to facilitate foundation goals. I mean, I think one thing I've always looked at from an outsider before we were involved in the foundation at all is just understanding what the foundation does, um, you know, for projects. >> Back up and tell them what you built first. >> Oh, sure. Well, I prop I I proposed a uh a mobile app for the foundation and it it really kind of pulls together um the primary sources, which is project information, um CPC type of uh documents, everything that's going on on open agendas. It's meant to give you sort of a snapshot real quick every day. Uh, the reason I knew about this meeting is because I actually saw it on the home screen right here and it told me there was an 11:00 a.m. Pacific cross project council meeting. And so I thought, well, I'll attend. And it's good to know what's going on because I think the calendar I had a I had trouble with the calendar even syncing with my local calendar um I think last year or the year before. And so I was missing things. And so I think um maybe it helps people stay more in tune as to what's going on. That's the hope. Um it's in a public beta channel. Everyone can try it. Um I can share an Android link too. Um it actually has already passed Apple approval and Google Play review, so it's something we could make public any time. Um the repo itself could live on the foundation org um and just be an open- source you know reference um for at least foundation level projects because you know it uses all foundation project level tech. >> So yeah there's something I can share about it. I don't know how well you can see, but um you know this is really the snapshot in a go. Gives you kind of a >> calendar. Oh, there you go. Yeah, >> I have the same. Yeah, >> this this brief can become better and better, but you know when you tap it, it gives you sort of an initial outlay of what's coming up next. It'll tell you immediately, is there another meeting today? Are there meetings tomorrow, next week? And it'll give you open for objection. This can get smarter and smarter. And so I think the primary function is that you know get in do the brief know what's coming up immediately. I think um Jordan mentioned logging into GitHub which is smart because it could dial and filter the meetings just for that person. Um and I think also probably isolate it down to what's pertinent for each person. You know if there's something that's open for objection that might only be relevant for a certain pool of people. So I think the more it can be smarter on, you know, what what each member needs to pay attention to, the better. So it's meant to be kind of a tailored experience for your involvement of the foundation, but also kind of spill out other things that are going on because maybe you want to be involved in something else, you know, but otherwise you just wouldn't know. Um, that's the whole point of it. >> Okay. Well, I didn't know where you were on like how public and whether you want to do a soft launch with the community or you want to go go big. >> No, I appreciate that. We we are planning a 9.1 release this month and certainly like alongside that release, we could potentially mention something about this. You know, I think if the if everyone here and and others, you know, think this is a good idea, you know, to do and make this public on the store, I think we could publish it this month. Um, let others try it. Um, make sure the the source code itself is I think it'd be better under the OpenGS Foundation or on GitHub than anywhere else. Um, and just make it a public resource. you know, anyone anyone can contribute to it. If they have an idea that they think would be better uh or more valuable to to add into it, people can can get involved and and do so. >> Okay, cool. So, maybe in the CPC channel and Slack, you want to share the links and people can give it a whirl? >> Yeah. Um, yes. Let me maybe it's better I'll just email because I'm I know you'll lose the Zoom chat when we get out of here, right? >> Um I think I'll just email the link again. I can't remember if Joe was on it or Toby was on the initial, but um I know a few people probably have the link. >> Yeah, >> send it to this. We do you want us to email a link in the description to the CPC list? >> That would be great. Is the Slack is there a Slack channel that's fair to post this in? I think >> the cross project council >> that's what I'll do. I'll just post it in there. >> That that'll Yeah, that'll be better. Can refer back to it and yeah, if anyone has comments, feel free to, you know, it's the way it is now is certainly just an initial um pass at it. I think it continually get better. There's a search in there. So when you go to the search, you know, I think this can also get better to do deeper and broader searches. Um, it does a pretty general decent search of what data is in the app. So, you know, if you're looking for something, the idea is that you could find it very quickly there. Um, so hopefully that could get better and better. Yeah, I'll share something in the CPC channel here when we get off. >> I love this. I like having my app on my home screen. That's pretty cool. Um, >> this is this is really cool. Um, and it kind of makes me think that it would be really nice as you launch like 0.9 um and start talking about this project that you come and present on uh what you all have been working on. [laughter] >> Yeah, I was I've been talking about that with TC. Yeah, maybe in September because after this release it would be great because Yeah, we do. We just updated the latest V8 engine and it is a it is a very deep >> update actually for a for a minor. >> Yeah. And >> Kylie's Kylie's plugged into that too on marketing that in September. So, >> right. >> Yeah, we br a lot to talk about there. I'll save it. Save it. >> Yeah. So, so uh um when like I don't know like um next next meeting or something we should um or once you have a sense of when you'd be ready to come. I think that would be great. Ben's been sort of like on charge of this agenda. But but I think u um we can sort of like pencil you in for like I don't know end of September or something. >> I think it's more me now because then I just >> oh >> ping our maintainer friends and say hey can you do this? >> So then Robin that would be great. >> Yep. Um a and just uh like a one last little point that I do want to make sure that we get to. Um if you're all at render next week, um I think we should cancel um the working session. >> Good point. >> Mhm. Yep. >> Is it the same day or or close enough? >> Yeah, both >> kind of flying out that day. >> Oh, yeah. Flying out that Yeah. >> So, I mean, if lots of people won't be there, then it doesn't really make sense to have a working session. Okay. >> Yeah. I don't know if you can do that, Robin, or I can drop a note on the CPC channel. >> Okay, you can do it. Yep. >> All right. Great. >> Awesome. >> Anything else for the last few minutes? >> Toby, thanks for mentioning the presentation. I'll keep you all posted on a date. Yeah. Whether that could be September. >> Very cool. >> Yeah. >> Uh I'm just going briefly through the the other open issues. Um I I think 1794 is like a broken link in the COC and that might require like someone else to a plus one it um and I think that's it. That's new. >> Yeah, we just need to give guidance, you know, work on the guidance for projects too and then um you know u related stuff to that. >> We're getting more spam on Slack. some that's just random stuff. And then we had kind of a dangerous one. So if you see anything, just please just take it down if you're uh one of our admins. >> We'll do. >> Awesome. >> I approve that PR to you. >> Okay. >> All right. Great. Awesome meeting y'all. Lovely to see everyone. Thanks Nathan Demo. Michaela and Eric for uh the Electron stuff. Uh all good stuff. So, um, thanks everyone and see you perhaps in Atlanta. Otherwise, we'll see you in two weeks at the next meeting. >> Yep. >> Take care everybody. >> Bye, folks.