 uh animal crossing no it was it's yeah sorry she's easier to play than trump anyway that's funny very good very good um cool so um we are live thanks everybody for joining another episode of the open j.s foundations cross project council meeting today is the last uh tuesday of march uh in the year 2021 we're working off of issue 737 um i see another attendee waiting oh i will unless maybe uh he was already promoted because i saw him on the list um yeah thanks everybody for joining uh don't forget to add your name to the uh the dock which i will paste in there and uh help take notes we've got a small crew today hustle through the agenda and then uh see what happens from there um do we have any announcements start there we've got a few and so uh tomorrow as an fyi i this will be super fun the web driver io team is going to do one of our um not we cannot q and a sessions we can't call it a ma because a ma's are this trademark term apparently a ma so that's true reddit has the trademark on on on a ma or ask me anything so we have q and a session we bring brandage uh and with the web driver io team they've got some exciting announcements that's tomorrow uh wednesday at nine a.m pacific um and so we'd love for you to join in listen and um ask questions and that kind of thing um other uh exciting announcements we want to say congratulations to nvm on their latest release good job Jordan and then um we also announced some exciting discounts on the new uh node training and certifications um well they're not new but uh there's some new features to that uh platform and celebrate where we've got some pretty deep discounts on the certification uh training materials and tests and uh you know check that out if you are so down um yeah and to add to that they're they're they have a bunch of free tickets to the environments to kind of try it out and get used to it before you actually do your training which i think was um a learning from uh people's uh experience you know their suggestions so um definitely check that out yep um let's see other sort of general stuff we're really uh planning forward on our um plan to announce open js world speakers really soon and so that should happen sometime next week we're really excited about the the talks we have so far um and so just reminder to register for the event if you haven't already that's on June 2nd um and i feel like there was something else we had a book club and the book club was really fun and i'm only saying that because there were people that said they were going to come to book club and they didn't make it and i'm not saying who that is but i'm looking at you in my zoom chat um we'd love for to do that again so please come on over to our channel wait who was that apologizing because i i think that was supposed to be me too that was definitely directed at toby i wasn't gonna call it out but i'm glad someone else apologized as long as there's more than one of us i think we're in the clear so uh we're looking for the next we're looking for the next book is like kind of the the thing and we're sort of uh chatting about that sorry jokes today uh so that's all the announcements i have the end well i dropped a link to the uh nojs uh tweet about the uh certifications and stuff too if anybody wants to help promote it or just find out more information it's a tweet read so um you know there are a few links in there for them oh no that's not the tweet thread that's a different one uh but that's still i think the right tweet right yeah yeah about the trainings um i guess i will say uh because i just confused myself that there is the uh node uh survey uh is happening um i think it's still uh happening i think it's still um you know open uh so you know the first 10 years were pretty good and we're looking for the next 10 years um and and there's a group of us who are trying to plot that out figure out what's important and stakeholders and and and you know constituencies priorities things like that so if anybody has um you know any input on that any thoughts about that feel free to take the survey uh here in this group or anybody watching live uh check it out um so that's another announcement um cool uh with that we can jump into um the agenda i suppose is uh was there any um sorry that was a bad page reload um was there uh is there anything from the board i mean i guess there's nobody here from the board but um i don't know if there was a meeting last week there was there was a meeting on friday obviously our our uh two cpc uh board director reps are not present today um so we'll have to get an update from them next time sounds good all right cool so if we are to jump into the agenda the first issue is actually from the summit repo issue 306 i think that this was maybe talked about um a couple of weeks ago um and i actually i commented here but i wasn't in that meeting so i don't know the conversation but i grabbed from the notes to drop it in there because we were talking about it in the um the no-jazz tooling um um meeting um joey you ran it last time did you do you have anything to um share on that front yeah so in our last meeting and after the discussion with the group president uh you know became pretty clear there was consensus for us to uh not plan on running any kind of conjoined event with the june 2nd open j s world and instead sort of keep the conversation open for potentially doing something else in the fall um there are a couple of like lf events that are more general like um open source summit north america and that kind of thing that are that are are still on for in person um and there was a conversation about whether that's something we might want to arrange um like a meet up there if there were going to be a chunk of folks who would be planning to attend one of those events um but effectively uh i think our our group agreed uh last week without necessarily memorializing this anywhere that we wouldn't do it with open j s world on june 2nd so um i'm not sure what we need to do to sort of update this ticket probably just maybe comment as such that we're keeping the option open for something in the fall that could be in person but but uh yeah yeah yeah we can we can comment on the issue um and just maybe keep it in mind um and the tooling group we were thinking we might do something in the fall uh but i don't know if we were thinking in person or or just online and i i wonder i think that the collab summit is a great thing uh the in-person ones were really uh effective the virtual ones perhaps less so but maybe that just presents an opportunity to figure out different ways to approach it and i'm even wondering if it should just be more you know focused one day things with each group you know like the tooling group could just you know plan their own dang summit online for now and you know spend a day working stuff but um anyway it's something i'm thinking about but i don't really have any actions or uh direction either could be an interesting um thing for just putting this in our in a future pocket like an interesting discussion to have at one of our working group sessions like if we were to take a topic of let's reimagine collab summits in a post-covid world what does that look like that could be interesting yeah i agree i agree um cool i had another thought but i think i just lost it so it doesn't matter um cool all right well we'll just kind of leave that where it is for now and um at some point we can take the agenda label of it but uh something to think about next on uh today's agenda uh private slack channel for no j s build team uh machine management closed since answered well no a closing since answered uh was not actually closed so i will close this issue um looks like everything is sorted so uh that seems fine cool closing that issue moving on uh this is actually the thing that i was thinking about and then lost it um travel fund allocation for 2021 um i don't know if this was discussed uh last we did discuss it last time okay um uh what michael sharing with us was this had been brought to the attention of the board that had to do further discussing about it and come back to us okay i'll come back was some movement around it yeah yeah okay um the gist is that the travel fund was uh diminished uh uh i don't want to say i don't want to be hyperbolic a lot um and the thinking is that traveling by two thirds might be yeah i was going to say drastic but i don't want to be um um it was two comments that were made of one by me suggesting that the money um saved that way should be reinvested in other um related efforts such as diversity and inclusion which are tightly related to this fund and i think um uh tyranny brought up the fact that many people had complained that in the rest of the world people were actually traveling now or were able to and so it felt very um american well western centric to have that perception yeah and also who knows we're not even halfway through the year things are gently improving um will there be more travel on the second half of the year you know what i mean it depends on what continent you are in but uh definitely i'm hearing really good things from north america right now less so from europe honestly i don't know well they're warning about a fourth wave here so we'll see we'll see all right well i guess there's not much to take from there sorry go ahead yeah for what is worth at microsoft we still have a no travel no participation in online events worldwide just as um so of kind of respect of how things are going in other countries uh so we don't want to start doing things in the us if things improve if in other countries are nothing going okay i think so we are in a no travel situation for now yeah okay that's uh good perspective thank you and you know i can report that that this is under discussion with the board committees um but i'm not sure what the exact status is um other than to say they were keen and happy to take it up and figure something out so yeah the response seemed to be rather positive that was my understanding too i'm sorry if that might that didn't come out in my summary cool well we will uh defer this issue uh till next time and see if there's any sort of updates moving on the um this is uh issue 711 um this is uh renaming master branches i think that the rename has largely happened and if i remember correctly scrolling down suggestion to email folks i'm pretty sure i saw that email go out um confirm that for me jewelry yep i did great so do we think i mean i guess we can check off the standard commission communication channels encourage other folks uh possibly create a dedicated place which i think we decided would just be the info channel um and eventually address issues uncovered by projects implementing this change which i think is if you say eventually then maybe that just needs to be a new issue uh if things come up or uh you know multiple things does that seem fair we can check all the boxes on this uh issue description and then call this done yeah i think so i'm wondering if how to handle issues like this we would sort of want to have a look in uh you know maybe like three month or quarter or like something to just check that um we can actually really close this and there's like no pending issues and and like the you know pound info i don't i don't really know how to handle this i mean we can just close it and say it today or we can sort of like set us set ourselves a reminder to actually really close it in a little while i'm i don't know what you all think about this i'm wondering if anybody has started any kind of like tracking right like it's we have a finite number of projects it would be you know probably a 45 minute task to look at all the different um project orgs we have and see which ones have updated um there that's a nice little script yeah or yeah 45 minute task ish so yeah or five hours writing a script your pick five hours updating ruby this morning and that's why i stopped using ruby um um uh that's a good question um what i've seen in the node space is that a lot of projects have have switched but some haven't and that's because of uh infrastructure and whatnot um so yeah i don't know do we have a list of the orgs of every um open js foundation project someone okay if if you share that with me i will write the script right uh michael talking about making this sorry just really we're not talking about making this mandatory right this is just we're encouraging an audit yeah yeah to see who who has and you know if you know if uh there's a chance somebody stuck on something or you know whatever right right cool oh that's the fact that you bring that up jordan makes me think that this is does it would it feel like this yeah nvm is still called master because i don't want to ping 300 pull requests with an update and so on and like have a bunch of in-flight maintainers or contributors having to like update their local repos at some point i will want to change it but like that's the only reason i'm i haven't bothered and if at if nvm kept popping up in a list of projects that haven't done something yet then that feels a bit shaming slash coercive right that was my question yeah i wasn't i'm sorry i wasn't trying to actually ask whether you you know the project that you were responsible for had done it oh yeah i mean i'm happy to use that yeah yeah no sorry like i didn't really um no it's just like just the way you brought it up felt oh this um um the skin feel that way and i actually do uh do want to take a step back if i think that feedback is valuable and important i do want to step back and doing like a fun uh three hour script exercise that potentially has uh human downsides feels like a different project suddenly so i think this is an important well i'm more i more think that the the thing that's useful is the making sure every foundation project maintainer is aware of the desire for the shift if necessary is informed of the reasons why it's important and if their reasons for pushback are non pragmatic or technical in nature then to avoid potential uh turbulence around those topics it's probably worth arranging private discussions to educate those maintainers we're unrelated to whether they actually make the change or not but once someone is informed and philosophically aligned if there remain technical barriers then it seems like it's just up to them and there's nothing the foundation has to or should do to accelerate that unless they ask for the help of course and that's just sort of the the general place i'm coming from i don't know if everyone agrees at least it's uh well very clearly and well articulated and i think it's important to hear that thank you um it looks like uh node you know i need to go through this whole issue but it looks like um you know there are um some issues and also some folks who are just not into it but i but i went there partially toby because um uh michael wrote a script that will go through all the repose in an org and um uh you know check the branches so i thought if you were going to write something that might be either useful or it might already be written depending on how far you're going to go so the last thing i posted was michael's comment which has the the script in it cool all right so we'll um leave this one for now uh i will close this uh our issue though and um or or do we think we should leave this open for now i'm torn we should close it and i mean the we've we've accomplished the tasks that we outlined in that specific issue and and folks here have raised great points about um other additional steps to take right at this moment and i think we can possibly close it and find other things to support um this whoops i commented without closing there we go um cool so that one's closed um next up is uh issue 699 this is the uh d&i uh improving diversity and inclusion uh issue um i'm not sure what we have for updates on this toby do you have any thoughts jory um well i can speak to a very specific sub sub component of um this project which is that the last couple of working group meetings now for the cpc we've tackled um a specific set of uh changes that we want to propose to the cpc for the code of conduct and handling code of conduct reports and that task is currently with um sarah divi and myself to memorialize some of the working groups and consensus agreement in in their working session on what the proposal should look like uh that's in review should go to the um coc working group team those folks who've been brainstorming on this um this week we'll have a follow-up meeting um to discuss and then bring that to um a cpc for uh for discussion and hopeful ratification um so that yeah i'm yeah i'm sorry to interrupt you um i think that we've been doing two separate things in the working sessions and i can see how the code of conduct and moderation work sort of could apply to the d&i effort uh but i've been thinking about them differently so i don't i mean separately i should say uh thank you for that update but there is is there any um uh any sort of updates on the d&i uh work that we were doing yes i will take um um the action item to organize a meeting um was folks that were interested in order to discuss the survey that we want to do and see how to move forward with that um we've discussed a number of different options around this um and or um well still looking at like different options and on as a second as a second part to that i'm also going to organize um a meeting with folks at the w3c who are interested about this issue too and looking at also working on a survey to see how we can synergize uh this this these you know two organizations one thing essentially to do the same work great thank you uh so it's like no sorry please no i was just gonna say what we'll do we'll we'll try to pull a meeting together that's uh a non-working session meeting just sort of uh yeah we'll figure out a time to get together definitely let me know yeah i'll set that up um and share it in in slack cool thank you toby thank you jory or should i say jory i see your exclamation point sorry uh cool last issue on the agenda is um this uh dcocla stuff um jory i don't know if this was talked about last week or if there's any sort of update here i know we were kind of waiting on something it was um so just uh to and i think brian updated the issue with the latest um so as an fyi brian warner has been working with the pro bot dco folks um to implement some changes and some features to pro bot dco that will work more um fluidly with our systems um and they've been making some progress but running into little minor issues um here and there that's slowing things down obviously the pro bot dco team is uh it's an open source project and they're all they all have other jobs and that sort of thing so there's no timetable exactly uh but we we are making progress and um hope to have uh hope to have it soon enough as a reminder uh our projects are able to use whatever dco or cla tool they um they use dco or cla if they like or nothing and there's a couple options um for each so we the these are just options cool cool cool cool uh great that concludes our agenda doesn't it um i guess the one thing uh that we should address is next week's working session um i don't know if we are doing uh coc stuff there moderation uh jory you've got comments yes i have comments i have thoughts um so uh you know i think it'd be great if we could maybe plan a couple of weeks of working group meetings out um in in a bit of an advance because um we've got so many different things we want to make progress on um we have uh tech strategy work that i think would be dope we've got j slandia stuff that would be dope we've got obviously the dei um and the coc stuff um there's just there's a ton and um i think what's working well at the moment is for their kind of like the more general group of cpc attendees to come into the working session have a great brainstorm or kind of proposal slash idea generation process in our um working group and then spin smaller teams of two or three folks out to go like you know build the thing that the working group sort of um consensed upon consensed sure that's a word i like that yeah um and then and then bring that back and so i think that lets us kind of free up working group meetings instead of say dedicate like three months in a row just to one issue which may not interest everybody so yeah that makes sense so what um do you have a sense of what we should work on next and are you it sounds to me like you're saying we should plan um to kind of alternate it's not the right word but just have action items out of each one and then can kind of rotate the more and have progress come through yeah yeah um and and i think it'd be cool like so we know because we're good at calendars so speciality and we're so not good at calendars um but we know that like you know the on on uh on the sixth so that's next week and on the 20th you know we can we can kind of pick a couple of topics for say april may you know for uh let's work on tech strategy let's work on on April 6th meeting or let's work on yeah so one thought that's coming to mind and anybody feel the interject if they have something they want to add here but um maybe we should have an issue for each of these like we have for the the dni one um and if we if we have some work that's a small group can go and do they could report it back to this to the cpc meeting uh because you know like today we probably have a good 20 minutes left over that could be a good chunk of time for an update on on any of that sort of work um so we can have a meeting focus on it figure out what the action items are people can go off and do them and then we could report back to the cpc meeting on any progress there if we want it um so i mean that makes sense to me uh jory uh and everyone what do do we want to pick something to pick up next or do we think that we need to touch on something that we're already working on for next week i don't want to over engineer it well i was going to say that uh i think jslandia hasn't been discussed in a while and it might be good to talk about it and i'll lose it i don't want to over engineer it but maybe having a rotation would be good kind of like what jory said um or maybe these things need to spin off into their own working groups and we can i don't know now i'm over engineering again i was just going to nominate jslandia for next Tuesday so i agree with you on both of those i think jslandia would be good for next week partially thinking about the upcoming events and just making sure that we're ahead of the game and can you know maximize any sort of promotion but also fun you know we can have fun with it and do fun things and whatnot um i i do think that maybe some of these things would not be bad to have its own meeting like toby had mentioned earlier you know the the dei work uh maybe that just kind of has its own meeting and we sort of work through that with that cadence uh those are my two thoughts i'd be down for doing jslandia next week um because while one of the kind of foundation to do is a mvp of like the passports um and and i'm confident we will have something to show you next week and we can brainstorm on that and cool sounds fun great does somebody want to take the action item of like creating an issue and throwing maybe a couple of agenda items in that or something things that we would expect to discuss or work on sure great uh do we also want to plan for the the working session beyond that yes okay you you had mentioned tech strategy yes that's what i would like to do next after okay sold what is that even um so just because uh this this is sort of like a like uh what's the word i want to use this is a hangover discussion but that sounds like it's been drinking a lot and that's not the case um carry over carry over this is side tracking really badly oh whatever that is i know um i apologize uh so a carry over conversation um that i think we've been having since um off and on since before the merger which is like you know how do we think about telling the story of like the technologies in our foundation how do we think about um uh like catering to or and describing um perhaps the types of projects that are going to be a great fit for the foundation um that kind of thing and it's always one that we kind of hit when we get a new project application um and we kind of go oh well this you know we've got this rubric but there's also an element of like feeling to it and i think it'd be great to maybe define that a little bit further that's something that i know um uh robin would value too that makes a bunch of sense it makes sense but it also makes me wonder like are there tech strategy reasons that we would not accept the project i mean i guess this would be what we would discuss yeah i mean i don't know yeah yeah i mean obviously it's saved that thoughtful later joe okay um okay i mean i'm game i uh this makes sense to me and i think um it kind of raises some questions for me um cool do you it sounds to me and i don't want to volunteer you jory but it sounds to me like you've got some thoughts on this so would you like to create that issue as well and i like making issues for people that's you know calendars and issues that's what we're good at yeah good at that yeah if i may and if you're in the calendar and issue space um i actually think that what we have for amp that i don't know where it comes from i'm wondering if it doesn't come from here actually works really well like one issue was all of the meetings that we're going to have planned and the topics that are going to be discussed um are you for real right yeah of course i am of course you are yeah god damn it but yeah you know that's a good idea it's like i've seen that before somewhere i don't know it comes from here doesn't it i don't know it comes from the amp i thought are you talking about doing the thing that we i did for the amp thing but that yeah yeah okay but that doesn't um yeah regardless i don't know where it comes from it's just it works really well it's very useful i like it i want more of that and everything that was okay i will i'll actually sure yes i'll take some time i'll do that i'm glad that uh you know that that they pay you jory so thank you but also i'm glad about that um let me know how i can help to you know consider me a resource you know where to find me got it um cool so that's like two working sessions we're thinking about is that good enough for now um and the dei stuff will spin off into a separate meeting its own meeting um and then we'll just see in terms of this the coc uh and moderation work we'll we'll wait for more uh progress there and then go from there i'm letting someone into the meeting paris that sounds good okay all right so good that's four things that's great nice um cool what else do we want to talk about today anything sorry paris you joined right as we were reaching end of our our business cool um no i can't think of anything uh i'm sorry that's okay we should um one thing that comes to mind is like incubating um you know i know we have a couple of projects there right do we do yeah um divya and i are going to talk to one of our incubating projects native script next week um they have a bunch of cool stuff coming up that they're going to be announcing and so they've been busy busy but um that's a uh hot potato uh and then um other stuff so it's just you know heads up in fyi the um standards working group has after talking to a whole bunch of projects and evaluating all of the options at our last meeting we elected to focus on two strategies the first one being uh the uh educational resources and curation for people who are hoping to on board into what mic champion is coined standards culture which i think is like it's a great term um so we're looking for uh resources right now to consider as part of that sort of set of curated materials um and that's an issue on the on the standards repository and also in the slack um so if you have some stuff that you like please share it there um and then the second strategy is on um discussing and and providing more of a community forum for uh understanding and providing feedback and that sort of thing on um on would be proposals at at tc 39 or within the wicg or what wg so uh we're also going to be brainstorming how to tackle that process um and if you're interested in that join us cool um i'm reminded of a potential calendar conflict for next week is that right yes um it looks like we do have a conflict for the standards working group and the cpc working meeting so we will um we will adjust in our standard slack group we'll adjust i'm sure um i see sarah has gone off video but i i wondered if we should double back on any of the uh board related stuff if there were any updates or anything to talk about there i turn on the video and kept the mic um yeah i can see uh michael isn't here today so uh what i can share is we had our board meeting last week uh i thought there was a lot of really interesting stuff shared by um uh rachel around growth with our newsletter and uh growth of the newsletter did we lose you sarah you froze you can you can turn off video if you want um exciting news um other board related i don't think there's any other board related news uh uh that we haven't shared here uh just um the summit approaching and planning for the summit and things like that the open j s world event yes great um and then i don't know if if there's any takeaways from anything regarding the travel fund i know we kind of touched on it briefly before you you got here but uh there's anything to share there let me know uh yeah i don't think there's anything officially decided to share there yet but uh i'll follow up next meeting cool sounds good thank you great um yeah rachel we we touched on some announcements earlier that are um in the notes but if you have anything uh you want to add before we wrap up just let me know um i only had the three um congrats to nvm on their release um we have a webinar a q and a tomorrow with web driver um and note certification and training big sale those were the three things that i had great yeah that's what we talked about earlier okay good good good uh great all right well um i can give every back everybody back 10 minutes if uh if they'd like and we can call it a wrap cool that's that's the sound all right thanks everybody cheers bye y'all