 Cool. We are live and this is a meeting of the OpenJS Foundations Cross-Project Council Standards Working Group. We have a few of our friends. We're missing a few of our friends today because they are at standards meetings and there's always a standards meeting somewhere in the world on any given day at any given time. And that is where they are. So hope you're having fun, y'all. We start with announcements. Do we have some announcements we'd like to share today? Anybody? Got a couple. Always do. Joe, is there anything big in Node that may have happened today? And you're muted. Let me jog my memory. Oh, yes, of course. Version 16 went live today. Yay. If you go to NodeJS.org slash whatever slash releases, you can see the schedule, but yeah, 16 went live today and that's exciting. Congrats, Node. Congrats. I wore green in Node's honor today. Nice. No, I actually just thought about it. So in less exciting but still important and related news, the marketing committee meeting is just after this one, if you want to stick around and join us for the foundation marketing discussions where we talk about how we can get the word out about our projects, please do. And we also have a board meeting on Friday. And there's typically a public session after that so we welcome folks to come attend that as well. And oh, another just sort of like announcement type thing in just over a week from now. And there's Caseros from the W through C who is the new chairperson of that spec editors community group I mentioned at our last meeting and also in Slack. He lives in Australia. Okay, so, which means that's basically the moon as far as I'm concerned, it means I will be getting up at 8am to join a call for him at like midnight. And, but we're going to have a special meeting just to make that happen is going to talk a little bit about the, the community group, and we'll record that for our community. You know, we make it work. So I think that's it announcement wise. This the last thing this week will be publishing our schedule for speakers at open JS world we're just updating the website now. The location's already went out. So you should see that in the next day or two as soon as we have everything ready to go live so if you have not registered go to open JS world.com. And we'll just send you nice little calendar reminders it is free. Great. Great call. That's a good. Of course that's happening that's like one of many things. So moving from the announcements then, unless there's others. We'll go into our agenda for today, and some of our items, one of our items in particular we're going to make listed items we're going to make a private session which is the discussion on our statement. So that's a surprise. The first item is dealing with the recurring CPC working session. I believe we settled this last week. I need to adjust the, I learned today that what I have to do is move the calendar invite, and then the node, like me make meeting tool will be fixed and Joe is offered to help. So I think that will resolve that periodic issue that we have popped up, but just to remind everyone on those days where we do have this or actually think maybe generally moving forward we're going to have this meeting at 1pm Eastern. So an hour earlier. And that that should fix this. So thanks for working on that. Next, unless there was any other comments I'll just roll on because I think that was, that was pretty. Do you want me to move that meeting now. Yes, 1pm Eastern time every freaking time, every time. Right now, continue on I will make the change 1pm. And that takes us to our next item, which is public for discussion the education and onboarding resources standards education onboarding resources that we've been kind of trying to compile on, and I think, especially with some attention that's being kind of turned toward how do we help people gain the skills that they might need or want to have. And then it comes to getting involved in standardization activities sort of like the context, you know what kinds of things would be good to read what kind of, you know, videos or things. We've got, we've got a nice little list that is compiling here, we brainstormed on several last week. I think this is obviously something we'll continue to add to it's not an exhausted list. I think our question is that we, we started to discuss but not make too much progress with is how, what we want to do with this information, like, do we want to put it on a website, and we could have it even be its own standalone website so anybody, you know, from any organization could say oh well here's you know, here's stuff that's, that's helpful for folks who are onboarding into blank org, you know, or here's the perspective. You may not see because you're in the web standards world but here's how the hardware people do it or whatever. The conversation kind of got cut off there and so I'd like to pick it back up for a few minutes if, if folks have the have any ideas or thoughts on the matter. But the simplest be to just have a repo that has maybe, maybe one or two documents in it, and therefore get help take care of the rendering and also the whole process of crowdsourcing it's further development. We could do I mean I like the idea of, I'll be honest, I like the idea of a website for a couple of reasons. And it could be a totally if we use pages. Can actually do all of that. Yeah, that I think I think that's where I'm like, I'm capitulating is to say, if it's a static site on GitHub, I think, but I think it's a like a web URL. It feels friendly. You know, I don't know. But I've, yeah, down with a curated destination and in our marketing committee meeting this afternoon we're talking about a way that we're templatizing websites for projects so we could do the same with this but we can have a little more fun with it we could give it a name it could be a standalone thing. So it just might, like, maybe be easier to find. We could give it a cool name. I'm super into cool names. Emily arrows, excellent education. I'm thinking trying to think of another E word. I was thinking that the branding would be more about the open JS foundation. I'm okay with this if you want to make it all about me. We can make it. You know, it's an open JS foundation program, much like JavaScript landia but it can be, it doesn't have to be open JS law branded. It's useful for the community if it's helpful for a neutrality to not even have open JS I'm actually I'm fine with that too. I guess it's a good point like you know do we think it will benefit from not being affiliated with specific group or you know would we because I mean at the end of the day we want to see these things just help people. We're the people that are sort of putting any of it to happen it's not going to escape anyone's notice who's behind it. So, there's no point in hiding the brand just on it. I love that too, obviously. I mean that counterpoint, although I am I do like, you know, I do also selfishly think it'd be great for it to have open JS all over it. You know I wouldn't want somebody to think about it, run into it and think oh well this is just this stuff just applies to open JS. For example, you know, and so we just would want to make it clear I think that like, this is a not specific to open JS, but it's been put together by the open JS and, you know, it's it's like SDO forum neutral, instead of vendor neutral it's because that's where it's neutral neutral squared neutral neutral squared neutral cubed. Okay. Yeah, so as Robin said, one of our projects q unit made like a dead simple like very nice. Jekyll template that's that I think is what we're going to use for the JS landing a program it seems like something that's very easy for us to kind of spin up. And not check. I forbid it. Well, first of all, we're the JS, the open JS foundation. I also hate using all that garbage. We're allowed to use tools if they're good tools, even if they're pretty good, you know, listen, in a different language. I do sympathize with that argument, Joe, it did take me four hours to upgrade system Ruby three weeks ago for some unknown reason, but it works. I for afford websites because we used you know, we had to use certain. I probably won't work on it just FYI, because I hate spending four hours updating my Ruby and my jams and all that stuff so. Do you have Joe do you have the bandwidth for providing an alternative solution. Honestly, 11 is what I would use. It would be made about like JavaScript. Okay, but you know what we're doing the thing, which is a symptom of it's like, okay, this is great. Let's make a blog. What's our stack, you know, like, that's the But okay. So I guess that the request here just to kind of close this out is to continue adding to that issue. This is issue number 130 with your recommendations like things you would encourage other people to read, or like, kind of dip into if they just sort of learn. And the second thing is, I guess more of an action on myself and I guess Brian from like a spinning up the like a template site for our for this. And we got a cool name. So that's another thing. Find it. Think of a cool name. The mongooses. That's a cool name. Right. All right. I'm moving to unless there's anything else, Mike or send ill. So way in on in terms of the resource piece, like what would be helpful. Okay, cool. Let's go talk about what's happening in in our different community right now. So obviously, there's a meeting happening today into or yesterday and no today and tomorrow, which is a TC 39 today meeting so we should be hearing from our teammates there what new things are up for discussion. And looking forward to getting that report next week is the W3C's advisory council meeting. And they've released some of their like pre videos and homework and stuff for us to review and be prepared with I haven't had a chance to read or and take a look at all of those yet. But some important things include some process changes specifically related to what they call the director free W3C. And kind of some changes in their legal entity. That's a big topic for the AC right now. And there's also a handful of charters, none of which at the moment are particularly pertinent to our group for example the automotive working group, not really sure. You know that we need to weigh in on that charter but those are some of the things that are that are on deck. And as things come in that look relevant to us I'll be sending that out on our standards email list for y'all to to weigh in on. And then last but not least that spec Ed meeting as I mentioned at the top of the call. Repo has been set up there's a handful of about, you know, 1520 issues of tutorials or educational things that Marcos and and team want to create. So if you're interested in that community group anybody can sign up, and anybody can go and weigh in and subscribe and start watching any of those issues so that is what I know. Currently about. And when then there's the advisory board elections which will be opening up as soon as the nomination period closes which is sometime this month. Yeah, that's what I know about W3C. Emily anything from from from Unicode. You want to share the Unicode message for my working group is considering right now we're meeting roughly every two weeks. The last meeting was actually yesterday. We still have been for four or five months now. Maybe more stuck on determining exactly the shape of the data model that we're going to that the whole spec is founded around, and the latest decision is effectively to do, rather than try and solve the issue. Specifically, just considering the data model is to in fact start doing parallel implementations based on these two different spec versions on on the various parts of the whole stack that forms the message format to standard. Well, one of the, I have strong opinions here because one of the two models being used is primarily written by ZB Bruniecki from Mozilla and myself. I'll, my part here is to effectively next time implementing the tooling. If we were to go ahead with this version of the data model, then have the whole parsing from source to to form a data model and then having a runtime on top of that. And we'll continue to be reviewing this. We're hopefully going to sort of simultaneously with this work soon be able to finally get to talking about the canonical syntax for this whole structure, which is probably the biggest open question for which we don't have anything. So the other sort of deliverables of the whole project we have a decent idea of what they're going to be or we have two different ideas on what they're going to be. There's of course many things still to do. It'll take at a minimum months for this work to conclude. I hope it's only months, but it's possible it'll take more than that. Months as fast in standards worlds though. We've spent already more than a month on getting to this point. Well, I guess congrats on getting to this point. Cool. Well, thank you for the updates and I think we'll kind of continue because you because you had an item for private session that might build on this. Let me ask if I'm missing Mike or Joe or Robin or Sarah group that we need to check in on Miles is our OSI affiliate. He's been super busy. So maybe worth pink hancing if there's anything from that. They are. Yeah, I chatted with him briefly about OSI I think they are rerunning the elections. Yeah, for the board. So I don't know if y'all were tracking that I think there was maybe a process error and so just to be thorough they're having an outside auditor take a look at it and they're rerunning the election. All right. Sounds not so fun. Um, all right, any other business for our public chat. If not, we'll, we'll close this early and go to talking about our statements and stuff. All right.