 Welcome to the Jenkins Docs Office Hours. This is the European edition here on October 13th, 2022. Today, we have myself, Bruno, and Liz is joining us, which is great. She's part of the Docs Team CloudBees, and is interested in Hacktoberfest, so it's great to have more people joining into the community and becoming engaged with it. For today's agenda, there's a few, there's some action items here. We had our LTS release last week successfully with the ChangeLoginUpgrade guide. We have our next LTS work is starting. Alex Bredes be the release lead, and we'll have some work on that starting soon. Small update on DevOps World 2022 in case anyone wasn't here last week or missed it. And then some Hacktoberfest news, since that's what is the bulk of what we're looking at this month and the events and projects that we have going on. And then we will have a weekly, of course, next week, 2.374. That'll have to be reviewed. But outside of that, we've got quite a few things on here. Bruno, Liz, is there anything else that we'd want to add to the docket today or anything that you'd want to talk about? Nothing that comes to my mind. Thank you, Kevin. Am I in the wrong meeting? I thought we were supposed to be doing like docs. Yeah, this is, so this is the docs office hours for Jenkins. So these are all the docs things that we tend to talk about. So we have our blog posts and the Jenkins community blog that we have the ChangeLoginUpgrade guide, which we take care of. And all the Hacktoberfest documentation stuff for Jenkins. Here are my places. If you have any questions as we go along, please feel free to ask and stop me. No problem there. Okay. So just as far as the action items go, Mark's not here this week. He's on vacation for this and next week. So he has a couple of items that I'll have to take care of, but that won't happen until he gets back. Most likely November-ish. We just, we had our blog post for DigitalOcean sponsorship that we just got more of a sponsorship from DigitalOcean, so that's growing. We announced that in the blog. And we've had a couple of Google Summer of Code blog posts from our participants' dirage in behind that were just published this Monday. So one of them is on the plug-in health scoring system, which is something that we've been working on a lot, and is just designed to make sure that people can stay informed and up to date on what their plugins look like and how they're performing. And then Vihon was, I mean, wonderful enough to help with the pipeline step stock generation. Before, this was a very, this was a very static thing and wasn't exactly user-friendly. So he's adding a filter here so that people can search for the different steps and get results that are specific to what they're looking for, instead of just looking throughout the page. And even past that point, they've also done a lot of wonderful condensing of the different plugins here. So while some of these items are not collapsed, there are larger ones throughout the pipeline steps. The pipeline steps that do get collapsed so that we're not having a bunch of redundant loads on the page for something that might be more extensive and muted on its own page, for instance. I think they might have been, I think Bitbucket might have. Yeah, so Bitbucket has something like this for the name string where it's been condensed. Now we have a great expansion option for these and if it goes further than what the expansion might be able to hold, there's another page for it to navigate to. So big thanks to Deraj and Vihon and all the Google Summer of Code participants for all of their work. Great, great, great things have been accomplished and we just appreciate it greatly. Today we also published a new blog post that we are going to have going forward called for monthly Jenkins newsletter. Alyssa has created that, compiled that, utilizing the information from the different docs or a different SIG leaders. So we have security, infrastructure, platform documentation updates, and advocacy and outreach updates as well. So we have a ton of great information available here. And just thanks to all of the people that contribute and had items to add to this. As we go forward and continue through time, we'll just have more and more information available. And once we start going, I think it'll be a really nice newsletter that can really showcase what we're doing on a month-to-month basis. And then the last thing under the action items is we are going to have Jenkins governance elections soon. In the next couple months they're going to be announced, nominated, voted and everything. I'm finished by December and I will be working with Damian DePortal, who is overseeing the elections this year, to work with him on getting a blog post for the announcement and instructions on voting and nomination joining, contributing, whatever it might need to include for that. So that'll be something coming up soon. And there will be more information when that's available. The October LTS release went well successfully. Mark and Darren Pope had a live stream for it and all the changes and updates. You can find that here in the link. And for the next LTS, it's going to be a November 2 release date. We have started the process of getting the release lead on board, which this time is going to be Alex Brandis. Thank you to him for joining on and taking on this one. And once we get that rolling, we'll have the change login upgrade guide to be reviewed and updated with any changes and updates that between now and then. DevOps World 2022 has been postponed due to Hurricane Ian. This is going to be online in the future. So once it's been determined when the best time is, we'll start the announcements and information will start to trickle out and be disseminated. And this is going to be open to everyone, not just people who had tickets to DevOps World. So this is officially going to be able to reach more and more people than we might have had a chance to before. This also includes the contributor summit, but instead of an all day summit, we're going to have a few sessions to do things over a couple hours. So broken up a little bit more digestible. But this will take some planning. And once it's figured out, we'll give, we'll provide more info on it. And then lastly, I'm going to actually move this up real quickly. We have our typical weekly release. So next week will be 2.374. There's a couple updates in the automated change log right now, but not seeing anything too out of the ordinary to fix up. And then lastly, and I wanted to give some time for this since we didn't have a ton on the meeting. But the Hectoberfest documentation has been going really strong. And I just want to share my appreciation for everyone that's been contributing and helping out. We've gotten over 15 contributions from 10 plus people at this point I forget exactly who up top my head. And in an effort not to leave anyone out just thank you to all of you. It's been really great seeing the different aspects of documentation that are getting updated or added or revamped or just enhanced at this point. There was one contribution where we were update we had to update some of this carry info for AWS installation. And there was, we have a whole new section on Kubernetes installation for Jenkins which is great. And that you know those are just a couple of the few that we've had. It's still going on till the end of October so there's plenty of time to get involved and join in. We have a Hectoberfest, the Hectoberfest main page for Jenkins. I'm going to actually add a link in here. But we have our main Hectoberfest page we've got Gitter connection for chat. We have the event website, lots of issue links so that you can see good first issues had toberfest issues. And if there's you know if there's something that you see is being worked on already or if you have an idea for what you want to work on by all means don't hold back please share you know. In the Gitter channel in Jenkins GitHub wherever you might want to. And we also have the Jenkins Dev mailing list and several other chat connection opportunities. So there are several places that you can get connected. Please feel free to reach out and share anything. I'm always I'm about the passion. So, for all this and I'm really excited about having people join the community and get engaged and feel empowered to do what they're doing. So, please, like again by all means, any ideas, good valid idea at the point. I'm not going to say no to anything until we figure out that it's not a good fit. So, and these are all just the different areas where folks can contribute. So we have plug in docs we have translations the Jenkins infrastructure, all sorts of stuff. So, again, Hector professed is in full swing, and john mark, who's been running this for cloudies has been an amazing help in just getting everything, keeping everything on track, and helping organize everything for the different participants to really get the most out of this. He has written a little blog post for preptember so couple weeks after that, but the information still very valid and helpful. So, if you have questions about, you know, just getting started that's a great place to start. We have the Hector professed 2022 kickoff live stream. So this was done on October 3 with Darren Pope and again john mark messing suit who is organizing this for us. And they just went through and describe the ways people can get involved, how to really impact your the the area you're working in and just in general, good best practices for a lot of that. And even though it's not listed there. I know the process for creating or contributing to these repose maybe new or unfamiliar in some way shape or form. So, I strongly encourage everyone to check out our YouTube channel because that has tons of other videos, mostly on different features and functions of Jenkins but also a lot of the basics of Jenkins work and contributing to Jenkins the. We also have a contributing guide available that helps spell out what kind of formatting or standards that we have right now. So there's a lot of information it might be too much to some people or it might be overwhelming but please just do it again. If you feel like you're getting overloaded just stop and take a break. Yeah, and the community is very benevolent kind and patient so even when you do something which is not great yet, they will help you to get it up to the levels to the standard that we are expecting. I've experienced that once again today. So I can testify that it's a very welcoming community. I absolutely agree I know that I was chatting with someone yesterday about the adopting a plugin tutorial because they haven't contributed yet. And just sharing my own experiences as a new contributor to Jenkins new Jenkins user and completely agree with Bruno the community is probably one of the most welcoming I've ever been a part of. And now that we're I'm getting to properly be a part of it I want to give back and encourage people just the way I have been. Continue keeping it up these channels these connect the chat channels are all connected or are getting connected. Some of them already are but for the most part we're working on getting chat channels connected so that regardless of which one you choose. You'll be able to see the messages between them. And we do have a page for this specifically. So right now, the Jenkins infra and Jenkins release channels are connected no matter what chat client use whether it's matrix whether it's Gitter, whether it's elements, whether it's IRC, they're able to share messages and threads so that you don't miss anything. And we are Gavin Morgan who is one of the government's board members is working on getting the other channels connected as well so that eventually we'll have seamless transition from one to the other without having to, you know, play favorites or picking choose. So, when that does happen will be able to provide more info and we do have some just added a little blurb recently for the chat, explaining that so. If there's anything anyone has any questions about or for anything that doesn't make sense or isn't clear here please again. These channels are where you can find out and ask Gitter specifically the newcomer contributions one has been really helpful for me. We also have a docs Gitter. So, I'm actually not sure why that one's not listed here but we do have Jenkins docs Gitter as well so specifically for the documentation questions. Oh, and we have a Hacktoberfest channel as well that's not listed here but I'm pretty certain is listed. Yeah, join our Gitter channel. So, everyone can join in here this is open. And yeah we've got a lot of conversations going on here we've got a lot of work people. Mark, myself, John Mark in here helping out. A lot of season Jenkins users that we work with regularly are in here answering questions for the newcomers for people that are working with Hacktoberfest so. Yeah, and you can even see John Marks update a couple days ago. We are over 160 we're over 160 valid Hacktoberfest pull requests from 54 contributors. That's incredible. That's so many. So that's just amazing and again, want to share our thanks for everyone who's put in work thus far and submitted a pull request. No matter how small or large that pull request might be they're all valid they're all important. Everything helps. So, all that being said, if anyone has any questions or suggestions or ideas regarding the Hacktoberfest documentation. Please feel free to share. Otherwise, it's okay. We don't have to discuss further if we're going to talk about for the issue. So, all that being said, it does look like we've managed to get through our agenda for the day. One quick note so the monthly Jenkins newsletter is not a newsletter that's sent out via email it's just a blog post right now. Alyssa is currently on PTO so we may not have a tweet or post for it right away but I will work with the rest of the community team to get that figured out see if we can potentially push that out there today or tomorrow so that it's visible. Thank you. Yeah, of course. Any other questions thoughts comments concerns before I stop the recording is what were you expecting from that office hours. Did you have any specific question about documentation or something you're working on for October fest or anything else. Are you asking me for. No, I was asking to leave. Oh, but I don't know she can hear me. I'm sorry. Could you repeat that. Yeah, sorry. I'm wondering what you were expecting from that meeting did you have specific questions on the documentation. Do you need help with one of October fest issue you are assigned to or anything else regarding documentation. Yeah, we help you in any way. I have not been assigned to anything. I am not familiar with, with, with this at all. I. Yeah, I guess I thought there was going to be more. I must have missed the meeting where it was explained how you get assignments and how you choose it by yourself. In fact, you, you're not assigned. You propose something, make a pull request and then assign was not the right term sorry about that. So, I think I can actually show in this case Bruno if you don't mind. So, of course. So Liz here. So this is the October fest event page from Jenkins. This is where we have all our information on the projects that we're working with. So here in the issue queries section. We have these Jenkins Jira issues suggested for October fast get hub issues suggested for October fast newbie friendly issues and Jenkins and dashboard. Good first issues and get hub these are the places that you want to look to. So for instance, I'll open up the Jenkins Jira issues. These are the Jenkins Jira issues specifically. These may not be documentation related they may be more coding and an actual scripting tasks. However, in the GitHub issues suggested for October fast. This is where a lot of the writing and documentation is going to happen. So, for anything that you'd want to contribute in that regard, either the good first issues on GitHub link or GitHub is issues suggested for October fast links are going to probably be the best case for contributing in this in this instance. The only thing that I want to make sure is clear on the October the GitHub issues suggested after October fast. This does not make it a good first time user issue. For, for instance, the rewrite review intro to blue ocean to reflect new status is a October fast option. But after talking with Mark, he was saying that this isn't even something you'd want me to work on right now, just because it requires a lot of customer insight. So the good first issue. So the good first issues is definitely where you want to look for. And then anything that's labeled documentation is up for grabs, even if it looks like someone might have, you know, made a comment on it like there's a few people that have commented on it. You know, if they haven't actually submitted a pull request, then there's not really work being done. You can assign yourself in any of these cases as well. Just going up here and adding yourself in here. But, yeah, for the for the actual October fast issues. It's really open. The key is that any contributions are really welcome. So, it doesn't have to be anything super intensive Jenkins knowledge wise it doesn't have to be anything intensive. It can be something is simply just reformatting some of the text. A lot of the text that we or the lot of the pages that we did have or do have. So we're coming from markdown. So some of the formatting might still be there in some cases of older documentation, cleaning that up would be a great option, for instance. The only, the only thing with that is it's not necessarily listed out which pages are still like that so it would be a little bit of digging and discovery before actually getting to work on that. That being said, like there's like there's a ton of stuff like there's only eight options here but that's not saying you can't come up with anything else if you if you like, check these out maybe you notice something is not necessarily a right a good fit for you but that's close to something that you'd want to work on or do. By all means, check it out. If you, you can always. We have our contributing guide, and it shows you how to explains how to fork clone repository submit pull requests, a lot of the good basics that we do here for the Jenkins project. So, he also has the links for the good first diffuse. It's got the mailing list regular meetings get our chat so and some standards for different processes with Jenkins specifically. But it's but like I said it's got this, creating a fork using GitHub data files using a global phone information, which is super helpful and just getting started. You're free to do anything that you feel is a fit. If you have questions about whether or not something would be a good, like place to do something. You can ask anyone of us will all have similar feelings towards it I'm sure is just because we're all working in Jenkins at the same. In, you know, not the same way but similar capacities. So, every, we have the October FET slack channel we have the community slack channels as well. The getter channels really are one of the best places to talk with other people about Jenkins and documentation just because it's going to be skill sets from the newest user to the to governments board members that know exactly what they're doing. So, this is that help clarify a little bit more about the plan for October fast. Yes, yes, thank you. Of course, and I'm going to actually link this page in the agenda since this is such crucial part of October fast. And there are all already lots of issues created for documentation but if you ever find something is that you think could be ameliorated which is not described in any issue yet. That doesn't prevent you from submitting a PR about that even if that does not exist yet you know in the issues you can create one of your own just proposing an evaluation of the documentation in Jenkins I or in the plugins or whatever. Okay, yeah. And one other thing too is I it's not necessarily listed out here. In the same way but for the plugins. There are a handful of plugins that Mark Bruno, Jean Mark, some folks that are committed to helping with October fast are actively watching and keeping an eye out for these for reviews are for pull requests. The reason being is we still need to migrate some documentation from the wiki to the plugins page. This is, it's not as involved a process as other doc migration might be this is a little bit more step by step procedural kind of moving and adjusting. But it's, it's an excellent way to just kind of do some work in the plugins or the documentation without having to completely rewrite or completely create documentation for something. As you're just moving everything over from one place to another, maybe updating some formatting again they might have been a markdown. But the idea is that we have some repositories that are specifically owned by people that are active that we are aware of maintaining it and are able to submit or review the pull request accompanies so that if you need any more information about that we actually have a list. I would there's a couple spreadsheets that we can that I can share that have the plugins that are being maintained by Bruno mark and john mark. There is a list of all the plugins that need to have that migration happen that we can share. And there's a couple other things that I can also send over so we have a ton of resources. We can also come through and decide what's actually useful of course but if we can help you get to that point here, then all the better for everyone else. I just put in the chat link to the shit. Oh, perfect. The plugins. Yeah. Just in case. Yep. I know I have access I don't know why it's not giving me access right now stuff. I'll get to that later. But yeah, these are all really great, great, great for questions about October fest because yeah it is kind of nebulous in that sense of do I get assigned something do I have to pick something out like what's the deal. And if you, if you missed like any of the kickoff meetings or any of the previous October fast stuff it might be hard to just figure that out on, like, without someone telling you. So, thank you for asking all those questions, I think it's been a great opportunity to just kind of explore that page and get some more clarity about October fast in general. You know, these are all recorded meetings so that could help any number of people going forward as well so great resource have. And thank you. Any other questions or ideas on October fast that you want to share Liz or are you good for right now. No, I'm good. Thank you I will take a deep dive into these links and I'll ask the community if I have a question. Yeah, definitely and if you if you want to ask me directly Ken to Bruno. It's a little late for him right now so maybe tomorrow but but yeah no we're all here we're all happy to help. And I think that's one of the best parts of working in this open source project is that it's entirely community driven we're all here to help each other and get the same results so we all want you to be the best it can be. No questions asked. Yeah, you're in the right place. Okay, great. Thanks. And then Bruno, do you have any last thoughts or anything you'd like to share today as well. Yeah, thank you. Cool. All right, then. So then I'm going to go ahead and stop the video recording. It might not be available as quickly as usual because I don't have access to the YouTube account to upload them right now. So, I'm going to have to check in with airbay or john mark or Damon, I'm going to have to check in with some folks about getting some help with uploading these. So, as soon as that is, it will be available online and the YouTube just like all the other ones are though.