 And I believe the recording is on. Okay. Hi everybody. Thanks for joining the Jenkins advocacy and outreach sick meeting today is Thursday, February 9. On the agenda I have just a couple of action items to go over. And we're going to do a recap of Fostum so I'm hoping Jean-Marc and Bruno can walk us through that a little bit give us a little bit feedback. And then we'll talk about G sock. She code Africa. CD con and scale. Is there anything else that we need to add to the agenda. Nope. Okay, sorry. All right, so I have already submitted the, the G sock application for for Jenkins as the mentoring org so we will wait for that until believe us to 22nd. This is where you have a drum roll. Yeah. So that's done. And we're, we're just in waiting mode at the moment. And then the January newsletter has been published. So thank you, Bruno, for all of that and thanks to all the sick chairs for their contributions there. So we're going to the agenda so Fostum. Jean-Marc, I'll start with you. What was your some of your key takeaways and what are some things that we can improve for next year. It was what was good. It was good seeing people and being able to interact with people. There was a huge crowd, a lot of interest, and a lot of that positive interest was triggered. First by the very nice. Mini cluster that Jenkins cluster that Bruno brought with flickering, flickering lights and all that that created a lot of attention as well as the new UI, the UI improvements. And at the same time, these two elements were great. Icebreakers or to start a conversation with the people and they were a lot of good conversation that were done there. Stickers were, I don't know what they do. They were so hungry that they were eating them. I don't know, but nearly all the stickers went away. We had a good collection of them and it's, it's a nice way to also break the ice and start a conversation. As you would guess, I had a lot of discussions around Google summer of codes and was somehow disappointed by the fact that at least in Europe. The program is not that no. So this is something that we could improve or an attention point. Now, what we could have improved. Well, Well, first thing the fun factor was very high. So there was good very good humor. My idea with coming from from sales from sales background there. We could make it even better in organizing conversations. Preparing or having a little briefing on how do you engage the conversation. What are the main messages to pass or a lot of questions were about what is the future of Jenkins where we heading. When will this be fixed. And unless you're deeply rooted in all the affairs and decision making process in the Jenkins and looking at Mark White here, most of us have to improvise a little bit. Preparing that part better would give even more efficient and powerful message to the various users and contributors. So that was one. That would that was the the main, the main improvement. I think the impact we had at that conference with barely lippin means was very high. And I was super satisfied by participation to that to that conference. To mark his hand. Yes, and you need to stop. Mark, I think I saw reference to a presentation of of Tim Jacome and Jan Farachiks. What's next in in Jenkins UI. How was that presented was it shown as a video on the screen was Tim there to talk about it was young there to talk about it. What was the what was the presentation mechanism and how was it received. Well, as far as I know, it was just a preview website, something that a mock up of something that we were showing up after the first time somebody asked on Twitter for some more information and then only answered about the video of team and project. Got it. Okay, so, so what was shown at the at the conference was screenshots or or a website, whichever it was. At best, just the visualization of their markup no conversation about it no, not presenting Tim's and Jan's observations about why this is important why that is important that kind of thing. Okay, thank you. And this goes in it into the direction. The people at the stands myself or others. We could have been better prepared to explain this or to share that, but even with the little preparation we had we had some very good conversation. So, I have an action item pending from the governance board to update and make the current roadmap on Jenkins that I owe actually current but I assume that during the FOSM segment you didn't refer to the roadmap probably at all. No. So, so the fact that it's badly out of date compared to actual implementation was not harmful to you, but it also did not help you. Yeah, okay. Sorry. But here that this this shows the the feeling of not having the right tools or not mastering the right tools to even better leverage the contacts we had. Got it. Thank you. Okay, thanks very much. Bruno does this this summary. Yeah, it perfectly fine. Thank you. We had the same kind of experience. I don't have much to add. No, frankly, the thing is, I've already said it to Mark and Alisa first and helped me to realize that open source is not just a bunch of people working on the same projects. It's more of a spirit of trying to help people and powering them to get, you know, better or something and just to be free. In fact, and that's something I felt deeply when being in the first dam. People just wanting to share knowledge to help each other to think of partnerships to, you know, to grow together and that's something that you don't always get when you are just interacting on GitHub, Twitter, whatever. This was really different. Yeah, less mechanical, you know, I tend to think of open source like just to get a punch card. It's much more than that and this showed up pretty big at first. So we know what we can improve for this or other conferences. For sure. Yeah. And did we did in the past conferences we've run a rotating slide deck with with mini-gen running on the screen that you had I assume you were focused on keeping Jenkins visible rather than doing any rotating slide deck. We had the rotating slide deck. We made it on the booth. So we had a few slides, but most of the time we were showing Jan and Tim's UI proposals, and then we were going back to the mini-gen control dashboard. So we were, we had three tabs and rotating between the three of them. Okay, so that was an important thing. So as Alyssa and I are going to head to a conference here in the United States in March, you rotated screens by just switching tabs on the browser. Yeah, yeah. Okay, all right. Switch browser tabs. And we had just one Wi-Fi network for the whole booth that holds the machines on the machine composing mini-gen but also Damian's laptop, everyone was sharing the same Wi-Fi but it was easy to show things. Okay. And Alyssa, you're bringing, you're bringing the screen to scale, right? I don't have to bring a screen. Bruno, your mini-gen has inspired, I'm intending to build my own, and I'm bringing a cluster of pies to the scale conference as well to have a physical device to to incent people to come have a conversation with us. We'll see. Yes. We haven't done that kind of physical device story in the past. And so we'll see if it helps increase traffic at scale. It worked one time. Hopefully it will work multiple times. We'll see. As long as people don't get bored, let's continue. But at least, at least it wakes up the curiosity of the people. Yeah, it was a nice eye-catcher. This is where you, where exactly, this is where you need to jump. It's like when you give stickers and you say, well, help yourself. By the way, are you using Jenkins? And what do you do with it? And where does it help you and what are the pain points? Yes. And the last thing I was not prepared to was people just wanting to come and testify about their love and use of Jenkins. I was afraid of getting some hate, something, you know, but no, people love Jenkins. That's cool. A lot of very satisfying stories. Very nice. So I mentioned to Bruno, the one thing that we have in common is that, so I go to a lot of conferences in the States and in Europe. And when I'm at the Jenkins booth, they come and they say the same thing, regardless of where I'm at. So the messaging is quite consistent. So I believe in it. I thought at first I thought, well, people are just, you know, it's just a way to break the ice. But they're just trying, being nice. But it's pretty much the same everywhere we go when we have a Jenkins booth. And I was amazed at the variety of industries that people are using Jenkins in. Of course, I already knew about embedded automotive, but we had somebody from CERN. I actually remember the acronym. It's something about nuclear in Europe. High energy physics. Yeah, that's where the worldwide web got invented. And boom, people are using, people from CERN are using Jenkins. There's lots and lots and even, I don't know, Domotique in French, you know, things to automate your blinders, your house, your door, whatever. OpenHAB is the name of the project. They came and said, we're using Jenkins. We love it and so on and so on and so on. Jenkins is just about everywhere. The only message that was not that good was that most of the people using Jenkins for embedded software were building with Jenkins, but not testing or deploying things to Jenkins. So that's something we should maybe have a look at. Great. Thanks, John Mark and Bruno for sacrificing your weekend to staff the stand. Totally worth it. I loved it. And to be frank, yeah, being able to come in country. Yeah, and see John Mark, Damien, Oleg, Alexander, Olivier, for example, for real, having them all for me and for the others just for the weekend, that was super cool. Very nice. Okay. So moving on to GSOC. So as I mentioned, we did apply as a mentoring org. We made it before the deadline. And so now we are planning our next phase, which is the office hours. So we're going to assume that we've been accepted. So we're going to plan as such a little bit snobbish. We're going to be optimistic. It will work. Yeah. And with John Mark's magic touch and meeting the GSOC folks in FOSTA, that's like 99.9% confidence in me feeling that we're going to get accepted so we're planning ahead. So the next phase is going to be the office hours where the mentors will go over the project ideas in detail and answer any questions we contributors potential contributors might have. Like I said, the announcement, well, the announcement for the accepted mentoring orgs is going to be February 22nd. So as soon as that is announced, we will, we're going to go ahead and schedule for the office hours to be on the 23rd. So if I can jump in there. So these office hours are the backbone, or the next important phase, which is where the students are preparing their submission for that. So that this is a month and a half long, and we'll start immediately. I'm currently preparing with the help of Alyssa, a poll to know what is the adequate time for that. So historically, we held the office hour around four o'clock p.m. UTC, which is about this time now this winter time. And so I have, I have some doubts. I'm going I'm preparing and reviewing the poll might go out tomorrow. I need to do a test review with a couple of of you. So because currently I think it's midnight in Hong Kong, or nearly midnight. Chris. I think it's okay though I prefer this time. Yeah, so I need to check with India. I like this this time because this is where we cover most of the earth and the other part of the earth that is not covered is just water, the Pacific Ocean. So, but we're fine tuning. Another important thing is currently there is a huge amount of activity and interest on the various channels that we have. And some mentors in particular Chris are super active, guiding the people, helping them out. I have precise figures of how many people are interested, but I would like to thank Chris here for his dedication and the great work he's doing in mentoring and helping all those people. So Chris, thank you, thank you very much for all you're doing. To recap, next steps for Google Summer of Code. We are helping out people that are still building their last Jenkins muscle as I named that face, we are preparing the first office hours. And as we are confirmed to be part of the program, February 22. We roll, and we start by explaining in details every project. This is where we standing. I listen back to you. Thank you, Sean mark. Any questions on G suck. Okay, so she code Africa mark I will hand that over to you. You're on mute mark. Me being the bearer of bad news. We've done the she code Africa contribute on I think two or three of the latter two or two or three years now, and, and felt like it was a good, a good use of, of our energy. I've told the cloud bees that they donated $6,000 each year to to fund the Jenkins projects participation. This year, I don't feel like we should do she code Africa contribute on and so I've made the personal decision, I'm not going to do she code Africa contribute on and since I was the primary driver in the past. That means the Jenkins project will not do she code Africa contribute on. I think we should focus our effort on Google summer of code. The, the realization came to me as I was describing to other mentors that even during this phase of Google summer of code a mentor should expect to spend four to eight hours a week on their project, preparing to mentor preparing for the selections preparing getting themselves more deeply involved, and I can't do that and, and also run she code Africa contribute on and so it's a this is an intentional choice on my part that she code Africa contribute on won't happen in the Jenkins project this year, because I believe we'll get more value out of focusing all our energy on Google summer of code. I'm open to other disputes, but my sense, I've told Zeno, I won't we won't be participating and, and they'll just have to go ahead without the Jenkins project. I personally believe that, given, given the current situation, we're, we're low on on mentors and people that are able to dedicate their time that we need now to be very cautious and thoughtful. About where we put the energy and there are a lot of, there's a lot of attention and also requirement in Google summer of code. As Mark, Mark said, it's a sad decision. Right, but we the choices have to be done. I think she code Africa, the challenge there. It's pretty much the same as G sock. There's finding mentors is really hard and mark in the past couple of years has been shouldering this on his own for a few years so I think it's a lot. It's a lot so now let's focus on quality versus quantity. Super. Thanks. That's all that I had on that one. Okay. Thanks, Mark. So CD con, we're still planning for that. The CFP is open until tomorrow tomorrow's the last day so mark if you want to make a submission there we have one more day. And then they're also talking about doing the Jenkins awards again so past couple of years, we've been doing the same award. Most valuable advocate most valuable contributor security MVP, and we will be driving this award within the project or from the project, and then CDF will showcase or announce the award at CD con. So there are some important dates there that I will need to work on. So the nomination is already actually. Yeah, it's already open but I need to get to create a pull request for that. So, keep an eye out for that so once that is open I will announce it via Twitter and LinkedIn and you got submissions nominations please nominate folks. And then scale planning is in progress as Mark mentioned he will mimic the, the great idea from Bruno and create a cluster of PIs and we'll have that on our table at our stand hopefully that will I'm sure that will attract attention and and be a conversation starter for us. I didn't realize it was so near. Yeah, nine is is. Yeah, for weeks so. Typically the open source events for us is it seems to happen beginning of the year the first one or two and three months. That's when we're most busy. Yeah. And then, okay. And then for today's security advisory. Yep. I got that so I will work on that after this meeting Mark. Yeah, and unless I was going to offer usually that's not when we want to put on you just because the phrasing has to be relatively precise. Okay, I'd even say if you don't mind let me take it, particularly because of how deeply I'm involved in that particular set of things that's a platform sig topic. And if it were phrased incorrectly it might look like it where I get plug in problem when it is in fact not. Okay, so so it's, it's the words, the words are carefully chosen when we do security, security tweets. And if we don't say exactly the right words, we risk that someone will be confused and will create unnecessary unnecessary angst or concern. Got it. Okay. Thank you for taking that over. I'm not going to play complain about less work. Okay, I, that's it. Unless anybody has anything else that they want to cover tiny little thing I'm giving a talk next week in the local university about open source and Jenkins. Right. Cool. Bruno, do you want to put the information on this document and then I will, then I'll send out a tweet. Let me know the link and the date and all that stuff. We'll do. Okay. Awesome. Alrighty.