 Welcome everyone. It's Jenkins documentation office hours. It's the 5th of January, 2024. Happy New Year. Topics today, upcoming blog post, Contributor Spotlight, Contributor Summit at Fosdom, GSOC 2024, the version documentation site. We had Vandit Singh join the Europe office hours earlier to 12 hours ago, adding sponsor attributions and integrating Dr. Compose. Any other topics you want to put on the list or things that you want to change the order of? No. Okay, then let's go ahead. All right. So first, there is the December newsletter will be a summary of the year. And so each of the leaders of the special interest groups and representative from the governance board will write sections for it to highlight some of the things that have happened in the year and there've been some really impressive things that happened in 2023 in the Jenkins project. So looking forward to that the whoops publication goal. Publish by January 15. Any questions there? Okay, next topic then is contributor spotlight. So Alex has has been posted. And so that means we are now at two. So Alex is here. Then we see if we look at the top level page. See back to spotlight you'll see here is Alexander Brandis. Well, and thanks very much to Kevin Martins to Alyssa Tong and to Chris Stern for his creating this site. We've got additional when pending so Uli Hoffner will be published after Chris and then several others we've got, I think it was two or three months worth of articles already collected. And there's a there's still an open question discussing what should happen when I click this link. When I click that Jenkins, should it go to the top of contributor spotlight. Or should it do what this one does and go to www.jankins.io. Success stories does it stays inside success stories and plugins stays inside plugins. So if I click, let's see, let's do it. And then click the top left, it jumps to the root of the plugins not to the root of all sites and still open discussion. Contributor Summit at Fosdom so February 2 2024 and I am delighted to say I'm going to Belgium for it. Oh boy. I'm looking forward to it so we'll we've we've right now got 20 plus confirmed attending, including four of the five members of the board, and all but one officers. So it's a it's a great representation. The community site has the agenda. The beginnings of the agenda organized organizing is happening there so we're looking forward to a discussion for instance, we think we'll have a discussion about, whoops, about blue ocean end of life, and about high availability. We may have some discussion about other hot topics like user experience and more. Any questions on the contributor summit. Okay, next Chris is a topic for you, Google summer of code. Yep. So do you want do you want to give a summary of where we're at do you want me to summarize it what would you prefer. I can talk a little bit about it because like I think like currently we have about 10 mentors volunteering. We could use more but it's kind of hard to recruit new members as mentors. Right. So that, as usual, the crucial challenge is more mentors. Right. Yeah. Now there's also the online meetup happened December 20. There is a meeting coming up either. I think I just saw the registration actually for it. Let's see if I can see it in my other page. January and January. Yeah, right. So let's see where did I see that it was me to. Oh, I don't see it. Okay, so maybe I've already already moved it out of my way. I need to look it up. It. There is definitely a event on meant meetup.com for it. I'm looking at the older minutes from. Oh, from this morning. You say. Morning in the US that there will be another one in January, February or something. Right, but I was trying to find the specific meeting invitation for it. So maybe what we do is let's let's change this and go looking here. Here it is. I think anyway. Upcoming events CD con. Mentor round up. Well, oh, maybe it's not published here yet. Okay. I don't know. That's, that's a little surprising. I thought I'd seen a meeting invitation. Maybe I'm off. Chris, anything else from you then. Oh yeah, I need to talk to you about the back end project ideas back and what's that called. Back end extension indexer. Yeah, that one. Any more info from you before I can submit a PR for it. Oh, good. Okay. So what, what, what more information do I need? Do you need or do you want me to submit the pull request? Well, you can. Yeah, if you, if you can do so, that would be great because like, otherwise I would need to ask a lot of questions. Yeah, so, so let's let me let me double check. I thought we already had a page. So obviously, if we don't then I've got to, I've got to do my duty and submit the idea. Ideas are here. Okay. Yeah, no. Okay. No, no page. So that's my, my task. It's the idea is that you want me to describe it to you, Chris, or would you rather I just submit the pull request? What's your preference? No preference. Okay, so let me show just briefly what the, what the problem is. So here are the lists. This is the page that talks about what extensions are in the Jenkins concept. It's an annotation that's used to mark implementations that contribute to a group of implementations. And there's an index that presents the list of known implementation, known known implementation or known known interfaces declared that can be implemented. And the problem with this list is every time a plugin implements incrementals, it gets removed from this list. So all the most popular plugins have implemented incrementals and therefore are gone. For instance, quick case plugin has not implemented incrementals. So it's still here. But if I try to replace this with get, which I know has an implementation, it says, uh-uh, there isn't such an implementation. So, so we've got to rework the tool and the tool is, is actually horribly inefficient. So, so reworking the tool is a good idea from an expenses reason anyway. Okay. So I'll, I'll mark submit the pull request for the project idea is a reasonable thing for me to do. Okay. Anything else on Google summer of code. I think we're seeing a lot of activity on guitar, as you have reported. But also like, um, I didn't think anyone has like, seriously started anything substantial yet. So we get way to see. Yeah, so that I would agree. I've not seen any proposals saying, Hey, please, please. Here's a document. Could you review my ideas? Here's a prototype. Could you review my ideas? I've not seen that at all. No, yeah, maybe it's due to only, but it's January. Right. We're, we're now at the point where they should be starting right with, they can, they can begin submitting their application to Google. Is it in February or March? Okay. So, so yeah, January is really the time for them to start writing. It could be March, but it's because like for the organization applications in February. Ah, okay. So if organization applications are February, then March is probably when they start February organization application. And then likely March for March or April. Right. Okay. Good. Anything else on Google summer of code. Nope. Okay. So on the version documentation site. Had a great conversation with Vandit when he joined Europe office hours. About 12 hours ago. And. Oh, go ahead. Yeah, I didn't make a correction though, because like with the issues to be reported. It's supposed to be at the new site. I just share a link to it. Not to the not to find it. Oh, and I thought that's what we had it listed was reporting them to the new site. Yeah. Oh, because he the way he described it was he thought, Hey, please be sure you report them here when you find an issue so that we can work together on it and be sure. For example, I don't have permissions on this site. And it hasn't been Zab yet because you will, you will have it, but because happy is on leave until next week. Ah, so that's what we're waiting for. Got it. Okay. That makes sense with the way. Yeah. Right. Okay. Good. I can certainly submit poll requests and I can submit issues and that was what was discussed with in Europe office hours was Hey, during the month of January while, while Vandit is preparing for and completing his examinations. The rest of us can be doing reviews so that in February or early March, Vandit has time to revisit any comments. His request was, Hey, if you're feeling like you're submitting. A lot of issues that are very, very tiny, you could also instead of submitting many, many issues, submit a smaller number of issues and use task checklists inside the issue. So that if it's related to a single topic, but many instances of it, a task checklist would be a good thing. Okay. Yeah. Good. All right. Yeah. And so here it. Oh, right. Right. No, I see what you're saying, Chris. That that that is just wrong. Right. It should say this. Yeah. So we just moved it. Right. I mean, we, we have. But the thing is that the previous site is not available yet. So we have to wait until next week. Well, but, but Vandit can certainly pull from the official repository into his repository and publish for the preview site. Right. I mean, if he wants to, or I can, I can talk him through what the get commands are to do that. He can fork it, they can forget that. Yeah, I think you can fork it and he can always use like a phone version on his. Good point. Actually, that's a good one. I should probably fork it immediately. Yeah, because I haven't done it yet. Right. Because I copied from my own version, which is the outdated version. I have to delete that and I have to fork it again. Yeah. There we go. Yeah. Anything else on version documentation? I think like, we have done a lot of work over Christmas holidays to make sure it works and and also to get with the bugs because there were quite a few of them. I was like, there was some linkage issues as well. So some pages were not linked to the correct page. Curiously, but we affects those. Good. Or we try to fix those. Very, very good. And Vandit is, is still using his repository for the prototype site. And that makes sense until we have a prototype site configured. Yeah. I think, I think it's like he's currently focusing on the gas beside things. Okay. All right. Good. Anything else? Let me check. I think we should. Oh, yeah. And also like for events, major events feature we had previously. It might be like, we might need to remove that from the new version docs. Because like, it might be kind of hard to make it happen. Do it to the current item. Okay. Yeah. So is, is it feasible for us to retain it if using the old awestruck generation if we need it or really we've. We can show us in Gatsby. To regenerate it. If, if needs be. Because we can do that. Okay. Could, could be done in Gatsby. I see what you're saying. It's that it's in the version site using Antora that it's not likely to work. Yep. Not feasible. Well, and, and that's not really not, not readily done. Antora that that makes sense. I'm not sure why we would ever want events to be versioned. So that's, that's a good thing because I don't think we should version events. They're not. They're, they're tied to a point in time, not to a release. Not to a Jenkins release. So we don't want people looking at. Yeah, so we might as well just change our whole thing to Gatsby side. All right. Okay. Anything else on version documentation. Yep. So next topic was adding sponsor attributions. Here we had a request from one of our sponsors and we've now had it from actually several where. Digital ocean, for instance, has just donated $20,000 to the to the Jenkins project for 2024 infrastructure. And JFrog has donated the hosting of our artifact repository. And what we've realized is we need a better way of presenting our sponsors. Today, the way we present them is on a single page on the top level page at the. At the very bottom we list them here, the major sponsors get a logo. Other sponsors get just a hyperlink. And what we've got a proposal for now is we really should have more than more sophistication than that. And Basel Crow of the governance board has proposed a draft pull request for consideration. With, let's see, let's look at it here with a concept of levels of sponsorship. And we've got various names proposed for those levels of sponsorship. Next week in governance board, I'm sure we'll have a conversation about what should those levels be and how should they be represented. So right now in the, in the working prototype that he's got what we what we can see is if we look at the deployment here. This one. Nope, no, that wasn't it wrong click. You deployment ignore. And then if we go to slash project slash wants project sponsors. You'll see first concept and anchor. Then in his prototype premier partner and supporter. And I countered with and then associate and mirror hosts. And I countered with, I like anchor a lot, but then I use the, the metal colors from the Olympics. So gold, silver and bronze. And then mirror. And that'll be discussed further, I'm sure. Any other questions or concerns there. Okay, now we did have, we do have some changes as of January one. The head hat is no longer a part, no longer a sponsoring member of the continuous delivery foundation. And because of that, we would, we should drop them from this top level page. Let's go to the top level page from this page because they're no longer actively involved enough to justify being on the being on this level of the pages. And likewise, there's concern that, hey, AWS hasn't donated Jenkins in well over a year. And so they probably don't belong on the sponsors page right now either though we've submitted a request for donation and if they were to donate to us, they would absolutely be on the list then. Okay. Any questions there or concerns. Okay, the next topic was integrating Docker compose into Jenkins documentation. This was a GSOC 2023 project that Bruno, they're Austin has carried forward. And is now an open pull request that has dramatically improved the Maven tutorial in the documentation. So if we go to that environment. We can see just how much simpler it is. So let's look at the tutorials and here building and a Java app with Maven. So if we look at this part right here. Okay, so sample repository and start your Jenkins instance. Remember how long the start your Jenkins instances it's two it's three steps. Boom, boom, boom. And you say Docker compose up minus D Maven. That's it. You've cloned a repository that has that definition and you run it. Now in the current demonstrate in the current tutorial, it is a horrible long series of detailed steps that must all be performed successfully in order for the tutorial to work. So, as an example, on Mac OS and Linux. 12345656. Okay, so you took six steps and the instructions are different on Mac OS Linux and windows so Linux gets Linux and Mac at one and windows get another in the new tutorial. So we don't need that complication on on every one of them you just say Docker compose up. Nice result from from Google summer of code. Bruno's also started the work on the next tutorial the Python tutorial. This this has the added benefit that it removes some very risky some things with a real security with risk that we do in the current tutorial where here we depend on a Docker and Docker container. And we rely on the ability of the Jenkins controller to run Docker from inside its own Docker container. And, and that causes the security people to go a little crazy because of the risks that are associated with that. This new way does not use Docker and Docker at all. Any questions or concerns there. I'm wondering, like, do we have a timeline for, like, when there's new tutorials to be released. So this one, the Maven tutorial, I think will be done before the end of this month. And the Python tutorial, I assume is relatively quickly after that. Okay, I see. Good question. Any other topics we need to discuss today. Not from here. All right, let's call ourselves done. Thanks very, very much recording will be available in 24 to 48 hours. Yeah.