 Hello, and welcome to the Jenkins documentation office hours. Today is January 11th. This is the EU-US edition. And today, we have myself, Kevin Martins, and Bruno Vrachtin. Mark's not joining us today. There are some other things going on. And if anyone does show up, we'll welcome women on the agenda. So we've got the 2023 recap log posts that we're working on, contributor spotlight updates, next LTS release, Jenkins contributors on it. Google Summer Code 2024 prep, the version documentation site, integrating Docker Compose into the Jenkins documentation, and the sponsor attribution page that Basil's been working on. And then the last item on the list is something that came up earlier in the Jenkins advocacy and outreach meeting, updating the Twitter link at the bottom of Jenkins.io to be something for X. Is there anything else that we want to throw on the agenda, Bruno? Anything that I want to make sure is on there? Yeah. OK. Cool. So starting off, so the 2023 recap log post is being compiled now by the SIG leaders. We have a document that we're all contributing to. So the goal is to have that published by January 15th. It's just a matter of having everyone put their two cents in there, making sure they recap things and submitting it. Once we get that pull request, we're pretty much good to go. But yeah, people have to put their updates in there first before we can submit that pull request. So in due time. For the contributor spotlight, Chris Stearns spotlight was published yesterday. Again, I want to just share a really sincere and deep thanks to Chris for all of their work on the Jenkins project over the last couple of years and helping getting the contributor spotlight page itself up and running like this. Yeah, just really, really appreciative of everything Chris does on a constant basis, heavily involved in the project in so many different ways that I don't want to start to try and list right now. Because there's always many. But yeah, just deep, deep appreciation and thanks to Chris for all of their work. I think it's great that we get to spotlight Chris for the first person of 2024. That's really exciting. And we did this intentionally to give Chris the proper spotlight towards the end of the year. People on holidays, works are slowing down. There's not as much traffic or visibility. We wanted to have Chris get that visibility that they deserve. So yeah. And then Uli Hafner is going to be the next one after that. So he'll be published later this month. And then we've got plenty lined up for the next couple of months as well. There has been an ongoing discussion as well about the Jenkins text logo navigation. So just to quickly summarize what's going on. Depending on what part of Jenkins.io you're in, this Jenkins text logo up here in the corner takes you to the root of the URL. So for instance, if we're on the blog and we click Jenkins, it takes Jenkins.io homepage. However, if we're in the contributor spotlight, we're going to go to Chris's spotlight page. We'll click the Jenkins text logo and we're at the root of contributors. Jenkins.io. Same thing goes for plugins.jankins.io and stories.jankins.io. You are brought to the root of the URL you're on. So there's been some discussion about whether or not that should change. For the most part, I think a lot of people are in a grants that having it do the root function is what makes sense. And based on what I was reading from Gavin's previous comments, changing it to be specific in that way is a lot more work involved. And it's a little bit more complicated than just simply having it go root. So it may be a change that could be made but this is fairly consistent with other projects and other sites as well. So frankly, I think it makes sense to leave it as the root that way people aren't navigating away from the plugin site if they want to remain on the plugin site. If they click that, they're brought back to plugins. So yeah, it could be a little bit more interrupted or annoying than anything else. But yeah, if you have any strong thoughts one way or another, feelings appreciation or otherwise, please feel free to comment in the poll request. This discussion is ongoing. It's not gonna happen today or right this moment. So there's plenty of time. Our next step. So the next LTS release is happening on January 24th. That's gonna be for version 2.426.3. The release candidate was made available yesterday via the developer's mailing list. So that's linked here in the agenda. You can grab that there, test out. And the change login upgrade guide has already been submitted or approved by Mark. So that's been added here. This is a link to the release checklist. This is something that we have for every release. The release lead in this case, Chris Stern. Once again, thank you. Put this together and just keep track of where we're at for the release. So yeah, if you have any questions, concerns, you can always check those out. Again, the checklist is a great place to have a discussion. And I'll be checking to make sure that the change login upgrade guide are correct for the next week or two, just before the release. That way, if there are any surprise additions or extra things that need to be added, I can make those changes. The Jenkins contributors summit is gonna be happening on February 2nd, 2024. So that's the day before the FOSDA conference starts. The John Mark Misen has created a blog post for the contributor summit, outlining key information, dates, times, et cetera, planned agendas, and we'll have a lot more at the contributor summit itself. But for the time being, we've got over 20 people confirming that they're gonna be attending. We've got four out of five members of the board that are gonna be attending and all but one officer at this point in time. Tim Jacome is still trying to determine whether or not he'll be able to get funding to come out for the conference. But if not, we'll have almost a full house, which is really exciting. Since I started with working in the Jenkins project a couple of years ago, I haven't met anyone in person. So this will be a really exciting time. I'm also looking forward to meeting people that we work with on a regular basis that are across the world. I have no way of meeting them. So yeah, this is gonna be really fun and exciting. And the contributor summit's a really cool opportunity to get insight into what Jenkins is looking towards for 2024 and beyond. What kind of products we're working on, what we have down in the pipeline. I'm not intended, but we'll go with it. And yeah, we have a meetup page for the event. So you can also share your intent to join us there. Jean-Marc is organizing the agenda on the community site. So we have that. And we have a few things that we're looking at in terms of presentation and discussions to have during that. Really excited about that. Again, we'll have more information a little bit closer to the event, but to really get everything you wanna be there in person or if there's only recordings after the fact that too. But yeah, really exciting and really looking forward to the summit. For Google Summer of Code 2024. So the preparation has started. We've got 10 mentors that have volunteered so far. We can always use more. It's always nice to have. There was a call for mentors blog post that was actually created and published. So we have the interest. It's great to see. We do need some more mentors, but that is a similar experience as to what has happened in previous years. So this is not unheard of. We just wanna make sure that we have given the ample opportunity and availability to anyone who wants to join up. So good news is the Jenkins Google Summer of Code Gitter channel or IRC channel has seen a lot of activity, a lot of discussion. Thanks to Chris, Vandeet for everyone for taking the time to respond to people and share how to get involved with this. I think I saw it even earlier today. Chris was recommending or yeah, even previous GSOC members like Akash helping to explain like what the expectations are, when things are happening. So really, really, really, just amazing participation and collaboration with everyone for the GSOC next coming year or this year actually, sorry. So yeah, more mentors are always appreciated. We're still looking for more. If you have interest in any of the ideas, they are all listed on the project ideas page. Yeah, check in. Reach out. Ask if you're curious, if you have even remote interest, check them out, follow up, read a little bit more. If I'm not mistaken, each project has the planned mentors or leaders. It's not like tied to them at this point in time. I could be wrong about that, but yeah, the project ideas page has everything listed and you can find out more there. And so these are some of, these are some of the projects right now that we're looking at. And then you'll notice stuff like alternative Jenkins IO build tools or something that we just finished up or are in the process of finishing up now, which also leads into our next topic. So the version documentation for Jenkins.io is a result of the 2023 Google Summer Code, something that both Chris Dern and Vindy Singh have been working on for the last nine months or so. And it's at a point where it's ready to, we're getting ready to push it live and have it be part of the Jenkins infrastructure. It's got an issue already created in Infra. So we're that far into this already. We wanna, at this point, we wanna make sure that the version doc site is reviewed, any issues are called out and noted now as opposed to later. And with this month of January being a bit busier for everyone, lost and prepped for some of us exams for Vindy. This is a great, great, great time to go through and do that review and do that in-depth checking of links and making sure content is where it needs to be and everything like that. That way they'll be able to come back and take a look, do that, but take care of those issues, anything that might need to be updated, resolved, et cetera, et cetera. They'll have the ability to do that on a bandwidth for that, more importantly, after January. Yeah, and Vindy was here last week, he was able to share, they've got the change login, but log's already done. They have a couple other things to still do upgrade guide, security, advisories. But for the most part, the site itself is good to go. I've gone through and did a base review of it. A lot of the stuff I've found has already been resolved. And it seems like there's a lot more of the transition from Antora, or the transition from Ostrac to Antora than anything actually being incorrect or wrong necessarily. So super, super encouraging. And once again, immense thanks to Chris and Vindy for all their work on that. Next up on the agenda, so integrating Docker Compose into the Jenkins documentation. This is something that Bruno's been working on. And this is also the kind of the last stages and the results of another Google Summer of Code project that we've been, that's been getting done. So this is the fruits of that. All that labor, fantastic to see. I've been looking at the Maven one. I haven't gotten to the Python one just yet, but everything looks great so far. I haven't run into any issues or anything that's inherently like breaking or wrong or bad. So things are going well there. Bruno, would you like to speak to anything or share anything about these pull requests or like what you've been doing with this? Yeah, not so much lately in fact, because yes, it's still need polishing and maybe a review. The first one about Maven is supposed to work. It works, yeah, it does work. I have to say the Python one, it's maybe too early because I'd like the Maven one to be merged before reviewing myself what I've done with the Python one. And I also have some modifications to make to the Python. Please don't lose your time reviewing this one. It's not ready yet. It's still in draft if I'm not mistaken. As for the Maven one, I don't know. We could merge it as is if people have a think it's usable, but it could also be refinished. So it could still stay this way for a few more weeks that we've no hurry. From time to time I see people asking in community Jenkins IO or in GitHub, how could I start with Docker and Maven or sometimes just with Docker and Jenkins, how should I do? So I give them the link to the actual preview of this tutorial, but I never ever get any feedback. So I don't know if that works for them so they're happy and they won't give us any feedback or maybe they do something else. I don't know. Anyhow, just to say no hurry. It will be, it will see a final review when it will see a final review. It's almost ready to merge. So feel free to do it if you think it's ready and I'm okay if we still wait until after FOSDAM to make a third review, maybe together or something. So I will pull back curtain a little bit on this one since you mentioned FOSDAM. So my goal is to have to use everything, these merged before FOSDAM. I would love to actually, so I'll share this a little bit now but part of what we'll be talking about during FOSDAM during the contributor summit is what we're looking at in the future for Jenkins. The version docs site is definitely gonna be part of my conversation as well as this, the Docker compose. These are two Google Summer of Code projects that we've seen to completion that are improving the website and documentation in various ways. I wanna make sure they're highlighted as such. So yeah, so Bruno, my goal is to have these reviewed and merged before FOSDAM, a little bit before FOSDAM. I definitely would have to screw a few screws next week to do some PLC on at least the Maven one. So are you? Okay, next we got to work on these two pull requests. Thank you for letting me know, okay. Yeah, yeah. And honestly, Bruno, if the Python one doesn't get done before FOSDAM, we don't have to rush this, it's not, it's not gonna make or break anything in that sense. The Maven one's at a really good point and I think it's gotten a lot of review already. I just, what I wanna do at this point is just really fine tooth comb grammar punctuation like this with the really small stuff. That's really where I'm at with it. The instructions are all correct. I'm not worried about that part of it. So that's really where I'm at with that. I think the Maven one is gonna be relatively easy to merge at this point. But again, everyone's very busy with a lot of stuff. The FOSDAM's coming up. We're all gonna be there. I don't wanna overload anyone or myself. So Maven will definitely plan on. Python will hopefully get to you. But if it comes down to it that it's just a little bit too much, we'll worry about it after the fact. But I want to at least have the Maven one in there because it's a great story and Dr. Compose's, the future of Jenkins world, that's what the point of Google Summer of Code is. So yeah, I think we should include it. Thank you, Katie. Yeah, of course. So thank you very much for not appreciate that. You're welcome. Great. So now that I've given all my secrets up, next up on the list is the sponsor attribute page. So this was sparked by a request from our friends at JFrog asking to be attributed to the downloads page, which that makes sense. However, JFrog contributes a little bit more than just downloads. So what this has now kind of evolved into is having a sponsor page. It's a great idea. Right now the Jenkins website just has a handful of logos at the bottom talking about our supports and our sponsors. We just actually removed Red Hat because they're no longer part of the CD Foundation. So I created a pull request to remove them from here. That got approved and taken care of. So that part's up to date, but we have more sponsors and partnerships and collaborations, whatever the actual term is called in this, but Basil Crow has taken it upon himself to make a sponsor page. So we have the pull request here where Mark and Basil have been talking about it. We've talked about the idea of using the kind of Olympic gold medal and silver medal, bronze medal sort of tiers where anchor is gonna be the utmost highest level. And then we have mirrors, which are different. They're inherently different terms of different kinds of support. So they would be in a class all their own. So this is being, this is still a draft, still plenty of times to converse, discuss if there's something that you like better than that or if there's something about the suggestion or even the idea of this, if you have any concerns or you don't wanna share this this year, please feel free to add to the discussion. But this is something that we are actively looking at and it has been changing a little bit due to the way some of the sponsorships have shaken out for this year. For instance, Oracle is not donating and Digital Lotion has donated for both 2023 and 2024. So they should have visibility here as well. So the sponsors page is gonna correct and address a lot of that to make sure that it's presented and everyone gets their spotlight to speak. And then the last thing that I had on the agenda for today. So this was something that again was brought up in the advocacy and outreach meeting earlier. But right now we have Twitter listed here under the community. The issue with this is Twitter is now X as of July. So we were discussing what this should be here or how this should be displayed. I looked at a bunch of other projects and most of them are still listing it as Twitter on the page itself. Or if they're using the logos and not necessarily providing a direct link, they're using the bird logo, the old Twitter bird logo. So for Red Hat, for instance, and you know they're not sponsoring us, but yeah, there's their Twitter logo there. For, where is it? Aji Tomcat, they're still listing out Twitter here under media. And something that Mark brought up earlier is there are other things called X that might be more familiar to the people using Jenkins. So just having it be X is probably not the call here. But from what I've found, everyone still seems to be using Twitter or the previous logo. The only ones that I've found are not using the Twitter wording are Spring and the CD Foundation themselves. However, they're specifically using the X logo instead of a text version. So they have the updated Twitter X logo here. Same with, again, the CD Foundation. They have the X logo up at the top and the bottom of their page. However, I also found CD Foundation is still writing out Twitter for stuff like personal links. So it's a little bit of a weird area. I don't know that changing it to X is the right call. I don't think it is. However, having it be something like X slash Twitter might make more sense. With all of these other projects not doing that, I'm hesitant to make that change. And it's more just like JFrog is still using the Twitter bird down here. GitHub is still using the Twitter bird. AWS is still using the Twitter bird. Like bigger names are still using the pre-existing naming conventions and logo. From a branding perspective, it's not the same. It's not gonna be as easily recognizable. The name's not the same. So people are gonna say what is X? But all that being said, I don't know that it's necessarily worth changing at this point in time. They could very easily change back sooner than later as well. I don't know. And that's nothing to say ownership or anything like that. But if they decide to later change back, then we're just changing back to what they were as well. Maybe we wait it out and see what happens. But I would really... I would really rub my book on. Yeah. Yeah. Bruno, any thoughts or feelings on this one way or the other? Interested? I'm part of the older people. I've been knowing Twitter since the very beginning. And so Twitter isn't X yet in my head. It doesn't click. Even when I type in a new browser somewhere, I never type x.com. It's always Twitter. Even if it takes more keystrokes. Sorry, X doesn't make it for me. And as for Mark, it remembers me of X11 and X in Unix, AIX and so on. X of Unix and Weatherbook. So no, it doesn't click with me, but I'm not representative of anyone except old, hairless people. Yeah. I mean, I still, I know Twitter is Twitter as well. And frankly, like my biggest thing is they're still using Twitter in the URL. So... Oh, really? Okay. At that point, is it... Like, yes, it's branded differently, but they haven't revamped entirely or they haven't completely shut down this idea of Twitter. I don't think they can because familiarity goes a long way. Does it even exist? Yeah, I think it was existing at one time. X.com. They bought it. Really? They bought it, yeah. They bought it, yeah. So there's... It's a very gray area for me right now in terms of what the best course of action would be just because the branding isn't necessarily there is X, correct? Technically, yes. But if you say, did you see my X post? No one's gonna really necessarily know what you're talking about. If you say, did you see that tweet or that Twitter post or something? Like, that's very recognizable immediately. So there's... For me, there's more value in keeping it Twitter at this point in time. X is such a mis... Like, just a void of what is that. And, you know, we're talking about it in this context. So we know specifically what it's referring to, but... Yeah. Yeah. So do we already have synonyms for tweet and tweets or not yet with X? From what I was reading, it seems like it's post, which is a very, again, general thing. Yeah. It's missing out on what it already had because of this change. And they haven't necessarily fine-tuned it to a point where there's, like, name or brand recognition as well. So it's very, very nebulous. And X just doesn't mean anything. Yeah. Okay, got it. Yeah. I don't know. It's a tough one. I'm not gonna rush to change that based on what I saw with other projects, though. I'm probably gonna take this back and check in with the advocacy and outreach group, see what they think about it, talk with Mark, talk with a few other people, see what they say. Yeah, it doesn't make sense to me to update it when no one else really is as well. Not to say, like, I go jump off the bridge if everyone else was doing it, but in this case, I think there's, I think there's something to be said for the fact that Google Open Source, Red Hat, Django, Ansible, Apache Tomcat, like, all of these names are still using Twitter in their page and their websites. So I'm okay leaving it with that. If there's a major seismic shift tomorrow and everyone decides to use the X and label it as X and Twitter is never used again, fine. I'll jump through that hoop right then and there and do it, but yeah, not convinced. Anyway, so, and look at that. I did all of that without getting into my feelings towards Twitter as a whole. Hey, look at me. Sorry. Anyway, that concludes the agenda that I had for today. Bruno, anything else you wanna talk about to throw out there or add on before we wrap up? No, nothing from my side, thank you. Okay, so then I'll go ahead and wrap up the recording in just a moment. It'll be available 24 to 48 hours as always. There'll be a community forum posting for it and welcome to 2021 talk, 2024. Thanks again, as always. Take care, stay safe until next time and yeah, we'll see you next week. Bye now. Bye bye.