 Welcome everyone. This is Jenkins documentation office hours. It's the 14th of March, 2024. Topics on the agenda, LTS, most recent LTS, contributor spotlight, weekly, Google summer of code, Jenkins community awards, version documentation, tutorial revamps and sponsor attributions, anything else that needs to go on to the agenda. Nothing I can think of. Thank you, Mark. Okay. All right. And I assume that you'll have some question or topics you want to address under Google Google summer of code. And we'll we'll cover them there if that's all right. Sure. Thank you so much. All right. Okay. So the next long term support release is coming it will be a little less than a week from now six days and the change log and upgrade guide needs to be reviewed and approved. And there are some changes in it that have been noted. And oh, that's interesting. Okay. So this one, I'll have to look at it further. I'm not sure what how that would have gotten into 2.440.2. So, because these two things didn't change in that release, so I'll have to look at it more closely. Any questions or comments on the long term support release that's upcoming. Okay. Next topic then is the contributor spotlight published about a week ago for Stefan speaker. And we can see it here it was published on the 6th. Our next publication will be next week so that let's see 6 plus 14 is 20 on the 20th and congratulations it will be Bruno Van Ochten. I assume you have reviewed and approved. Yes, I have reviewed and approved last week, I think. All right. And other spotlights are will be will be created after Kevin returns from vacation. Great. Thank you. And thanks Bruno for your contributions to Jenkins. Thanks very, very much. You're welcome. My pleasure. All right Jenkins weekly 2.449 has released. And this one highlights a new feature of the change log thanks to Daniel Beck. Notice that this is showing one and only one change log. Now if I go to the download page I can still see all the change logs here. So 4449 448 they're all here, but this permanent to the entry gives me exactly one on a dedicated page makes it a lot easier to see a single page. The same thing applies for the stable stable releases the LTS where if I click this one I see exactly and only 2.440.1 special thanks to Daniel Beck for the work to do that. I love how it feels and reminder that Jenkins uses a mirror system and one of those mirrors unfortunately is down. Let's see. Oh, I take it back. It's back. Well, this is great. I love live live data. This mirror was down Monday, Tuesday and Wednesday while its operating system was upgraded, but obviously it's back now. And this is 2.448. Let's see if they've already completed the synchronization of 449 this weekly and they have so they have obviously resinked very good. So thanks very much to the Oregon State University open source laboratory. They host that for us. The other one of their mirrors this NYC mirror will be down soon for again a an upgrade of operating system. All right was down and is now back. Anything else on that weekly release. No, thank you. But I think there was another mirror about to be up for Jenkins. I think in the coming weeks or so in Romania, if I'm not mistaken. Actually, there are several new there are a few new new mirrors proposed or in progress. Right. And if we look at that page we can already see I think one of them. This one. Oh, and it's now live. Good. Okay. So mirror dot free diff dot org is in Singapore just like Savannah is. So if we look over here if we zoom in really close we should see yes there's number nine in Singapore and now where is number eight. I don't remember where well number eight is not visible on screen here so I'm not sure where it's hiding but number eight from Savannah is definitely in that at that same rough distance right. They are both somehow in Singapore within a few kilometers of each other. Oh, that's why. Oh, wow, so close. Yeah, so and and kind of exciting that we've got to so we that will more evenly spread the load from places like India. Right. Instead of just being served by the one at Savannah we've now got to that will be reachable from India so much appreciated very much appreciated. That's pretty cool but we don't have any in India yet nor near China. No, no, we have to we have one in China, single University, and we may and yes and there are certainly other sites that are mirroring but are not subscribed to our mirror network in China. Added and it was I forget what the name of that one was. Oh, free free diff that's right in Singapore. And then to have been proposed for Romania. And we'll we'll see how that goes. It's really great to spread the load, the bandwidth demands around the world. Okay, next topic or anything else on weekly. No. Okay, Google summer of code so I use was there something you wanted to ask March 18 is the opening of submissions to Google by potential contributors, the, the, they will close. I believe isn't it early April. I think so. There's a period of roughly two weeks where applications can be submitted mentors are evaluating are reviewing and commenting on proposals. Right on draft proposals. So submit draft proposals through the Google form listed in the Gitter channel right. And that gives us a link to, to review the document. Yeah, so the reviews, I'm reading a Alice has post on committee. So the deadline submit the draft proposal for review is March 22nd. Ah, okay, good. So that that's challenging be all right so let's let's find that when we're not in a hurry to submit to Google yet. Okay. I don't know what they have to, I can't remember what applicants have to do. I think it just something that says I'm part of the G suck. I'm a last time, last time they had to submit a PDF of their proposal already. Okay, right. So, so at least as far as I know it's, but we want to do the reviews of the draft proposals in Google docs, and that's what's being coordinated as far as I know through this Google form. So you said that Alyssa had posted. Yes, that we have to contributors have to post their draft proposal for review before March, March 22nd. Okay, all right. Great. So I'll check with Alyssa I've, I'm not sure I've got access. I'm not sure that he has access to the sheet with the Google dot with the proposal links. I'll share an old one. Oh, that would be great if you could Bruno. Of course. All right. Anything else on Google summer of code. Yeah, I have one doubt. So basically, for the reading the proposal for doubt personal so we, is there any kind of a maximum limit that a mentor can do without proposal. So you're asking is there an upper limit on the number of the number of lines or pages in the proposal. So, kind of how many times a mentor can give you so one or two, three. Oh, wait a sec. Okay, so your question was, is there an upper limit on the number of these projects that a mentor will mentor will act as a mentor on is that correct. Yeah. Okay, yes, so there isn't one enforced by that enforced by Google, however, there is one that we haven't been enforcing in years past. So, we, we have limited ourselves to one lead mentor. To lead mentors serve a single project. So meaning Mark weight, let's use a very specific example Mark weight will lead be lead mentor lead mentor for one and only one project. Did that answer your question I use. Yeah, thanks. Yeah, so I have one. Go ahead. Hi, thanks so much. So hi, I have one more doubt so in the last year we discarded to two projects also due to the inevitability of the mentors, like, so is there and did Jenkins and do have some kind of improvements in this year so that we didn't over this kind of problem. Yes, so we what we've done is done what we did last year which is mentors have been recruited, recruited and clearly identified, and let's call it lead mentors right lead mentors have been recruited and clearly identified. And we've stated that that a lead mentor will have only one project. And if I read correctly, I think Chris is noted as a lead mentor for more than one project. So, of course, one of these projects will have to be abandoned. Right so so Mark and Chris are both listed as potential lead mentors for more than one project. Right, and, and the reality is only one of those projects will be selected. Now, the challenge is, okay, which one will we select. Mark, at least I know what Mark will do Mark will look at the project proposals and select the one he thinks has the, the most benefit for the Jenkins project, the most interest for me and the most. The best chance for success. So, so the yes, I issue you choose a project submit a proposal for it. And there is still a risk that your project is not selected because the lead mentor looks at yours and says no this other thing was more more important to me or more valuable to me or a better proposal. Okay. Uh huh. Yeah, lead mentor is a heavyweight role is a heavy role. And requires lots of time. Right. Oh, yes. We're looking at typically we're looking a full day a week so eight or more hours a week that ends up being demanded from a lead mentor and that's an awful lot when you're employed full time. Did that did you have other questions I use. No, thanks so much. Okay, great. Bruno, was there anything you wanted to highlight on Google summer of code. You know, I think you said it all, I know it's a pity to see some projects not being selected in the end, even if they are really important for the community. But that's one of the rules you have a different number of mentors, you have a different number of slots for the Google summer of code so you have to choose. And yes, it's painful to choose but you have to. That's part of the game. Thank you. Thanks very much. Next topic then Jenkins Community Awards. Alyssa Tong announced the, the nomination, the opening of nominations nominations have now closed. And the, the, the award possibilities most valuable contributor. And there's a voting form available here and there is also a voting form for all the CDF awards so CDF has a broader group of awards. The Jenkins project presents three awards. And then CDF has others like the one Kevin's nominated for which is top documenter voting closes in less than a week. And yes, they will, they are checking you only get to vote once because you have to authenticate to the, to the voting system. And yes, we know that means your ballot is not secret and we accept that. Okay. Anything else on on Jenkins Community Awards. No, just don't forget to vote for Kevin. Yes, I agree. Don't forget to vote for Kevin. Kevin's an excellent candidate. I've looked at the three candidates for that award and I think Kevin's the best choice. So very good. Next topic then is version documentation for Jenkins.io. This is a Google summer of code project from last year that is still being evolved and developed. The, we've got a delay on the infra team is busy with, with other items that need their attention. And we're, we're, we're delighted to see the continuing progress. Vandit Singh is the lead developer. And Chris Stern is the lead mentor. And Kevin Martins is a key reviewer. So thanks to thanks to everyone involved in that it's it continues to look quite promising. Any questions there? No question, just a comment. Vandit Singh is also mentor this year for GSOC. Yeah. And we like that we like it when a, when a GSOC contributor from a previous year comes back and says as a mentor I've had help from get plug in GSOC contributors with later get plug in projects as mentors. Yeah, and I think Chris is in previous GSOC contributor, right? Yes, Chris is, that's correct. All right, next topic then tutorial revamped. So Bruno, why don't you give us an overview here. Oh, yes, it's also GSOC 2023 follow up. In fact, with a shooter Saxena last year we worked on a way to rework on the existing tutorials that were making a heavy use of Docker and unfortunately Docker in Docker. And frankly, these tutorials were pretty intimidating. If you didn't know much about Docker. Frankly, I knew a little bit about Docker when I started these tutorials and I was still intimidated. So not an easy task and I guess that some new commerce to Jenkins where afraid to even start with Jenkins because of that. So we decided to do something easier for end users via the use of Docker compose. So we created repository into Jenkins docs organization and one of the end user clones the repo and just enters a command such as Docker compose minus the Maven for the Maven tutorial Python for Python node for node and so on. The tutorial then becomes much more Jenkins centric and the end user doesn't know to have to know much about Docker anymore just how to install Docker on his machine and launch a Docker come on compose come on. And bam, you've got Jenkins controller and agent working to help you with tutorials. So we've done up to now Maven Python node. The multi branch pipeline tutorial isn't a review right now. And now I'm starting with the rewriting of the install Jenkins on top of Docker tutorial which may prove more difficult to to revamp we'll see. Okay, so you're you're on the the big picture instructions the ones we said at the very beginning were the worst example. Yes, indeed. Great. But we'll see if it becomes a catastrophe later on. That's that's excellent Bruno. Thank you very much. Okay, so this is already in progress. Yep. Any questions for from others on on the tutorial rework and how that's progressing. Super. I think it's a great story to show one how how Google Summer of Code has benefited us and two to highlight the very practical reality that many Google Summer of Code projects need extra work after the project has finished. Before they have given all their value to to users and we have some other examples like that the GitLab branch source plugin was a Google Summer of Code project originally, and is now in major production use in all sorts of places and has been through two or three different sets of maintainers in since its initial creation. And I think also the plugin installation tool is also a G suck product. That's that very good example plugin installation manager tool was a G sock project that is used in every Jenkins container image. Very good. Okay, last topic I had was adding sponsor attributions. And this is this started with a request from JFrog that we add attribution to the downloads page for their involvement in the Jenkins project. Now they're actually not a provider of the services that are on this page. These these things actually come from our mirror providers not from not from JFrog. But the request is absolutely valid. We need a better way to highlight those major contributions like what JFrog does like what GitHub does. Where like what Atlassian does we rely on a donated Jira instance we rely on major donations from GitHub to host our 2,500 and more repositories that are Jenkins. So, so this is an ongoing project. We're grateful to AWS for their donations to digital ocean to Microsoft and recently to ampere for donation of equipment to that they've lent to us. So, right now there's a governance board action item will hear a report on it on its status next week at governance meeting. Any questions there. I don't know if it's a question or comments but we were discussing I think it was last week with Kevin. I don't know about the hardware that we get, for example, for ampere. So, should we create a new type of sponsor, or should we just thank them in another way via blog post or something like that. And for the very small donations of hardware, be it risk five pine 64 and so on. I'm not so sure that they these donations even if they help us a lot deserve to be listed in the sponsor page, maybe just a blog post will do the trick and frankly they even don't ask for anything. So, yeah. Good, good idea. Very good idea for sure. Certainly a blog post showing. Hey, here's how we were using this here's, here's what we've what we've gained from it. I think those are blog post sponsorship page. One of the things that Basel has been investigating are considering is, how do we assess the relative levels. And one possible way to do it is cash value right so, but with cash value then we have to look what does it mean for an organization like JFrog or GitHub, where we can't directly assign a cash value to what they're doing for us. They're supporting, in the case of JFrog, probably 100,000 Jenkins users, or the case of our Jira instance we have 100,000 plus user accounts on that Jira instance. And so if we were buying that license it would be enormously expensive. So those kinds of things, I don't know how to judge donations that are not pure cash donations. So it's, we'll see. Yeah. And for the servers, for example, they are not a real donation without the deadline. I think there is a deadline. They're just loan us. So the servers are valued to quite a bunch of money, but as we don't get them forever. I don't know how to value them, but correct. And therefore that makes it all the more interesting. How do we deal with how do we how do we properly and fairly recognize these various contributors to the various donors. Yeah, great. Any other topics we need to discuss today? Nothing on my side. Thank you, Ayush. No, thanks so much. Okay, and I was going to, okay, I can report a one added item. I was looking for this earlier we've had 24 proposals, 23 proposals submitted for review to Google Summer of Code already. Yes, you're right. Last year, I think it was 54, but contributors have until the 22nd of March. So, right. Well, and, and I think the 54 was submissions we received from Google. So if someone submits something to Google that doesn't submit to us for review that that could easily boost that count finally right now. This is these are the ones that are certainly the most likely to get our attention because when we review them, we have a much better chance of, of having the proposal tuned to be a better chance of success. Yes, and some proposals were pretty good from the beginning, but for some of them, some things were missing so the review process is really helpful both for the Jenkins project and for the contributor, even if the project is not selected in the end, the contributor, the potential contributor will know more about Jenkins and the open source and everything that is linked to Jenkins and GSOC. So, definitely, if you hesitate, don't hesitate no more, submit so that we can review your proposal. Excellent. Thank you. I'm going to end our recording now. Thanks very much. Thank you Mark.