 Welcome to Jenkins documentation office hours, it is the 27th of January. And here are the topics we've got sorry that I hadn't assembled an agenda yet. News and a post to discuss chicote Africa ideas, including ideas opportunities in project management and test design so this is what we wanted to discuss with using up to see if these two ideas could be considered for addition to the chicote Africa project ideas. We talked them through in see the notes from the 24th. For more and will so we'll talk through them here. Are there other topics we'd like to add so is enough are there any topics you want to add. Not for me. Okay. And make any topics that you need to add. I don't think so. I need to talk to you separately but I'm in trouble on scripting. Okay, I'm happy to happy to help with with scripting. Absolutely. Okay, so, Zina, let's let's take on so in terms of news. Jenkins 2.332 is has been selected as the next baseline as the next LTS baseline. There are significant UI changes. And it will need early and extra effort on the upgrade guide and the change law. So that's a that's an activity will probably start maybe even as early as next, next office hours in this group. Okay. Mark create initial draft review with others. Oh, and then I guess I've got one other topic which is the chip for Java eight and of support, and that needs review comments, etc. Okay. And it covers all the all the news that I had. Oh, no way to say one more Jenkins 2.319.3 release candidate is is ready for test. And it needs a change log and upgrade guide. And those are both quite simple. Very little change between dot two and dot three. Any other news items I should add in. Okay, next topic then so Zina I'm behind I haven't yet posted the community Jenkins that IO topic. It will probably be tomorrow or later before I do just because I need to do some thinking organizing and structuring before I put it out there because it needs to describe ideas for various projects but one of the things I discussed on Tuesday in or Monday night late my time Tuesday morning India time was two more ideas for roles or opportunities that might be mentored and might be good for one or more of of the program participants one or more of the mentees. One was project and program management. And there the idea was, I would be the mentor, and we would have somebody shadow me or doing the kinds of things that I do during the mentoring activities to watch over how things are going and are the is everybody making progress etc. It's a little different. It's not really a software task at all. But you had mentioned earlier that you might be interested in things that were not strictly software development tasks. What's what's your, what's your sense of she code Africa's interest in that kind of one on one mentoring opportunity. Maybe think of something. I wish I could participate I would love to be that many. Okay, so, so it's, it would be okay if we propose that. Yes, included in our proposal. Yes, it's very key. All right, good okay so that's great so just have a little bit Elizabeth what to apply. And that, that's the kind of thing where shadow, having somebody shadow me, and basically work as work as do do much of the work that Mark tried to do last year. You know the scheduling meeting is that kind of thing. Yeah, yeah. Okay. But with this specific need to have any kind of technical background to be able to do this. Not well depends what we mean by technical background, able to use able to use Gmail confidently and able to use Google calendar confidently and able to use Google docs, Google docs confidently. Yes, those, those kind of things if we if we call those technical skills ability to spell get. Okay, hey, wait a second, wait a second, everybody can spell get especially English language speakers. Right, but I, but I mean, I would, it's, you don't have to be a hard code coder or something, but you need to be understand the terminology a little bit software lifecycle and all of those things I would say. Yeah. This position. How about tools, do you use things like Julia, or is it just it's home. I know. Jenkins used used to have like a jury board or something where you create issues I don't think still active used to use them. They are and we do and there I would think not that they need the skills but they're willing to be mentored on them. Okay. All right. We come out of this project with more skills and they start right. Yeah, the idea there is, if, if they're not interested in developing those skills they'd be a bad fit. If they're interested in developing the skills they would be just fine as a fit so long as they don't so long as they're willing to develop the skills. Okay, this is really great. I'm really excited to hear this. So, so we'll, I've got to, I've got to assemble still some some some sort of an idea and and we are will begin actively recruiting mentors right now the just like last year the biggest worry is not getting funding for the program it's getting people who are willing to help with the mentoring exercises. Okay, good. The next idea was automated test design. And I'd say it's design and implementation actually so. So what we've got is there are many, many places that would benefit from more more automated test. They don't have, we don't have a mentor. And this is a relatively rare skill in open source. I'm sorry to say that it's kind of embarrassing to say it that there are, there aren't as many people who are actively focused on the software testing side is there are the software development side of open source. But there they are there aren't people who are skilled in testing there certainly are, but getting someone who is an attester and heavily focused on open source. I don't know many of them. Totally agree. So I would put it up there hey, if someone wants to offer their skills. But we would not staff it would not have that position without an assigned mentor. But I think I have an idea of someone I can speak to, to have people because the programs and partnership leading she could Africa is a software tester. And experience QA and I know she met us a couple of people and she knows people who are just starting out and also experience this piece. So I'll speak to her, if we could get people from there will be interested in getting into open source. Great. Okay. That would be fabulous. Yeah, so as Meg says we would love to have more software test skills. It's, it's, I consider it more difficult and more technically challenging. So it requires much of the knowledge the developer has, plus the ability to think about the things that might fail and could fail and all sorts of interesting. Great. Okay. So I have other questions on that so again my apologies that I'm on behind schedule on getting the post out. I hope to have it done by, by Friday end of day. So you should be able to see it by Monday. Do you have any other ideas of types of projects that would be particularly of interest to the she code Africa participants. So I think things like technical rights it also. I would love that. Yeah, I think we'll be able to get people also that are interested in going into technical writing. I think we have a channel for that. Yes we do. So. So I think at the end of the day the idea is, since we are not looking for people who are experienced in open source so to say the most important thing is, okay this skills you have. The public understanding is not like you're a complete beginner, and you are willing to put this skills to use in open source. So, since as young we are looking at it from we should be able to get people in all these areas. I know we have a couple of channels for different. So it's just to go to those dedicated channels and let them know that something like this is happening if they would like to participate. Great. All right. Okay so when I when I send out that when I make the post asking for mentors, I will, I will note that we won't, we won't create a role in our proposal without at least one mentor known for that role. So technical writing, for instance, much as I enjoy it, I'm not going to volunteer for it. So if Meg were to be available to mentor that would be great. Otherwise, we would probably not have it work out. So, but that's that's the kind or maybe I guess we could check with Meg and Kristen to see and maybe make Christian and Deraj if one of the three of them are willing to mentor. All right. Okay, great. Anything else on on she called Africa contribute on ideas. Nothing for me. All right, next topic then, and this one is very brief. I am creating a Jenkins enhancement proposal for the Java eight end of support by the Jenkins by Jenkins core. And so, Java eight was introduced in 2014, seven or eight years ago, and Java 11 was introduced in 2018, three years ago. And Oracle has declared that they will switch support mode of Java eight from their usual premier source support to the next level next year up beginning March of 2022. Other providers are providing are giving longer life for Java eight but Java eight and is coming. We're seeing that that a number of open source projects like for instance J get no longer are doing active development on the Java eight code, they're only doing it on Java 11. And so the project is now laying out a plan what will it take for us to make the switch to no longer deliver Jenkins run able to run on Java eight. And the, I'm going through this plan I'll send. I'll post a link to it and probably mentioned both of you just to invite you to, to read it and comment, because it's a big project and big projects benefit by having lots of eyes review their plans. All right, that sounds like it looks. It is you can imagine that removing a removing a major JDK from from support for a project is is enormous. And there'll be a lot of work to do. And including technical writing it could be a technical writing project. Oh, there. Yes, absolutely there is that well you can you can imagine all of the things for instance, the rollout plan includes things about. Hey, how do we roll it out on www.jankins.io what do we update on the various support pages, etc. This thing is still very much in in development, but the reality is there's lots and lots of things there are many many that we have to take before we're ready to say yes this has been a successful project. And I should just put a link to this draft in there. I haven't published it yet as a pull request because it's still very, very preliminary but my goal is to have a pull request ready for tomorrow's platform special interest group meeting so I've got a little less than 24 hours to finish the writing. Piece of cake. And that's, you know, nothing like writing immense plans that, yeah, lots, lots to think about and lots, lots for people to critique and help with and that's, that's the reason right what we need is we need a, a dartboard that people can use to throw darts at and propose, propose corrections. It's much easier for everybody if somebody has done initial thinking that they can then say oh no we should refine this and improve this. All right, anything any other topics for today. Okay, then I'm going to go ahead and call us done for today's session. We'll meet again Tuesday and then we'll meet again next Thursday. Hopefully by then we'll have more to talk about on community that Jenkins.io she code Africa, etc. Yeah, hopefully I'll be dropping the link to the form for project ideas also see. You could start feeling it. Very good. Excellent. Thank you Zenon. Thanks very, very much. Bye everybody. Bye.