 Hello, welcome to the Advocacy and Advocacy CIP meeting today is April 22nd, we have several contributors on the call and we have a few topics on our agenda. Just my screen. Yes, we can. Okay, so yeah just put a few random topics, which we had in progress and if you want to discuss something else just put them to the list. And, yeah, let's give priority to your topics so that we can discuss them first. Okay, so what I put the agenda jinx contributor summit updates. Thank you. Anything else we want to discuss today. So we have pending meetup. I'm way behind on getting it submitted but a proposal for a meetup with Uli Hoffner talking about his developer onboarding techniques uses with his university students. It doesn't have to be. Yeah. So we have. So let's take a full list of upcoming meetups. So we have tick ton client plugin works. We have open telemetry in the works but unlikely to happen the next few weeks. Open telemetry that's the work that Victor Martinez just announced. Excellent. Victor and serial. So actually we are likely to have two meetups. One will be in English strings online meetup and the one will be in French together with Swiss elastic meetup organizers. Well, it depends on whether serial is up to date to meetups but initially he was interested. So then we have it up for Jenkins, but not a separator. Then we have CDFC. Dope sold CFP. And we have a meetup for developer developer best practices right. Right. Yeah, developer best practices with with Uli Hoffner. Well, there were other discussions like, for example, we had a discussion with somebody in Twitter that we would host a meetup for preview environments support in Jenkins with these tools, which is kind of interesting topic. Right now there is no confirmed date, no confirmed application. In addition to that, I might do online meetup for Jenkins roadmap updates ahead of the contributor summit, but I'm sure. Anyway, the list is quite good. If half of them happens, it's good. And yeah, we will have Jenkins room meetup. We have a session this meetup organizers this weekend. So we are funded to contributors who are interested to volunteer with the organization and other organizers are also interested. So we'll definitely run something. But yeah, most likely in May. The Jenkins room meetup will certainly be in Russian. Right. And that's the idea. Excellent. We also have not so active discussion about reviving Jenkins meetups in Spanish because we have three contributors who are interested. So if we do, we will definitely use one of our meetups published on commas additional platform for promotion, for example, Madrid meetup or CV meetup or all of meetups. So we will definitely use the determinants of the local meetups where relevant. So the question what we do is this meetup accounts and longer term remains. Okay. So let's go forward then. Okay, Jenkins contributor summit. Thanks to Jacqueline and they can easily read the foundation everything is published. So this output. There is a registration form way. Basically when you register to CD con you have an option to register to the Jenkins contributor meetup as well. It's announced in the agenda. It's also listed here in the events. We can use Jenkins contributor summit to which points to all pitch. So I want to improve this page a bit but yeah, whatever works. Jackie, do you have any, any data that you can share in terms of how many registrations we have. Yeah, you guys have to 17 right now. Yes. And so that's also something that I wanted to chat about because I know that are we going to have a cap. Do we need to have a cap on registration. Or can, like, you know, I know the actual attendance will be probably lower than the registration. But if we need to put a cap let me know because I don't want to have like 500 people register and like, be a limitation. Yeah, so our platform can support checked yesterday. So I'll count setting says we can support 300 people. Normally the webinar we break out rooms. And up to 500 and other things. Figure out what exactly. We can start working only when we get to 1000 registrations for that there is no chance that we will hit limit. Okay, okay, yeah, just, just wanted to ask that. And then the other thing is I'll start adding the Jenkins contributor summit on the rest of the groups for the meetups. One question I had was regarding talks. Sorry, this is also related to CD combat CD con talks that are Jenkins related. I'm going to ask Roxanne if she could put a list together because she's doing all the tweeting right now, and we were wondering if the Jenkins account would retweet any of the Jenkins related talks. I'm going to do. I monitored it I've seen one tweet already. So yeah, so I'll ask Roxanne to just in a document, put all the links to all of the tweets that are linked in post that are related to Jenkins talks. And then let me know what that process is if I need to submit it somewhere for approval. We will be posting additional summary blog post on the Jenkins site with all the links. Because yeah and if I understand correctly we're still missing some sessions for example Jenkins both isn't in the agenda at the moment. Yeah that's still that's still being worked on. I'm sorry I have to just take a call really quick one sec. So, oh like, perhaps we can ask Roxanne to blog about those sessions. Yeah, that's what we discussed with Roxanne. So she would be doing blog post specifically about CD con agenda. I will be doing blog post about the contributor summit. And of course we cross reference. Okay. One thing from what I know Roxanne is off until the next week, end of next week. Because yeah there is a stage blog post for Jenkins contributor awards. And yeah she asked me to get it over the line so it's what I will be doing right after this meeting. Okay. Yes we have. So for contributor summit we started assembling the agenda on the top level. So if you go to this document, there are some entries. It's not a final agenda we just have a few items in the list. So what we have, we definitely want to have Jenkins three discussion in some kind. We want to discuss Java 17 support, because it's going to be released in September it will be some demand. After Java 11 I'm afraid of saying in high demand but yeah they will be different with some people reaching out. And then we want to have a session about Jenkins and Jenkins X collaboration and interoperability it's confirmed. I think it's in Tecton. It's confirmed to be awaiting for the list of contributors but then Lawrence kind of the confirmed that so I think that we shouldn't be fine. Then, yes simple Jenkins and other projects. So for example they will be talking to CD con about using the Jenkins and our studios together. So it's also something we could have if there is a content for contributors summit discussion. It's something we can discuss but it's far from being confirmed and announced. Then we want to have Jenkins and user panel having multiple big Jenkins users presenting just sharing the expertise and more important sharing the planes and expectations from the community so what they want to see changing is what the expectations demands, etc. So basically having a kind of direct channel of feedback from users to contributors as a part of the summit. We are working on that together with us every day because and we will be reaching out to the CDF because one of our items is to actually get CDF members and user members there, because we know that many of them have really big Jenkins instances. So for me it's one of the focuses. Oh like in terms of proposing, I would love to at the contributor summit have a track on documentation. Should I be writing it into that contributor summit document as a proposed change. Yes, we discussed the previous meetings and so we have something tentatively. I propose something for documentation. No. No, we don't because I haven't added it or there's confirmed entities there but we need a session and some what that would mean and why. Yeah. Yeah, we have declared interest. But if you want to have a separate session documentation definitely need hosts and you need some kind of agenda. Plus, yeah there is open question about timing because if you do it is one day event, then the timing will be tight, especially if you do it in the US East time zone as we do it now. And it would be okay if, if we if we said hey the time timing doesn't work we could do separate sessions outside of this and bring this summary of the results to it. So, yeah, I don't need to let timing be a barrier for me on that one. Yeah, right. So, for example, we can easily announce that a few sessions will happen after the contributor summit date. Yes, you're welcome to join. But for me, the main concern is how do we do the main part. Right. Yeah, right now we started for something. Oh, sorry, 10 am Eastern time. So, well, it's not that late in Europe, but you definitely will have opening maybe one round and then the most of people in Europe will stop start dropping out and it will be still for Asian and Pacific region. Yeah, so really quick it's 9am Eastern time that we put you down as starting if that needs to get, you know, pulled in just let us know because we we can definitely do that. We can update. Yeah, so I basically just put the same as others for now. Yeah. So if you need help and like the suggestion, like one of the things we did for example, all of the European speakers we put them in the morning, and then, you know, switch over to somebody in the US in the afternoon. If you have that concern of European folks not being able to support the event. I think that it's a contributor summit. So it implies that we would have active discussion between contributors. And so it's not just having a speaker there and it complicates the things because, you know, usage of suspects for many areas. So finding a time where we'll be not that easy as we discovered the previous contributor summit. I don't have answer for that. But I definitely tend to find answer within the next few weeks. Anyway, they went proceeds. Yes, we published almost everything except the online meetups. And hopefully we will also get that in the mailing please. And the newsletters if possible. And also, yeah, there is this links foundation site and the protocol correctly jinked cement is still not there. Okay, let me follow. No, it was wrong. Okay. Yeah. Oh like for my convenience is that is a link to the Google Doc with the outline available in the notes from the SIG meeting here. Yeah. Okay, so I can find it in there. Great. So you just need to click a few links. So you click here and then you click a link to the Google Book agenda from this. Oh, got it. Thank you. Okay. But yeah, thanks a lot to the CDF Jacqueline Tracy and everybody who helped because we decided on this event quite lately. But it's great to see that everything is published. And now the ball is totally on our side to prepare. And then also just let us know as well, because one of the things that we can do as we're getting closer to the date is also instructions on how attendees, you know, you know, log in or if they need to register through the zoom link first. So just let us know so that we can send that email out a few days before the event starts just like kind of like what to expect for for Jenkins contributor summit and, and how to participate. Okay. I agree. And you're likely it will be also blog post. Let's see. But yeah, definitely put this section item myself or somebody else will come in it. Okay. So that's all but yeah so far so good and we have plenty of time to adjust. Okay, for CD corn. Yeah, I think that we discussed all the topics or do we have anything else to cover. No, I think that that was it just, you know, let us know when we have like the blog and then we'll get that published and pushed out as well through all of our channels. And then let us know also how do we if Roxanne needs to submit, like I said all the links to the retweet for retweeting for Jenkins sessions. Just let us know on next steps because we, we definitely want to let the community know. That's great. And thank you. Okay, so the next is actually. Yeah, can I can I ask Jackie something about CD con as well. And so Jackie, I'm sorry if I should already know this I can't seem to remember but will we have an exhibit hall virtual exhibit hall. Yeah, we have the virtual expo hall so every sponsor has a booth. So every project will every project have a booth. Sorry, I don't remember where we left off. If we agree to it or not, I'll bring it up to Tracy Miranda again and ask her what we want to do. Are we giving each of the projects a booth. And then I think where her concern was it was just like the community of each of those projects will then you know what we would put that responsibility on the project community to staff that booth. I mean, let me confirm on what she wants to do. Yeah, and yeah, and I can certainly help with getting people sign up to help at least staff the Jenkins booth. Yeah, yeah, of course. But yeah, let me confirm what she wants to do and I'll circle back. Okay, thank you. Yeah. So then more forward. Okay, so the next topic is actually about Jenkins X 3x. And you may wonder what we're discussing here the Jenkins the focus energy seek. And the main reason that you guys discussed yesterday Jenkins X 3 restores support for Jenkins as well as the ICD engines. So there is the command and support for Jenkins and putting classic business up and the Jenkins file runners are up to be sticked on. Yeah, as we agreed at the governance meeting we want to promote it through the Jenkins channels because we can see the Jenkins X is our sister project. And we have actually a plan for that. So we discussed a few tweets LinkedIn post I have also started to send them to the blog post draft for that. And we've got some quotes from KK and James Strachan. But yeah, we will post it a bit later. And of course, once it's posted to be creative, like and here's the foundation could also help this promotion. And yeah, but yeah, I will be LinkedIn tweets, etc. So it's just heads up for that focus and outreach seek and still waiting for feedback regarding the content. So, so far, good feedback on the from Cara and from James's. So some of the from the Jenkins community, it will be great. But yeah, I think that it's important and beneficial for us. And just to add yesterday, we had a blog post by James Strachan on the Jenkins website talking about the client plugin for Jenkins and apparently by using this plugin you can invoke not only tick tone pipelines but also Jenkins X pipelines from Jenkins. So, yeah, it's a quite long but you're very informative blog posts so take a look and I think that it's important we should push such interoperability stories forward where we can. And then we'll follow ups about tick tone tasks upon walking Jenkins, because there is a request from a contributor for having official tick tone task for Jenkins. And I guess it's could be also a subject for the contributor summit. At least I invited the participants in this Twitter thread. Okay, anything else on that. We discussed with terminology. We discussed yesterday and at the governance meeting. Quick update the focus and outreach because we started doing it under a preload of the seek because Alex Ola and the market checks in the heavily participating to be sick at the time. So, we announced knowledge changes in August. We had two remaining action items one to define subterms. So for example for Jenkins main node. It's still called master and we had an action item to rename that we interrupt the ball on that due to various reasons. And we want to continue that so cover the discussion after a few kind things by Daniel Beck. And it's going for same for localizations. So hopefully in a few weeks we'll have decisions on this term. Okay, I don't think we will be making a huge pass out of that. Most likely we'll just approve that at the governance meeting. And what we actually need to that to integrate changes because there are staged pull request by Daniel other contributors including for example, one of these teams contributed to the technology to not across the plugin ecosystem. So we will lend these changes and then we can think about making it a featured project or whatever just to highlight it as a part of additional program, maybe use some stickers I don't know. I mean, it's happening. No action items are quite from the six specifically. But if somebody wants to contribute, please join the program. Any questions. No. Okay outreach programs being really quick. So Google summer of code applications are over. We put the old applications to different projects we participate in the level of the contingency foundation this year. Currently that is ongoing review we are seeing can help with mentors, you may have seen a lot of emails from me especially if you're an orchid mean. And yes we expect an answer this email so please take a look. And basically the results will be announced on May 30. So in three weeks and we still have some things to do within these three weeks. But everything looks good so far. The season of dogs, we applied at the jinx project, we are not accepted. There is a retrospective doc I created when he did the documentation seek. So far I didn't get it back. I guess I owe you feedback there like I've got, I've got to look at it. I was interested in the relatively few number of the smaller number of groups that were accepted and wanted to do some more looking at, at the level of those groups based on what was posted on the Google season of doc site. We are certainly not an experienced group with Google season of docs. Yeah, so personally, I don't make a big deal out of us not being accepted. So last year they were 50 organizations this year they were 30. And this year you should consider JSO that basically has a completely different program because of the change in the framework now it's organizations paying to do hard rank etc. So, yeah, it's a different program, except the name. And yeah, if you take a look at this project I compare it to the list of two seven. Yes, maybe there are half of organizations there, but other half on your organizations and I guess the preference of JSO organizers was to have new organizations. So, yeah, it's one of the main reasons why we weren't accepted I think, but there are still some things we could improve in my opinion and that's why I started this retrospective doc. And I will provide feedback there. So, yeah. And yeah, so we don't have a season of docs this year, we have an opportunity to run our own program. So, if there are mentors interested in that we can do that. Most likely in the September 10 frame because I don't think that we have capacity to run JSO and JSO and parallel. Well, not JSO but our own program. You're right that we don't have capacity to run it in parallel, at least I don't. Yeah. So, next, she caught Africa. So we have five participants. The program has just started but actually it tends in about one week. So, not that much time left, you have five contributing participants. There is a blog post. There is several submitted pull requests. You also helping students to communicate with particular plugin maintainers to facilitate the reviews. It will be also key. Yeah, you will also do retrospective, etc. But you know, no specific highlights. Hopefully out of that we will get a blog post and maybe some additional promotion by participants. It will be great if they share their own experiences. I'm not sure whether we have enough content, for example, to have a Jenkins online meetup to talk about the program results. So it's something for you to consider Mark but certainly I'd considered writing a page about what it means to add help to Jenkins. Based on what we've learned from Sheikot Africa, because we've learned a number of places where I wasn't realized I wasn't aware and so I think it's good, good question, I'll, I'll explore it with them. Okay, so whatever content, we need that. So, Mark, I mean, even if you're interested, I can save a slot for you at DevOps world I think I think this this this is great stuff that you're doing and it's good to give it some visibility to a wider audience. That's a good idea. Yeah, so I may propose a, I fear that I may propose a combined talk with me and me and maybe Kristen or me and Kristen and Angelique and one or two of the. So yeah, that's a good idea thanks for the suggestion Alyssa. Let me think about that I know that CFP is open for DevOps world so Okay, so. Anything else on outreach programs. So there was an ongoing discussion about doing something with open source design. Right now I'm just tracking open source design and main increase, etc. So we want to miss the upcoming event, hopefully, but yeah there is no specific update and definitely with the current load I'm not ready to facilitate that. So we'll, if there is a program we will try to join, if not. Okay. So, onboarding online event organizers and also outreach program organizers hopefully a couple of weeks ago, we did a series of blog posts about that. We also had a session for contributors who responded to the call for participation. And at this session we've got five participants, we also had some follow up discussions for those who are unable to join. Yeah. Yeah, so we have a few follow ups, including organizing events, etc. Hopefully you will be able to onboard these contributors to organizing events and this list. Yeah, I was, I was very pleased with that events orientation because out of that I got a volunteer to assist with co hosting the webinar with the online meetup with Uli Hoffner so that already for me was very positive. Yeah, now we just need to make it happen. Also, yeah, there is a slide deck which we created. Well, we shot advance for this event to be honest. But yeah, that's how I create slides always. Maybe I will keep improving them and maybe we will. So I have an action item to convert some of these slides to documentation, etc. Because our gene sales slash specific events are quite shallow when it comes to organizing meetups. So if I recall correctly, he was participant in this session. So, yeah, anyway, we have a plan for that. So let's hope it works because you usually need more organizers. Okay. Then we discussed the box walk safety and asked me anything meetup. So, at least said that the best date would be May 4. And yeah, let's do that. I guess there will be a lot of Star Wars related imaging during this presentation. I'm not sure. But yeah, let's do the meetup and I started the poll in Doodle. So please vote for the time slots. And yeah, we will try to announce it shortly so that we can also see through DevOps world and Jenkins and whatever other channels. One question about that, that what we do call for papers specifically for the community track or for community and CDF tracks. I'm not sure what is the plan of the continuous different foundation for their track. So, you know, right now we have, we just did the CFP for for DevOps world through. We have a track there so we're just pushing people to, to the DevOps to submit their, their, excuse me, I can't, I don't know I can't speak but to submit their talk through the CFP process from cloud bees. I just need to sync actually with Katie and also probably you Alyssa on, like I know I'm the chair but then I also need to just recruit a few other people to join the committee. So, yeah, whatever that the CFP process ends up being through cloud bees that's what we'll follow. Yeah, so basically it means that you can have more or less the same discussion for both. So Jackie for for the CFP. What happened was that we, I think the so called bees was only able to purchase a certain amount of seats for the portal submittal. So, so what's going to happen with the CDF track is that you're, you're going to the be the chair so that means you have access to the portal to the tool, and then, but your graders won't. Okay, we'll probably have to work through a spreadsheet. Okay. Yeah, that's, that's fine. We can definitely help out with regards to inputting the data. I know it's a panel but but we can help you out with that too. Yeah, I mean I figured I probably probably what I'll probably try to do is just get like a community member from each of the incubating projects to represent. And, or if not all ask the ambassadors and basically whoever has time to volunteer to help grade them. But yeah, I'm okay with just exporting it and then having to do the manual input. Okay. And yeah for the CDF track, do we formally consider CDF track as a as a second community track or do we consider it as an industry track or what's the positioning for promotion of this track. I pretty much I left it pretty wide, I left it pretty broad so basically, I took the description of CD con and any talk that you would submit to CD con is, you know, we're going to review and integrate it as part of our track but, Alyssa, is there going to be any, for example, any specific guidance that cloud beast wants us to follow as well or. It's your track, you make it your own so cool. I can speak about the community so basically the way that we want that is to make this a broad community effort so yes we will focus on Jenkins as typically we get a lot of those submissions, and then we're open to to, accepting other open source projects as well. Right, so the term is community and then, and what are some of the, the best practices in building a community and how to maintain a community, those kind of talks. So, community in general. Okay, that makes sense. I'm sure there's going to be lots of overlap so Jackie probably will have some Jenkins sessions in her in her CDF track and I'll probably have some in mind and then there will be practitioner track. I think that probably has Jenkins in it as well see how people using the enterprise so there may be some overlap, but we'll get together and make sure that it's a balance agenda. Okay, for me what it means that you should definitely promote both tracks. If the safety, safety process is the same and application. Well, and that is not clear the borderless promote everything. So then I see community tends to be abstracts. Yeah, and I have probably like what we ended up doing last year as well was like, if it didn't fit in the community track like it got pushed to our track as well so we're flexible I'm okay with that. Yeah. Me too. Okay, anything else on this meetup. No. Thanks a lot stories for green to present there. Look at the agenda. Alyssa sorry this is related to DevOps world but I know on Tuesday on the 20th they Selena sent out a hey like hold this slot but there was no like link so I didn't show up to a meeting because I didn't know what way to show up. Oh, so that was this week. Yeah, it was on Tuesday at on. Yeah, the 420 at two, two o'clock. Yeah, no worries. I'll send you the recording. It was just session, a training on the portal. Yeah, I know I wanted to be part of it but in the invite there wasn't a zoom or a Google link or anything. Oh, that's weird. Okay. Yeah, the recording. Okay, cool. Yeah, please. Okay. No, it's it for me. Okay, thank you. So, Schwark package updates. It's quick. No updates. I do did some background work started drafting the form so that we could understand how many issues we want to send to different places. And yeah, even this process seems to be really complicated. But yes, you can do that. Yeah, one update to for you, Oleg on the swag. So one of the things that they proposed. So they were like we are, she's like we the estimate that we're getting is based on, like, regular mail we're not using ups or FedEx. And I actually can attest to that I tried to go ship something yesterday to Scotland, and it was going to be about $40 and it wasn't a big package either. So she her suggestion is she's like what we could do is we can. We know the quantities that for example we know that we need like 50 t shirts in Europe. She's like we've got partners that we could do a drop shipment to Europe and then we need to provide them with the addresses and then they'll distribute it from Europe. So it'll reduce the cost. So that's one thing that we can do is just do like four or five drop shipments to the regions and then work with those partners there to deliver locally, instead of having to do international like several international packages at once. I don't know if that works for you. But again we just need to get organized and be able to provide them like the list with addresses. So then then that local distributor can create the packaging and all that kind of. So this approach would work if you're shipping let's say only socks, stickers, etc, because you can invest some time, some money upfront, build a stock at all this local distributors and then quickly distribute that. Yeah, if you talk about sending different types and sizes of t shirts, I can assure you it will be a logistics nightmare. Yeah, because we need it, we would need to know ahead of time, for example, what sizes to send over to that local distributor ahead of time. So I just thought I'd share those options with you guys. Yeah, thank you and you're totally right. This option would work if we were doing let's say a massive for the distribution. But in our case, we do limit the short distribution. And in this case, yeah, this thing will likely distribute liquid things even more. So I think that for this time, what we should do is that we create requests on our own. We send it to our local distributor as a would be a Jenkins contributor. Okay, and basically we are done with it. So we will be still using financial but for one for one shipment. Okay, just just let me know and, like I said, we just need to know numbers and if you do want to do t shirts we just need to do sizes. So just let us know and then I can ask pinnacle to just do one drop shipment to that person and then they can figure out how to distribute locally. Okay, here's the previous plan. Okay, so double is totally on my site I just need to provide this lease for that I need to create a group form in recipients and here like headache sauce. But yeah, I will do that. Any other topics for today. Nope, I'm done. I have no topics as well. Then we say that the meeting is done and thanks to everyone. So if you have some time I would appreciate reviews for Jenkins X LinkedIn and blog post routes because this is a big content. Some keys might be sensitive content. Okay, for the rest of you let's just keep working. Thanks. Thank you for hosting. Thanks. Thank you. Thank you. Bye.