 Welcome to the next installment of What's Up with the Collaborators. Today, I have with me Joe Seppi, who is a core collaborator. Before we get started, do you want to tell us a little bit about yourself? Sure, I'd be happy to. My name is Joe Seppi. I work at IBM. I joined IBM through Strongloop, who were key to early development of Node.js, and so I was able to get more involved in the project at that time and really focus on open source, and I've been a long-time community committee member, which is something that we wound down not too long ago in the Node.js community. I also was a part of the small team that helped to merge the JS Foundation and the Node.js Foundation into the now open.js Foundation, and out of that work was elected the cross-project council chairperson, which is the top-level technical advisory committee. I continue in that role. It's been two or three years now, and Node.js core collaborator. Yeah, it's great been working with you on the open.js side, very important work there, as well as it's great to see the ComCom members yourself and Tierney getting involved and continuing to be involved in some of the activity within the project, even with the ComCom having been ramped down. The interesting recent news is you've been nominated as a core collaborator. We want to tell us a little bit about that. Yeah, sure. It's funny. I've been in the space for a long time, but I don't do a lot of work on Node.core, so I've never needed to be a collaborator per se. But I recently volunteered to be a security release steward, and along with that, I need the admin privileges of the core collaborator. Since I've been a long time contributor in a variety of ways, and even I'm representing Node.js at the open.js foundation, I was nominated and people gave a thumbs up, which is cool. Thank you. Yeah, that was great. And thanks a lot for volunteering to be a security steward. It's an important role, and I'm quite happy actually that we've managed to get a few companies lined up to sort of dedicate and commit their people, because it's something that the steward has to coordinate the security release, not do all the work, that it takes actually quite a large cast. But it's not something that you just can do when it's convenient, it's something you have to commit to do when it's needed. And it's great to see that companies will support their people to do that. We could use a few more, so that's an important thing. But thanks for taking on that role. I know one of the things, the other things I know you've mentioned you've been working on is on the tooling team with the arguments part, so that's kind of interesting. I'd like to hear a bit more about that. Yeah, it's really interesting. And we've been getting a lot of interest from the community as well, as things have been taking shape. The short story is, you know, we had a bit of a fall start a few months ago, our colleague at IBM, Chris Hiller, who left a little bit ago, gave a stab at it. We kind of took a step back and I worked with Darcy Clark from NPM to kind of design a good simple argument parser that we would like to get into node core. And, you know, we're not trying to replace yards or anything like that. We just want to have some basic functionality out of the box for folks to take advantage of. So that's exciting. It's taking shape. We're hoping to propose it in the coming weeks. Check out PKGJS is the org on GitHub slash ParseArgs. And, you know, we've got a few open PRs that we'd love some more input on. And we're just we're kind of, I think, nearing the end of that work to be able to introduce it back to node core and see what the response is there. Well, that's great to hear for people who don't know that PKGS org is another org under the node project. And it's a place where we're like we're building some tools, but also incubating some things like the parse, the arguments parser there. And so, yeah, it's great. Great to hear it's you're making good progress. Yep. I know another another area that's that's quite important to the project is your work on the social team. Yeah, yeah, the social team is really interesting. It's it's basically just me and Tierney, Tierney Siren, you know, also a partner in the community committee. Great person, love Tierney. And Tierney and I manage the social channels. We primarily focus on Node.js and we're very focused on the community. So we have a few regularly scheduled tweets, monthly tweets. One is to thank the build sponsors that provide hardware for the build team, which is great. And then another one that we have is jobs related tweets. So monthly, you know, ask of the community, do you have Node.js related jobs? If so, reply to this tweet and we get a lot of great engagement there. People looking for Node.js roles and people who have roles open. So that's a great benefit to the community. And then we also are trying to make it so that, you know, people can request tweets through the GitHub PR process. So if you go to Node.js GitHub.com slash Node.js slash tweet, you'll see some instructions there. You can open a PR. Obviously, we need to be focused on the community and providing a benefit there. We're not just going to tweet anything. But, you know, if there are certain things that you think would qualify, then by all means open up a PR, Tierney and I will work on it with you and then merge it in and it goes out to the Twitter account. We have, I think, 771,000 followers now, which is impressive. So, yeah, that's that's fun. That's a great service for the for the community. Yeah, the build one, I think, is really important. We have lots of great donors and the automation that the social team put in place to make sure that that goes out regularly is as meant. It's been much more regular and nobody needs to follow up on that. So I'm really happy to see that going out. Yeah. And if anybody has any other, you know, things like that, that they think we should be amplifying or thanking, please, by all means, reach out, my Twitter DMs are open or open up a PR. That's good. So we're almost out of time. But before we go, just, you know, what are your thoughts on the most important, most important issues that are facing the project or open source today? Yeah, I think the obvious one that comes to mind is security. It's really top of mind for everyone in our community, but also the text sphere overall, you know, all the way up to the White House, which have meetings with foundation folks and, you know, people from large companies recently focused on security. And that's something we're really focused on at the project level, as well as the open JS level. You know, we have another number of things we're looking at for the project, but also at the foundation, we're looking to spin up a security-focused collaboration space where we can really provide some best practices, build out some infrastructure for the projects and, you know, provide any sort of thought leadership or training or any ways that we can help the community and not just our projects, but all the projects in the space, if we can be helpful to them and a security, you know, around security, that's the goal of this collaboration space that we're excited to have. We have a draft proposal going and we hope to have that space opened up in the coming weeks. Yeah, I think it's great that the Open JS Foundation can kind of take that on and provide a home for, you know, not having to have any one project figure out all those answers. But trying to figure out, you know, some good processes, some baseline, you know, good ways of doing things. I think that'll help a lot in terms of, you know, bringing sort of raising the bar without having any one project have to be the, you know, figured out by themselves. Yeah, yeah, you know, hopefully a rising tide lifts all boats and many hands make light work or whatever phrase we want. Cool. OK, yeah. So I think that's all the time we have for this time. Thanks for coming to talk to us, Joe. And thanks to everybody who's been watching on the video stream. And we hope to see you next time. Thanks, Michael. Cheers. Yep. Bye.