 And we'll get started. All right. Welcome, everyone, to the Jenkins Docs Office Hours, the European edition. This is today is the 20th of October, 2022. Today it looks like myself and Bruno are here for attendees. But if people come and filter in, we'll be sure to add them in. Small agenda today, we had some action items. DevOps World 2022 update. The next LTS that will be coming out in a few weeks. We have our weekly release on Monday or Tuesday. Yesterday, we had a plug-in security release as well. And then just dedicating some time to Hectover Fest since it's in full swing. And we've got tons of work coming in. So very exciting. And yeah, Bruno, do you have anything else you'd want to add to the agenda today? I'm afraid I don't have anything else. Thanks for asking. Yeah, of course. And yeah, it's OK. No one has to have anything, I promise. Anyway, so action items. I know that there's one for Mark that he hasn't been able to action on since he's not here. We're just going to skip that one for now. He'll be able to address it when he comes back. In the meantime, we've had the Google Summer of Code project has finished up. And thank you again to all of the participants. We've gotten a lot of amazing work and just innovation done in such a short time. We also had a couple of the participants, Dheeraj and Vihan, were able to submit blog posts about their experience and what they were able to do. So kudos and thank you again to them for being able to share that with the community as well. Another thing that just got published last week was the new Jenkins Monthly Newsletter. Ideally, we're going to have it coming out at the beginning of the next month to just do a quick retrospective on all the things that we were able to accomplish in the previous month. So that includes all the different SAGE officers. That includes events that anything that might apply to Jenkins. That's going to be an update on there, which is great. And hopefully we'll have tons. Well, I know we're going to have tons of Hacktoberfest news to share on the next edition. So it'll just be a matter of what else in addition to that. Yeah, that's what I'm sorry for interrupting. But if you who are watching the video wonder, hey, I haven't received the newsletter in my mailbox. That's perfectly normal. It's a newsletter that won't be sent by email. It will just be a blog post on Jenkins.io. That's why. Yes, this is actually a great point, Bruno. The newsletter is not a newsletter in a literal sense in this case, but it is something that we're going to be posting to the Jenkins community blog. So it's always available here. And we will be tweeting and sending out other notifications throughout our social channels. It's just a matter of making sure everyone's here to do that. So keep your eyes posted. There will be further additions. And yeah, if there's any ideas or suggestions that anyone might have or want to know more, please, by all means, share that with us. The community discourse is always open. And anything that we can do to make this more informative or make it a better resource for folks, that's the idea. Cool. Anything else on that one? Bruno, I just want to make sure I don't get it. Yeah, yours. And then the next action item is I have created a blog post announcing the new Jenkins Governance Board elections. When that is published, everything will be opening. So voter registration and candidate nomination periods will be open from today until November 10th and 17th, respectively. But once that's posted, I'll make sure to update the agenda here with the link to it. And again, that is something that we'll be discussing and sharing out on our social channels. The community discourse and any meeting that we have for the Jenkins community will undoubtedly bring it up at some point, I'm sure. Big thank you to Damien de Porto for partnering up and helping oversee the elections this year. Wouldn't have been able to create this without him. So big, big thanks to all the work that's gone into this. This is not a trap, Kevin. I just wanted to know if we could talk about the rules for being elected or being able to vote for someone. Do we have any prerequisites for that? Yes, absolutely. So what we have is you have to have made a contribution to Jenkins in some way, shape, or form by September 1st this year. Now, the nice thing is there are several different ways to contribute to Jenkins. It doesn't have to be a pull request updating something. It could be helping someone in the community. It could be translations for different languages. It can be any sort of review for existing pull requests. There are several different ways to contribute and participate with Jenkins. Since there are so many ways and since within those ways there are even more ways to actually participate, we don't have a way to accurately measure each contribution. So on our system, we're trusting everyone that signs up and registers to vote does have at least one. But there is no concrete hard and fast rule to say you need to have X, Y, or Z to show off or showcase before you can register to vote. I see. But if you made it, you know it. Yeah, exactly. I mean, the idea is that the users who want to participate in the election have some vested interest in the Jenkins as a project, the community, et cetera. So obviously we're open to anyone. Anyone can be involved. But we just ask that there is an account with the Jenkins community and that you have at least tried to contribute. Again, any help is wonderful and accepted. It doesn't have to necessarily fix everything but the fact that you care enough to help Jenkins users and the Jenkins community is everything that we need. Got it. Thank you, Kevin. Hello and welcome, Pam. And speaking of people contributing to Jenkins, Pam made tons of work last week in regards to October phase that we'll address later on in the meeting. So welcome. Hello and congrats. All right, thanks. Thanks. I was with the help from Mark. I will tell you that. He kind of held my hand on the first year and then he went on vacation. So I tried to do a couple on my own. So. And now you know how I've been feeling. Yeah, I think a few other people. Mark is very, very helpful, I will say. Yes, Mark is very helpful indeed, especially when it comes to getting started with these things. It's a game changer. But yes. Well, I digress. So contributions are always welcome. The blog posts will have more information about contributions, how to contribute, what you can do to contribute. And it does explain a little bit further that because there's no way to measure these accurately against each other, that we're just excited for all the assistance. So great question, Bruno. Thank you for bringing that up. And yeah, like I said, there will be a lot more information available once the blog post is published. It has all the deadlines for the different phases of the election. It has some great info about the election process itself and what we use for that process. And it just sets up expectations for what's going to happen before, during, and after the election itself. So yeah, that'll be available in the Jenkins blog later today, if not already. Yeah, thanks a lot for writing that blog post really helpful. Of course. Yeah, and it has been vetted by several community members. So I'm not just going over anything. So all right. Next item I have here is DevOps World 2022. So it had been postponed due to Hurricane Ian affecting Florida. And unfortunately, that just didn't happen. However, we have rescheduled. We have persisted and risen from the ashes. And DevOps World 2022 will now be online and held on November 9th this year. So there are different time frames, depending on where you're based in the world. And so this makes it really accessible to everyone as opposed to just having a singular time period that we try to get everyone in. This has just taken to another level. Anyone who had signed up for the initial DevOps World will automatically have access for this. And yeah, so here the EMEA and APAC time frames 12 p.m. to 4.30 p.m. CT. And America's have 12 p.m. to 4.30 p.m. and 9 a.m. to 1.30 p.m. or that's the same time frame. It's just these in the Pacific. So yeah, two time frames. But DevOps World 2022 is going to be online. It's going to have a different format. There will be smaller sessions. Or there will be things broken out a little differently. But a lot of the speakers are still going to be present. And a lot of the same discussions, topics, exhibits, et cetera, will be happening. The contributor summit that we were going to hold just before DevOps World is still being planned and rescheduled. It's going to be in an online format. And what will probably end up happening is it'll be broken up into a few different sessions so that we can go through the process of modernizing, adopting, and contributing to a plug-in. But in a way that is more respectful to the person who's working with us on that. So more details will come from that. And we'll be able to share more, most likely, in November once we have the planning going. Next item on the agenda is we have the November LTS coming up. So that will be 2.361.3. It is set right now for November 2nd release date. And Alex Brandes has been so kind as to be the release lead for it. The change log and upgrade guide have been created and added to the LTS checklist pull request. So that is available for review. I know that I saw Alex already able to comment on it, review it a little bit himself. So any other feedback is appreciated. And I'll make sure to update that link as well so that that's there for everyone. We'll have the upcoming weekly release of 2.375 next week on Tuesday. So the change log in upgrade guide will get reviewed on Monday and make sure that there is nothing inaccurate on there and updated once that's merged. And then just yesterday, we also had a plug-in security release. But this is not a version release. So it is not part of the weekly line, but it is something that happened yesterday. I forget exactly, but I want to say it's 20 or so plug-ins that were affected. But everything was updated and an email was sent out as well. So if you're curious, there should be some sort of notification available. And last thing on the agenda I have today is Hacktoberfest 2022. We're in full swing now. We're in the roughly third week of October. And it's really ramping up. This is incredible. We've got almost 400 pull requests submitted. There's 336 that have been accepted and merged. So that's just an incredibly high percentage. Kudos and thank you to everyone for all of that. And this is time for 90 Distinct contributors with 75 getting accepted and merged PRs, like overall. Documentation, it's obviously a little lower since things are broken up. But this is incredible, incredible work that has been provided to Jenkins from new users, old users, any users. It doesn't matter. Again, all contributions are welcome. So just seeing this makes my heart swell up a little bit like the Grinch, though. It's great having so many people want to get in on it and help to make it better. It's fun. It's really fun, yeah. And I'm getting to connect with a lot of people I haven't before. We're getting to build the community further. And it's become a really great introduction for folks that maybe aren't used to Jenkins whatsoever to take a step in and get familiar with it. I know several of the documentation contributors have not necessarily used Jenkins before and are just getting started. And to have them just dig right in and start submitting updates for different documents or pages is unreal, frankly, for me. So just again, huge, huge, huge, huge, thank you to every one of our Hectoberfest participants. Your efforts are more than appreciated. I can't even figure out what to say for that. So yeah, thanks. The other thing that I wanted to mention here is that we do have a live stream every week for Hectoberfest. Held on Tuesdays. That is hosted by Jean-Marc and Messrin. Darin, Bob. Darin, yeah. Sorry. No, yeah, I was just trying to remember. I thought you were searching for Darin. Of course not. You weren't searching for Darin, but which is a rock star. You're searching for Jean-Marc Messrin, who will become a rock star in a few weeks after Hectoberfest? I mean, he's already a rock star in my eyes for all of this work. But yeah, no, Darin and Jean-Marc are hosting the live stream every Tuesday to go over Hectoberfest, answer questions, just to review and recap all the progress made thus far. It's a great time, a great place. It's on YouTube, so you can always check it out after the fact. I know people are always busy, including myself. So it's there for your benefit. But if you can't make it, you can't make it, we have it uploaded to our YouTube for you. So you can never miss out on the phone. And as the last part of the Hectoberfest topic and what I wanted to dedicate the most time to the meeting is if anyone has questions, concerns, ideas, anything at all about the Hectoberfest work they've been doing, I'm more than happy to have an open forum, discuss, answer anything I can. And worst case scenario, point you in the right direction if I can't answer it. Don't have a really question, but maybe a remark. I think we already got that conversation you and I a few weeks ago. Translating documentation is still documentation, right? OK, so I got a notification from Crowding yesterday, I think, which was telling me that one of the nine plugins which are registered with Crowding needed new translation. So if you never tried Crowding, it's really a nice UI and nice UX, by the way, to translate Jenkins documentation plugins, documentation for Jenkins plugins to internationalize it. And even I do it on a regular basis just for French, because I'm a French speaker, as you may not have guessed by my terrible accent. But if you know any other language than English, please have a look at Crowding, it's pretty simple to get registered and start working with it. I think this should be counted as Octoberfest. But I don't know how, but for Octoberfest, if you write a blog post, if you make a video, if you give a talk at a conference, if you make some translation, this counts as a valid participation. But I don't know how you should declare yourself having made a translation by using Crowding. But yeah, that should work, I guess. Yeah, definitely. Thank you very much, Bruno. I forgot about Crowding for a second, even though we had it on so many editions of the Docs Office Hours. But Crowding is great for the translations, just like Bruno mentioned. It's also somewhat community-sourced in terms of people submit the translations. And you can approve or reject the translations themselves to help make sure that they're correct. So even if you're not doing the translation yourself, if you review a translation, that's still a huge help. And it's, again, just another way to participate and contribute to Jenkins. So the Crowding experience is very nice, though, I will say. From everything I've seen and tried out myself, it's a very simple, clean UI. It allows you to see multiple suggestions for the translations as well. So you don't have to be 100% accurate. You can use those to work from as well. As far as the recognition goes, though, Bruno, I think there's still a question mark on that part because it is going through Crowding and not necessarily submitted as a pull request normally. But I believe that is one of the topics that we have in the Hectoberfest committee, I guess. I know that there's at least one person that's been working on that or looking into that specifically. So they may have more information. I'll make a note to grab that and check out with them for sure. Thank you. And if you are a Plunging maintainer and you have not yet switched to Crowding, the process is pretty easy. So don't hesitate to get in touch with us. If ever we could help you migrate your plugin to Crowding. I will do the French part, I promise. I wish I was more useful in this case. But my French skills, I think, would be offensive at this point, considering how much I forgot. But yeah. Cool. Pam, again, thank you for joining up. Did you have any questions or anything you'd like to share about Hectoberfest or anything at all? No, I mean, I have blocked off my calendar. It was like you said, it was fun. It was fun to get into doing something. And I did learn a lot. So just how the repositories were set up and everything. So I'm very new to Jenkins as a whole. OK, thank you. I don't want you to share a secret if you don't want to. But are you going to get your t-shirt? I think so. Congrats. Yeah, we'll see. I have a couple more. I've been trying to block off at least a couple hours on Friday to be able to participate. So. Nice. That's awesome. Well done. OK, thanks for everything that you put in there. And Bruno touched on a really specific piece of information that I don't know if we talked about. But anyone who participates in Hectoberfest and gets four or more pull requests and merge does get a t-shirt or a tree planted in your name. So you can either be stylish or have some conservation in your life. Either way, I think it's a really good opportunity to participate and at least show off a little bit. Yeah, and even if you don't reach the four plus pull requests accepted and merge, you already have the adrenaline boost. Each time you get one PR merge and people happy clapping and saying, yeah, your code, it's part of Jenkins now. You're famous or not, but you enjoyed it. So let's. That's how it plays out in my head for sure. So I definitely agree there. That little adrenaline rush of getting it merged is fun. It's a little, yeah, it's nice, a little dopamine rush. Great. Cool. That looks like the end of our agenda today. Did anyone have any other topics they'd like to throw on their chair? If not, no worries. Cool. Thanks for the update. Of course. Thank you very much, Pam. Good to be in here and sharing. Thank you as well, Bruno. You're welcome. OK, I'm going to stop the recording now. It'll be ready in 24, 48 hours, maybe a little longer. But we'll get that figured out and uploaded as soon as it's available.