 Welcome all to the European Docs Office Hours. Today is September 15th. Today on the agenda, we have a few items about blog posts. Google Summer of Code update if Veehan ends up joining us this afternoon. A quick update for DevOps world since that's coming up soon. And hopefully we get to have a little bit more discussion around Hectoberfest documentation and what we can do to contribute to that, ideas, et cetera. So first things first. Mark, do you have any updates on blog posts or any of these items here? So no progress on the ones that are on mine. So the both and probably no progress for at least another four to six weeks. Sorry. Yeah, that's okay. Makes sense. DevOps world is coming up Hectoberfest. We've got a lot going on, so. Exactly. And there was the, we are also announcing our re-upped sponsorship from Digital Ocean. I've written a blog post that's been reviewed by the community team, a few other folks and that will be ready for publish on Monday. And that is just a big, again, thank you to Digital Ocean for their continued support and sponsorship. They are allowing us to dedicate ourselves to Jenkins and use as many resources as we have. Mark, it looks like you might be able to have an update for Google Summer Code for us actually. Yeah, so the coding phase is complete. Thanks very much to Veehan. He's done, the project has had great results. Very pleased with the outcome. The pipeline steps reference is more readable. As a side effect of the work, not only did the pipeline steps generator get improved, but it exposed to us that the back-end extension indexer had a problem and it's also been improved. So very nice side effects on both sides. Awesome, thank you so much, Mark. And I know he's not here, but thank you again to Veehan for all of the work and effort put in for this. It's night and day difference, how much improvement it is and just appreciate all of your hard work. Next item on the agenda is DevOps World 2022. It's coming up in a couple of weeks. There's gonna be a lot of sessions, talks, workshops. It's a great community event, so perfect opportunity to connect and meet people that maybe you've only spoken with on Mark. There's gonna be a workshop that Mark Bruno and Jean-Marc are gonna be doing about adopting and modernizing a plugin, which will then make its way into the Jenkins documentation itself. So that will be available for everyone after the fact that just because you're not going to DevOps World doesn't mean you miss out on it. There will also be a contributor summit on the second day, which is the 27th when I'm not mistaken. And that's for any contributors to Jenkins. So if you are attending, keep that in mind, feel free to go, it'll be a fun time. And again, you get to meet everyone that you've worked with online in Jenkins. Mark, before we move on to Hacktoberfest, did you have anything else for DevOps World 2022? Just the poll requests that's still in draft, I hope will be out of draft today so that we can say, yes, it's ready to go. It needs a relatively few minor tweaks and certainly we could then extend it later, but I've been asked in Asia office hours multiple times, Mark, when are you going to merge that poll request? And I would love before Asia office hours later today about 12 hours from now, that's merged and visible so I can show it to them and say, look, I did it finally. Sounds like a good plan, I like it. And yeah, hopefully that is good enough that they are excited to see it finally ready for review and open. Cool, all right. So then the last thing that we have on the agenda today is just talking about Hacktoberfest. It's coming up. We all know that it's a few weeks away just after DevOps World 2022. The site went live last week, so that's now available and describes all the different items and topics that are included in Hacktoberfest. And we've also gone through and updated our own documentation page in Jenkins to reflect the updated in general participation options and things like different issues and where to find problems or items to take on. There's more information here as far as migrating the plugins and just in general in advancement in the information that we have available for anyone that's gonna be participating in Hacktoberfest. Especially thanks to Mark for updating that page and including all of that, looks great. And we are talking about this as much as possible outside of Docs Office Hours as well. I'm sharing it with as many people as possible, trying to get as much interest as we can. It's a great opportunity to, again, make community connections and empower the community and make it so that people who have never worked on Jenkins have the chance to experience it and get a bit more familiar with it. We have a couple lists of documentation tasks that would be perfectly doable for Hacktoberfest. We have some good first issues. These are all minor issues that do not require Jenkins knowledge. And we have some other issues that would be listed under our Hacktoberfest filter. And these ones do require a little bit of Jenkins experience but are still typically a little bit lower impact or lighter weight in terms of what they were looking for. And we'll be able to go ahead, Mark. And Kevin, I realized I had used the labels backwards from how the Hacktoberfest organizers asked that they be used. Okay. So Hacktoberfest label is applied to everything that's eligible for Hacktoberfest. Anything we recommend, whether skills needed or not. Good first issue is the one that is flagging but they are also flagged with Hacktoberfest. So the problem is if you only look at Hacktoberfest, you'll also see good first issues. That's okay. It's just people need to be aware that sometimes something's flagged as Hacktoberfest that is not a good first issue. This is now compliant with the Hacktoberfest guidelines. Awesome, fantastic. So then the list of good issues or good first issues is the only list we're gonna need then? Or should we? Well, if you've got Jenkins experience, the Hacktoberfest list is good. If you don't have Jenkins experience, the good first issues list is the choice. So the definition that's listed there still holds. I just had to change things a little bit. Okay, got it, got it, got it. Thank you very much, Mark, for explaining that helps clarify things. And yeah, now we know. And if anything too, we do need some volunteers to go through our open issues and if there are any items that they can recommend, this is a great place to do so. You can see that some of them do not have the Hacktoberfest tag. So some of these are gonna be a little bit more involved again, but anything that comes up as potential, we wanna make sure that it's included. When we do go through that, we're gonna look at closing some issues that are resolved or no longer applicable. And we'll do that in Docs Office Hours. Today, the next couple of weeks, et cetera, until we get to Hacktoberfest. And then a couple of the ideas that have been additionally put on here, the plugin documentation migration from GitHub, or to GitHub. The plugin documentation for the plugin's documentation is now being directed from GitHub. Previously, it was on a Wiki that's now read only and close out, so we have to migrate the docs. The migration is not as involved Jenkins experience, but do need to know about working through Git and making pull requests and whatnot to make sure that that's all transferred properly. Darren and Mark have a video demo of doing such thing. So there is a lot of information out there and we will have Office Hours and there will be live streams for Hacktoberfest as we go through the month of October. So there'll be lots of opportunity to continue to ask questions, learn and get assistance with anything that you might be working on. As far as the plugin documentation goes, we are hoping or looking that the first choice for this option would be ones that are currently owned or maintained by Mark, John Mark or Bruno, because we know we can get to them and talk to them and work with them instead of having to worry if the maintainer is no longer paying attention to the plugin. Those ones are gonna be easiest to change and move and so as we get closer, Mark, John Mark Bruno will be able to assist with all that. The second choice for the plugins would be if we can ask the maintainers to review but we are only doing so if the maintainer is actually available and agrees to do so, otherwise it wouldn't be a great experience of trying to submit changes to someone who's not responding. The only issue with submitting it to the maintainers is that, again, it's communication line and we need to make sure that that line is open if it's not open, if there's something happening where the maintainer can't respond or react to any of the pull requests, then we've done the work and we've tried our best but unfortunately that change might not be able to get enacted if someone's not responding. So best thing you can do is ask, find out the maintainers are listed in each GitHub repository for plugins and on the plugin page in Jenkins.io. So you can always find out who's available and if not, it might be up for adoption and that's a wonderful time to check it out and see if you're interested in that. I did just do it recently myself so it's not that bad and I'm a writer, so yeah. And then there had been discussions on general documentation migration to GitHub but this is not the best idea, it's not going to be the most conducive for new contributors and there's a handful that are stalled and aren't being moved right now because of the amount of work and just in general administrative tasks that required for it. Yeah, the improved plugin developer tutorial also includes the docs migration page so again that will also be part of the plugin adoption tutorial and workshop that is presented at DevOps World. Now, before we go to the good first issues or open issues list, did anyone have anything else they'd like to point out, share, mention about Hacktoberfest? Well, so on the plugin documentation migration, it's really healthy for people to help us with that. You noted the complication, the complication is finding maintainers who are willing to review and so now I'm not sure, one of the challenges for me is how do we show the list I get like actually I take it back. I know how we show the list. The Hacktoberfest project tells us how we do it. We ask people to remove the Hacktoberfest topic from their plugin if they're not willing to review Hacktoberfest poll requests. That way people know not to submit it. So sorry, here I am talking to myself but I think I've realized this has a simple solution. We follow the rules that the Hacktoberfest definers have said and tell people, please, if you're not willing to process a Hacktoberfest poll request for documentation or otherwise remove the Hacktoberfest topic from your repository. Good. Yeah, that all makes sense. That's nice and simple. Yeah, following the rules, who would have sunk? Right, okay. But yeah, no, awesome, fantastic. Thank you so much Mark again for adding and clarifying that that helps a lot. And yeah, we really wanna make sure that Hacktoberfest is the next experience possible for whoever wants to participate. So if we can follow these guidelines as closely as possible that's just gonna help make that mark. So. And yeah, Mark, did you want, so should we go into the open issues list and start taking a look at some of these items? I think we should. Unfortunately, I suspect, well, could you open that open issues list and let's see if you have permissions to add a label. So pick any one of these anchor links, no longer work on blog posts. Over on the right hand side, are you allowed to add the label? Yeah. Okay, good. So as a triage, you can, now you need to take it off. But great, so we can have you do this, perfect. I wasn't sure if the permissions for that were limited to copy editors, but as a triage, I remember the triage team, you've got it. Good, so let's do this thing. And. Okay. So last time we started from the front, I propose we take a different approach this time. Let's start from the back. Okay, yeah. So yeah, so oldest one here is from 2017, it looks like. Yeah, okay, so, and I just wanna stare at these for a little bit. So just hold the screen still and let's ask everybody, please stare at them. And when you see one, you think is a, is a Hacktoberfest candidate, raise your hand. Or say something. Oh, there you go. I think fix the mailing list page, top second from the top, is probably Hacktoberfest, if it's not already resolved. Okay, pressing the link, whoops, go up. Pressing the link, how to ask questions the smart way. Oh, nope. Okay, this one, there is no way to solve it. Ah, okay, great. Because I remembered this one, so let's just go ahead and close it. So, yeah, can you close it? You can, so close as not planned. The problem here is to tell the story, this links to a webpage and in the modern world, we all expect webpages to be SSL secured. This particular webpage is so old that it is not SSL secured and it will probably never be SSL secured because the writers just didn't care if you didn't trust them or not. And it's a very practical approach that they took. This is very unique, very much distinct. So, victory there, now you can close this tab, Kevin, and we can go back to the list again. All right, sounds great. Oh, hey, there's an interesting one. Somebody who wants to do JavaScript or wants to do, make a webpage look better, the rework, the roadmap coloring scheme. Yeah, I think this one would be worthwhile to give it a Hacktoberfest link. This is something people, it's not simple. You have to understand how this thing is generated. I wouldn't make it a good first issue, but I think it's a valid Hacktoberfest issue because it's a look and feel thing. This is the kind of thing that Vihon did so brilliantly, right? Find places where the website would be better if we did this or that thing. Right, right, got it, right. So then we've made that part of the Hacktoberfest tag. So, is there any other context or anything we should add, Mark, or is that a bit for what I'm talking about? No, Oleg's description here is really great. Okay, wonderful, thank you very much. There's a lot of Wikimigration tags as we're coming up on this too. And those we can ignore because Wikimigration is, I know is not a good fit for Hacktoberfest. Interesting, is there a way to ask for GitHub to remove things from this result, which include a particular label? Can you say things that don't have the label? That's okay, oh, it's not, try it. No, okay. At least you tried, nice. Yeah. If you click on filters, do you have anything that you could add, Kevin? Oh, right. You never know, advanced search syntax, maybe? Yeah. Oh, okay. Is in. No, okay. My label, label, yes, okay. Okay, we'll just search for it. That's if you want to find the label, or if you don't find it. But if you do, okay. Maybe not then. Yeah, it seems like we can find it if we wanted to figure out only Wikimigration ones, but it doesn't seem the inverse is possible, necessarily. Can't we just put a shebang in front of something? So an exclamation mark. Yeah, an exclamation mark. Sorry. I don't know where this term comes from. So then, or it would, no, be label. I would have put the exclamation mark before label, maybe? Oh, okay. Just a white guess, I have no idea what I'm doing, but, okay. I don't either. Bruno, thank you for all of your sessions. It's okay. Okay, now you got to go back to the end of the list. Yeah. All right. So, yeah, could you open 31, 34, the valid how to guides link for testing page? I'm not sure what, okay. Problem. All right. So keep scrolling downwards. Interesting. Is it still broken? Okay, now, okay. So let's, let's, so scroll up. So the, you see the problem with testing. Mm-hmm. So open that page. And now on the how to guides under manual testing header. So about two thirds of the way down the page, left side. Yeah, that. It's definitely not broken. Yep. It leads to something. Yeah. So that issue is resolved. Okay. So then, just close it as completed. Yeah, it's done. Great. And there we go. Perfect. Okay. Going back to the next page. Since that takes care of everything there. Open that. Whoops, whoops. Open, build a Python app with Python. So three, two, five, one. Build a Python app. I think that's working. I've run it multiple times. Okay. Okay. So let me, let me see what they're saying there. Okay. Jenkins. Jenkins documentation. Tutorials. Build a Python app with pie installer. Okay. Add to final delivery stage. Okay. Says. First sentence me. This un-stash step. Okay. This dirt step. The first sentence ends at stash. And then afterwards it's a fragment maybe. I don't know. I don't see it as a fragment when I look at the page online. Open up the, open up the, yeah, open up the hyperlink. Scroll down now, Kevin. And it's quite a wait. Whoa, right there. It's item three in the annotated list. Keep going up. Okay. Up. Right there. Okay. So it says. The final program will be created in that directory by pie installer. Something, this un-stash step of the basics. What is the, oh no. Okay. So four is the un-stash. Three is the dirt. That looks correct to me. I think this might be what's happening, Mark. This weirdly broken image piece. Bug, right. Exactly. Okay, good. Thank you. So there is a bug. There's a picture of that, or you know what? I can do it, Kevin. We don't need to take time in the meeting. That's, that's still, oh, good. Okay. That's still a bug. And so it stays open. And that's a good first issue. Yeah, definitely. Okay. Wonderful. And then let's put that here real quickly. I might have to fix that, but I'll check it after our meeting is over. Okay. Open up number three, three, three, five broken links. Mm-hmm. If there are still broken links, that's certainly something that is worth putting, putting on a Hacktoberfest list. Okay. There we go. Okay, this one is very much a, a good first issue. Okay. Vlad ran this report for us. And so no reason not to include it in the list and let people make progress. Could you also, Kevin, while you're there, see if you can remove Rushdie Modi as the assignee. Oh, yeah, no problem. Because Rushdie is certainly no longer working on it. Okay. All set. Good. Okay. Open up three, three, four, zero issue reporting page. Oh, no, okay. This is too complicated for Hacktoberfest. Okay. It's, it's a good one, but it's too complicated for Hacktoberfest. Having someone who doesn't do regular issue reporting, try to describe the issue reporting process is a recipe for failure. Yeah. It doesn't sound too fun for whoever would try to do it. Okay. This one here, Mark, it's content duplication. Yeah. And that one, that one is complicated enough. I wouldn't put it on first time users because we can't break existing hyperlinks. And so in order to de-duplicate content, we really have a lot more work that has to be done than I would put on a first time contributor. Okay. Okay. So I think we're ready to try one page before this one. All right. Hey, could you open the three, five, eight? No, no, forget it. Nothing, nothing. That's too complicated for a first time contributor. I saw that. I was thinking about it too. I realized I had to do Docker, but it's not easy. And that's something I should tackle with, by the way. Right, that is, yeah, that's very much unwise. Okay. Okay. Oh, open three, six, four, five. Three, six, four, five. Open Liberty profile thing. It's a wiki page. Oh, no, this is wiki migration. So could you, while you're there, label this wiki migration? Yep. All right. And we've only got two minutes left before we're out of time. So. Okay. Yeah. We can continue going through this in the next couple of weeks. That's not a problem. So, and I know that there's already, there's a couple of are definitely getting listed here, which is good. A lot of these are, yeah, wiki migration, it looks like. Yep. Well, we made progress. The list is a little bit smaller and every time we make it a little bit smaller, that's a victory. That's all it matters. And we did it. And so, as October fest approaches, we get a little closer to having the right list. So, exciting. Yeah. Great. So then I think, unless anyone has anything else, I think that we can call it for today and that should cover everything. Okay. So, the, we'll stop the recording. It will be available online in the next 24 to 48 hours.