 I'll say hello and then we'll get going. Hmm. Great. Thank you everybody for joining another episode of the cross project council meeting. Today's the 25th of May. And yeah, thanks everybody for joining. Before we get into our agenda, do we have any announcements? I know a big one. What is it, Joe? Open JS. We're all. Someone got some details they want to share. That's just this little shindig that we're putting on next week. It's become so awesome. It's become a two day event June 2nd and 3rd because we have not only wonderful content on day one, we have an incredible workshop brought by the IBM developer team on day two, as well as a number of speakers who have signed up on Slack channels in time zones around the world. So hopefully you'll find one that works for you. So yeah, June 2nd and 3rd we'll have speakers ready to chat. Yeah, that's exciting. Anything else to add? We're really all hands on deck on this right now. We're just like down to the last just over a week and pulling kind of all the content in and making sure everyone is ready and aware of like the opportunity to chat with speakers and obviously also the signing up for the workshop and stuff like that. So I feel like the only thing that exists right now is Open JS World. So it's possible I'm missing something. Well, the URL is openjsworld.com. I'll boost that. And if it's not clear after you register, anyone watching now or later, definitely check out openjsf.org slash collaborate to join our Slack and things like that. So yeah, we'd love to have you join in and have some fun with us. Cool. So any other announcements or anything like that or anything from the board anything before we get into the agenda. The board meeting for this month was canceled. So the board meeting, but as always, we don't necessarily have to wait for a meeting. If there's something we need to get approved or whatever, just let me know and for Sarah know, and we can make sure that we bring it, bring it through an email type boat. Yeah, we have a US holiday on Monday. So our board meeting was Friday afternoon and we were going to be missing a few folks. So yeah, the wait until June. Yeah, makes sense. Cool. Without further ado, then I will switch over to the doc here and get into the agenda. The first item is issue 762. This is approved the NodeJSTC charter revisions. Did I not approve this? I thought that I had. And this is almost two weeks old. So I'm going to put my LGTM on there. I remember reviewing it. When this came up. So if others could take a look and make sure everything looks, you know, there's, there's nothing that you want to call out or put your thumb on. Please do so. Anything to add here, Michael. I'm just quickly looking at the charter at the. The process. So charter updates. Proving project charters. Right. Okay. The press has approved when there are no outstanding objections. There are two more approvals by voting DCPC members. The board has been consulting the case substantial changes, which is not the case in this. And it's been open for 14 days. So yeah. So it's basically, please, you know, take a look at your plus one. But it sounds like as, you know, once we hit the two weeks, we'll, we'll have met the requirements unless there's any further discussion between now and then. So that's good. Great. Cool. I am finding the agenda again. Great. Okay. So yeah, take a look at that. Moving on. If you all don't mind. The next item is poor quest seven 60. This is moving NVM from incubating to at large. I think I had some nits, but those are addressed. And we've got some other approvals. This is 14 days. This seems like this can go to. I'm not mistaken. I believe it can. Great. Shall I just. Drop that in there. Oh, that's the wrong one. I will merge this while we're hanging out. Yay. Cool. So that's good. Cruising right along here. Next on the agenda item puppies. You can't wrestle on my lap. It's not going to work. Put me down. Next item on the agenda is reminders for longterm events. I don't know. I don't know. I don't know. Tierney was going to look at some GitHub action stuff. This is essentially as Toby comments here, a placeholder. Press to remember to implement something. I don't know if there's really anything to do at the moment. Yeah, I think this was also something. And we were going to. Add to. We were going to add to that. But having something. To automate, say an issue creation or something like that. Was what Tierney was going to look into to make it even nicer. But I don't, I know he was very busy and wasn't sure that this was something that was going to be. High priority. Yeah. Yeah. He and I talk about. We have a lot of stuff that we want to try and get done to make. Things like those in open JS as well as the node space to, to work better. One comment. I'll just make really quickly and then turn it over to Sarah. Maybe we can use this issue to just capture the specific events that we're thinking about, you know, the elections and anything else that we need to do. Sarah. Yeah, that was going to be my question. I don't know if we have a list of things that we want to put in the open space. Maybe this would be a good use of a working session. If once we have that list together, I don't know if people want to watch each other set up, get have options, but sometimes. Like that's kind of what's needed. It's just like me making the time. That's a great idea. I think mostly I think of the elections because those are. But I know there's other stuff too. So it's a great idea. I think we can use that for the longer term. But I think we can use that for the long emergency. It looks like for Joe. No Prob. So maybe we'll capture that and we'll use that issue to capture those ideas as well. So I know there's the voting. Member from. Voting members from impact projects. Voting members from regular. CPC membership. And I think that like that's the immediate ones that are coming to mind, but. Write that down in the issue. Does this still need to be on the agenda. I don't know if it needs to be. As long as we just kind of. In the back of our heads, I don't know if it really needs to be on the agenda per se. So I was thinking like if somebody's got it, but it's not a short term thing. Having it come up every week isn't necessarily needed, but. Yeah. Yeah. We can take it off or we could just, you know, breeze over it. We should have maybe a label for like, you know, secondary. Don't don't let this slide kind of things. Well, we had that on the TSC and they never got that. If you, if you want the painful reminder, just leave it on the agenda. Yeah. Right. Like if that's what you need, if that's what's needed then. Or, but if it's somebody, you know, somebody's actually got the ball and they're going to run with it. We don't need to ask them every week if they're, you know. Yeah. Although I predict and I'm not opposed to taking the label off. I predict that the next time we need this, we'll be like, don't we have an issue for that? That's my prediction. That's a great prediction. Yeah. But we can see, I think taking the label off is fine too. We'll just get, get back to it as soon as we can. I'll, I try to review the issues and PRs when I can, when I'm not totally swamped, but so we'll, we'll work on it. I don't think we need the agenda label on there. I also like Sarah's suggestion of maybe it could be a working session for, and maybe there's a time where like Joe and Tierney and a couple of other people have, have time. We could just set aside an hour to like, pair slash quadruple program a solution for this. Agreed. Cool. All right. So, you know, we can consider that for a working session in the future. I'm not sure what the schedule is, but I guess maybe it makes sense for Tierney or I or both of us to make some progress in the future. So, I think we'll get to that first. But let's keep that in mind. So if we move on. The next item on the agenda is issue 756. This is create proposals for the community fund. This is, you know, this issue is meant to be a placeholder to track those proposals. I don't know if we have much yet. I think this is something that he opened up a couple of weeks ago at initial proposal for community fund logistics. Does anybody have anything they want to add to this or talk about? I think this one would be a great one for a working session. Like what Brian opened was more, how would we potentially manage these, but not what would they be, right? So a working session that on what else would it be that people would, you know, would want to be able to approve. And I guess, because it relates to that other one, at least in my mind, whether just a blanket, you can ask for anything. And that, you know, the way the process is written by Brian. Leaves it open to like. I come up with a new idea how I want to spend funds. I just ask for that, right? And I'm wondering whether we want that or whether we want to, sort of as a CPC said, these are the kind of things. And here are the approval processes for each. Or maybe just the anything is okay. I don't know. Yeah, I think what Brian and I and the team worked on, it was sort of more than process. It was a little bit of parameters as well. So if you take a closer look, you'll see like, must not already be funded at the foundation level. You know, must be related to one of our projects and things like that. So there is, it's scoped a little bit, but it's not programmatic. It's not what programs. And I think that's kind of what I was, was trying to say was like, do we want to come up with the bucket? Like the concepts of where like, you know, like the travel funds are well-defined program versus they come with us with anything that meets these other parameters. Yeah. Like, you know, I would love that a brainstorm on programs, not just for the travel fund, but perhaps future grants and other things like that. So. Yeah, that's like, I mean, I think the travel funds there is a little bit different. But I think that the brainstorm would be what other things, you know, grants and for what? And are there other, other like, you know, certification support or all sorts of different things, but. Robin, sorry. Where is that scope? Are you saying it's part of the funding tool? Where does that scope currently exist? It could be linked in that issue. Let's see. Is it in 725? 725, I think was the one. That teed it up. Yeah. That's the one I think I just closed. So where's the doc that Brian and I worked on? Did it disappear? Is it the community proposal? It's 759. Yeah. It's a PR. PR. Dropping it on the chat here. I wonder if it would be easier. I just want to take a look at that. And I wonder if it would be easier to come up with a list of things. That this is for, or a list of things that it's not. Well, yeah, maybe both. So do we want to put this then? Cause I like, I do think this is a really meaty topic and worth a whole working session, probably a couple. Do we want to make this the topic of the next couple of working meetings? Because. We've, we've got stuff that doesn't feel. You know, super pressing, but this feels like one that's high impact. And the year is slipping by. We have budget. So let's do it. Yeah, I agree. Okay. Well, then I'll make this the topic for the next working meeting, which is June 1st. Assuming that that works for everyone. Knowing that that's between a Memorial Day and a conference called open JS world. Scary. Yeah. We may want to skip next week. So yeah. Okay. All right. So we'll cancel next week. And then we'll put this on the June 15th one. So everybody think that's fair. I hate to be the suggestor of canceling. I think that's fair. Yeah. Yeah. Okay. Great. What are we doing? Okay, cool. So we have. A plan for this one and we could move on. Okay. Next item on the agenda is issues 747. This is Slack moderators and volunteers requested. I know we've got a couple of people who responded here, but since this is sort of a last chance. To go over this before the event. I'm going to go ahead and go ahead and. Explain what the ask is and see if we can get any more. Yes. And actually, if you guys don't mind giving me two shakes, because I'm trying to update our. Our, our issue list really quick to make sure that we get. The working meeting. Scheduled. Properly. So. Give me one minute. Okay. And while you're doing that, I am looking at the working session for next week. So I can cancel that so that everybody has their calendars up to date. Excuse me. I'll be June 1st. Yeah. I'm going to mix this one. There's a standards working group meeting that, that day too, but I assume that we'll just leave alone. Okay. So I'm going to go ahead and get the standard script to see about their availability for the first, but okay. All right. Now I can. Now I've been that second. So. I will. Screenshare really quick. Cause I think that might be. Easy. So hopefully y'all can see my screen at this point. Sorry about this. We have a couple of things. One is, we've talked about this before, we just want people who are interested in supporting us throughout the year to help us moderate the Slack channel. And so if that's something you're interested in, let me know and I'll sign you up as an at moderator. And that means anybody who needs help can say, hey, at moderators, and you can help us. But the time sensitive request is the opportunity to help run Q&A for the talk tracks that we have. So you'll see in column B on my screen, we have automation and community and development in general and performance and security and all that fun stuff. So all of these tracks and the speakers have elected different time slots that work well for them to come in and do Q&A with our attendees. We'd love to have folks sign up. I've just literally just added this column A here to help us moderate or just be available for the speakers during their designated time. So if you're available for a chunk of time, say Wednesday afternoon and you can help moderate or just be active and say the development channel to support the speakers doing Q&A there. I would love for you to raise your hand and say me. So yeah, I know that we're recording. And so this is sort of putting all of you on the spot right now, LOL, to pick a time. But yeah, we'd love to have you in hand to welcome the speakers and maybe prompt discussion. Sometimes we just need somebody to ask one question to sort of kick off a conversation. Any volunteers real quick? If not, you know I'm going to come at you privately this afternoon, so. I'm noticing just really quickly the top time, 1400 to 1400 PDT, that should probably be 1400 to 1420. Yes. Excuse me. I was going to sign up for that time. That seems like a really short amount of time. And that, yeah. Sorry, Sarah. You'll notice too they are very short windows. It's not a long period of time. But yeah, 15, 20 minutes is probably all we need per section. And so the expectation. Oh, sorry. No, go ahead, sir. This would be the Q&A after the speakers session or is the Q&A after the speakers session. And this is happening in Slack. This is happening in Slack. Because of the way we're doing the conference this year, all of the talks are going to premiere after the keynotes. So we'll kind of kick off the speaker Q&A, a little bit of a time shift after the keynotes. But this will, I think it's because the keynotes conclude around 1 o'clock, I think. Is that right? So then speakers start signing up at 2 o'clock Pacific. But it's not the case that talk will have just concluded. It's possible that somebody's just finished watching it. But they all premiere at once. So you can watch what you want when you want. And then go to Q&A. Yeah. Great. I can sign up for some if you want to. Yeah. And some are the next day, too, right? And some are the next day. That's a great point. So on Thursday, the third, we start with some different availability, again, because we're accounting for time zone here. So 1 a.m. Pacific may not be everyone's jam. And we also were ending the keynotes at 12.25. And then from 12.30 to 1, before the breakouts are released, we're going to have a happy hour, which we'd love you all to attend. No alcohol necessary. I'm going to bring my pomegranate cherry juice, which I've just discovered. And I love it. But happiness is required, right? Yes. I'm bringing my water-flavored water. That's a great idea. So Sarah, thank you so much. I will sync with you in Slack for what times you might be available. But OK, this is so obviously staff will be around all day, both days. So but we'd love the community to get involved and ask questions, too. So all right, that's what I got. Thank you, Joy. What were we doing? Oh, yeah. Let's talk about CPC. Where is my window? Cool. So moving on, the next item is, I believe, one that's Michael merged as we were getting started. Yep, the ad travel fund allocation for 2021 is merged. Then the last one on the list here is the DCO ICLA guidance. And I assume this is still in a holding pattern, which is fine. I know that there is work being done. And that will happen when it happens. Anything else that we want to touch on or discuss or whatever? Where's my window? There it is. We could jump into a private session early, then, if that's the case. I'm trying to rack my brain about. I know there's other things going on, but I feel like I'm tunnel vision on this next week ahead of us. So I apologize for things I'm probably not thinking about, is all I'm saying out loud. I'm with you in apology and in forgiveness. That's OK. I think we have about over half of our folks met their deadline to submit their OpenJS world sessions, which is actually pretty good. So they're trickling in. So if you're watching, it's OK. But yeah, it's crunch time this week. Yeah. All of us. Yeah, lots of stuff going on. Cool. And I just looked through the issues and pull requests, and I don't see anything jumping out at me that we should be working on. Although I do see there is a project board for post-bootstrap housekeeping. We might want to see what's left on there and work through any of these open projects if. That sounds like an after OpenJS. Summer project. Not today, Joe. Yeah, no, no. I'm joking, not today. Cool. So I will stop the stream, and we can go into our brief private session and kind of have a short meeting today. So thanks, everybody.