 for 321. All right. Hi, everybody. Welcome to the Jenkins Advocacy and Outreach SIG. Today is March 24th. Make sure I have my date right. So on the agenda, I have the discussion to remove. Jenkins is the way on the Jumbotron. The Ukraine imagery messaging on Jenkins.io. Jenkins is the way hosting sites, GSOC, and CDCON. Is there anything else that we should add to the agenda? Those look good to me. Okay. Okay. Let's get the party started. All right. So Remove Jenkins is the way on the Jumbotron. So I know John Mark has been doing some work on that. You want to give us an update on that, John Mark? Actually, I think that one was my action item, Alyssa. Sorry for me jumping in, John Mark. Okay. Sorry. So John Mark, go ahead. So, sorry. So what I did was adding the CDCON announcement. Yep. But I don't remember removing or being asked to remove the Jenkins is the way. Right. And that was my mistake. So, Alyssa, let's put the action item on me to remove Jenkins is the way from the Jumbotron. It's an easy removal or we could have, John Mark, I think you're at the end of your day. So it's probably just quicker for me to do it just because we get it done. Sorry that I forgot to do it. I just completely forgot. Now, and the Jenkins is the way.io.junk or the Jenkins is the way.io is available for us as a URL for quite a while. Right. It's at least until end of this month and you renewed the DNS, Alyssa. So we still own the name for that, even if we don't have the hosting for it ultimately. Yes. Okay. Good. Now, we do have a, we probably want to do a, could you put a separate note here, Alyssa, that we need to work with the infra team to make a redirect from the old location to the new stories.junkans.io location when it's available. We're on the old location to the new location and that's a good enough description. Okay. After, we should actually put after the new location is available. Okay. And this is your action item, Mark, or who is? Yes, that's for me. Okay. Yeah. So this is a little bit of domain name server configuration stuff that we need to do and we may need to work with you to get the permissions to do it, but ultimately it's something that the infra team can help with. Okay. All right. Moving on to the next topic. Okay. So Ukraine invasion by Russia and the Jenkins project. So proposals to temporarily change the Jenkins logo on Jenkins.io to support the Ukraine war or the Ukraine issue. The board has agreed that CDF message can be placed on the site immediately but would move to vote and more discussion to be had about the Cossack image as Oleg has concerns. So I know that Jean-Marc is working on that. Thank you, Jean-Marc. And I'm working to obtain the SVG file for you if you still need that. Yes. So I can show you a prototype of what I have. I quickly whipped something together with Gitpod. So do you want me to show that? Sure. Should I stop sharing? Yes, because then I'm going to share my screen. So there we are. So this is Gitpod, like just going to make it a little bit bigger. And so what we're seeing right now, Jean-Marc, is an IDE view, right? Right, correct. So this is where the configuration is living here. I'm on my fork and on the master branch. So I have the local environment running and I can see it. So it's running in the cloud. And this is how it looks currently. And see the size of the icon here. I am going to change, now this is in my way there, I'm going to change the branch here from master to stop the war one. It will reload and either it does it, where I need to restart the server. Oh, yes. Oh, that's a cool demo, Jean-Marc. You look nice. There's huge potential with that tool, especially for Jenkins.io to do these kind of experiments. So enough sales pitch. This is how the icon that I have been provided looks like. So the comments are there is a white background here because it's a GPEG. So there is a little glitch here. We see the difference between white and gray there. And the image is wider than the initial one. So that means that the sizing is not equal to the other. The Jenkins is smaller. This will be an issue to have it as large as the other in the same rendering. But I think, well, this is what I got working. Jean-Marc, just for experience, would you be willing to make your screen increase if this Chrome do a control plus? I want to increase the zoom factor. Yeah, keep going, keep going, keep going, keep going. Okay. And it's still looking okay. Good. All right. Go back down now. The largest I have, I think it's a little bit more reasonable. So the picture works, the GPEG would work, but I'm bothered by the background. So we make it transparent. And we could convert the GPEG to a PNG and then make the background transparent with some online tools. I've got an online tool I've used that will make an image background transparent. Yeah, or what's her name? Cassenia. Yeah, Cassenia can supply the other one. So unless we don't want to continue over-engineer the resizing. So I did reach out to her this morning and she's been quite responsive, but I'd wait until let's give it to, like towards the end of my day here and for her to respond. But she said she's really, it's really important to her and she appreciates that we're using this image for this messaging. Yeah. So Jean-Marc, you mentioned about the sizing. Is there a specific sizing that I should give her to resize the image? No? Well, yeah, sorry. So for the dirty details, the image can be resized that way. This is the maximum I can do. Okay. Because then going above, because this is how I forced with going further gets clipped by the inner working of the system. Then to get that working, I need to start getting into the plumbing and so for me, if there are no remarks on the sizing, it's the best we can have and is good enough. My humble opinion. Okay. It doesn't hurt the eye. So. Right. Okay. I also had asked Cassenia to send us an image with just the regular Butler. Since we're going to be talking more about this and voting on it, I thought we'd give another option just in case if there's, because when I received this image from Cassenia, I also question what does this, the character mean? Yeah. Right. So and it seems like Oli had the same question. So I figured somebody else is going to have the same question. So I, so let's see what she comes back with. I think that the second option is again, just the regular Butler image with the flag in the back in the circle and that flag stopped the war messaging. Okay. I'm going to show it again. Here you see clearly the sizing thing. So so changing the background here to have the Ukraine and some wording stopped the war or something like that. Yeah. She may do something with his eyes because now his eyes are closed or she might have it open. I don't know. But and I like that Oleg noted that the Captain icon had switched, they switched theirs, which is a relatively simpler icon to use the Ukrainian flag colors as a background. So the the red, I think was what you were alluding to, John Mark here could be could be the two colors of the flag of Ukraine. So interesting idea. Yeah, get but change their logo also to have the two colors. Nice. Okay. So there, if I get two images. So first question, do I fire this as a pull request? Do I wait for a better image? Well, I can mention it as a comment and fire a second one if we have an alternate picture. I'd put it up as a pull request so we can use that as a way for people to view and discuss it because I had to think a little bit about what it meant based on the wording and the posting on community dot Jenkins dot I always I think people will will do a better job if they experience it by going right to the product, the preview site. So if you're okay with doing a pull request, John Mark, I think it would be really great to have a pull request just because we could do a preview site of it. Yeah, everything is ready. And I can I can do that. Okay, so good for me. I think we looked at a practical example. So I can stop sharing, I believe. And we showed off dynamic development using a web hosted Jenkins dot IOS site. Well done, John. I need to prepare something to show off. Great work. All right, okay, so we're going to move on Jenkins is the way site hosting on the and URL update. Just just a little question. The board message. So text in this we live we leave for a second phase. Not for a second phase, but for a second pull request that I'll submit separately, John Mark, because the board said yes, go ahead, no vote needed. It's the same text that CDF used. Let's get it in there. Whereas yours will be using your pull request will use for evaluation discussion. The other one, I'm going to get it in there and get it merged pretty quickly. And where are you going to put the text? Don't know yet. I have to go find the place on the page. Because I know where it is. If you allow me, Alissa, can I show my screen again? Yes, sorry to be nitpicking, but this is great. It can share. So this is controlled. So this text here is controlled at the same place as the the icon. So this is where we could put it. We just need to see how it flows in these kind of details. Otherwise it needs to be in the jumbotron. And I like where you highlighted. I think that's the best choice for where to put it. So I will I will propose that as the location. And then we can look at it in the preview to see how it how it flows. Okay. But we won't separate PRs. Otherwise you look at where I change it. And I just show you here. This is where it happens. Yeah. So this is where I put the image. And this is here where you can. Okay. Now, sorry for the interruption, but these little details can save us time. Back to you, Alissa. You're on mute. Still on mute. Sorry about that. Okay, you can see my screen now? Yes. Okay. See moving on to the next topic. So the hosting of the site for Jenkins is the way I we've decided stories. Jenkins.io. Anything else you want to add to this mark? Gavin Mogan shared that he's making good progress on it and and has good hopes that he'll be done with it by the end of March. He may be done with it. Before that, he said, hey, he's got the the caching configuration ready that's used for the content distribution network on Fastly. He's got the Gatsby site done. He's got the repository ready. So it's it's getting very close. He just needs a little bit more time to work on it and felt like he's pretty confident he'll have it done before the end of March. Okay. Great. And by the way, he's using this also as a place to experiment with alternate site generation techniques with other things that may ultimately help us on Jenkins.io on the documentation site. So he's he's he's doing the great kind of stuff that Gavin does. Yeah. Yeah. It's it's it's a lot of he has spent a lot of time on it. So I really appreciate it. All right. So moving on to Google summer of code. How did the one hour brainstorming went, Mark? I for me, I was thrilled with it. We had so we had Rashab, who was a former G Sox G Sox student. And we also had harsher who was interested but unable to attend who wants to mentor as well. So we had two additional mentors plus me plus Chris Stern and two candidates involved and one who couldn't be there. So we had four of us of a group of six or eight that were interested and had a very good discussion in the process of the discussion. We found three or four or five different topics where any one of us would have missed it. But because we were all sitting together talking about it, we realized, oh, this is important. This is important. It was one of those experiences of remembering why public and open collaboration is so valuable. Because we benefit from each other. Yes, I admit, the two people were effectively preparing two different proposals, and yet they both benefited by being together to talk about how they think it should be done. Nice demonstration. Great. Yeah. So do you suggest that we do that for other project ideas? That was what we launched this morning in John Mark, I think was interested. John Mark, maybe you want to talk about how you envision it working for plug-in health score? Yeah, indeed. So the topic was raised at the end of today's office hour. Some very good questions and with a different point of views on it. And so we agreed that there was a strong consensus to make likewise a brainstorm session on the plug-in health score initiative. And so the current proposal that was published on the Gitter channel is to hold it on March 31st, hoping that's correct English, at 2 p.m. UTC. Okay. So and we're going to collect the same process as for the get cash. So going to collect as many questions or ideas or topics beforehand. So that's rolling. Okay. So that's for the plug-in health score. What about the rest of the project ideas? Should we? There, I think it will depend on what I think is we watch for that. In order to do one of these brainstorming sessions, we need someone who is very actively willing to run the session, who is actively willing to gather the questions, facilitate host. And I'm not sure that the other project ideas have that same active thing. I would expect, for instance, Chris Stern will probably want to do it. But let's go through a couple of these sessions so that we learn from them before persuading others. Okay. Okay. So one step at a time. Well, at least, John Mark, your thoughts? I think it's an idea. It helps. Let the people come with a question and let's feel on the Gitter channel what is the sentiment there because it's, I won't say expensive, but energy-wise it requires the mobilization of resources and stretching time zones on that. It's worthwhile to do, but it would be a pity to waste it unnecessarily if it can be done out of waste. This is my standpoint. Okay. I just wanted to correct one thing, Alyssa, on the next line you're saying there's one proposal, a draft proposal received, there are two and probably a third one today. The second one just come in, John Mark? I didn't. I've seen it yesterday evening. I have it on my planning to read it. A personal comment on that, it's a very powerful method. It's not easy to do. It's an important step for the attendees to do, but it's super powerful and it prevents wasting time from the mentors reviewing the proposals. So we definitely need to promote that and the community gains from the exercise. So very good idea. The other one is, I'm going to tell you after the meeting so you can- I can look it up. I can look it up after the meeting. No worries. I'll just leave it blank for now and I'll fill it in after. So we will be doing a call out for mentors to review the proposal drafts. Yeah, even if it's not their specialty. So it is my personal point of view, already be acquainted on the subject and there are enough comments that can be done on the document by just looking at it and these comments can help the students or always forget the word, but the candidates to have a more powerful presentation. The more people look at it and comment at it, the better everybody will grow. That sound okay, Mark? Okay. Yes. I'm going to send it out and try out the mailing list for mentors. And then I took a stab at working on a template for grading and let's see what it's here. So this is just my initial stab at this. I will reach out to previous mentors and solicit their feedback. But basically what I have here is a ranking system number from one to five. Jean-Marc and I discussed this in great details yesterday and again, not really knowing what Google is going to send us. So basically I'm thinking, okay, we'll send, they'll give us a PDF file, we'll have links to it and then links to each of the proposals and then reviews, reviewer notes. I've got reviewer notes and grading from each of the mentors, average score, final decision. So based on, so I will take this and solicit it amongst the previous mentors and see what else that we need to add, delete, edit. Okay. There are two things we discussed yesterday that we may maybe add for. So one thing is we need to describe beforehand how we are going to deal with ties. So meaning when two have the same grade for preventing a straightforward ranking, what is the method, how we vote or how it works. The second thing that we need to work on is what are the questions, what are the things that's being graded. So meaning what is the question that the mentor is answering when accepting or why not and give some guidelines. So we're making progress. We start to have a good understanding thanks to the work that Alyssa is doing with the previous mentors. So looking good, we're getting prepared. So Jean-Marc, I think one of the things, so you mentioned about how do we resolve ties. So in reading Oleg's notes from previous year, the things that's going to, I think the thing that's going to be helpful for us is the reviewers notes. So that's going to be looked at carefully. And at least that's what I do too when I'm doing the CFP for DevOps, World or CD-Con. That's where the reviewers note is going to come in really handy. But nonetheless, I will still ask that question from our previous mentors if there's other techniques or ways to cut the ties. Yeah, what I want to prevent is, what I want to help us is that we have some objective criterias that we can look at to help us in making a decision. And that the decision is not made, there's always at the end a human decision. But I don't want to fall into the pitfall of, yeah, okay, I like this person and I'm choosing him. No, I wanted a straight, clear process with guidelines and described before him. So there's my personal point of view as we discussed yesterday. I've been through enough of these because it's important for the people. So we need to respect that. Sure, absolutely. So the question I have is, do we need to do a pull request for this, the template, just to get discussions or input on it, Mark? That's a good insight. I think we certainly want, just as John Mark said, we want to find ways to express objective criteria for the evaluation and the template's a good start for it. Yeah, why not? I wonder if maybe it ought to be rather than a pull request, open it as a discussion on community.jankins.io in the mentors list that John Mark has started. Because really, it's probably good that it be publicly visible discussion, but that the voices that are being heard are mostly mentors, not the candidates themselves saying, hey, I want to be judged by this or that. Okay, so the community list that John Mark created, that's for this year's mentors. But what if we want feedback from previous year's mentors? If I would guess that we're unlikely to get a lot of feedback from them, but if we do, we can certainly accept it by email and then sure as a proxy. Right, exactly. Okay, got it. John Mark, does that sound okay to you if we use community.jankins.io? I worry that if we use a pull request, we will be much less likely to get feedback than the very approachable format that community.jankins.io is. Yeah, this is what I had in my mind when starting that. Great, I will do that then. Anything else you want to add on this topic, John Mark? No, it's looking good and a very interesting experience. For sure. Like it. For sure. Okay, so then we'll go on the next, the last item, which is CDCon. CDF finally got back to me about our Jenkins contributor summit. ETA, this is just an ETA, is that the Jenkins contributor summit will be on Friday, June 10th. I asked for a Thursday, June 9th, because many of us have to fly back out, but most likely they said it's going to be June 10th and they won't know for sure until they announce the agenda next week. Okay. They will not have, they will not have like an exhibit, exhibit or booth, but I think they just have a small area. Probably with tables, I think they don't probably don't have the details on it because I asked a question and they couldn't answer it. But I think right now they're looking at something quite small for us if, you know, to staff. But at this point, we don't know, we don't have enough information to plan how much staffing and what is needed and all that yet. Okay. Mark, when do we start working on, on that subject? We're still waiting or? No, we could, we could certainly start any time. I think we ought to set ourselves an April 1 start and just agree that we're going to get started then. I haven't launched it yet, but I think it's, it's getting time. We need to, we need to be sure that we, we generate interest and that people who are going to be in person. Oleg did ask a question in governance yesterday. Hey, what about since CD-Con is now allowing remote presentations, should we have a remote contributor summit? And my thought was, or what CD-Con is allowing is hybrid. So they're going to have both remote and local. But my, my thought was, I don't want to attempt a hybrid contributor summit. Let's either be all remote or all local. And for CD-Con, I think it should be all local. We've got some good participants in Austin itself, who are local to that community. And I think we'll have others who will be joining the conference physically attending. So let's, I think we should do this one local and then maybe two or four weeks later we could consider doing an all remote contributors summit. Yeah, I think that makes sense. Just don't forget to, that I'm, I'm available at least for the preparation part. And so I'm new to this, but I think I can add my stone to it. I can help dig up some of the material that was used to set up for the last contributor, online contributor summit and that, hopefully that can help us get the ball rolling. Jean-Marc, so I'll dig something up and I'll share with you. Yeah, going to see, just that I want, I'm busy with the mentoring and, and administration of TSOC, but just a reminder, I can, I can give a hand too. And I'm interested to learn. Although this one, because it's co-located, I think really it's best for Alyssa and me to work it together, Jean-Marc. We appreciate your, your help with the organizing, but ultimately I've got strong incentive to do this because I'll physically be there running it. Right. Okay. Makes sense. Yes. I just watch and learn from it. Okay. That's it. There's anything else? Thank you.