 now. Okay, thanks. Welcome to Docs Office Hours for Jenkins. This is the European edition for Thursday, May 26th. Today's agenda, we have some action items that Mark wants to go over the doc mailing list archival and switching to the community.Jenkins.io for Docs Sig. We have our Google Summer of Code update regarding pipeline step stock generator and the harness here, so we can talk more about that. Localization and internalization progress for it. Alex, if he joins, we can definitely talk about that. Right now, since he's not here, Mark will be the stand-in for us. The June LTS change log upgrade guide and blog post is something that I'm working on, and we'll be able to speak to. And we have the Require Java 11 Epic as well in addition to the June LTS. So, I'm working on the documentation there as well. And finally, we have some recap info, and since we're getting toward the end of our She-Code Africa partnership, Mark's going to have an update for us there. So, first off, Mark, did you want to go over the topic here, the archiving of the Docs mailing list? Yeah, just to remind me that I've got to do it. We've got agreement and consensus that the Docs mailing list is too low usage to justify keeping it, and Google Groups is just not evolving. Whereas community.jankins.io and the Discord server that hosts it evolves very nicely has a great user interface, much easier moderation tools. It's just better for us. So, we'll follow the model that some other communities have done of switching from a Google Groups-based mailing list to using a Discord site. In our case, community.jankins.io. Wonderful. Makes a lot of sense. And as far as the Google Summer of Code, Mark, would you want to share anything about that or perhaps? Actually, I think that's where we let welcome Veehan. So, Veehan, tell us something about yourself and give us an introduction to the project. Hello, everyone. This is Veehan and I'm from Pune, Maharashtra, India. And I've been selected as a GSoc contributor for the pipeline step documentation generator improvements. And under this project, I aim to improve the pipeline steps that are generated on the jengins.io website. And specifically, there were a couple of things that were in my mind right now. So, the first thing was improving the layout of the page. So, as you can see, the page has a lot of information that is not abstracted or abstracted in the least way possible for the user. And this creates, this actually crowds the page a lot. And if a user wishes to find a piece of information that they want, it becomes eventually harder for them. So, the first improvement I thought of was to go ahead and create a navigation bar, a sidebar sort of structure. And I've included that in my proposal as well. So, first of all, the number that we have on our documentation currently, even for that, if you see if you scroll down, so if you have a longer page and you scroll down, that number sticks to the page and it eventually disappears when you scroll further down. So, first thing, a general improvement on the entire documentation side would be to create a sidebar that is static on the page, which does not move. So, usually able to navigate easily. Then what we can do is for pipeline steps specific documentation, I plan to create a separate sidebar, which would be stacked under the main sidebar, much like the Java documentation if you would have seen that. So, the Oracle documentation from Java, you have those classes and then you have those objects different. So, you have, for example, AWT and then you have all the classes for that. So, something like that for the steps as well. So, for every plugin, we would have a section for them and when the user clicks that in the navbar, it expands and shows them all the steps associated with that section and when the user clicks on that, they will be led on to that page and that page, again, would be consisting of a sidebar that has all the parameters of the steps. So, for example, if we take a step as checkout step, so for that, we had different parameters. So, those parameters would be listed down and eventually what will happen is a piece of information that was present on a single page for a user, it will be divided and the way I plan to do it would be either configuration based. So, we know exactly what steps need to have a separate page of their own. So, what parameters need to redirect to a different page. So, that can be configured either manually or we can do it automatically by considering a fixed threshold value of the length of the documentation for those parameters. So, these were the two basic things that I had in my mind right now and yeah, I'm in a phase of actually learning how the documentation generated. I'm trying to get some pull requests on Jenkins.io as well as the pipeline step doc repository to get a look around the code. So, yeah, thank you. Wonderful. That all sounds really amazing. I'm excited to see what happens and what you're able to get done with that. And just as a piece of info, Kristin and Mark, who is the other mentor for the Google Summer Code? I'll actually have to look it up. I don't recall but the mentors may back to your point, Kevin, continue. Yeah. I was just going to share that the mentors for the Google Summer Code project are more often in the Asian hours for the Docs Office hours. So, if you want to collaborate with them, it might be easier to connect with them at that point in time. It's totally up to you. You don't have to go to that meeting but they are typically there as far as just being able to meet them, talk to them and get some more info from them. So, and if you don't have the link to that, we can share that. And it's also on the Jenkins events calendar. So, you should have that if you have access to get her and everything else. Yeah, sure. So, we actually discussed probably meet time for us. And as of now, Kristin has not reverted to that meet but we would probably find Thursday's office hour to be most suitable because Friday's is slightly early for me. It's like 7.30 in the morning. So, this is perhaps a time that is fine for me. And the other two mentors are Tasneem Koshir and Harshad Chopra. And they both are also from India. So, I guess it actually depends on them. So, we'll probably discuss and find out a suitable time for the meeting. And Vihan, one of the don't be shy at proposing an alternate time for Asia office hours. If it turns out that Harshad and Kristin could have a better chance of meeting if we were to shift Asia office hours one hour later, we could do it. Two hours later gets a little bit more of a push, but one hour later is quite easy. So, don't be shy about saying, hey, the reason for Thursday's for the Friday Asia docks office hours is so people in Asia can get there. And if that hour of the day doesn't work, let's look for a better time. Now, you have to be mindful that I'm 12 hours away from you. And therefore, choose carefully. If you choose noon India time, you'll have to have to do it without me because midnight is just too late for me. But if you choose nine o'clock in the morning India time, I can probably do that no problem. Yeah, sure. So, we'll have to find a time that does not conflict with the GSoc office hours as well. So, right. Well, and that was why that was why the docks office hours, the Asia docks office hours were set where they were as they are exactly after the old Asia office hours. Now, the docks office hours have changed. They are now only happening during Europe time. So, that gives us more flexibility on when we want to do Asia docks office hours. Oh, that's great. Yeah, we can sort of discuss and then we'll let you know. Super. Thank you. Wonderful. Sounds great. Thanks, Vihan. Appreciate it. Mark, thank you. So, Vihan, did you want to, did you have any desire to show us any screenshots of ideas that you've already prepared? It sounded like you've done quite a bit of good research. Do you have anything you want to show us? Because it's kind of fun sometimes in these office hours to let a contributor share their screen and show us something. It's okay if you say no as well. So, yeah, current firm proposal, I only, I had designs which were not implemented in the website. So, currently, I've not prepared it on the Jenkins and IO website as it is, but I plan to do that very shortly because the problem with that is I'll have to understand we have to create a different nav bar, right? So, because we'll have to use something that is not in the bootstrap which is used in Jenkins.io because bootstrap has a very fixed nav bar layout. So, even in the recent pull requests if you would have seen, I've changed like the bootstrap nav bar, the default behavior changes slightly to suit our needs. So, I have to add, that's the issue with current. No problem. Great. Thank you. Thank you for what you're doing, looking forward to it. Yeah, very exciting. Thank you very much. Yeah, and I just had perhaps one doubt regarding that nav bar itself. So, it was like if we create a nav bar that stays stationary on the page, that would create an issue in the mobile view. So, that was something that I clearly overlooked by writing a proposal. So, I forgot about the mobile view. So, I wanted to get some ideas from the community of how we can manage that kind of a nav bar in a mobile kind of view. And unfortunately, I am the worst of all possible people to ask for guidance on JavaScript and page layout. I rely on page layouts people to do something smart and I just write HTML or even better ASCII doc or markdown. But if you were to ask the question, for instance, this might be a good excuse to open a question on community.jenkins.io and say, hey, let's talk about maybe what you do is open the topic as jenkins.io navigation bar. And that would inspire Gavin Mogan, who maintains the plug-ins, plug-ins.jenkins.io, that uses the same nav bar to give his inputs. And Gavin has very good insights into how to do that well. So, if you're willing, just open the question on community.jenkins.io. Yeah, that's great. I'll do that. Thank you. Well, the benefit there is it also helps us centralize longer-term discussions like that on community.jenkins.io, where we can remember the context of the conversation and and collect ideas. It also inspires people. Oh, GSOC's starting to talk about things on community.jenkins.io. And Gohan, did you have anything else you want to mention or talk about before we move on to the next subject? Or where are you at? I guess that was a film I said. Thank you. Okay, no worries. Thanks so much. And Mark, do you want to go ahead and discuss the localization and internalization? Oh, I was right the first time in internationalization with Crowden. Sure, yeah. So, Crowden is now hosting eight or nine plug-ins. We'll be doing a, we'll be presenting an internationalization live stream with Darren Polk that will describe how to internationalize a Jenkins plug-in. Documentation updates are needed, and there is a lot of work to do to do internationalization because it requires code changes. And so this is a good opportunity for us to look forward to Hacktoberfest or to other contributing events. So DevOpsworld, contribute contribution sequences, workshops, those kind of things. And in those places, we'll try to encourage people to help us internationalize plug-ins and Jenkins core. That's it for me, Kevin. Awesome. That's, that all sounds really great, Mark. I'm excited to see what happens there. Next up, we have the June LTS change log upgrade guide and blog post, which I'm actually working on. And I've been partnering up with the community developers, Basil Crow, others to get a better idea of what they're looking for in the blog post, and just as far as what we need to do for the end user in this case. There are going to be some changes since the LTS will be getting released in a few weeks. There will be some changes that need to happen to the documentation and some updates in regards to the requirements and baseline, not baseline, but the Java version that is being used, among other things. Further backwards are expected due to the amount of change that's going to be happening. And one of the bigger changes that's going to be noted in a blog post that I'm going to be writing is that the GIF and PNG images in Jenkins Core have been updated to SVG images. And the idea is that it's going to create a better user experience. The images will be higher quality, more clear, and will just overall lead to a better view of Jenkins in that regard. There are some hangups with the plugins that we'll need to address, but they'll have to be addressed by the maintainers. So I'm keeping all that in mind when creating the blog post and making sure that everything is very clear and descriptive enough that we should be able to get everything taken care of. The LTS may appear differently from the weekly to some degree due to the release cycle, but all the information should still be 100% correct and accurate and valid. And then we also are looking towards the future and the requiring Java 11 epic that we have. So the package documentation and user documentation will need to be updated, which are the two tasks that I'm currently working on as well. I've again checked in with Basil, checked in with Mark, and collaborated with the community team to get a sense of what needs to be updated and what we need to be able to look out for. And thankfully, everything's been very, very collaborative, symbiotic, just clear, concise, however you want to put it, that I know what to do and take care of and who to ask if there are any questions along the way. My goal is to have a lot of that taken care of by the end of next week, beginning of the week, the next week, but it'll come in time. And also working on screenshot updates for Jenkins itself. So I'm working on that to get the screenshots updated and be reflective of what Jenkins is now as opposed to what it was previously. That just means making sure that everything looks correct and updated, making sure that icons are represented properly, and ensuring that the descriptions of these images are also accurate, making sure that there's no excess or unwanted information tied to them. And the idea is to have that finished by the June LTS, which is going to be June 16th, so that everything is looking nice and pretty and right for the release. I think that's all from me on that stuff, Mark. Do you have anything to add or want to bring up as well? No, that's great. Thanks, Kevin. Yeah, great. Then if you want to go ahead and talk about and share about the Chocot After and Tributon, and I know it's wrapping up shortly or soon. So yeah, so I'll be creating a blog post and a brief video to highlight the accomplishments, highlight the results. Screenshot updates is really timely because of the June LTS that will change the UI in significant ways. Inclusive naming, we made good progress and identified a number of places where we still need to do more checks to see have we removed as much of the inclusive naming issues as many of the inclusive naming issues as we can. And then Pipeline Help, we got three or four good poll requests there on a relatively complicated topic. That's it for me. Okay, yeah. And so do by end of this week. Oh, there is a, I take it back. There is one more thing. On Saturday, Saturday will be the, is the final wrap up meet, is the conclusion meeting of the project of Shekot Africa Contributon 2022. Exciting. I love that I've been able to join and be a mentor in all of this. I've learned a lot and I've really enjoyed collaborating and working with the women in the project. They've just been fantastic and have done so much good work and everything. So just a special shout out to them. Thank you. Of course. Great. Well, that covers our agenda for today. Thus far, Mark, Vahan, did you have anything else that you wanted to bring up? Talk about mentioned here in the office hours? Nothing from me. Okay. Yep. I guess that's it from my side as well. Thank you. Thank you so much. Appreciate it. Great. So in that case, we'll stop and record it.