 to the cloud. Cool. Alrighty. Let's get this party started. Hello. Welcome to another fun, exciting edition of the CPC meeting. This is a regular meeting, so that means we're going to go through all of the issues that were tagged with the CPC agenda tag on our GitHub org and kind of go that way. One of the things we do need to do today, which I'll put at the end for any other business, is figure out what topics we want to cover in our working sessions for May. As always, yours truly has ideas for you, but it's up to us, so we'll cover that of course when we get there. Let's go to announcements. Announcements. Who's got announcements? Obviously, we always have announcements about OpenJS World this time of year. In case you haven't done so already, we're really hoping that everyone has registered for OpenJS World. We did get the speakers announced on our website this week, and so we're really excited about that, as well as some of the Slack channels and stuff are starting to get set up. If you want to do some pre-event conversation about the topics or talk to some of the speakers, that kind of thing, join us in those Slack channels. Of course, there's still space for community talks from our projects, because we're doing this like Netflix style on demand. It's really easy for us to make sure that we're covering all of the content from our projects that they might have to share. If you've got something from one of your projects and want to make some space for a lightning talk or a short session or something like that, we can do that. Let us know. Those are kind of our OpenJS World-related things. The other little thing that I have is that tomorrow morning at 8am Eastern, which is definitely earlier than I like to have any meetings at all, but still, it's worth it. We're going to be talking with Marcos Caseros, who is a new W3C employee, but he's the chair of the Spec Editors Community Group, and he lives in Australia, so hence getting up at 8am. We're going to talk about that exciting community group and record it so that the rest of our standards working group community can watch it later. But you're welcome to catch that live, and the link to all of that info is in the standards repository. If you want to get up early and talk to the nicest Aussie in all of the W3C, Marcos, join me. I will be highly caffeinated at that hour. Project announcements? Anything like that? Whales wins? What have yous? I mean, I'm not ready to release it yet, but the next version of NVM will actually have limited Windows support beyond just WSL, like PowerShell and Git Bash and stuff. I'm using very hedged, fuzzy words around it, like maybe and things like that, because I expect a flood of bug reports, and I have no way to test them myself, because I have no Windows machines. But if it, assuming that it works, then a lot more people will be able to use NVM. It's exciting, congrats. Preemptively, congrats, and also preemptively, like, you know, condolences for the bug reports that you will likely get. All right, cool. That takes us down to board meeting updates. Sarah and or Michael, you all want to share any fun stuff? We had the board audit and finance committee meeting just before this meeting, so we did discuss the request around the travel fund, and there's going to be a recommendation made back to the board, so hopefully we'll have an update on that. As we mentioned before, you know, the discussion was positive, so, you know, just that we'll have closure on that fairly soon. Awesome. And let's see. That's it from that. Now I guess we can move on to our, our regularly scheduled slate of issues. Our first issue is issue number 747, and this is for a call for Slack moderators and volunteers for our newly formed app moderators team on our Slack organization. We want this for like two purposes. One is the long term sort of ongoing year from now and sooner, like, if somebody has something that they need help with, or they see something that looks spammy or whatever, they can just at tag at moderators, and whether Joy's online or Brian's online, this team would be able to, like, clean it up and handle that. The second need is actually more imminent for OpenJS world, but we're hoping to have is a team of us who are able to just help, you know, keep things clean and safe for our OpenJS world attendees who may be joining to participate, particularly in those chat channels around the tracks that we have, and to help MC and moderate those channels when we have the speakers available for Q&A. So this is my request. I know not everybody may be available to do the moderation on the day of the event, but if you think you would be around and available to do it longer term, you know, we can get you added there. Or if you'd like to raise your hand to serve as a MC for one of the channels, we'd love to have you too. Questions or comments or observations, concerns, volunteers? I would just add that we have identified four different time zone chunks where we're going to invite our moderators slash MCs and our speakers to sign up for that way we can hit every region around the world. So if you live in another region and you can sign up for a time that's convenient to you, or if you're here and would love to backfill some of those hard hours and other time zones, we'd appreciate that as well. So I will add those time slots on the issue. Okay, so if there's not any other questions, I know some of you've already like privately volunteered with me, thank you so much, but otherwise, you know, ping me in Slack or just raise your hand on the issue and we will get you all signed up. Honestly, doesn't look like it's going to be a heavy lift, but it's a good thing to have. All right, that moves us to a probably trickier and lengthier topic. This is issue number 745, the voting CPC members election. So as you all may recall, in our charter, what we do is have a couple of representatives from all of the CPC members elect folks to represent them in the voting CPC members group. We need to run two different elections as Emily points out, one for the non-impact projects and the other one for the regular members. So this is something that typically myself and Brian Warner as foundation staff execute. We have talked about finding ways to automate this so that we don't miss the election windows as we have done in the past. And then also too, we need perhaps to add some language to make it more clear that like in the event that we accidentally missed that window as we have in this case, that we don't go without these representatives that they serve until the next election is run, for example. So a couple of different sort of hygiene things that this issue has popped up. So I think the first thing that's very tactical and practical is we need to open a nomination issue for both of these spots. And then where we may have multiple parties nominate, run that election. Other insights or observations here, this is what the second or third time we've done this one now. So it starts to feel a bit more routine. So I guess my only question is what's the next step in terms of kicking off the elections? Is somebody got the ball for starting that? Unless there's something we want to do from a process perspective and differently than I would suggest that the next step is to open the call for nominations. We can do that on an issue and then also send it out to our projects list as we have often done in the past and kind of go from there. Typically that's been the CPC chair that kicks that off and obviously Joe's out today and we may want to go ahead and get this going so I can certainly copy pasta a past language to open this up. But I don't want to lose the the insights obviously that we've highlighted here one being a need for you know the language that may help us in the event that we make this mistake in the past and in the future and the second being a way to automate these issues so that we don't accidentally do it again because you know we probably will. Alrighty well so and also if I could just request somebody help take some notes here um I'm trying to uh I'm just taking a note that you volunteered to to create the issues right? Yeah I went to go do then the add the minutes from some of our last couple meetings and realized we hadn't done so good about taking taking actual notes so uh probably time to pester on that again thanks Michael. Alright um okay well I suppose uh if there's nothing further on 745 we can move onward. The next issue on our list is issue 744 this is an issue to remove growth project distinction on the open js foundation website and this one feels um seems like a brian issue yeah seems like brian ought to be doing that right now during the cpc and in fact yeah I'll take care of that right now okay it's like who's to say brian didn't already do it I don't know I haven't been to the website today uh so don't go for another 10 minutes okay okay thanks brian no problem cool um great great so issue 725 add travel fund allocation for 2021 so this is the update that that Michael just hopefully gave from the audit and finance committee meeting which was like literally ended right before this call so the the freshest news possible was delivered until and it looks like we're going to have um next steps and closure on this soon so uh thank you Michael and Sarah alright issue 699 um this let me scroll down and see what is the latest on this so okay and Sarah Toby's really the one running point on on this do you know um the issue hasn't been updated since we last met do you have have any updates I don't but Toby and I are meeting to uh to uh our meeting some time to talk about it so that's what I got um I think it might be worth having like a circle up so we can figure out strategy um would you like us to take this um agenda okay we can take it off we can take a label off leave the issue open obviously but then y'all could put the label back on when they're when you're ready to report something back to the cpc regular yeah that sounds great yeah I can get one update on my wall I think right now just so you know if you hear that scratching and if you see me just a quick update if you all saw I think there was a blog last week the Linux Foundation is building out a research division I've met a couple of times with the new head of research and flagged our request to do some DEI stuff as well I know it's maybe not the going to be super early on on the editorial agenda but it will come but anyways we can follow up when we have that other meeting but that's cool very cool yeah that'll be great if we can get additional support on that that's cool um the uh next item is 632 uh this is provide implementation guidance for dco slash cla and this has been sort of open for a while because we are working with an open source maintainer on updating the pro bot dco um so we don't expect it to move terribly quickly but just in case brian do you have an update on this yeah so I've been talking a bit with um with the maintainer and also some other folks who work on pro bot um the maintainer is busy uh but has said that they are able to review it hopefully sometime soon um I am trying to get some other eyes on this as well because that that may also help lighten the load um just basically making sure that the the pr which is non-trivial admittedly uh making sure that it does actually going to do what it's supposed to do so um if anybody would like to volunteer to do an unsolicited code review on it that would also be cool um but at this point it's it's one of these things where it's you know it's it's out of our direct hands um and we're just going to I guess have to continue to wait for uh for them to have the time to really get through it all right well thank you for your patience and working through that and obviously um you know uh thanks to the pro bot team too for their patience with us um okay that takes us actually to the end of our tagged agenda issues we do have things that were called out for any other business and because we didn't quite get an issue filed with the array tag in time before this thing agenda was generated um and that big big kind of exciting thing is uh anticipating the graduation of some of our upcoming our incubating projects nbm slash jordan is one of them jordan's got a project charter for our review and I think this is basically the last piece um we we met earlier this week yeah so I just dropped the link to the charter in the zoom chat it's not on the main nbm repo it's on my personal fork so it's like public it's just not advertised um I'm I was waiting to push it up to the main repo until uh Robin and Jory had kind of given me the go ahead to do that but it I think it's pretty much ready so feel free to review it now um it's largely I basically just took fastifies and like replace the project name and you know took out some sections that didn't really apply and you know so it's it's um it should be very similar to that and given that there's a single maintainer and no team structure or anything like that it's it's a much simpler uh governance at the moment so um we do require a majority of our um our cpc members to thumbs that up on so please take it take your time and go mosey on over and review and so we can get that last checklist item done for nbm the other two projects are anticipating their chart I'm anticipating getting copies of their charters for for you all really soon so um be on the lookout for that if we can get those approved as part of our kind of last mile thing then we can we'll be um well on track for uh just celebrating their graduation at open js world which we would be very excited to do in terms of visibility have we I'm trying to remember have we opened an issue in the cpc repo that says please approve this charter over here and then we can at mention the cpc members because I'm not sure we can do that on the issue that's in the mvm repo the issue that uh the checklist we're using is actually in the cpc like the uh project test project status repo um which is owned by the open js foundation so I think we can at mention everyone there um yeah we've got that but I think also Michael might be talking to um what some other projects have done in the past which like here's for example in the zoom chat here uh from fastify where Mateo just opened an issue that said you know fastify charter review and and here's here's the link um so is that what you mean yeah that's good that's what I'm that's what I'm thinking so that there's a clear place to have a plus one and you know that then stays there versus it's like we plus one the checklist I'm not sure if it's as clear maybe you could checklist uh comment or something but I think this makes it easily discoverable there's an issue there's somebody goes and looks they can find it it's in the top of the list I'll file that right now and we'll close it once we say we have enough people so okay thanks um cool so thanks for for taking a minute to go take take a look at that it's really important um for just sort of our last uh you know onboarding steps um and very helpful to the projects so thank you very much um the next any other business item uh is just to call out that we have two uh working sessions coming up in May and we should uh determine what we want to do what projects we want to work on with that time the last couple um that we have taken on include our um technical project strategy which was last week and and then prior to that was JSlandia and we've done some sessions on DEI and um code of code of conduct improvements um on that note we do we do have a PR um on some COC improvements that were was driven out of those those sessions ready for your review um so we could use one of those working sessions to um memorialize that PR or and or take up an additional uh improvement which we've we had identified a shortlist so that is one uh one's one option um a second option is you know going back to the technical project strategy we had a actually that seemed to be a topic that there were several avenues that we didn't quite follow all the um calves of in our first session um but obviously the options are boundless in fact and I'm just curious if anybody has a uh preference or dealer's choice to talk about Slack I'm also keen to talk about just like improving people's experience on Slack what's what's the issues with the experience on Slack just this context oh just like making it like really welcoming and you know making it easier to find sub chats that you might be interested in or you know that that kind of thing useful there's like 1400 good sorry I got a conference uh I think I think something that might be useful would be a little bit more guidance on like what acceptable use for the projects is like I don't think there's been any problems but I think uh having some like pointers on like what it could be used for uh would be helpful in like making it more of a good space for to actually like the projects to engage uh not that like like I think node has done a okay job I've also been the one doing it so of course I'm gonna think it's an okay job but like in setting things up um but yeah like having having you know different kind of recommendations on how to do things we might also want to get on the path of something like uh what CNCF does for the Kubernetes Slack where it's all managed through YAML and like people can't create random channels because like I can just create channels uh which some random person could also come create channels and like not great channels or something or like name things with bad names or something like that and we'd have to do do work um and that that might also help kind of codify how how this experience goes a bit more to uh if we kind of bake that in from the beginning of this discussion but uh yeah so sounds like Tierney would love to talk about Slack sorry I have opinions about Slack other other um ideas or preferences okay all right well let's let's do um let's do Slack and also the uh kind of follow-up slash take two of um that initial exploration on tech project strategy that we started another idea could be maybe identifying other potential collaboration spaces that we would see would be helpful for the CPC to help drive Michael what do y'all think sorry I was just distracted for a second what was the question again maybe use a working session to identify some other you know uh collaboration space uh topics that we would want to encourage yeah that's a good idea or I mean we could continue on sort of related to that we could continue on with the strat you know we're trying to come up with that sort of project areas or I forget the word you the project portfolio strategy yeah I think we still have a bunch to work on that so that would that would be a good one cool um well I we've got many weeks worth of meetings potentially um I will take the opportunity to call out issue um 739 which has that schedule for the rest of the year um and so if there's actually a session that you want to host or drive for a working meeting for example feel free to go edit that issue make yourself a little you know spot and super do it you know so otherwise I'll I'll pester you once a month and probably more so there you go um cool and then uh the last uh the last thing that I uh wanted to share was was actually that pull request that I mentioned earlier um so the group had been meeting um for a couple weeks and then a small group went and took a pass at um at updating we've got a couple of outstanding sort of questions and comments which I think are perfectly fine for us to work out on our work out on our pull on this pull request but um thanks to Michael and Anton and Matteo and Joe and Sarah and Divya and others for their um work on this you know draft of the document so we're ready for for broader cpc um comment uh and input and I just tried to port over all of our all of the sort of outstanding comments um from from the doc from our google doc so reviews welcome there um and that happened right before this meeting so I don't suspect anybody has had a chance to read it so thank you um cool any other business oh Tierney's got a great little note uh Joe ran unopposed at the no js com com and will continue to serve as the com com rep yay Joe and abstention of course thank you Joe for continuing to do that uh other private news or anything fun anything fun nothing fun well you have squirrels that are going to fall through your yeah I don't know what's going to repeat that what is going on with the squirrels I don't know I just hear like in our walls you could just hear it scratching away I'm just waiting for it to break through the drywall any second just jump on my face I had that the other day and I banged on the wall a few times and they went away so you can try oh I've been banging on the wall I don't think these these are new york squirrels they're not interested they're like not afraid of anything that's great all righty well I think uh uh the squirrel report being concluded I will stop our recording uh there we go