 Welcome to the Jenkins Docs Office Hours, EU edition, today is September 22. We have quite a few items on our agenda today. We have some action items that Mark and I will give some updates for. We have just a quick mention of DevOps World 2022, which is next week. We have the upcoming October LTS release, the weekly release line needs to be reviewed with DevOps World happening next week. I'll be kind of heading that one. And then we have an item for the October Fest documentation efforts that we have available that we're planning on sharing with the project and the event. So let's get started. Is there any other items that we should add to the list before we get started actually? I don't have any. OK. Then as far as the action items go, Mark, any updates on the ones under your name? Yeah, so upcoming blog post, I propose to drop that action item completely. And just admit that I've failed. My blog posts are not going to happen for those topics between between DevOps World and then vacation time I'm taking after DevOps World. It's just too late. We'll need to do a DevOps World contributor summit blog post or multiple blog posts. And that will be the better approach. Makes sense and well deserved time off as well. So yeah, so on that note, we had a blog post that was published on Monday that I wrote regarding our digital ocean sponsorship. Digital ocean is the organizer and main sponsor of Hacktoberfest. And they actually just recently granted us, say, just over $18,000 sponsorship with which in addition to their earlier sponsorship this year brings us to just over 20,000 big, big, big, thank you to Digital Ocean for all of their sponsorship and assistance and dedication for making to help make Jenkins as great as possible. We also have a blog post that was recently published for by John Mark, who has created a little post about the Hacktoberfest 2022 event going over just how we're getting ready and gearing up for it. You can see there it's called September, which is exciting. And yeah, a couple of weeks left before that actually finishes out and we start. And then one of the biggest things we actually have published the adopt and improve a plugin tutorial. There's a blog post showing facing that and this is going to be the content that's used during the DevOps World Workshop. So first hand experience, big thank you to Mark and Derage and everyone who contributed to this. This has been a long time coming in a process that was started since DevOps World last year. So having it finally come to fruition is really, really nice to see. And just it just goes a long way of and reinforcing the community aspect and having people join in to the contributions as they can. And we received our first and merged our first pull request to improve it. We're already on the right path. Fantastic. OK, Mark, did you want to have it? Did it was there any other notes you wanted to share about the tutorial? No, I just encourage people to use it. Remind them that it's a it's a candidate to give goods. It gives good suggestions for things that you can do confidently and that are valuable for Hacktoberfest. Awesome. And yeah, as a newer Jenkins user, for me, adopting a plugin seemed very daunting. That tutorial made everything easy. I just had to make sure that I was following the steps and taking my time with it. So a little patience goes a long way here. Yes, same for me. I was really scared. I don't want to add up the plugin even that would be fine. And now after trying the steps described in this tutorial for a few plugins. I could become maybe a maintainer for one plugin. That's not that big of a deal. Yeah, it definitely takes some of the scariness away for it. So yeah, very, very much so. Thank you. Yeah, so nicely detailed. And yeah, it really helps. That's a fantastic job. Thank you. Great. Next up on our list, I just again mentioned that DevOps World 2022 is happening next week, which is 27th to the 29th. I know, surprise, Runaugh, out of the blue. That does also mean that with nearly everyone on the community team being at DevOps World next week, most of the events have been canceled. If not, all of them have been canceled, but does include Docs Office hours. We have already shared that information with the Asia Docs Office hours participants and wanted to make sure that that was brought up here as well. So next Thursday, we will not have Docs Office hours. It will, however, start back up the week after and we'll be really just getting into Hectoberfest at that point in time. So it's going to be really exciting and all new. So definitely keep posted on that. Next next month, coming up in a couple of weeks, we also have our 2.361.2 LTS release. So that'll be happening October 5th. I've created a change log and upgrade guide entry for this. It's available and open for feedback and suggestions. If you have a chance, take a look, see if there's anything that might need updating or any kind of changing please, by all means. More than happy to work and figure that all out. On the release line note, I'm also starting to do the weekly release line reviews this past this week we had 2.370, which was a security release. So we're already keeping eyes on next week for 2.371 and the pull request for the change log already has an update to it. So we'll be keeping an eye on that. While everyone is at DevOps World, I'll be reviewing and editing that as we go. I'll be out towards the end of the week next week as well. So I'll make sure this is taken care of before I head out so that no worries, no anything left hanging after the fact. And finally, the biggest piece of our agenda today, Hectover Fest is coming up in a couple of weeks. Mark and I have been working alongside the community and everyone in Docs Office Hours to go through and confirm the issues that we want to have and make sure that the topics available are spanning both Jenkins and non-Jenkins experience and documentation, otherwise, et cetera. It's really a cornucopia of ideas and we just really are excited to have people join up and participate. Again, the two set of topics are good first issues where no Jenkins experience is required. This will include things like updating some of the documentation based on current versions, making sure that the sections are in the correct order, more low level or low impact documentation work. And then we also have the Hectover Fest section, which is going to include topics that have a little bit more Jenkins experience involvement. So not necessarily going to be for everyone, but if someone does have Jenkins experience, we want to make sure that they can leverage that to their advantage and make a meaningful contribution if that's what they're looking to do. So we'll be continuing to refine this a little bit more as we go along, but for the most part, we do have the topics categorized and labeled. So pretty much what's there is going to continue to be there as we move towards Hectover Fest. There's also going to be an option for Plugin Documentation Migration. This is specifically the Plugin Documentation, not the Wiki Migration. And this is a great opportunity for folks because we have plugins that are maintained or owned right now by Mark, Jean-Marc and Bruno. So using these as the first choice plugins, these are going to be reviewed and maintained by people that are active right now. So the pull requests are going to get actioned upon. Other plugins that have maintainers that while they might be interested in Hectover Fest may not want their plugin being part of this. So whereas others are going to have the Hectover Fest label on their plugin, this is the place where you can submit to those maintainers. However, if they are not active, if for whatever reason, they just don't get a chance to review the pull request within the month of October, it's going to just sit there. So we want to try and avoid that limbo as much as possible for all the pull requests. So we have a migration report that lists all the plugins that need to be migrated. We have the documentation page that describes the task. And Mark, will we have a list or it's going to be the easiest way for people to make sure that the plugin's a good choice, maybe owned by yourself, Bruno or Jean-Marc. I'd say it's a good question. So I think if you look at that worksheet sorted by various attributes down at the bottom of the list, let's open that and let's talk about to see what, because maybe it's as simple as we put this one. Is this the topic you were thinking, Kevin? Yeah. Yeah. Or are you thinking more generally in plugins to which you should contribute, not the documentation task? Yeah. So I was thinking more so. We have the first choice of you, Jean-Marc and Bruno having the plugins. The second choice is asking maintainers to review. I was thinking, is there a place that has these ones specifically listed so that we know for sure which ones to contribute to versus is it going to be a matter of searching for the repositories or plugins during Hacktoberfest and then contributing to those and we're checking with the maintainers and then contributing. Okay. I put in the chat the link that we created the other day. You know, Marc, the spreadsheet. I don't know if we should share this one but that's our reference for the time being. Oh, good. Yeah. So let's open that one and see. Oh, yeah. So this is the sheet that we'll be using in the workshop to decide, okay, who's adopting what? And we could easily open it up and say, hey, we'll let anybody make a comment on this sheet proposing to adopt it. Okay. And that can be, obviously that can be done after DevOps world. So we're not. Yeah. So this is the, yeah, the list of the plugins will be on the deck ready to merge pull request or make some reviews and so on. Okay. So all of those will be perfectly active and we can then just use that as a basis, essentially. Right. Yeah. So the thought was, hey, let's, here's a list of plugins that we know the maintainers are willing to review pull requests. Now, these are willing to review pull requests of a more general nature, right? These pull requests are not just docs transformation. They're anything, for example, anything in that modernize a plugin tutorial would be a good candidate for these. Awesome. Yeah. And I can see like the get lab authentication and a couple of the other, the other ones I didn't see as far as documentation goes. So yeah, I see where having this just be available as for the community would be nice to have is just informative purposes at the end of the day. Now, to the question, which ones are doc migration? Kevin, if you'll open up, I'm gonna paste another URL for you to open and let's look at it. Cause I'm not entirely sure that, that if we want to have a list for the docs migration tasks specifically, we probably ought to use, well, actually, why am I doing this? Go back to the, go back to the sheet that was there before the, yeah, that one. Yep. This one is specific to docs migration. Okay. And the reason, let's see, let me make it, let me make it editable to you. But the reason that the specific to docs migration might matter is what I was looking, what I was seeking was which plugins seem like the maintainers are more likely to be willing to evaluate a pull request. And my guess on which ones there would be more likely to evaluate is which ones have the newer release date. So this is sorted by date of release with count of installs on the right, but not its ignoring count of installs. And for me that was, okay, the, for instance, the deployment notification plug-in released less than a month ago. Somebody was working on that thing less than a month ago and may be willing to review pull requests. Right. But then we've still got to reach out, contact them and say, are you willing to do that? And that means we've got to dig out their email address and that may not even be feasible for some of them because some of them, the maintainer may have only published their Jenkins username, not their email address. Okay. And if they haven't looked at Jenkins in a while or GitHub, they might not see those notifications just to their user. Right, right. We could certainly ask a question on the plugin on the, as in a plugin pull request or something like that. But if they ignore us, we haven't gained much. Right, so. Okay, that makes a lot of sense. And this cleans up very well, shows everything that I was curious about. And I think it would be a great resource for a community. Thank you. But so maybe we ought to come to a decision there because I like, if you'd switch back to Bruno's, the sheet that Bruno had because that one is much more general purpose, right? This one is, hey, these plugins, you can contribute, if they need, maybe what we ought to do here is identify which of these still need documentation. And that's an additional thing. And we say, okay, here are ones that we know need documentation conversion. And you could, or a doc sig can certainly offer those exactly as translate those to convert their documentation from Wiki to GitHub. And Mark, if ever we don't get them all modernized during the workshop, shouldn't we after the workshop create a series of issues for each of these plugins saying, you know, labeling them with October fast and modernizing, you know, the issue being modernizing the plugin because we are there, we can help, we can merge pull request, but people have to know what to do. So maybe we should create after the workshop if they aren't all modernized, one issue per plugin saying, please modernize me and here is the documentation. And yes, this is a hacktoberfest issue. What do you think of that? Good suggestion, I like that. Yes, because then we could open that issue and label it good first issue. We could even at that point, if we have a sample of that thing, we could point to it and say, you can look at this for an example. Good, yeah, I like that. Good suggestion. Thank you. Yeah, I like that a lot too, Bruno. Thank you for bringing that up and having that. Yeah, and as Mark said, we can set it as good first issue. We can set up the labels on it so that it comes up as we want them to. And that would also have a little focus for the user, the person contributing where they want to go and what they want to do. So yeah, no, I think that's a wonderful idea. Cool, and Mark, you show us, sorry, go ahead. No, I was just going to tell you several of these on the list that have that. So row number seven, conditional build step, needs docs converted. Oh, no, no, no, sorry, it doesn't. Artifact Deployer, which is a little further down. Oh, okay, so what this hints is probably most of these have already got their documentation updated. Artifact Deployer is definitely one that needs it. I know it does. Others I'm not as sure of, and in the top six or seven, none of them needed. So this list may not actually be a great choice for the pure docs focus. We could, could we still do something like that with these, Mark? Or would that just be too much at this point because there's a lot of bugs here? We certainly can, any one of these, the challenge with the challenge with this list is we don't have control of these repositories so we can't merge the proposed change. Whereas the other list, Bruno, John, Mark and I are reviewers on it and we can merge the changes immediately. Right, okay. We will know so we can share that with people. And I think we'll be okay at the end of the day. I don't think that's going to deter anyone or anything from happening during October fest. But yeah, these are all just, I'm just curious. Thank you for sharing all that. I appreciate it. And I think that helps clarify a lot for all of us that like what we're going to be able to do and achieve it. Mark, you showed us earlier today in the Outreach Advocacy Sieg meeting, a link that would list all the kind of contribution people can make to during Hacktoberfest for Jenkins. And some of them were translation, for example. Could you please share once more that link? Cause I thought that it was well written, all the list of things that people could do. Would translation be valid for Hacktoberfest and documentation Sieg? I mean, it is a subject we should address in here in documentation Sieg or not at all? It's not Sieg, it's office hour. I don't, it's not that it's not well suited to office hours but rather, well, let's have Kevin open it first and let's look at it. So Kevin open up a new tab to Jenkins.io. Yep. Sorry if I muddies the water. Oh no, this is great. So now if you look under, I think it's under community Hacktoberfest. No, okay, try, maybe, yeah, there you go. Great. So yes, so here we go. So as you scroll down, what you'll see is here is a list of issue queries and then featured projects. And between those two lists, the list of issue queries and the list of feature projects. So if you click good first issues on GitHub, we should see the, it's the very bottom most one. This will give you issues from all sorts of repositories in Jenkins CI and Jenkins Infra. And these are issues not just, not specific to documentation, but in fact, related to anything as an issue on that plugin. Now go back to that page, because then if we look at the Jenkins website, let's see, there's not one there. Okay, maybe Kevin, this is one we ought to update. Okay. So here what you see is it says, hey, here it offers some suggestions of ways you can contribute, but it does, oh no, there it is, the good first issues link. So on the sort of top center, right hand side, yeah, there it is. There you go. So this one shows good first issues and there are currently 13 open. Now we may wanna mutate this to be good first issue. I don't know, yeah, that's actually a good choice because any one of these that someone decides they're going to work, we are willing to label it Hacktoberfest, right? If they do it during October, we can certainly label it Hacktoberfest. If that's a concern for them, we say, hey, why isn't it labeled Hacktoberfest? Good, okay. So back to that page. So, okay, so Jenkins website is one documentation location. As you scroll downwards then, there are others and I think we've got one further down that talks about, yeah, here's a good one, non-inclusive terminology cleanup. This one needs a sweep across all sorts of places looking for non-inclusive terminology. So I'm not sure we want this one in this particular page. It's just too complicated for a new contributor to find those locations successfully. Most of the easy ones are already done and it's a common pattern for a contributor to attempt something and not realize that what they're doing is completely flawed and will break things much worse than if they just done nothing. So this, could you make a note? We just need to be sure we delete that from the list because we don't really want to ask people to do things where they are unlikely to succeed. The inclusion naming also, I know this has come up before. It's not as simple as just replacing the words. It also has to deal with the context around the words. So it's not just as easy as replacing things which will be great. But yeah, in this case, it's a little bit more involved or difficult. With things that way, she cut off her credit here. Right. And by with direct coaching, they were successful but it required direct coaching and an awful lot of interaction to assure that they didn't make mistakes that would cause the plugin maintainers to say this pull request is harmful, not helpful. So keep going downwards, Kevin. There it was, plugin docs on GitHub. So that was the one where we might, yeah, see, I'm okay. So could you try opening the GitHub good first issues link that's on that row? I suspect it's no better than, oh no, no, no, it is better. This one's really got good first issues in documentation. Okay, back to the page again and let's do one more check. So this time the newcomer friendly issues link that's right next to it. Yeah, and that one, okay, those are reasonable but probably, yeah, okay. And that's not a bad list. Okay, good, thanks. And then, yeah, there's this section specifically for French translation, which is what Bruno had meant or not specifically the French, but there is one for this translation specifically and then some internationalization documentation. I also know that we have crowd and enterprise too. So, and if I recall, there was questions before about how to make sure people get credit or recognized for the translations they're doing. And that's a part that I'm not, I haven't read the Hacktoberfest instructions well enough to understand how things that are not submitted as pull requests to a GitHub repository can be counted. Bruno, maybe you can give us an overview of how they, how do they do that accounting? How do I tell them I submitted a translation through CrowdIn? That's a problem for the time being, haven't read the detailed details of that. I don't know, because they also talked about writing a blog post, doing a presentation. So how would they count that as an issue which is linked to Hacktoberfest? I don't know yet. I have yet to find the right documentation that details all of that for the time being. I don't know where it is if it ever exists. Got it. Okay, so you've got the same open question I do. For me, the French translation topic is interesting if a team were to decide as a group, hey, we wanna work on French or we wanna work on German or Italian or Spanish or Brazilian Portuguese. Any one of those would be great, but it sort of needs more than one person. This really isn't well suited to a single individual approaching it because there are likely some problems hiding here that will have to be discovered and resolved. Yeah, and there may be some prerequisite too because you were talking about CrowdIn, Kevin and somebody has to configure that in the plugin before starting the translation. So, my second question was, can we draft that subject within that documentation office hours because it's linked to documentation but it's not really documentation. Yeah, I think it's a good topic for office hours. Unfortunately, I don't think we're gonna be able to make significant progress on it in time for Hacktoberfest. Of course, because we have to find the maintainers who accept our first pull request for going to CrowdIn and we have, first of all, to convene them, this is useful for the plugin. And so, no, I don't have any expectations, but yeah. And Bruno too, someone actually else has brought up the translation stuff during our Hacktoberfest prep meeting. So, that is something that other people have been considering. It hasn't come up as part of the docs topic specifically. It's kind of considered its own thing. And they had similar questions. So, yeah, I think it's something that is a little, maybe outside of the scope to some degree, but that doesn't mean we can't bring it in and talk about it. Like Mark said, discuss, we can do what we can, but making progress might be a little bit more difficult. So, thank you. Yeah, cool. Is there anything else on this page that might have had to do with... Those were it that I was aware of, Kevin. Okay. Okay. So, in that case, I think we've gone over all of our Hacktoberfest information. Was there anything else that you wanted to add on that, Mark, or anything that you wanted to share? Nothing else for me. Nothing for me either, thank you. Okay, fair enough. I appreciate that. If that's the case, is there anything else that we would like to be brought up today, Nami? If not, great. We'll stop the recording in a minute. The recording will be available in 24 or 48 hours. And as always, thank you to everyone for all of the hard work and joining. There's been, there's newest contributions coming through every day. And I'm very happy that I get to be a part of this and help this community. So, thank you, everyone, always. Thank you.