 Okay, and welcome to the Jenkins documentation office hours today is February 23rd, and this is the US EU edition of it today, we have myself Bruno Verrachting and scientist I'm on doll which is I think this is first time joining a sign on No, this is not my first time. It's my third Awesome, welcome back then in that case I've been having some weird issues or I'm out late the last few weeks. So if I haven't seen you, I'm sorry. I apologize now But yeah, great to have you here. Thank you very much for joining Today on the agenda. I had a few action items FOS stem recaps by our wonderful Jenkins participants The Google Summer of Code participation announcement has gone live We also have opened up our CD foundation awards issues and we'll talk more about that First item on the list after the extra items is the Jenkins awards for 2023. So we'll talk about The ins and outs of that and just some general information about it where you can do to nominate where to go all that sort of stuff We'll talk briefly about the documentation transition to Java 17 There's a new release of WN 12 coming out which is going to change how things Are going to be written and constructed it for the documentation But it's in the best interest of everyone Something that we've been discussing the last couple weeks is an end-of-life checklist. So When something is reaching end of life, what are the areas we check? What are the repositories? We should refer to what kind of things should we be looking out for and play and Instances could this be potentially used in so we've got some idea some Items that are coming to end of life within the next year and then some of the checklist ideas Next is prep for cento seven end-of-life. This is something mark has been put has proposed There are some tickets to track the work for this, but It's still in the proposal stage. So nothing concrete has really been happening on that front And last but certainly not least Google summer code preparation And we've got a couple of dates on the participation in our status as a mentor organization In some just if anyone has questions or ideas or anything they want to share about the projects or Google summer code in general We'll have time for that too Is there anything else that would be good to add to the agenda or is that cover everything for today as far as everyone's concerned? Fine with me say and then No, fine. Yes Okay. Thank you very much So first things first the action items. So we have three new blog posts to talk to Highlight what the first one is the Fozdom recap. So Fozdom is an event that's held in Brussels and this was a great chance for a bunch of Jenkins team members to go and interact with the open-source community So you can see here Damien Bruno Stefan and Alexander Brandis all hanging out at the Jenkins booth Having fun interacting with people lots of crowds And they gave some really great insights as to, you know, their experience in time at Fozdom so just a really nice recap to Showcase what we were able to do and just follow them in general and thanks to the to all the participants and Folks who made this possible for the Jenkins booth. I know Alyssa I did a lot of work organizing and getting things Set up so that we were we were successful. So yeah, big thanks to everyone and Just a great response and crowd if I'm not mistaken based on what I've heard Bruno, you can attest to that for sure Yes, you're right We had a huge crowd for the whole weekend and people were really enthusiastic about Jenkins it was my first time at Fozdom for the Jenkins and I was a little bit afraid of people coming to round You know, not happy about Jenkins, but no that did not happen one time people were just spreading love We do love Jenkins. Okay. It's sometimes ugly. Sometimes documentation is missing some parts, but it works So that was cool Nice it's always nice when things work. We show people appreciate that fact. It's reliable. Everyone likes reliability. So reliability Great. So yeah, so that's the first blog post The second one here is our Google Summer of Code participation announcement This just went live a little bit earlier and essentially we've been selected as one of the mentoring organizations for Google Summer of Code 2023 and this is our blog post to announce and celebrate that fact Thanks to John Mark Mason for creating the blog post and putting all this together And Alyssa Tong for helping organize and get this together as well They've they're too there are two of the org admins along with Bruno for the Google Summer of Code in Jenkins and just so far it's been a really great experience They're doing a wonderful job of organizing and engaging with everyone and again This is just a blog post to celebrate and announce our participation John Mark's also gone ahead and included some information about next steps how to apply if you want to be a mentor The timeline which is really helpful Yeah, just a lot just like a lot of good information And there are links to other posts that we have for call for mentors information for mentors We had a previous one about talking about being a mentor and what that entails So just a lot of good information here to get us ready for Google Summer of Code And again, thanks Alyssa for the nice Collage of all the mentors that we have signed up really nice to see And we are still accepting project proposals We'll get to that a little bit more when we get to the Google Summer of Code section, but We've been announced that doesn't mean anything's set in stone yet besides the fact that we're participating There are still plenty of time for people to submit ideas proposals applications to be mentors etc Yep, we still can communicate via the community Jenkins.io via the Gitter channel And we have lots of meetings and one which is called Office hours meeting which is every Thursday. It was Three hours maybe from now for PMUTC. Yeah, you got it. So if ever you are interested just Join the Zoom meeting and let us know why you're interested. I know Yeah Good point Bruno and and in addition to that we have the document here the agenda All the meetings will be recorded. So they'll be available on YouTube after the fact as well So even if that 4 p.m. UTC time is hard to make it's obviously later in other parts of the world earlier earlier in others so this is not the Perfect time, but it's the best time we had available for now and individual projects will also have their own meetings to to organize and schedule and work with after that after we get to that point So Yeah, there's there's plenty of places As Bruno was saying we have our Gitter channel for the GSOC. We have the community discourse Which is on our community Jenkins.io site. So lots of places to communicate engage ask questions, especially The Gitter and community are excellent places to ask questions and get insight from other community members a lot of folks are active in the chat and Are quick to respond we were talking earlier about I think it's like 800 plus messages have been sent in the GSOC channel It's only been a few weeks. That's crazy. Yes, and Chris turn handle most of them. That's Yeah, it's big. Thanks to Chris for actually handling like half those messages Very impressive Okay, any other questions on that one? Next up is the CD foundations award CD foundation award. So this is something that we've participated in years prior This year. We're just going about the process a little differently, but same idea applies the CDF awards are ways to highlight and celebrate people that really put their all into this and have You know, as you can see here for Jenkins, they're a valuable Advocate, they're a valuable contributor. They're helping out with security and a really stellar way And these are our specific awards for Jenkins With each of these awards you can nominate someone to So that they can hopefully be in the running for it What we've done this year is instead of having the CD foundation host the issues and the nominations on their repository Each project is hosting them in their own repository. So this year, we've got three separate issues for Jenkins Again, most valuable advocate most valuable contributor and security MVP They're all separate issues in another own right. They have a similar content here But the idea is that you can nominate someone share reasons why that you think they should be nominated and then people are gonna just kind of support that with stuff like emojis voting and then Once the nominations have closed The CD foundation will then gather all the names and then voting will take place at a later time with a Google form. So Down the line, there'll be a more formal way to vote right now. It's all happening in the github issue and stuff like emojis and whatnot. I Don't know that we have any nominations on our tickets as of yet. So please by all means take time check them out They're in the issue tracker for Jenkins.io github. So they are readily available and they also have First off these little trophy emojis But more importantly, they also have the community tag Which is something that I created recently to make sure we can highlight these sort of posts a little bit more clearly and have The community realize that that's something they can take on and engage with and not have to worry about fixing something so Yeah, and yeah, so a couple notes about the awards So you do need to have a github account to nominate or vote Last year's winners cannot win the same award this year However, they're gonna be nominated for other awards. So that doesn't make them ineligible for anything You can see here like Basil Crowe one most valuable Jenkins contributor last year He can't win it this year, but he could still be nominated for most valuable Jenkins advocate So Yeah, and then yeah, and again the CD foundation award site has a lot more information about all the different awards and their processes and stuff like that, so It has some information a lot of the information we have posted in our blog post now though, so Pretty much the same information you found here Yeah, so you can rely on our blog post as well and again big big shout outs and thanks to Alyssa and the CD foundation for Organizing this and getting everything set up so that we can proceed with this the award nominations And just yeah nominations do close next Friday March 3rd So if there is anyone you want to nominate, please don't hesitate make sure you go into that issue And just even if it's not a super detailed reason why right now if you want to just put it in there So, you know, it's there perfectly fine. You can always edit things after the fact. That's not a big deal And then voting itself will open five days later on Wednesday March 8th voting will close at the end of March on the 28th and then The results will actually be announced at CD con in 2023 where the winners will be given their awards and recognition Any other questions on the Jenkins awards 2023 Cool. All right. Thank you Next up the document transition of Java 17 So this is something that with the release of Debbie and 12 coming in this spring sometime in April or May There is going to be a transition of the documentation on Jenkins to move from using Java 11 and things like the install guide To using Java 17 This is just for the fact that Java 17 has more functionality available and it's fully supported at this time Java 11 still fully supported. It's going to continue to be fully supported. It's not gonna we're not dropping support for Java 11 anytime soon, but in the Interest of trying to make sure we're ahead of the game or ahead of everyone else Transitioning to Java 17 in the documentation provides a better baseline for people to start from and again the functionality is more Abundant there. It's more testing is available. It's just better experience overall for development as well So the idea is that we're going to move the documentation to use Java 17 and that'll be throughout the documentation as well The windows and Linux install docs will also be transitioned from Java 11 to Java 17 Again, it's making sure that this is consistent across every platform not just one or another And then I simply need to do this, but I need to email Tim Jacone who is our Jenkins release leap officer and let him know that this is gonna be something that changes just so he's not Surprised all of a sudden when Java 11 now says Java 17 everywhere. So I'll be sure to take that action item and make an email him for this before the end of the day today And again, this is all coinciding with the release of Debbie and 12. This isn't just some independent idea We had Debbie and 12 is not going to roll with open JDK 11. So It's part of their overall next steps to So end of life checklist Again, the end of life checklist is something that we want to have going forward. We don't have anything like this right now It's really just searching and finding the places that may mention the end of life product or platform So things like Ubuntu 18 Alpine 3.14 and 15 These are all coming end of life this year sent us seven is going to be end of life next year So the fast the sooner we get ahead of it have a checklist ready and know what places to look for all these things The better the more prepared will be when that time comes So in Previous sessions we're talking about checking the dot obviously checking the documentation checking the packaging sites And packaging repository that the releases Pository for anything coming out container images. We have the updates at Jenkins the IO site for any references So there are a lot of places to check out and I'm sure that there's more that we haven't come up with or listed here yet but if anyone has ideas or any Best practices that they might have had in previous experience with what to look for or places that we could also look for By all means feel free to share message in the doc skitter channel anything like that at all and We are going to be looking at a couple of site generation projects for Google summer code or at least one site generation project The Google summer of code So this may come up in that instance where we're moving dock the site Some the content might need to change or be modified in some way shape or form when it comes down to it, but ultimately This is just something that we want to this is going to help us do our our due diligence as we Come to the end of life on these things and then so prep for Cento seven end of life Again, this is something that mark has proposed Cento seven's end of life is coming dream 30th next year so There are a lot of reasons to not have it anymore Mark's arguments and biases that because it's looking at agent command line versions And just older versions of dependencies and operations. It's not the best choice going forward It's not going to be viable after next year. So really the idea is to clean this up make sure that we're providing the most up-to-date and Useful information to folks who are browsing through the documentation. So If that means into seven is not going to be using longer That means making sure that it's not Misinforming someone in the documentation as well Again, these are a lot more just of the reasons why deprecating and removing the Cento seven information is a good idea Stuff like the fact that it's been the dock containers been deprecated since this past September It's not supported by the RPM installer It's been in maintenance since 2020 and again the end of life is happening next June So there's a lot of reasons why we should be moving on to the next option the next set and we have actually started including the Elmo Linux Rocky Linux and Oracle Linux information in documentation marks gone ahead and started putting that into some areas and there will be a jet for Containing all of these things. This is clear. This is going to be more than one ticket To take care of so the JP will help bridge that and connect everything together that way we can keep track of the Removal and changes that we're making And then the last item on the list is you Google some more code prep So first and foremost Chris thanks to Chris Stern for updating the Google Summer of Code status page The Google published their list yesterday, so we were able to update our page yesterday afternoon So you can see GSOC 23. We've been accepted. Yeah But and there's an application mentoring org application form here for anyone interested Like we mentioned, we'll have weekly office hours Thursdays at 16 UTC and The project idea of this is very live and very available to check it out and see what The projects are starting to look like So yeah, so again weekly office hours. They're hosted by Jean-Marc mess in those are going to be Thursdays for PM UTC The agenda is there there are two different agendas right now in the Calendar meeting invite It has both last year's and this year's and the nice thing is I Don't know who took care of it, but the 2022 agenda does actually the first line is saying hey if you're looking for 2023 It's right here. So Either way, you'll be able to get to the correct length And then I think the last item in here was something that might have come up during the previous Asia Docs office hours with Marc Rajeev and Meg But one of the projects for Google Summer Code is site generation for Jenkins.io moving from What we are currently on which is off struck to something like Antora or another version documentation And it looks like Rajeev is willing to mentor that project Yeah, and like we said the idea is to use Antora to build Jenkins.io instead of Off struck and then just move everything over accordingly That would allow us to use version specific documentation as well So we can have detailed instructions for the LTS versus the weekly versus an older version of it that we're still supporting So this is just going to be a really nice way for us to make the documentation cleaner and the site a lot more user-friendly in terms of navigation So that covered everything I have on the agenda today. Does anyone have anything else they want to share? highlight Mention I have a question. It's not exactly related to this Docs, but can I ask it? Yeah, go for it. So I was going through this plug-in site API and What I was thinking like the plug-in side It should be pulling the data from the API, but when I inspected the Side it's pulling the data from Algolia and I'm not able to understand how I mean and the documentation is not clear in the Plug-in site API. So I'm very confused. It's getting the data from And As far as the Algolia stuff That is new that was something that Gavin Mogan was recently able to take care of and Fix up because the search was a lot more basic prior. That's just something we added within the last couple months. So Now the the full all the Jenkins searches are done through Algolia But that is separate from the rest of the site in a sense I Because I I think the Algolia is a little bit independent of the rest of the site I'm not a hundred percent sure how that works but Is the question why is it? Oh, no, my actual question was where's the plug-in site API being used and what is the endpoint for it because in The GitHub page it's plug-ins. Then Jenkins.io, and I'm very confused what's happening Gotcha. Okay. I I Am not a hundred percent sure about the back end the API stuff as far as that goes so Do you have an idea? Okay Yeah, so the only the I Really don't know the answer to that. I'm sorry about that Yeah, I think this is a good question though to find out from The rest of the community team. So what I'm gonna do is let me see here Yeah Sounds reasonable. Yeah, I Can take care of that. I'll also throw out the option if you feel comfortable or want to You can check in one of the Gitter channels. We have a bunch of different ones newcomer contributions as you see an outreach, but I think Newcomer contributions would probably be the best place to ask that's one of the more active channels with a lot of different users I know Gavin Mogan is pretty active in that channel as far as helping to guide people and Gavin knows a lot about the back end that API side of especially the plug-in site. It's a little separate from The Jenkins the IO site like they're all this they're all connected, but they're separate so Yeah, it's a little weird in the back end of it But but if you want to if you feel comfortable and want to ask there you can again, you don't have to I will Be more than happy to take this up with team and check in with folks because it might It might be that someone else knows too. No, no, I will ask and then you'll come up on That's a good idea. Thank you Yeah, great. Thank you so much really appreciate it and again, if that's something that ends up being a deeper discussion it can be taken offline on or it can be taken out of Gitter into the Discourse site the community at Jenkins the IO site where we can have real In more in-depth discussions there as opposed to the chat which can kind of get bogged down depending on The number of responses and folks and threads and everything else going on The discourse is just a lot easier to keep track of and be alerted about so But that's that'll be decided at that point So, yeah, great question. Thank you very much, Simon. I'm gonna I'm now I'm curious too So I'm probably just gonna ask around for my own information anyway But yeah, no, I'll keep an eye out on the Gitter channel obviously of course to make sure But yeah, that's that's great. Thank you very much for Inquiring about that. It's something I don't necessarily think about myself too too often I'm documentation officer for Jenkins. So my concerns are mostly with the documentation and and how they how it Reads and looks and stuff like that. So I don't necessarily touch the the API end of it the back-end the calls and responses. So Yeah, no, it's great perspective. Thank you very much for bringing it Okay, and does anyone else have any questions for the session today or any other comments? Because no So then I'll go ahead and stop the recording. It'll probably be available within 24 to 48 hours Mark usually takes care of the uploads and he's out today and tomorrow I can handle with that if you want to. Oh, you can. Oh, thank you. Yeah. Yeah, cool. Never mind I'm a I'm just talking for the sake of hearing myself talk then in that case. Thank you, Bruno. Let's do that Yeah, no, I'll stop the recording now