 Hello and welcome to the Jenkins documentation office hours today is October 26th, and this is the US edition Today we have myself and for over often Welcome and if anyone joins up, we'll welcome them in So for the agenda, so as far as who's on our code that's been complete now Really the main focus for the documentation sig is the version documentation site for Jenkins I also will stick to those updates the other Three projects were completed successfully and everything needs a little bit more work to get it deployed into production with the info team So all that work is being done in the background, but for the version documentation Chris has been working on this After he and Biden to finish the project in Google summer of code He's continuing to work with the info team to get that determined and what we need to do to just get that last Little bit or it finished up and past the finish line He's got a prototype site that we've linked Previously and still have here which shows the version documentation site. It's built using in Torah So really nice really great to see and yeah more to come, but we'll get there when we get there Next thing on the agenda is the blog post for the plug-in health scores announcement that was written by Adrienne and This is just published yesterday But as part of the Google summer of code the plug-in health scoring project and adding probes to it So this is complete. These are this is now live and you will see a plug-in health score on the plug-ins that Jenkins To IO page So let's just go to one and we'll just go to coverage or I'm sorry is the overall plug-in this page It's got me Yeah, okay, so yeah the health score is visible here And yeah, the health score tab is what we're actually looking for that will display the health score itself In each and every individual aspect that contributes to the score so you can see here Security update center deprecation etc. They're all reaching a hundred the repository configurations out of 65, but it's for a Couple different reasons not just one overall reason and then you get the aggravated score, which is great As again has written the blog post to help us understand that plug-in health score and what that all means Explains a little bit further about what the background is and what the scores mean And some background on everything else. So really great to see really lovely development This has been ongoing for the past year or so. This was a project that started in Google summer code 2022 So to see it finally released live on the page really really great to see that Progress and that completion so the big thanks to again for all of that all of his work and The Google summer code participants that helped get this along as well. None of this would be possible without the community So wonderful. Thank you very much As we've been saying for the last couple weeks prototype JS has been removed as of Jenkins Weekly version 2.426 This is going to be implemented in the November 15th LTS release, which will be 2.426.1 that is the baseline choice that will be releasing in a couple weeks and that prototype removal will be part of it along with all the other updates and changes that have happened and I've started compiling and reviewing the change log entries so that we can get that change log an upgrade guide added And available for review Little bit sooner than I have been able to in the last couple releases just to make sure there's plenty of time for review And any updates that might happen for October fest 2023. We are getting close to the end It is the 31st is next Tuesday. So Data to report between last week and this week. So We've had 832 total PRs created between the Jenkins CI and in-front organizations, which is great It's up from 653 last week total. October fest PRs created. So to 340 which is another 80 since last week, which is great five new contributors, which is fantastic and then the total validated October fest PRs So out of those 340 we have 280 281, which is great again up about 90 or so And 18 more contributors, which is great. So we're just seeing those numbers increase despite there being a Drop between last year other previous years and this year. It's a little bit lower. However even though the spam rate there and the Contribution is a little bit lower. This is a common theme across other projects But the important part is we are seeing great work from these contributions The the important piece is the effort and the work and the experience these folks are getting as opposed to, you know Pure numbers obviously more is better in this case, but If we're getting a hundred percent success rate from the 45% of contributors or whatever that number is That's fantastic. So October to fest 2023 is going really well There's and there's plenty of reasons that there could be a dip in participation Too many to go over so thanks to Sean mark and Alyssa and Everyone for their help with October fest. That's really a truly appreciate it Documentation updates for the Debian packages. So this was something that was just done recently and was back ported To make it sure that is too part of two point four one four dot three But basically we've updated the installation pack package instructions from using curl to W get This was sparked by a discussion from a contributor who submitted a pull request saying, you know This isn't necessarily Universal as we would like it to be Maybe we should take a look at other options something that might be defaulting within the installation Granted everyone's installation process and set up an environment could be very very drastically different the basics are there But there are always little things. So Well, it's it's an update that we're gonna have there now see how it goes. Hopefully everything is okay No one has any issues with it But the process is the same there. So hopefully this doesn't hurt anyone's experience We had the September newsletter published just last week So thanks to all the sig leaders that have provided updates and continue to share what we've been up to It's really nice having a newsletter to look back on and share with the community as a whole and Those outside of the community as well Something that's more digestible and a little bit higher level to share all the success Jenkins has The new one is in the writing by the way the October one Yeah, we're getting to the end of October the October newsletter is Being populated now and we'll be publishing that in early November hopefully next week or the week after yeah So sig sig meeting owners Please if you don't have your section filled in yet Think of it That is directed at me. That's fine. No Yeah, you're one of them, but frankly, I haven't done my part yet either. So I'm guilty Everyone's a little guilty right now. It's okay. Um, yeah, no the October edition will be coming soon enough and Like Bruno said, hopefully we can get it all taken care of so publish it next week where next week is November 1st So came up out of nowhere Anyway Anything else on that newsletter or Do anything else that we've gone over so far that I haven't given you a second No, I may have a few words to say about Java 21 and 17. Okay. Yeah, okay Well, we're there. Perfect timing Yeah, the Java 11 17 and 21 Proposal has been turned into a Jenkins enhancement proposal. Thanks to mark for submitting this Everything we've discussed over the last handful of weeks is here including all the documentation Images diagrams visual aids, etc. Etc. Etc. Etc. Everything is consolidated here And what's great to see is that there are several different discussions happening Within this jet. So that's really fantastic to see and we're getting a lot of different perspective both from Jenkins Higher level Jenkins users and contributors to others and everything in between So this is really fantastic to see a lot of the discussion is trying to determine how Useful and how can we make sure that the notifications in the monitor is as useful as possible There's a fine line between saying something way too early and getting ignored and saying something way too late and not having enough time to fix things So there is a balance. We're working on that balance right now. The discussion is happening And it's great to like I said, that's great to see so people like Tim Jacob Daniel Beck James Nord mark is commenting on a lot like these are the important questions and discussions to be having And getting multiple perspectives on how this may or may not be useful is invaluable Yeah, we won't be able to make everyone happy. We'll have to Take a decision in the end But these discussion is really helpful because we can hear here about all the different people having different Thoughts about that and I even saw earlier today in the mailing list I guess somebody saying that oh your proposal is pretty nice But I don't think you're right when you say that we'll have a Timurine release every two years for The LTS and so on so I may have Misunderstood but the discussion was kind of interesting because Mark then gave a link and an orc serve forum Timurine that say that yes, we'll have an LTS every two years or something like that So don't you be afraid you won't have to use oracle JDK Just because we say that we would switch from an older version of JDK to a new world one Every two years or so, but yes, lots of things are bubbling these days around JDK 21 of the future of Jenkins with other LTS JDK and I love seeing that the committee is very much alive Definitely and yeah, and I think referring to the thread that you had mentioned in the developer thread or the developer mailing list rather So my understanding was they were worried that what happens if something is no longer supported and there's no one to take it over and manage it after that fact and Mark's response was like you said he provided a link some insight and some reassurance that That's not going to be the case with this stuff, which is really fantastic to have that kind of Just like I said reassurance of that sort of thing And I like the fact that Different types of users are commenting like Daniel Beck is part of the security team So he's looking at it from a security perspective or from a perspective of someone who deals with that end of things James is a developer. So he's looking at it from how does this help my development? Tim she come also developer looking at it from how does this help my development? You know, this is the kind of these are the kind of things that we need to have discussions around Because like you said, we don't we can't please everyone but we can come to a consensus and make a decision That does support the most people we can or that is the best decision for Jenkins as a project going forward there are ways to determine that part and that's that's what this is about and For the record too, I think something I wanted to mention just a little bit about that that idea that what if this is not supported in two years time and and I think the the biggest thing is the fact that the idea is not necessarily to just drop it completely but that we have a Two years where it's supported two years where it's required two years where it's getting phased out kind of thing It's not immediately going to drop overnight like that until we get to be the end of that cycle But that will be plenty of time after we start supporting and requiring the next version out. So There will be plenty of time to take care of any loose ends, but Yeah, that fine that fine line of is this going to be ignored or heated in With a with a 12 month, you know, lead up time or an 18 month lead up time. What's that look like? And what I found funny this week. I already talked about that in the Platform meeting earlier this week is that we have kind of a large or huge spectrum of end users On the left we have users say, oh, you already made me quit JDK 8 last year. It's been a nightmare And now you want me to get rid of JDK 11 in 18 months or something like that on next year October 2024 I'll never I Won't be able to do that. That's very difficult for me. And on the other hand of the spectrum We have people who say hey, I'm maintaining a plugin. I want to write JDK 21 code, you know, when will I be able to write JDK 21 compatible code? That's funny Yeah, it is it is interesting to see like those two ends of the spectrum He said just like, I don't know that we can do this. I want to do this yesterday Let's go like that's a really funny mirror to But but yeah, but like both those perspectives are hugely valuable and and actually completely correct, you know There are tons of reasons why that changeover could be a nightmare for some folks and That has to be but that has to be respected that has to be considered when it comes down to how are we gonna do this or facilitate this change Yeah, and that's also why we see JDK 8 vendors Okay, we is dealing with JDK 8 for several more years as long as people pay for support Because yes, some people just can't move away from JDK 8 like that They have very heavy processes and it's totally legit. They can do so, but Sometimes we have to progress with the project. So Yeah, let's go ahead and move This might be a US thing specifically, but I'm just picturing going to like the doctors of the hospital and seeing them using windows XP back in like 2011 2012 when that was very out of date and Yeah, like there are those circumstances where holding on to something older makes more sense sometimes Or is valuable for a reason. We don't want to take that away. We're not saying you can't have it but We have to make decisions for the betterment of Jenkins or for all the future I'll you know, how are we gonna sustain this in two four six ten? 20 years down the week You know things can change now and then but these are important to consider and I know it's obvious But it doesn't hurt saying it's it's not because Jenkins does not support JDK 8 anymore that you can't use JDK 8 for building your software, which needs JDK 8. So it's just May the machine the control can't use JDK 8 anymore your agent can't run on JDK 8 anymore But you can use JDK 8 or even maybe all the versions of JDK if you need to with your bills. That's not a problem Yeah and yeah that For there's going to be further developments on there. That is not something that's going to be Determined and any times at least in the immediate future so this is all just proposals working and Discussions at this point in time. So please keep that energy up and if you feel strongly one way or another Feel free to comment contribute or you know share that in the jet in the JEP so that We can have that conversation. We can have that discussion So last thing on the agenda as far as discussion goes is the update CLI discussion that we've been having the last couple weeks before we start that Just really quickly Yeah, it may need sorry. It may need a few Tweaks here and there what I was hoping for is the community discussing Utility of this if it's needed. Is it a good idea? Is it a bad idea? We'll see So it could be merged as is but I don't know I would like to get some more reviews just in case and then I know I have some other Draft PRs which will be follow-ups for this one because we can ameliorate that so no hurry But if we don't get any more comments in the coming weeks, maybe we could Merge it Yeah, and I mean I yeah, no, I think it's I think it's reasonable that we could potentially merge it it wouldn't Do it wouldn't change anything about how anything is being run or anything It would just be creating a new log at that point or new logs So it shouldn't interrupt any usage or any sort of anything else in that regard, right Bruno Yep, so I mean, thank you. It's I guess what I'm saying is it's low impact if we merge it Or I guess low risk if we merge it could be high impact if we merge it. That's good High impacts good in this case But yeah, I I definitely agree like if we want if you want to give people a chance to review a comment discuss Share any points they might have thoughts Yeah, we'll leave it for a little bit before we Properly merge everything And I've shared my opinion before but that was last week because this week I like it I think it's a good idea I think having a historical log of when changes are happening is really helpful something that isn't necessarily just The github logs or the github history is really useful and can help pinpoint those changes So I think it's really valuable. I like it. I'm more than happy to merge it I'm actually gonna I should probably comment on this in the actual pull request so that I can be a voice of reason here, too I'll do that after we wrap up here Yeah, still work still Still available still still there nothing has been merged as of yet, so Yeah Thank you very much Bruno, and thank you for the work you've been doing with the update CLI overall That's been really great to see just a little What pull request coming in here and there to update things like that's really nice And I think it's just really cool to see that go from like not existing to you just putting it together and having it be there Yeah, we need Thank You Kevin except it makes more work for you It keeps the documentation up to date Yeah, but that but it also does The work that I would have to do to go through review find that Yeah, it just does the updating much better of these way Yeah, so I can just review and approve or mark in a review and approve and it's actually probably a lot easier So thank you very much And the last note on the agenda here is Doc's office hours Asia I think aren't canceled for this evening I don't have the event on the calendar Let's just make sure here Let's see if it was removed from the calendar the Jenkins calendar It is still there so I could still be happening Mark wasn't exactly sure last time we spoke and last time we were here So it may or may or may not happen if you decide you want to show up feel free but Mark may not be hosting that to this evening. So words to the wise If no one shows up and if it's not happening It is canceled for this week. It was just Okay, I don't know much about the agenda in the US I Even don't know if the term is correct but do you have any coming bank holidays or Thanksgiving that would happen on the Thursday or Friday morning For the next week's Would a great call out Bruno because I'm pretty sure November 23rd or November 20 or November 30th is Thanksgiving I forget exactly But that is a few weeks away. So I don't know about bank holidays in for Asia though Hmm Oh, we also are Okay us will change time on the 5th of November so next week meeting won't change But the week after the time may change depending where you live Which it looks like it does change Where that is Yeah, so that might be a little so not next week like you said but the week after We move over to forget whether daily savings time ends or starts. I don't care. It's annoying and yeah, but yeah That's happening Yes, it will happen sooner in Europe. So next week for EU folks I don't know if it will be all year or later, but that won't be the same time anymore Yeah, yeah, the time zones are gonna time frames are gonna change but For the the EU US Docs office hours, it'll just be moved back and moved earlier an hour I don't yeah, I don't know how that how that will fall for the Asia Docs office hours. So We'll see you. Yeah Also, I just remembered since we have a few minutes before we wrap up today Jenkins governance board and the officer elections are currently go open So the nomination period closes tomorrow October 27th If you have a nomination, please please please go to the voter registration group and submit that nomination Vote registration itself is open till November 5th. So you still have some more time to register to vote but there's going to be a There's a group to sign up for you'll join here instead of leave You can and then you'll be eligible to vote and there's a blog post that Alexander Brundes had submitted That goes through the time frames and just the Explanation of how to go about doing the voting nomination, etc So yeah, so nomination of candidates is over tomorrow at the stroke of midnight and voters registration is open for another week after that Last time it checked we only have one candidate for each open position So if that is still the case after tomorrow There may not there may or may not be a voting process if we don't have two candidates to vote for we can't really vote for that So it may reflect this past election cycle where we had only one candidate for each position and they were by default granted that position so If you'd like to see the democratic process in action, please submit any nominations you have Before the end of the day tomorrow We'll see but Yeah, no outside of that They got everything's going swimmingly for the process It's just we what we would love people to voice their opinions or suggest anything if they have it and To vote your country you just have to have contributed to Jenkins in some way shape or form prior to September 1st 2023 Any sort of contribution doesn't have to be a pull request could be helping in the forums could be doing Events and organizing social gatherings giving talks There's a there's a plethora of ways to contribute to Jenkins So as long as you've done any one of those things you're you're part of the community and you should and can vote Alright, so that covers everything I have had on the agenda for today Bruno anything else you want to talk about before we wrap up No, thank you given Okay, sounds good So then we'll go ahead and stop the recording in just a moment the video will be available in about 24 to 48 hours And yeah until next week take care stay safe and yeah have fun with all your Jenkins doings