 Hello and welcome to the Jenkins documentation office hours and happy new year. It's the first edition of 2024 today is January 4th. And this is the US version. Today we have myself, Kevin Martins, Mark Wait and Bruno Roche then. And on the agenda today. So we had our LTS release back in December. Everyone thing when smoothly there. Small update in 2023 recap post that will be that we're putting together now to notes on the contributor spotlight. The contributor submit that's coming up at Fostum. A few recent updates to Jenkins.io. Google summer code 2024 prep. The version documentation for Jenkins.io progress. Sponsor attributions and setting sponsors up for Jenkins in general. And then a couple pull requests about integrating the doc compose into the Jenkins documentation and tutorials. Is there anything else that needs to go on the agenda for today, Mark or Bruno or does that cover everything for discussion. So we've got version documentation there. That's a good one because Chris has made really good progress with Vandeet and I think we were looking at next steps then. Sponsor attributions. Yeah, I want to be sure we talked to that one as well because we've had changes as of January 1 in some of the sponsorships that I think justify an immediate change to our sponsor page even before the long term. So I want to be sure we talk about that one. Integrating Docker compose. Yes, I want to be sure we talk about that one. So at least those last three on the agenda. Very much for me. Great. Let's go. Okay, great. So then starting off. So again, happy new year. Welcome back everyone. Happy to be here and happy to have you with us. We had LTS 2.426.2 released back on December 13th. Thanks again to Chris Stern for being the release lead. Darren Pope and Mark did a YouTube or live stream about what's new in Jenkins that day for the following day that's available on our on the YouTube channel. And the next LTS is going to be released on January 24th. It is 2.426.3. Chris turns also the release lead there as well. So thank you again for that and progress on there is being done. So just like last year, we'll have a 2023 recap blog post. The SIG leaders are putting that together now. And we're hoping that will be published by late next week early the week after. But yeah, we're aiming for the next week or so for that. For the contributor spotlight. So we publish Alex Earls back in December and took a short break due to the break for Jenkins LTS and just lower traffic. We want to give Chris Stern spotlight the attention and visibility that it deserves. So we pushed that back so that Chris Sterns will be the first spotlight we publish for the new year. Chris's spotlight will be published on the 10th of January. So next Wednesday, and then everyone else was moved back one cycle as well. So after Chris, Louis Haftner's spotlight will be published and everything will continue from there. There was the page navigation discussion that we've been having. It's been ongoing in the components pull requests but essentially whether or not the Jenkins text logo should lead to Jenkins LTS. .io directly or the root of the URL that they're on. So if we were to go to contributor spotlight that Jenkins text logo, if we are, it's not even available. Look at that. Oh, there it is. So yeah, so basically. Jenkins text logo leads to the root of contributors Jenkins.io. So if we were to go to Alex's page. Takes us right back here as opposed to if we were on the Jenkins blog, for instance, this takes us directly back to Jenkins.io. There's been discussion talking about the Kubernetes page functions very similarly. Tindjiko mentioned stating that, you know, it's leading to the root of the page you're on so it makes sense in that regard. And then Gavin had mentioned that it's just a very specific function and that to make the change it's more involved than it might appear to be. So yeah, more discussions being happening there, but I'm on I'm of the opinion that I think leading to the root of the URL you're in works. So for the time being, it's going to remain as it is. If anyone has a more compelling argument against that needs to happen in that discussion in that pull request, but we can examine it later at that point. For the Jenkins contributors summit. So really just excited about this. It's going to be happening on February 2nd. So the day before Faustum, which is the third and fourth, the first weekend of February. The meetup page is available for the event so you can register. Let us know that you're coming. The blog post that Jean-Marc Missin had written details a lot more about just Faustum in general and what the contributor summit is. And, you know, anticipating agenda for everyone that'll be there. Really excited. I'm actually happy to share that I'll be there this year, which is really exciting. I just got my passport in the other day. So I'm good to go. And yeah, I'm looking forward. We're going to have we're looking to have the full team there. And I think right now it's looking pretty good for a lot of us, if not all of us. So just really excited to for that to be happening soon. And Faustum is totally free. So if you're curious and in the area just happening to be in Brussels, stop by. Come on over. A few recent updates to Jenkins.io. So Basil Crow submitted a request regarding the escape hatch that was added or introduced for a recent update. So that's been added and merged. Thank you to Basil for implementing that and capturing that. Really appreciate that. Alexander Brandis did a just some work recently to make sure that internal workflows are restricted to just Jenkins infra. That is something that was updated recently by GitHub. Now it's we don't have to worry about unnecessary emails and runs that we're not doing that we're not necessarily working on. So this is one that I need to apply. I get lots of these messages all the time. So I think I've got to understand how he did this so that I can apply it to all sorts of other places. And we and I think we may want to put this into the into the next generation of improve improve a plugin tutorial or into the contributing to open source document because the the annoyance that I suffer of getting these email messages from my forked repositories. Oh this build failed this build failed this run failed. It's just obnoxious and getting if this actually works in these those other places. It'll it will save time for me and for other Jenkins developers. So this one is this one was particularly nice. I just haven't had time to apply the technique to all the places where I get spammed right now with run failed. Same for me. Yeah, same. I've been getting a few more recently than anything else. So yeah, need to apply it as well myself. But yeah, really, really fantastic. Thanks again to Alexander for taking care of that implementing that and getting that in there. So really nice to see. And then the last recent update I had was contribution from a new contributor by the name of Shivam Pandey. So just how to list installed plugins and their respective versions. Great work. There was some feedback here between Mark and Shivam as well as thought I saw someone else but Yeah, just thank you very much for contributing, stepping up and adding some stuff, some content here. Yeah, really great. And then we have that instruction available as well. So just another positive for Jenkins.io and the documentation overall. Next up so Google Summer of Code prep has been started been working on we've published a call for mentors blog post as well. And then we did have the mentor roundup in December Bruno mark any notes on Google Summer of Code prep how things are looking there or anything that you want to note here. I think we'll have another meeting in January or maybe early February regarding GSOC but I just can't remember if it for mentors or for mentees mark, you know, contributors. So we did the mentor summit the mentor session in December. So the launch for the potential contributors will come in January or February. And yeah, there's right now it's the usual set of challenges, which means we've got interest from people, but not enough mentors. And that's been a consistent story every year right we we have far more interested contributors than we will ever have mentors simply because contributors get paid and mentors don't. And there's no shame in that right that's that's the nature of open source. Yep, it's okay, but it's hot warming to see what's happening in the Gitter channels. These days lots of people show real interest and even have started to work on proposals for example I saw something regarding LLM somebody's working with Chris in order to start something ahead of time that's pretty cool. That is really exciting and I'm it's really nice to see it like seeing all the activity like you said on the Gitter channel. Really fantastic to see it there that participation that response that conversations that are happening. It's great. Cool. All right. Thank you very much. Next up on the agenda so the version documentation site for Jenkins.io. So again, this is something that Chris Stern and Vandeet Singh have been working on for some time now. Before the holiday break, we had been I've been reviewing the version documentation site for content for navigation for anything that might have popped up. And so I've submitted those issues, Vandeet or Chris has gone been on top of these really, really well. Most of the things that I had brought up were resolved already there's still some stuff going on with some of the links and where they navigate to. But it's being worked on it's been addressed to this is being worked on and attempted to be resolved. So thanks to Chris and Vandeet for their constant attention and work on this. We had originally I think the discussion was happening originally that we were looking to launch it potentially in December. With these things that have come up we had to push back on that a little bit. So now Chris and Vandeet are still working on this they are making sure that things are navigating properly that the content is correct in the present everything like that. But I think there's still a few more things that need to be done verified checked out. Mark I think would you have more insight on this that you want to share at this point. Sorry I was unfocused ask your question again Kevin. No I was just saying the version documentation is coming along originally for mid December we've had to push that back a little bit. So there's still some review and the and verifications that need to happen but I wanted to just see if you had any other insights as far as like what Chris or Vandeet might have. I think with Vandeet in the call now that's that's a great chance for Vandeet to comment as I haven't done a recent review of the version documentation but I saw that Chris Stern had. Revisited the pull request asking for hosting for docs dot Jenkins dot IO and that to me says that Chris's assessment is he thinks we're getting close to being ready to at least host it as a prototype Vandeet you want to comment. Hi Mark hi hi Kevin hi Bruno. Yeah Chris just told me that Jenkins IO version documentation is hosted on GitHub repo of Jenkins Insta I will drop the link in the chat. And the issue and all the issues Kevin Mark pointed out that was a big help because it was really it was really difficult to work on things and check them since when you work on things you. It is it is it happens that you miss many things when you work on something that one issue that is still open. I will ask Chris to close it since the PR solving it has been merged. It's like three weeks ago so after that I'm currently working on the Gatsby side of things that will host the change logs upgrade guides and the blog. The change log and blogs is already done in the Gatsby part some things that are still to be completed are upgrade guides and change upgrade guides and security advisories. I think we will need to revamp them how we document security advisories or I will try not to do that since. Before 2008 before 2018 we followed a different format format and after 2018 we followed a different one. So either one either we will unify we will uniformized all of them so they fit in or we will I will come up with something that we don't have to change the documentation since the those are multiple files 4050 files. That will be a lot of manual work because I don't think so it will be possible to automate it and check it at the same time and we don't want to lose anything like that since advisories are important. So yeah that's that's what always. Thanks Vandit so so that's that's encouraging so if we were to do another now that we're hosted on Jenkins Infra. That means we've got we've got a place where Kevin or I or Bruno could submit pull request we could also do do checks there and see hey is it looking the way we think it should etc. So we can start this this is certainly the next step in the evolution of the thing right because we also need to check permissions to be sure that Kevin and I have administrative permissions over it and that all the other right people have those things so very good. Yeah, so it would be really awesome if we can have some checks for two to three weeks and I'll be I'll be hyperactive during that time. I if if I but since I have exams in January, like complete of January, but if that will happen of this ratio start popping up. I would definitely try to solve smaller ones, but for the bigger ones I will give my time complete time in February. So I wanted that to be out there. Well, and that's a good thing for us to know because my January is busy getting ready for the Jenkins contributor summit that happens in early February. Kevin's may likewise be very busy that way. And so if you if we know that hey you're focused on exams right now but we could we've got a few weeks where we do these reviews sort of queue up or pile up things that you might look at. And then in February you can take a look at them as your time allows we certainly don't want to harm your ability to succeed in your examinations. But but would love if you can if you we know that hey we queue things up and you can take a look at them as your time allows in February or even in March. Yeah, that would be perfectly that would be perfect. I can just start working on things where I left off or all or when that where the things are in the issues and anything like that. We can create one check one task list for linking issues because I know there will be a lot of them. So having multiple interface linking issues would be spamming kind of spamming in the issues section. So I would if that happens we should use a task list for that. OK, well so you tell us whatever you prefer I'm I'm my simple minded approach is typically OK submit an issue an issue per thing I find. But what you're saying is it may be better to group them into larger themes and then check them off on on a task list. Yeah, like have the we can have them on a checklist and the issue section we have we can create by them and they we can update that checklist since whoever since people with administrative rights will can update existing comments and issues. So that will be one place where I can check where I can start looking and keep ticking off things from that list. But if that's not something suitable I can I can manage that's OK too. Great. All right. So so you're OK receiving issues and you'll guide us if the issues are are too. If that we're creating too many issues and sort of flooding it you'll then you can guide us and say hey no just put this in a task list. Here's this bigger picture thing it needs a task list and we can then that gives us an excuse to try GitHub GitHub task lists as well. My experience with them has has been limited and mostly about me deleting them from from pull request templates and changing them into simple lists. So good. Let's try that. Yeah. Awesome. That would be really nice. Great. Thank you so much for the welcome as well. Also sorry I didn't see you come in there. But thanks for coming in. Thanks for sharing all that. I appreciate that. Quick question for you. So for the issues that I had submitted previously is that a good standard. Yeah all have been resolved. One of them is still to be marked as completed. But the PR solving that is linked in the comment. Yeah. But I was just I was just curious as to whether that was like a good format for submitting issues for you or if that was too much. Once I tried to do that idea of grouping things together and provide the example so that it was clear. But if it was too much at once I don't want to know the concern. My concern is not about how much issues pop up. It's just if I can see them at one place like how you submitted Kevin. It was easy for me to just pick up things and I created like the all the interface linking issues were in one issue. And all the other related issues can be multiple issues. That's OK. But I'm just I'm just suggesting for the interpage linking issues because I know there will be a lot of them. If we see that I that just link you to another page on Jenkins IO docked site versioned site. Okay. That makes sense. Great. Thank you very much. Welcome. All right. Anything else on the version documentation. Bruno no. All right. So next up on the agenda is the adding sponsor attributions. So we've been discussing this in previous sessions just to give a recap. One of our friends from JFrog asked about having a sponsor attribution or just being attributed to being a sponsor. And so that kicked off the discussion of why don't we have a sponsors page or something specific for the sponsors. And so Basil Crow took it upon himself to create a sponsors page. It's right now in a draft state. But it's a mockup of what it might look like. And we've been discussing potential tiers. Mark had used to be Olympic medals as the intermediate in between levels when while we have an anchor for the largest of support and mirrors for specifically mirror sponsors where it would be relative to a monetary support or amount of support. Whether it's monetary or otherwise so that we can have it segmented in a way that makes sense and presents everyone's all these sponsors in a very neat way. Mark had mentioned earlier that there was a recent update to one of the sponsors. I believe that changed where they would where they would potentially even sit in this sort of distribution. So yeah Mark did you want to or would you be able to share like what you were hinting towards previously. Yeah so well so so one of the if you if you'll open the page we can look at open www.jankins.io Kevin and let's look at it and I can talk about what needs to change there so scroll to the very bottom. And you see the list of our sponsors. However, the list is inaccurate because as of January 1. Red Hat is no longer a member of the continuous delivery foundation and therefore they're no longer a contributing sponsor at certainly not at that level to to to justify their logo being that prominent on the page. And I discussed that with them with their representative at a recent meeting of the continuous delivery foundation technical oversight committee and they agreed that hey there's since they're no longer an active member of the contributing member of this continuous delivery foundation. They should not be on this page at that level. Likewise, AWS has not donated to the Jenkins project in a very long time. And so having they didn't donate to the Jenkins project at all in 2023. So having them on that page at least for now is inaccurate. Now we've got a request submitted to AWS asking for a donation and so they may fix that within the next 30 days. And if they donate to us we would certainly put them on the page but those those are two examples the other is Digital Ocean donated over $20,000 last year to the Jenkins project and has again donated $20,000 this year to the Jenkins project for 2024 so they should be on that list. As with their icon visible etc. Now those are those are very short term. I think Basel's longer term view is the the correct one and the governance board will review it next Monday and discuss it further. The reason that Basel's proposal is so much better long term is he's envisioning that we will have thresholds for the the various levels of sponsorship. And those thresholds will have some definition that will let us decide which which tier someone should be in based on their contributions to the project. So that it's it's fair and in this case I like anchor because cloud bees cloud bees donates all of our AWS cloud costs are covered by cloud bees. So that donation, plus many many cloud many many Jenkins contributors are employed by cloud bees full time, including me. And therefore, there's there's an awful lot of cloud bees donation to the Jenkins project. So, so that that's the other is JFrog for instance Atlassian Atlassian donates our, our Jirae instance and that would be immensely expensive we had to buy it ourselves. GitHub hosts thousands of repositories for us. So, so again, these are there are plenty of sponsors that need to be recognized here with with sincere gratitude oracle there should be dropped. That's a good one to this in this example oracles oracles contribution stopped and they haven't donated any further and so they shouldn't be listed here any longer. Got it. So, so did that did that answer your question and is that I guess potentially more detailed than you ever wanted to know. It's exactly how much details I was hoping for Mark. Thank you. That was perfect. But yeah, no that covers everything that helps explain what I was curious about myself in terms of what changed and what kind of what major change happened so knowing that should I submit a pull request to remove red hat from this from the homepage or Jenkins.io or No, if you could actually yeah maybe well yeah if you don't mind doing it it's easier than me doing it. That it's someone needs to do it and the I'm the one who detected it because I'm part of part of the CDF technical oversight committee but if you're willing to do it that would be great. Yeah, I can I can definitely take care of that I can. Would it be would it be prudent to submit a pull request separately for red hat and AWS. Let's just do red hat for now we'll leave AWS for another two weeks. See what their responses to our donation request if their response is that they donate, then they stay. If their responses no we won't donate then they clearly get removed. They've then made a very clear choice, not to donate to the Jenkins project and by that choice, we would remove them from the list. Okay, great. Thank you very much. And yeah and I know I know that one of the things that have been discussed. As far as like the mock up goes partner gets a little messy so having the Olympic medals you having the different tiers is a little bit cleaner in terms of what that means and what that kind of signifies. So, yeah, I think that's probably the best way to go about things and yeah, take care of things. So, so thank you again very much mark that appreciate that and help clarify a lot of that. And then, finally, the last thing on the agenda is integrating Docker compose into the Jenkins documentation. So, first and foremost thank you to Bruno for doing this and incorporating compose into the tutorials or at least could be submitting the pull request to do that. And then going through the Maven one to verify and checking everything looks to be good there. Instructions are clear things I've been able to do perform the Docker compose functions without any errors or anything so things are looking really good there. Yeah Bruno, what would, is there anything you'd like to share a pin point out. Well, I wanted to mention that it's far from perfect. Yet we still have some issues to solve for example when somebody start the tutorial then does something else and then comes back three weeks later to finish it. There have, there will be some plugins update that won't show up for example. So there are still some maintenance things to do when somebody starts Jenkins instance and then continues a few weeks later. And same for when somebody exits the Jenkins instance, there are some things that stay, but that should get removed in fact so maybe when somebody and the tutorial things and everything up and then restart a few weeks afterwards. There could also be some old things laying around like old plugins for example so I still have to clean data but frankly for somebody starting from scratch never having started Jenkins in a way on another, finishing the tutorials and getting everything cleaned up that does work. There are a few places where we could do better explain things in a better way, but for them being, I think that usable as is, but I'm not against ameliorating the way it is phrased or presented. Mark already found a few issues here and there. I corrected, but it could have been better corrections. So yeah, it could be merged. We can still wait. There is no hurry. Whatever. If you want to give it a review Kevin or make some adjustments, feel free to do so as for the Python one, it is dependent on the Maven one because they share some files together. Mostly the new prerequisite, for example, so I don't want it to get merged yet for this reason and also because I think we have to modify the way we envision using Python free in bookworm because it doesn't work the way it used to do you have to use a virtual environment. And I'm not so sure this is what we are recommending in the tutorial so I have to redo it from scratch on my machine and see if it's working the way it's supposed to work. The text may be correct or not yet correct, I see, and we also may have to change the support repository, you know the sample Python app something which is in Jenkins doc organization. It may not be up to date when it comes to newer Python's requirements when using bookworm. I hope I made myself understandable. Yes, totally. You did and you actually addressed a comment that was received in the Jenkins documentation feedback pages. This is a on on each Jenkins on many Jenkins documentation pages. There's an was this helpful to you link and then it pops up a little dialogue that allows them to give feedback. And one of the comments was your Python example is Python two. And what I think you're proving to me is no it's not it's Python three good so. Okay, so and it was unrelated to your to the real the real challenges you're facing or the things you're doing with the Python tutorial it just says that okay the person who submitted it was mistaken. It's it's not Python two you are you were doing you've done all the things you did with a Python tutorial were certainly with Python three not with the obsolete no longer supported Python two. Yep. Great. So, whenever the maven PR gets marriage, feel free to have a look at the Python. Okay. Thank you. So that really gives us two things that Kevin and I and anyone else interested in documentation can review it's the version documentation site that Vandy it's working on and the maven tutorial that Bruno's working. Thank you. Yeah, both really nice pieces of the work so far really excited about where they're at where they're headed. So yeah, thank you very much Bruno for creating all that and putting it up and giving opportunity. You're welcome and thank you to Ashutosh Saxena and Jean-Marc Mason and I forgot the name of the last mentor for helping with this project during Google some of code 2023. Leo, but then go. Got it. All right. If that takes care of everything for today unless anyone has anything they'd want to add or throw on there for last item. If not, we are a time I'm going to go ahead and stop the recording in just a moment here video be available 24 to 48 hours from now. Thank you all as always take care until next week say safe and yeah we'll see you then. Thanks again. Bye bye.