 Welcome, everyone. It's the 17th of June. This is the Jenkins documentation office hours. And reminder we abide by the Jenkins code of conduct. All right, so here's what I've got as proposed topics for today. So one is pull request review. That was if if Zenab had attended today. I've submitted a review and no feedback from Cynthia yet. The other was contributor summit pre preparation and dirage I wanted to talk with you specifically about this one because I just got one more volunteer for our session on next at next week's contributor summit so this was what I was hoping to make a primary focus today. Are there other topics that anyone else needs to add. Nothing from my side. Okay, all right, so. And there's I guess as a let's see as a matter of, there's no docs track at the contributor summit I will give a mark will give a status report. But we're not going to do a dedicated track for it because we've got other things we want to do with the time. We're not going to attempt to change the roadmap at this point the road maps already the biggest challenge for us with the documentation roadmap is making progress on it, not having a roadmap. Right. All right, so I'm going to shift this pull request thing then to the bottom and we can talk to it later if we'd like. We're going to do some preparation so dirage. I am pleased to note that I had a conversation earlier today with Aditya Srivastava. He says he's one of your classmates at the university there. And he's also agreed to assist with the newcomer with the newcomer new contributor track. He's currently outlined I think as a 40 minute track dedicated to helping people contribute to Jenkins. Now, I've got a new piece of information. We now have over 1200 registrations for the contributor summit. Yeah, even even if 90% of them drop out that's still three or four or five times bigger than the last contributor summit we did so that's even if all we get is 120 attendees, that's still dramatically bigger than we've had before. So, delighted with that the CD con registration process has done great things for us. Now the question is, how, how do we want to approach the new contributors track so what I had proposed in the session earlier today with Aditya was Mark create a slide deck, describing some general general concepts, and then Dheeraj talk about his experience becoming a the changelog main writer. Alright, because there's something to be learned from your experience there and I thought that would be great for you to say, Hey, here's what went well here's what didn't go so well here's what I could have learned better and this is why this worked and this is why this then Aditya has agreed to talk about his experience in infrastructure and advocacy where he's been participating as well. I wish I thought it might also be good if you'd be willing to talk about the react JS opportunities if you're interested. Are you that that may not be I don't know if that's yours, if that's a specific spot of interest for you I know you haven't, haven't actively done any react work yet in the on the plug inside or places like that. Would you like to talk to that, or would you rather not. What will be the eventual aim for this talk from my side. So what I was thinking is if you if you were to highlight highlight several areas of the project that use react. And maybe, for instance, the plug inside. But the problem is you, you would have to get enough experience between now and then to say yeah I'm ready. The other is I could ask, could ask Gavin Morgan to share. I'm just not sure he's going to have time. Are you if and if react is not a passion thing for you if you're just asking for somebody else let's not do it. Well, I have contributed like a small PR to the custom distribution project and all of them were based on react JS. Oh, okay. So I can talk about that. And as you said, the specific focus should be on the plug inside. So I can so we still have some time so I can research more on that like on plug inside where react JS is used. So I can talk about that. And so will Gavin will be able to help me, as you said he's busy so Well, it's even if that's a good point even if all you talked about was your submissions the customer distribution service. That's already a good way of saying, look here is a very specific example, using react JS that I submitted and I didn't do any Java. I didn't do any, any, anything other than this was a react JS project. I can do that. And if, if others are if other things are are available. Great. That's optional. Just having the problem for me is I cannot. I cannot reasonably talk about react JS contributions because I am. I don't contribute react, whereas you do I can talk about Java and I can talk about documentation and I'm actually credible in those two areas. But I am utterly not credible when it comes to react. So it would be great if you're willing to share. Hey, look, here's what it was like for me doing this. It's, it's not hard. You just do these things. I would love to do that. Definitely. Great. All right, we will put you on that list then. Excellent. Okay. So you, you should plan you'll probably have between five and 10 minutes between those two things total. So I'll, I'll send the slide deck. You can put your slide what you would like to say as guidance into it. And then we'll just have you share. So, can I also get the information about what particular time that I have on. So what I'll do is I'll mark place insert placeholders in the slide deck and assume. What should we assume we got a total of about, I think we've got a total of 40 minutes maybe let's outline the agenda here so So in the 40 minutes what I'd say is let's do. Maybe we say 10 minutes of of general and opening of opening in general. Contribution. So, Java and docs. And then give you five minutes on weekly changelog. Additia five up to five minutes on infrastructure and then Would you willing to take five minutes on react or would you rather have more than that. I understand there's a lot of things that we need to have in this small time so I am good with five. Okay, great. All right. And then I would think we want question and answer. For probably 10 to 15 minutes. So that if people have specific questions they can ask them and we can help with them. And I think that takes the whole time. Yeah, so that would be the 40 minutes. I like that I like a lot having different voices, especially not my voice so that's great. Thank you very much for being willing. Now Kristen, I would be happy to include you in this if you would like. I think I don't really have much to say. Again, I've been trying to like focus on G stock for this like period of my open source life. But, and I would like to get back into this maybe in the fall. I do have some general like ideas of what I think could be maybe help get people to contribute or to encourage contribution. But yeah, I just, well, I helped with the last one and there really weren't too many people that came to our breakout session. So I can also help if we're, if we'll have a breakout session to documentation, but I don't really have much. I have unfortunately not done as active and actually producing documentation. That's great. You're, you're focused on G soccer deeply appreciated I am so pleased with our results from Google summer of code. When, when Oleg sends a status message and says things look look like they're going well. That is really high praise. Yes, I have to say exactly it's like I want that to go out this summer so I apologize like I'll try to be more active after that period. No, no, no apology necessary that's that's great that is absolutely wonderful. Okay, good. All right, so I will send you all send send the link to the slide deck and dirage you and I will also discuss it I assume at our Tuesday office hours. If I remember correctly you're still available for next Tuesday is that correct. Definitely this. All right, great. Excellent. So we need to discuss on contributor summit any areas of concern dirage for you or things where you're you're worried about this or that. Before this I was concerned about how I'm going to contribute so now I have clear plan about what I need to speak so I'm really happy. Okay, great. Excellent. So this 40 minutes is for given. This 40 minutes is given us for the documentation or just full contributors and I'm not sure. Well so the 40 minutes is for. Let me bring it up the 40 minutes is for the track that's focused on new contributors so here I'm going to bring up. This is the schedule draft. Let's put it in the links draft draft outline. And then the draft schedule. And the schedule is the more detailed thing the schedule is a sheet that Olivia Bernan has been assembling. So, and I don't know if you can see here let's make the text bigger. All right. So, starts at 9am Eastern time, which if I remember correctly is about 630pm or 7pm your time, then we will, we will be on this one right here so this row contributed contributing to Jenkins. So we get 40 minutes, and it will be you and me and Aditya. And we'll lead that session hours will be running concurrent with a plug in end of life policy session that James Nord will be leading. And then we will end and switch to other topics like me I'll probably go into the next session which is outreach program and then the next one I'll attend is Java 11. Can I answer your question. Yes, no it makes sense. Okay, great. So let's put this. Yeah so and we've got we've we've done many of these presentations on how to contribute the for me the distinction of this one is your voice dirage and Aditya's voice, rather than it being my voice and I'll use I'll bring in some of the old materials some of the previous materials I've used so that that'll be basis but really the I think the most interesting is hearing from brand new contributors saying yeah this is what it took for me to become a contributor. Aditya is working a Google summer of code project. Here you are working documentation and helping with react work on on the distribution service so I think those are really interesting. I think that will encourage other students or other newcomers to contribute as well. Good. Very good. Okay. All right, then, then that's that's what I had. And I see the only other topic I had for today was the pull requests that are pending for the Jenkins documentation site. And here if we look at those. There was this one right here from Cynthia. One of our she called Africa contributors. And I've given feedback, and I don't think she's seen it yet so so nothing really to do there. Others. Oh, this one is a major one that why our pseudo car had done that I've done initial reviews but it needs reviews from other people. Right. Okay, good. I saw that Tim was on the as a reviewer and it's like I really think that Tim would be one of the best reviewers to comment on this absolutely well and and I'm as I'm watching in the plugin installation manager Gitter channel. I'm realizing that there are probably more use cases that should be flagged in this to be described in this then are currently described so so it's such a broad thing and plugin installation manager tool is so capable of so many things that that this document is even more important than I initially thought it would be. So yeah, crucial. Yeah, it's like, can we start with something small and then if we find some cases, where should we flag those like it should be open a I want to be able to record them. Where should we open something so we don't lose them like is it going to be a something in the plugin instant installation manager tool like backlog or is there a way we should put an issue in Jenkins IO in terms of the page. I'm not entirely sure we're documenting documenting it here. I would create an issue, an issue in the Jenkins that I oh site for the documentation of that. Okay, but now that you there isn't a page yet to even associate it with because this hasn't been merged so for now it could just be in the poll request. I kind of put it as another comment but yeah I didn't want it to turn into a you know the pull request that can never close because we just keep finding more. Right, right and that's, and that's a valid point and I think, I think we want to get this thing over the line, right and add to it. Absolutely. So let me let me put a note on that one. So, here's PR for plugin installation manager for Cynthia was this one. And this one actually has an interesting side side challenge that maybe it's worth exploring with you Kristen. What Cynthia's PR does is it takes a very we have an issue reported here. You can direct this page from the wiki page to the dock site. And those are good things to do because it's removing content from the wiki. So that's that's a big plus. This is a tiny piece of a bigger picture story this one is just a little bit of warning about don't try to start agent jar without arguments. It doesn't, it doesn't be okay you think it would. The bigger picture is this page on using agents is has very little in it it only does Docker, it has nothing about static agents, nothing about EC to agents or Azure agents or, or Kubernetes agents or open shift agents. And so it agents is this great big open space and what what her change is going to do is it's going to add one more section to the end of this thing that's a very specific thing and, but it's not, we've got a whole lot of more work to do on this page. Okay, my thought was okay one step at a time we'll do one little thing and then do the next thing. Right. Okay. If it's if it's taking if she's not able to come back to it, maybe in a couple weeks is it possible for one of us to just cut, can we commit to the PR. Oh yes, absolutely yeah. In fact, I described that to her in the PR I said, I gave her my apologies it was two weeks that it sat without me reviewing it. I got to reviewed it. I said, hey, so sorry. But if it takes you more than a few days, I can I certainly have the permissions to go in and make the few changes that are needed. Okay, right yeah because I sometimes you know you go, I think she's a student you know go back to school and maybe time flies right like next thing you know it's been a month, and you're just in class and it's just a lot. Exactly. Well, well and it's what she's done is helpful, and therefore we don't want to just let it sit. If, if in a week or so it hasn't been merged I'll probably just make or hasn't been modified. I'll make the changes and then merge it. And that way we can close the issue because it gets an issue off our backlog. Sure. Okay, good for. And, and Deraj one of the, one of the topics in our talk in this general section that I'll do is docs migration from wiki to www.jankens.io, and another is docs migration from, let's call it this way, plug in docs migration to into plug in repositories. And those two topics, those two topics alone we've we've done one hour webinars on each of those. So, there's plenty of plenty of work to do in both those areas. Yes, there are lots of issues on this one. Right, exactly. So, I think we talked about pull requests, we could do a further look, I'm not aware of any, any large open oops, here we go, let's find. Yeah, so there are some relatively quick ones to review and yes here's one that's coming that dirage you should be aware of. There will be a weekly release of Jenkins in at some time in the future that will declare boldly that certain plugins are no longer supported. And this non Java plug not plugins that are not written in Java. And we have several that are written in Ruby, and one or two that are written in Python, and the Ruby runtime has been problematic at all sorts of levels. And so we are finally admitting that we're going to stop at some time in the future supporting Ruby plugins based on the Ruby runtime. And I suppose you mean that there will be no bug fixes and feature enhancements, right? No, meaning they will just stop working. It's this is even more dramatic that there's, we are the liability of carrying forward this thing is so great. For example, it doesn't run correctly on Java 11. And we're confident it will never run correctly on Java 17. So it's just not, it's not a, it's not a viable thing for us to bring it forward. And since it's not viable to bring it forward, it's just time to admit, we're not going to, to attempt to maintain this thing anymore. So, people are using some Ruby based plugin so how are they going to deal with this? They will have to look for alternatives. And thankfully, most of the, almost all the plugins have a very tiny installation count and a very small installation count, or are so old that they've long ago been replaced. So for instance, this one last released five years ago, and there are several much better choices than than that. This one, likewise cucumber. This one likewise. So each of these. And it isn't until we get to really tiny installation numbers way down like here, if I remember right, where this one may not have a replacement, but it's so old and so untouched that we think there are very few harmed. Right. Okay. Yeah, so, and now the, the when that happens hasn't been finalized yet but just be aware that there will be a weekly changelog coming your way that says hey we dropped this. And there will be a blog post to go with it. Right. And, as you said, there's going to be some sessions on migrating the key docs to Jenkins.io. So on that, as you said there's going to be some prizes for top five contributors so is it still there? So say that again there's going to be. Yes, so there's going to be any kind of competition like top five contributors to get some swag or something like that. Oh, right. So is that what you're asking about is will there be, will there be. Yes, so that's a good question and, and I've still got an open question that I have to answer with the organizers. Open question. And how much swag we can send and how we choose recipients. So for example one of the one of the ideas was we may just be able to send swag to those who present, or we may present send swag only to the first 50 who join or something like that, but that's the continuous delivery foundation that we observe they cannot afford to send a t-shirt to 1200 people. Now that's that's just more budget than they've got to spend. Yeah, so, right. Mark to find answers to the swag questions soon. Yeah, anything else on contributor summit. Yes, so the video. So the presentation is going to be live or I'll be recording a five minute and sending it to you. I had planned to do it live. Are you okay doing it live. Definitely. Okay, great. All right. It's going to be dramatically easier for you or if you say hey I'll be sleeping at that time, we could record it but for me making it live allows you to show and then allows people who are absurd who are watching to ask questions and interact with us. Okay, so there's going to be some questions. Afterward just so at the end of the 40 minutes I hope to spend at least 10 minutes doing questions and answers. Okay, that's great. Okay. Oh, and I should say it live percent, it will be a live presentation but I believe we would also intend to record it for later sharing so don't don't show something secret or confidential on the screen it will be remembered. Sure. Okay. Anything else we need to discuss today. In coming Tuesday, there's going to be definitely a week. So I was trying to, I'm trying to ask you when is going to be the next. Practice for me. So the, so this coming to this coming Tuesday next Tuesday will be another weekly so that's that we'll plan to do that as a change log. And we will in next Tuesday session if time allows, we'll go through and I'll do the LTS change log so that you can watch and ask questions so I'll do the 289.2 change log during next week session. Did that answer your question or did I ask answer the wrong question. Yes, you answered it correctly so just to cross it, the LTS log that you're going to do. It's going to be done next Tuesday or Thursday. Next, so I'll, I'll create the first draft of the LTS change log next Tuesday in our office hours. This session next Thursday will be canceled, because it will collide with the continuous delivery conference with CD con. Got it. It's a good, good reminder. No meeting next week. Next week. CD con is next. That's called this way. No meeting next Thursday, or what day of the week is it for you right now is it Friday, your eyes are Thursday. It's Friday. Yes. Okay, so next Thursday slash. I have to have to remember where we are in time zones. So you've already reached Friday your day. Okay. Yes. All right. Any other topics. Nothing from myself. Okay. Then let's, let's call this a done session. Thanks very much. And talk to you again on Tuesday, dear. I'll send you a link to slides before then and we can collaborate through the slides as well. Sure. Looking forward to it. Thanks very, very much. Thank you. Bye everybody.