 Welcome to the Jenkins documentation office hours. This is the December 22nd U.S.E.U. edition. Today, we have myself, Mark Waite, and Bruno Verrachton joining us. So quick note, just as a side, next week we will not have Jenkins documentation office hours. We'll be out of office. Most people will be busy with holidays and whatnot. So next week, we won't be anything just as a heads up. Aside from that, we have some action items. Just a quick note on the pipeline Docker plugin and what that means for documentation. And for the most part, just looking at the 2020 to recap newsletter topics and ideas and then a couple of pull requests to take a look at and just make a note of, considering that these sort of things are gonna be really important when we get back into the new year and just get them forward for Jenkins. And Mark's adding a note regarding the Jenkins backboard. So we'll get to that at the end as well. Does everyone have anything else they'd like to add or anything I missed? All right then. So first action item here on the list is right now what I'm doing is going through the Jenkins JIRA and going through all the website certificates specifically. Alex Bright has submitted a ticket to the help desk to make sure that this is taken care of and these issues are cleaned up, closed if we don't need them or migrated if we should talk about them further. So I'm going through that list right now. I've gotten to about 60 to 70. There's about a hundred or so altogether. So a lot of them have been able to get closed out because we've just gotten the documentation now. So yeah, that'll be again, something that gets finished up in the next couple of months probably sooner than that and we'll be discussing those really valid and potential additions as we go. Next thing on the action items is archiving the doc mailing list. This will be something that gets started in January. Mark and I will be discussing what we need to do to get to the starting point and what needs to happen after that. So more information to come, but just say no. And then I wanted to highlight a couple of blog posts that we've published recently. One is John Mark Messon's blog post for the Google Summer of Code mentorship. It just goes really in depth on what mentorship means, what mentorship looks like in Google Summer of Code, the expectations, what opportunities they have, et cetera, et cetera. But Google Summer of Code is super in progress where the Call for Papers is coming up in just about two weeks. I think January 5th is the Call for Papers deadline. So we're in full swing, looking forward to Google Summer of Code right now. So if you have any interest, you wanna chat ideas, topics, how you can mentor, how you can participate, whatever have you. You have plenty of resources and blog post is a great way to start. The other blog post that I wanted to call out and highlight here is the recent post from Basil Crow. He wrote a wonderful and very detailed blog post about the new baseline requirement for a Jenkins plugin development, which is Java 11. This is a more recent update. The Java 11 requirement has been part of Jenkins itself for a few months now, but the POM itself was upgraded to utilize Java 11. So this is something that we wanna make sure is addressed and highlighted. So folks are not getting lost or confused on what needs to happen next. Anything else on the action items or good to go? Cool, all right. Anything for me. All right then. Next small note, just the pipeline Docker plugin. Maybe we're looking at deprecation there. This is gonna have far reaching impacts beyond just Jenkins. So would you need to figure out and really do some research and find out what the impact will be for Jenkins, for other companies, for other usage, platforms, et cetera, et cetera. This is not something that can just be done without anyone noticing. So Mark is gonna work with Darren Pope, Damian, DePortal and myself. We're gonna figure out what needs to happen and then once we know what kind of impacts we'll have, we'll start updating documentation and making the necessary modifications. But again, that's not something that's gonna happen in the next week or anything. So new year. And then again, we have our December, the December newsletter is actually gonna be a 2022 recap newsletter for us. So when we post it in January, most likely in the first week, we're gonna be looking back at all the wonderful accomplishments we've had over the last year. For me, I've only been here part of Jenkins for about eight months or so. And even in my eight months, I know that there's more than I can remember. And obviously Jenkins has existed before that. So tons to list and go over and share and highlight and celebrate. We have been able to create this list previously and we're still continuing to use this as an outline and kind of just a marker for where we should be and what we should be including. So we've got themes like platform modernization, development acceleration, website improvements. So for Jenkins.io, localization and simplification or outreach and advocacy, security, infrastructure and sponsors. And we wanna make sure that we celebrate and highlight as much as we can with this. Bruno and Alyssa are working on the newsletter itself as far as putting that into phone requests and getting that published. And every SIG leader is working on their own updates to include as much as possible. So sorry to interrupt you, Kevin. Go for it. So the source of truth keeps being the same document we've been using for the monthly newsletter. It's not that Jenkins Docs office hours document. Am I right? I'm keeping. Yeah, okay. Thank you. For the Jenkins newsletter, we're still gonna be using the draft template that Alyssa created and set up and has shared with everyone. So that's still the one source of truth for all of this. This is just the list that we've been working on to make sure that if anyone forgets one of the many, many, many, many, many things that have happened this year, we can help fill in the blank a little bit. I'm sure stuff like Java 11 and 17 and a lot of these were very, very large things that I'm sure won't go missing. But we've also had other things happen. Like the development acceleration is a lot of behind the scenes stuff and work that is not necessarily seen but felt. So making sure we call and highlight that stuff out is really important. We have a lot of great developers and maintainers in Jenkins. So these are really things where we wanna make sure everyone gets a chance to be recognized even if their name's not attached to it. Everyone knows what they've been working on. So yeah. And then we might end up moving some of these things like the localization simplification maybe switched over to development acceleration or platform modernization or website improvement. It can be, some of these are not so hard and fast set in stone. I had a few things about the elections and we moved everything into outreach and advocacy because it just makes sense. And then things like the community site which I mean for me now it seems like it's just always been the case but I realized that that's new. So these are all things that we wanna make sure people are aware of. Community site's really nice and has a wonderful area for everyone to discuss Jenkins and any capacity they wish. That's something we should really highlight and celebrate and make people aware of. I'm sure everyone's using it but something so simple is having a large impact and I always love making sure that that sort of scale is called out. When can I consider that the content of the newsletter is frozen, ready to publish? I assume not until January 1. Oh, okay. Yeah, this is all, be still. Yeah, my assumption is it'll be at least January 1. Now I hope to start my writing today on my pieces. The governance board topic and some of the items that are in the early list, the platform modernization things, I'm planning to do most of the writing, a bunch of writing there and development acceleration. And I may in my past role as Docs Officer and as a Google Summer of Code mentor do things on the website improvements because of how personally grateful I am to Veehan Thora for what he did there. So that piece, but that will need at least several days. So if it's okay with you, Bruno, that it waits until January 1, we don't intend to publish until after the first of the year, but if you need more lead time, we could set ourselves an earlier than January 1 date if that's really needed. No, no, that's perfect with me. I'm not in a hurry. So that's fine, thank you. And sorry, I had another thing in mind. I saw earlier today, because you were speaking about GSOC 2023, that two people wanted to become mentors for this year, two more people, so that's a good thing for us. That's awesome. I hadn't seen that, I must admit that. Thank you very much for sharing that, Bruno. That's awesome. The more mentors, the better, obviously. We can reach more, help more people, work with more people, the more resources we actually have. And it's no small commitment. We absolutely appreciate every mentor taking on the time and effort and work that comes along with it, but that's amazing. I'm so happy to hear more and more people are getting interested. Thank you. And as far as my update goes, I'm looking right now, I'm doing a lot. The documentation update is not listed here, but my idea right now is just to highlight and share how much contributions and changes have happened. I'm working right now with the community stats to just kind of recap how any blood posts have been created, how many authors have participated in the blog, the number of pull requests we've gotten merged over the last year, which is almost 900, that stuff like that. So I'm working on making sure that we're highlighting the community and their documentation contributions as well. So yeah, lots of good stuff to come. And yeah, like I said, I'm also writing up little things for a lot of these items, just in case, like I said, the gap is there. So we'll have something, even if I'm not the most well versed on something, I have enough in me to go and figure it out. So yeah. And then Wattic and others will be working on the security stuff. And so we'll just keep checking on that and we'll get that taken care of. And yeah, I'm most likely somewhere around January 3rd to the 5th, I would imagine. So anything else on the December newsletter? Or... Nope. Okay. Okay. No worries. No, thank you so much, Bruno. And then, so just to, as we're reaching the bottom of the agenda here, the second to last item is pull requests of note. These are just a couple of items that are coming up and that have been submitted that we want to bring to everyone's attention. First and foremost, the 2.375.2 LTS release, which is going to be January 11th. I've gotten the change login upgrade guide created that pull request is submitted and open for feedback. So if anyone wants to take a look and review, I appreciate that. And thank you in advance. And then the second item here is the web components for Jenkins.io. This is something that Gavin Mogan has been working on for some time now and has made a lot of headway and we've got the header and footer already kind of working in the plug-in site. And this is just adding more Jenkins.io components in addition, removing a bunch of stuff that we don't need anymore. So making the page load lighter, we get the consistency of looking feel across multiple sites, regardless of whether or not their plugins, plugins, whatever have you, they can all use the web components so that there's unity across. So this is fantastic. We do want to get some more review and testing on this just to see how everything looks and works, but this is a really fantastic effort from Gavin and again, really appreciate all the work he's doing for this. Marcus, is there anything I missed on the components that we should also mention or does that cover everything? No, that covers it. I think the concept of web components is brilliant and I'm so grateful for Gavin to Gavin for being willing to bring it forward. It's even being considered for possible inclusion inside Jenkins Core. So now the exact components Gavin's creating don't belong in Jenkins Core. They don't make sense. They're just for the Jenkins website, but the concept of web components is an interesting and very attractive kind of thing. Nice, definitely. That's fantastic. Great, thank you Mark. And lastly on the agenda here, just the pull requests backlog. So one thing that we want to of course always do is encourage users to participate and contribute to Jenkins. The pull request backlog is right now at 43. We can absolutely get it lower, but we want to make sure that people feel they're being heard and their participation is noticed and is being acted on. So our goal when we get back from break is to make sure that we start getting this cleaned up and closing out. Some tickets are merging things that can be merged and making sure that we're acting on these things. They're not just sitting there waiting. Contributors want to make sure that they're heard, felt and at least talk to if not worked with forever. So this is the absolute easiest way to get started on that and make that impact for them and hopefully empower them to continue contributing. We've had a lot of great additions and improvements this year from the Google Summer of Code projects, ECODE Africa, from all of the different projects we've participated in this year have been immensely fruitful for Jenkins as a whole and we want to keep that going strong to 2023. So more to come on that, but something that we'll be taking care of in due time. Now with that, that takes care of everything on the agenda. Does anyone have anything else they wanna share or add before we stop the recording for today's session and say happy holidays? If not, great. I'll go ahead and stop the recording. It will be available within 24 to 48 hours. And again, thank you to everyone for the past year or 2022 has been amazing. We've had so many Jenkins. It just events in general, whether it's Jenkins.io, actual events or just the projects and participations we've been able to collaborate on. So thank you to everyone, all the contributors and especially for me personally, I wanna thank Mark and Bruno who have been here with me every session being a very nice audience. You're the best. Thanks, Kevin. Happy holidays to both of you. Yeah, happy holidays to everyone and happy new year.