 Hello. Hi. Oh, I should turn on my video. I don't have to be, I don't have to be hidden. How's it going, Mark? Just fine. Okay. Now before the recording starts, is it okay if I use Jackie or do you prefer Jacqueline? Jackie? And how should I, Jackie, what? Jackie? Okay. Jackie is okay. Good. All right. Okay. Thank you. Of course. Good morning. How's it going? Early. I don't know yet. Early still. Oh, wait a second. Come on. The sun is already awake. The sun is up. It's shining. It's probably, it's probably 70 degrees in San Diego, California, like it always is. We had a lot of rain last night, which was really nice. Oh, nice. Yeah. See, they're, they're predicting half a meter of snow in my area for the next couple of days and, and threatening that it might be a meter of snow. Oh my gosh. Yeah. You're in the Denver area. North of, north of Denver about an hour. Yeah. Okay. Colorado. Yeah. I've been thinking because Santa Fe is so boring. It's like, it honestly is like the Florida of the Southwest. It's like the, the, the, the average age I'm not joking is about like 60 here. 60 enough because it's a retirement city. Right. So I've been thinking about Denver. Moving up to Denver, but I'm like, do I want to with all that snow? Oh, it's, I love having four seasons. So yes, it's, but you have to admit it's four seasons. It's not like Santa Fe or Tucson or, or San Diego where you have, you have beautiful and better than beautiful or a little worse than beautiful, right? I mean, that's okay. Yeah. All right. So we, let's see. I think we could safely get started. I put a number of items on the, oh, I put one item on the agenda. I'm not sure if others have agenda, agenda topics. I know. So I know the past few times. Like we, I didn't catch everyone. So I think there were a few things that like Alyssa and I discussed, but I think the thing that we wanted to bring up again was the contributor summit. Yeah. And then figuring out where we could, where, if we can align it with CD con and where we would put it. And how we would execute it. Yeah. Yeah. So, oops, would help if I put things in there. Oh, there we go. Oh, like, oh, like's got it. And I am colliding with you. Oh, like, sorry. No worries. It's fine. Okay, great. So, well, so I think, I think all like Jackie was referring to contributor summit in the context of CD con, right? So we should do a recap and probably should also talk about contributor summit for June. Yeah. Yeah. Yeah, CD con is June. Right. Okay. And then. Yeah, I think. Oh, DevOps world 2021. Anything you need on that topic Alyssa, are you comfortable there? Did you get the review committee you wanted, et cetera, or do we need a topic on the agenda? We don't. I right now we have, I have about, I think it's about the. Yeah. We have a lot of live people who will help me to review the submissions. So the CFP is not out yet. We're still, I'm working with the events team on that still. So we're shooting for our end of March for that to be available. And I'll help you too. If you need another reviewer. I've been reviewing so much. I feel like I've got this. Yeah. Yeah. All right. Yeah. I think we can definitely use the help. So I'll include you. Okay. Thank you. Yeah. Oh, we are recording. I'll just say the screen then. Yeah, I didn't think that the recording is going on. Yes. I may need to edit out my early rather comments. People. My brutal. Yeah. My retirement city comment about Santa Fe. I can't let that get out. Yeah. So topics we have for today. Just in case we cut it. Yeah. So I should call the Africa. Yeah. Those look good. Yeah. So for she caught. Africa. Mark. Yeah. So, so what we're. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. And Zina Babu Bacar as part of the docs, office hours introduced us to she called Africa. Contribute on their having, which is a coding camp. That will be happening the month of April. They fund by so sponsors pay funding in and they then use this. Those funds to pay African women to contribute to open source projects during the month of January. So that's one of the sponsors that are willing to fund it. They need mentoring organizations like the Jenkins project, and they are, they are working. They are working on participants. So, so that's the, the caliber. And I got word today from cloud bees that they are willing to fund. So that's one of the sponsors and Alex Earl in our last platform, and he's been working on it for a long time. And he has asked me to ask Broadcom and he has asked, he hasn't had an answer back yet. So there's, we see it to potential corporate sponsors from just our influence. I'm going to ask a few other corporate. Contacts that I have, if they're willing to assist. The, that's the, the funding part to help pay these women in Africa to assist with, to contribute to open source projects. So that's the project ideas challenge. Yes. Yeah, there you go. So the project ideas challenge. My thought was. We should choose this time to do a single project idea. That invites up to three contributors on the same idea. And they work together with each other in addition to our mentors. I've got agreement from Kristen, I've got an agreement from Meg McRoberts that all three of us are willing to, to mentor during the month of April. So Meg is the, is the third. And Meg is willing to mentor during the early hours of the African morning, whereas Kristen and I are better suited to end of African working day. So after their, their working day ends. I think that's a good, a viable set of mentors there. The idea was just a single project idea, not multiple and keep multiple people on a single concept. That would give them a chance to do compilation, to get some experience with Jenkins and to provide some examples as a result. Now open to others. If there are better suggestions for project ideas, this was the one that most excited me. We'll go ahead, Jackie. Yeah. So the CDF is sponsoring as a gold sponsor. So we committed to money, but we told Zaina that the challenge was going to be providing mentors. And so I need to follow up with her. But I, we did invite her to the last TOC meeting, the CDF TOC meeting to present and see, to basically say, Hey, CDF is putting up the money, but they didn't commit to mentors. So if you're interested in helping us mentor, let us know. I haven't, I didn't follow up to see how that went because I was out of office that day. But yeah, that's also just FYI that the CDF is sponsoring. So if cloud bees or Broadcom falls through, and if you guys could help with mentoring, then we've got that covered. Well, and there, so Zima, the contributon's goal is actually $40,000 of sponsorship. So they need, they definitely need CDF. They need Broadcom. They need cloud bees. They need anybody else we can recruit. Cool. And now Jackie for your. Oh, go ahead. Yes. Speaking of that, would it make sense to actually announce the participation? Because currently we have a kind of chicken and egg problem. So we are not listed as mentoring organization. But if there is agreement that we are mentoring organization, we could probably promote it through Jenkins channels. Yes. I send it to the developer. Yes. And that's, I think we should put that as an action item for me. Oh, like, I agree wholeheartedly. We, I was trying to confirm that we had sponsor organizations and only got the enough confirmation today from cloud bees and now from Jackie. So I think, I think we are ready to promote the event. Yeah. Ready to do a cloud beat or not a Jenkins. I'll blog post and put it up with some ideas there to, to actively promote it. Yes. Absolutely. We sent in the paperwork and the payment already. Oh, you did. Okay. So, so we've already got one, one contributor. That's good. Because cloud bees has not sent in the funding or the paperwork yet, but is, is getting close. Yeah. So if, oh, like, if you want to just put that action item for me, I'll, I'll take that one. And then Mark, once that blog's ready, we'll cross promote also on the CDF blog. Great. Super. Yeah. Also developer, at least we will cover our social media. Are there CDF projects participating? No, not as of right now, because that was the thing that we said, Hey, you know, we brought it up to the TOC committee to see if they, anybody mentored, but I, I didn't hear anything. So that was our challenge where we said, Hey, we might not be able to provide a mentor, but we'll provide the funds. So Jay frog is checking with their management to see if they can provide funding as well. So I also put they now in touch with the CNCF community. So I don't know if she was able to, to work with Priyanka and them to, to get this sponsored as well from the CNCF side. Anyway, I think that they have a good chance of collecting sponsors. We can help. We can definitely help. Yeah, regarding commenters, yeah, probably we could find a bit more. April is a good time frame in terms of JSOC. And yeah, also some of students might be eligible for Google summer of code. So cool. Yeah, that's true. Yeah. Yeah, so, so this one, they intentionally placed it to avoid any collision with Google summer of code. So that's, that's why they chose April. And so I like that a lot that, that it's, it should be a relatively quieter time. Google summer of code is still in the exploring phase at that point, right? Hasn't started coding yet. Yeah. So, yeah, basically one application a period, it's in the middle of the event. So, and my understanding that participants of contribute on technically can apply to JSOC this year. Yes. Yeah, the terms are still a bit blurry. So I wasn't sure. Well, and this, the, so contribute on is not limited to students in that sense. It's there. They're not, it's just women in Africa and that's I think that's a good choice for them finding the, the contributors, the, the participants is, is sort of their responsibility. Yeah. Yeah. So anything else on this topic? No, thanks. Thanks for the time. So, let's see what's next contributor summit recap. So basically, I think we could briefly cover the outreach part because you had the feedback, which Mark sent to the developer management. Yeah, for me, one of the questions is what could we do better in order to attract more contributors through such event. Because as we had 25 to 30 people, which is good at the same time, we had almost no new contributors. Right. So it's something to be cool change. Yeah. So, oh, like I was thinking to start, we could pop, we could highlight the current contributors that we have. Right. So highlighting them mean giving them a spotlight, like talking up, you know, giving them space so that we can write about them and share their story, why they're contributing to the project and, you know, what are their, whether, what are they doing, whether aspirations, what did they find value in contributing. So, and then we should lay it out in a way that we are promoting diversity in it as well. So I know that there's a lot of familiar faces within our contributor pool, right. So maybe we also include diversification in there. So that way we're killing two birds with one stone. Okay. So diversity. Okay. Yeah. So that's it. Another action item, which basically appears constantly is that we still don't have a way to send the contributor communications. So maybe if we had a way, we could just send it in the newsletter or non-suit through different channels. But for me, the main impression was that if you're not acting as contributor, you wouldn't know about this summit. Absolutely. Absolutely. In fact, even many active Jenkins contributors do not know about, did not know about the summit because. You're right that reaching them is, is challenging. Right. I, we posted very briefly on the developer mailing list, but if you're not a regular reader of the developer mailing list, completely missed it. Posted a tweet. But again, if you're not following the Twitter feed, posted to LinkedIn, but are there better ways that we could do that. That would actually get their attention more like, be more likely to get their attention. Yeah. So one way, which we discussed a few times before that we should have mailing list or whatever to distribute announcements. So pretty much like CDF newsletter. So, or continuous information being sent about Jenkins by cloud piece and other stories, but focused specifically on contributors. So anyone who is interested in contributing or who is like to contribute or just subscribe to this mailing list. And we will distribute information there. I like that idea. The idea there that would be a low, a low bandwidth, high content channel. Whereas Jenkins developers is quite high bandwidth. Yeah, it's definitely low bandwidth. So we could just send us a couple of messages per month, maybe even less. I definitely use it on a contributor summits, maybe call for papers for key events like CD con. But no continuous traffic going there. I have a question about the promoting of the summit. Did you promote it over Gitter? Cause I think also you have a lot of the community there, or was it purposely kept off certain channels? Cause you are, you know, you're going after a very specific audience. So, so we, I think we did mention it on the channels, but the, the challenge with the Gitter channels is they are, they are sort of sub topic specific. And I did not put it on every channel, right? And maybe I should have where I should have said, look, I'm going to blast this onto every Gitter channel that I'm on. And I certainly did not do that. Yeah. The other thing too is we can, if it's okay with the community, we can also leverage the CDF channels to like, if there's a blog, we can cross promote the blog on the CDF. We can add it to the newsletter. We can add it as an event. You know, there's, there's a few ways, you know, we can also like the internal mailing list. But again, is it, you know, are we intentionally keeping it off those channels? Or is it okay to do that? Totally okay. So one of the reasons why we didn't do that is time constraints. Okay. Yeah. If there was more and more organizers, then we could promote it more. And I don't think that it can be only limited to Jenkins because, for example, we could have joint sessions, like interoperability, let's say Jenkins and tick tone, how we integrate, et cetera. So even if it's a Jenkins contributor assignment, we could involve other communities as well. Okay. Yeah. Okay. Yeah. So let's, you know, for moving forward, yeah, let us know because we, you know, the newsletter is doing pretty well. We have a good open rate and a good click through rate on that. So it's always, you know, let's, let's use those channels to help promote in the future. Yeah. Maybe another thing we could do is to have special sessions related to new contributor onboarding. Because we do it for community events, but we didn't do it for contributor assignment though, it could be an opportunity. Yeah. I mean, like we could do a podcast episode or a webcast episode through the CDF channels to help promote and to just kind of lay the land, like the lay of the land of what to expect at a contributor summit. If you're, if you've never been to one. I like that idea a lot. Oh, like, because I think people are intimidated to go into a community and, and, and seeing where they can help, unless they have like the technical expertise and they feel comfortable about that. But for, but I know we need help in a lot of areas. So maybe we can, another thing is, you know, we have, they are webpage on Jenkins.io. This is how to participate. But maybe we can drill down to a little, a little bit deeper in like getting it down to the, this is how easy it's shown how easy it is that people can, can participate just making things easy for people to help out. Yeah. Or maybe like, if you have a breakdown, the types of roles or types of tasks that you need help with, I think like for me, there was always such a misperception on open stores that you needed to be technical, but like, I could have always been like Mark, I could have been somebody who did documentation or somebody that helped planned events or, you know, some different other types of skill sets. And I think that that's probably what stops a few folks from, from coming in because they're like, I don't, I don't know how to write code. Yeah. We did it at events like October 1st, et cetera, where we explicitly say that it's not just code or that it's not just Java because for Jenkins perception that everything is about Java, but not. Is there a recording of this or is there like a, cause then we should just, you know, add it to the CDF YouTube channel. I can ask Roxanne to also do some, like some social media around it, especially as we're preparing to do like the second contributor summit in June. And then people can just have reference points to understand, you know, how to get involved in the community, how to start just, just getting in. So for this event, yeah, this is opening of the Huckfest from 2019. I believe that it's relevant. Yeah, it's exactly this presentation. Okay. So I will put it in here. Cool. And then we had multiple instances of similar recordings for Huckfest events. Okay. And then oh, like maybe make an effort to like have one of these breakout sessions at conferences. So we have CDCon that's coming up. We have DevOps world. So, and I know that like Google summer of code, right? So at the beginning, when we first talked about it at DevOps world, it, you know, there wasn't so much interest in it, but it takes time just like anything else. It takes time to build it up. And then as I seen it over the years afterwards that, you know, the crowd gets bigger, the interest, there's more people participating in it or interested in it, or at least being aware of it. So maybe we can also do that. Yeah. And I know like for CDCon, we're trying to have birds of a feather for each of the project sessions again. And maybe this is a good way to like kick off the, like the birds of a feather session, do a like a 15 minute talk and then just open it up for the, the rest of the attendees to ask questions and. So I think there's opportunity there. Or maybe just a genetic workshop. So that's a feedback for contributing because many approaches and concepts are profitable between projects. Each project needs documentation. Each project has newcomer friendly issues. Hopefully. So we can just go through these general concepts. Yeah. Okay. We could do that. And if there are slots with CDCon, we can use it as a filter. Anything else regarding contributor summit? Yeah, like, I guess I have a question. Yeah. Oh, go ahead. Well, what went really well about the contributor summit? We had, we had people involved. And multiple time zones worked great. Which was, was we, it was better than a local summit because we had people who would never have made it to Belgium. As an example in the past, we've done this at Fosdom. And by not being co-located, we had people involved there who could not have attended otherwise. And they actually attended were active participants. So, so that was, that was a plus something that we got from this contributor summit that we can't get when we, we are co-located. Yeah. Now, now. One of the things that might be worth still touching here. Alyssa had identified as part of the outreach. I mean, there's a lot of, there's a lot of vision there that education outreach. And there are a couple of other key topics that came out of the contributor summit that are going on to our roadmap. But I don't know that today is the time to, to do that because we need to get those onto the roadmap and, and talk through. Plans are still evolving. Alyssa, is that okay for you? We just, I mean, I, we know that they, we, they were included in the roadmap presentation at the end of the summit, but they haven't been actually added to the roadmap yet. Right. So we need to do that. And that's, that's an Alyssa and me have that action item. It's not exactly impressive for three. Right. Exactly. And that's, that's why we've got two or three. One is educate educational institution outreach. And the other one is, you know, to improve onboarding experience. If I remember, I was one and we've got to get those into the roadmap. Into the official roadmap. So. Getting more new faces to contribute to the project and then diversity. And inclusion. Is the other one, or. Is the other one. Is the other one. Is the other one. Is the other one. Is the other one. Is together with the. Getting more, more contributors. Well, one thing that I'm not sure whether it's a roadmap item. Because well, it's an important topic, but I believe that it's continuous topic. Right. So. Yeah, I think that the education. I think it's a good idea to start with a definable start and end and specific objectives. So I think it is a reasonable fit on the roadmap. I agree that. Seeking more contributors may not be. Well, it's just. If it's a special, a special program. So, for example, if we define. Months of. Jenkins contribution or whatever. Months of outreach. Let's do that. But yeah, we just need to think how to properly frame that and how to properly fund it. Right. It's going to suffer which we definitely should be doing. Okay. So, yeah. Next contributor summit. Yes, the governance meeting we had a discussion. And my understanding that currently CD con schedule is packed. Plus there are quite a cost limitations. And the proposal from Tracy was that we actually do it as a day after CD con or maybe a minus day minus one. So current plan for CD con. Yeah, so we'd be looking either at that Monday, the 22nd, I believe, no, sorry, the 21st. Or we'd be looking at that Friday, which would be the 25th. I think both options are quite fine. Of course. Yeah. And she also said, you know, we'll, we'll make it part of the CD con agenda. We'll include it in the schedule. I think the challenge is. Like we have two day zero events happening. So there's that additional costs because we have the platform reserved for a few days. So that's why we, if we could do it through like zoom or through an external platform, but we just link out to it. I think that that's one of the things that she said she, we could swing a little bit. We'll be fine. We don't need the main conference platform. Yeah. Number of participants. We will get lucky if it will be 100 people and 100 people is something we can host the zoom easily. So we don't worry about it too much. Okay. Yeah. Just then, just we just need to make a final decision on the day. We'll just get it added to the, to the schedule and then also so we can start doing promotion or add it to all of our CD con promotion. I think that if we agree in principle that we do that, we can just create a placeholder. So I guess you need to an abstract or whatever. Yeah. Just give me a title and an abstract and then we could, we could add it. I'll probably start the Google doc. So that you just put all the information there and collaborate on that. Yeah, that sounds great. So like in Mark, what are you thinking in terms of the date for now? I, I guess for me, Friday, is that good for the folks over in Europe? Cause we do have a lot of contributors from Europe. Unless we do that during the European time, time zone. Personally, I'm not even concerned about the day. Maybe even doing it on the weekend. I'm not sure about that, but it could be also an option. Okay. If we choose between Monday and Friday. Yeah, no preference at all. Okay. Friday is better for fun events. But yeah, I guess that's it. So, okay. So CD con is Tuesday, Wednesday, Thursday. Is that right? Yeah. So it looks, so we are having spinnaker summit day zero on the 22nd and then get up summit also on the 22nd. And then CD con is the 23rd and 24th. Got it. Okay. So basically we can do the same spinnaker summit, just have it on this page. Yeah, yeah, we could add it. We could, we could add a page for the contributor summit just like that. So, so then would, would that be allowed for us to do a day zero event that doesn't use the CD con infrastructure because we can't afford the CD con infrastructure, but be announced as it that was the, I think, then the 22nd would be, would be great, but that may be seen as a competitor to, Hey, you're doing a day zero thing, but not using the day zero infrastructure of CD con. Yeah. Because it's more general. And many of our visitors may go there. Yeah. So that's why we wanted to stay away from the 22nd was because of the get up summit. Okay. So, so then Monday the 21st or Friday the 25th. Yeah. Okay. Yeah. Also, both of these options are fine. So we can probably launch it. Do the inside advocacy and outreach seek or maybe in the wider community. Just to get feedback from others. Personally, I don't have preference at all. Well, and I think it might be good when you create that doodle, I may use this, the list of people who registered for the last summit and email it to them directly. Yeah, that's fine. Just because. Hey, you registered for the last one. Here's a new one. Please give us your opinion on this. If you'd like to be a participant. Yeah. I promised I wouldn't share their email addresses with others. I didn't promise them that I wouldn't occasionally. That's fine. So. Yeah. I think that it should be enough. If you're good to use our platform. Yeah. I don't think it will be my job to. Configure that. Yes. That's it for that. Yeah. One question about CD corn. Yeah. Yeah. Yeah. Yeah. That's fine. So. Yeah. I think that it should be enough. If you're good to use our platform. Yeah. I don't think it will be major effort to. Yeah. Yeah. Yeah. One question about CD corn. Should we expect the project? The project. Project. We asked Tracy about this yesterday. And I totally forgot what she said. I remember. Okay. So she said that. Yeah. Yeah. Yeah. Yeah. Yeah. I think that was, that was the concern last year was that. The reason why we didn't do it was because we didn't have volunteers staffing the booth and we didn't want the booth to be empty all day as people were in sessions. And so if we can, if we can staff it, then she said that we can have a boot that Jenkins can have a booth. So Jackie, is there a dedicated expo hall hours or time? I think we just left it open all day. We didn't have a set schedule. Okay. So, so knowing what you know now. Are you still interested in doing a booth then? Oh, like. So my experience with supposed virtual events is not that positive. Yeah. That's one of the concerns. So we could have one, just a kind of live chat, et cetera. But yeah, we're really focusing lots of feeder. But if there is interest to have both, we definitely can prepare on our side. And we can find contributors to be around. Right. So if you just need it for the content, we can help. We can also ask the ambassadors. There's a lot of ambassadors who are also Jenkins community folks. So maybe they might also be able to help staff that. So there's two pools we can try to pull from. Right. So Jackie, from your experience with, with last year's event, what was the, the visit, what was that like when for sponsors? Was there a lot of. So I think they, the average was like some, somewhere around like 150 leads per booth that, that they got. This year we are using gametize to incentivize folks to visit all the booths. So we are trying to increase that booth traffic by, by gamifying it. So, you know, we're going to ask each of the booth sponsors to see if they have something that they want to give away. And the way that gametize works is that each of the folks actually have to engage with somebody to get a code. And then they go and enter that code in game, in the gametize platform to increase like their, their leader board position. And then, you know, if you get to certain tiers, for example, you're going to be able to get a code. You're going to be able to get certain giveaways. So I think it'll, it'll depend on also like one of the things that I noticed people are actually downloading a lot of content. So if you, if there are like Jenkins is the way material that you can share with them or, you know, spec sheets or case studies or any of that stuff around Jenkins, I think this is a good opportunity to, you know, customize the booth for that. Right. Yeah. And we can definitely do that, have content available. Or like videos, if you can link out to a video or, you know, yeah, all that stuff. That's, that's when I noticed the booths do better when they have content to download than when it's just, you know, informate like high level information about the project. But if you've got content to download and you've got people who are there to engage the booth traffic ends up doing a lot better. Okay. Okay. So we just need to decide whether we want to, to do one for the project. Yeah. And I think we still have some time to decide. Yes. So what would be the decision to plan approximately? I think we probably need to know. Probably by June 1st at the latest, because Jennifer would need to go in and build the booth out. And that's the deadline that we're using for all sponsors to submit their contracts by. Okay. So we have plenty of time. Yeah. Probably I would say a little bit before that. Oh, like, so if we need the booth to be staffed, I'll probably have to, I'll probably need time to reach out to folks to, to ask for volunteers. Right. And so they need to make sure that their, their time is available or block time for it. Yeah. So May 15th. Yeah, sounds good. Okay. Let's just revisit it at the next meeting then and see whether you have preferences. Yeah. I think you shouldn't really focus on events like those are feeder or maybe this contributor session, because session will be more efficient than just having caboose. Yeah. Yeah. So let's keep working on that. Yeah. Yeah. Yeah. So, so DevOps world. It's still on schedule slated for end of September. We're expecting CDF to be a part of DevOps world just like last year. You know, Keynote have its own track have its own booth. And then I'm building the community track along with the folks within the community. And then CDF Jackie will be leading that effort for the CDF track, just like last year. And then the theme. I have the theme. It's again, it's similar to last year as well. It's something along the line of, oh, building the future of software delivery together. It's similar to last year, just rewarded a little bit differently this year. Mm hmm. Yeah, definitely. CDF projects fill this theme well. Yeah. Taken that we have confirmation about JSOC, we can assume that we will be able to have presentations like last year. Absolutely. Yeah. Whether it's community track or CDF track, we can figure it out later. Yeah. I'm not sure how many participants will be there, but hopefully enough. It's virtual. So hopefully we can get. Yeah, a lot. Definitely. Stay tuned for code for papers. Yes. Yeah. Yeah. Yeah. Yeah. I'm excited for an end of this month. This is great. Then we will start preparing for that. Mm hmm. Yeah. It's a good time to start thinking about what talks we can present. Yeah. Alyssa, quick question on the CDF track. Do we use CFP or do we curate that track ourselves? That's a good question. So, um, the events team is still shopping or whether I think they're probably narrowing it down to, uh, I think they're using a different platform than what we used last year. So I have a meeting with them at the end of this meeting. So I'll ask, I'll ask them for you. Yeah. Yeah. Yeah. Probably through the, through their, the tool just to keep everything together and so that they can send out communications as well, Jackie. Yeah, that would be great. I rather try to do that instead of me trying to curate everything because we sort of did it last minute last year. Um, and I think at least this way. Like if, if I could get community members to also help review the submissions. Um, and then we can, if we have to curate them, that's okay too. But, um, yeah. Cause then I could just start promoting that and asking folks to start submitting their content for the CDF track. Yeah. I'll, I'll bring that up with them. And I think, I think it's probably much cleaner to have it through the tool. Yeah. It'd be nice if we could do that. Yeah. The only difference is that if there is a track or let's say a workshop located event with latest CFP date and it allows more contributors to submit the, let's say last minute the developments. So if they create something right before the contents or if they miss the main deadlines. So if there are events with such delete CFP deadlines, it's also useful sometimes. Yeah. Yeah. For the main STP. It's fine. So. Thanks a lot for the materials and for your time. Do we have any other topics? I think I'm good. Yeah. Thanks everyone and see you in two weeks. Thank you. Bye. Bye.