 Hello, Esther. Thank you for being here. I just finished a one hour session tutoring sixth grade girls and remotely and so I'm thank you very much for being willing to delay till later in your day that was very kind of you. Hello, Meg welcome. Now I've got to find my office hours notes, or if I remember it we were just putting them in the contributon document weren't we. I hadn't taken any significant notes so let's all like put his notes and let's put today's notes as well so it is April 30th. Hello Cynthia thanks for joining. I'm just drafting the agenda right now. Hello. So I don't recognize 540-207-3161. Hi, Mark. It's me, Kristen. Hi Kristen. Okay now I recognize all I had to do was hear the voice. That's great. That's cool using multimodal technology I like that even better. Yeah. So that probably means you can't see a shared screen, can you. Okay, that's all right we'll do mostly talking I think. Yeah, that's okay. All right we are at the time I'm going to go ahead and share my screen and let's, let's start our session. Thanks everybody for being here. And if you've got screen screen available here's the proposed agenda that I've got I'm open to others so Mark, did you want to record. Oh it's recording is on. Yes, I'm sorry. Okay. Thank you Meg. They're very good. Thank you. Yes, it says, yeah, the recording. I think we're going to want this one. Well, I hope so. I hope it's useful, but we definitely record. Yeah. All right, so welcome to the concluding session for our Sheikot Africa contributon reminder that we adhere to the Jenkins Code of Conduct. 30th 2021. We are nice to each other we're kind to consider it and decent and good. Don't be rude, don't be crude etc. All right. So what I propose is let's talk about the end of the project. What worked well what didn't etc get some retrospective feedback. Talk about what's next. And I'm open to other topics what other topics so Meg or Kristen are the topics you'd like to bring as as mentors. I specifically want to hear from our sheikoters whom I think are a fabulous group of people. What could have made an a better experience for them. I agree and so I, and I think that's included in what you've got so super agreed. And Kristen, anything particular in addition that you'd like to request. No, I can't really think of anything right now I think kind of similar to what Meg was saying I really want to hear what we can do better or how we can help and currently kind of talk about maybe continuing on with certain things or like what can we do to help. Push through the maybe the full request and stuff that were not accepted at the time and just kind of like help get that finished like get us over the finish line. Okay, yes. Alright so what I propose is let's let's give voice to you to each of our each of those who's here with us. So I'm going to stop sharing and just take notes. And Esther I think you were first in the meeting would you like to tell us both, or maybe what we could do is you start we unmute and we'll ask you some questions and get some insights from you. So a second sure on you would you be willing to go first. Good evening. Sorry for joining in this. Yeah, so what am I supposed to. What we were thinking is if you'd be okay if Meg and Kristen and I just asked you some questions to help help understand what we might do to make the experience better for you. What things would be what things worked well what things didn't do this with each of the people in turn so that so we get some hints so one of the things that I think was well how did you how did you overcome some of the technical challenges you encountered. Are there things we could have done to help you be more successful with with some of the technical problems that you encountered. Okay, thank you for that question. So, the questions were technical some of them. However, I was able to to make more research. I was able to stop the Internet. I actually to be honest with you I had had sleepless nights, because I needed to get things right so I had to keep like, while working, I could have hundreds of tabs open. Because I keep looking out for, for help, and also for information that I need to work so it wasn't really easy. What you could have done you actually did what I was supposed to do because on the task, the tax, the document where they were really helpful the steps in the document. The only thing was the fact that we needed to do more research, yes, needed to do more research, and I actually did like many research I watched YouTube videos, I looked at documentation. Yeah, so that's it. And you did a marvelous job by the way, was it fun to do that research or would it have been better if like at the first meeting somebody had walked through those initial steps of getting everything set up and doing your first builds, and you'd been able to watch that and would that have been easier for you or would it have taken out the fun that you got with all the research. So, so many makes question I thought was a good one is would it would it be better if we started the session with an introduction that showed, and maybe recorded even the steps to do that those initial tasks because the tasks were pretty pretty detailed, but I assume there were things you bumped into that were really complicated or that, as you said caused you sleepless nights. And if there are things we could do to help reduce sleepless nights and have a bit have a good experience I'd like that to so should we show a demo of the tasks in the first sessions. The document was well detailed enough, like you said, yeah having sleepless nights. It's just my own persona initiates me because I have some other things to do during the day, and I needed to meet up to the expectations. So, for me, the tax, we're well detailed. And that's why we have mentors that are eventually we have maybe were blocked while following the task, we should screenshot and then show to our mentor so they could help. So for me, I'm cool with the way the tax. Great. Thank you. Thanks very very much. And maybe what we do is mega you're okay if I think what we do is let's rotate the same question through each of the each of the participants and then we'll come back for more questions would that be okay. I like that. Okay, so Cynthia, or no Esther we had said you would be second Esther. Are there things that where you encountered technical problems and if we've done something different we could have reduced your technical problems. Hello, can anyone hear me. We can yes go ahead. Okay, so the technical problems that I had were not really. I think not really problems that you can foresee, because I think the only technical problem that I had with Jenkins was the whole research issue which I figured out a week to fix. But I think what would have gone better would be some, like I already said in my article some helpful links to documentation that introduced Jenkins. And all that because I felt like like it was cool. And I understood the task and the steps and all that but I kind of just jump into downloading Java and maybe know that and I didn't really understand what any of them did. But I was just following the steps. So, and it was during when we had to start creating pipeline and all that but I know how to, I started going through the documentation so if we could go through the documentation. And in, at first things that I think that would have been nice. Very good so so in your case if we had provided as say for instance as links in that step links to documentation or videos because, because many of them. In fact, some of them even have entire courses around some of those topics right when we had you create an initial pipeline. So truly there's a full day course that I've taught in the past on how to do that kind of thing so I've spent eight hours in a classroom teaching people what we described as one or two lines. So, so absolutely that's that's a very good insight. Sorry, I'm sorry, I kind of missed you. You said you have a full day course. So, so we have a full I've taught a full day course in the past on what we we listed in that steps document as two or three steps. So use Blue Ocean, create a pipeline. Yes. And I have truly spent. Meg I think we spend six hours in that class don't we. Yes, I think this was the YouTube video wasn't it. That's that YouTube video is a condensation of the course. So, so we've we've done even more than that and so so it's and I am a little embarrassed here we could have potentially sent our you participants through the through the self paced course. Yeah, sure that it would have been as successful as what you already did but we could have done that so let me because the Linux found. An option. Yeah. Yeah. Thank you good good insight Esther thank you. Yeah, very good. Esther anything else before we go to Cynthia. No, nothing else. Okay, Cynthia you want to be next so the question is what could we do to reduce technical problems that you encountered. Thank you to you. Yeah. Sorry, say that again Cynthia I missed what you said. It like can you hear me well, because I'm currently yes yes I can hear you just great. Okay, okay. Um, I think the. So maybe the Internet connection was the biggest one. I don't know if I can say it was a technical issue but yeah like attending some meetings was so hard for me like I had to reload every time. But I think it's on my side that's something I should work on. Also, and making like there was a poor request I met and one of the contributors say that I don't remember the name but he'd say that should have done it another way, which looks different from what the task was asking for so I was confused. I spent time working on that for best and yeah it looks like I have to close it. So maybe it would have been better to. Yeah, like communicate with other contributors to just make sure that you know what they what we are doing, or maybe suggest something that we should have done before. Yeah, I think also for the code review was kind of yes, again some contributors were not that fast to give their review or they left some review and never came back to, to, to just see the status of the PR. Also, that would have been better so apart from that I'm really happy for the, for the documents that you provided us at the beginning it was really helpful it was clear. So yeah, we just had to like, as I say, do some research on how like the behaviors of some arguments called examples which was really fun on my, on my side I learned a lot by just reading other people's articles using stack overflow. Yeah, thank you so much. Thank you so you mentioned and I'm, I'm now curious, because we've seen it before sometimes internet issues get in the way when we're trying to do these multi continent experiences right here I am sitting in Colorado in the United States and you're, you're at an ocean and a continent away from me. So, so that's, that's no shock. Do you think it would have been more effective if we had used slack instead for for asynchronous communications without without even bothering with these meetings. I mean, if, if we had said oh we're not going to do meetings will mentor just by slack, do you think that would have worked for you or not so much. Not, not really I really love the meetings. So I wouldn't say that the one should stop, but like for other meetings that I usually have with other people I use Google Meet and it really work for me well, so I don't know why zoom is always the problem on my side. So I would prefer zoom or I don't know also, but I don't think slack video call would be better for like a group of people, but Google Meet was, yeah. I really prefer Google Meet. Yeah, okay and Meg and I and Kristen actually all three of us have access to Google Meet very readily so good insight I didn't. Maybe one of the things we ought to put on our list Meg is that we intentionally test and do it do the first meeting half in zoom and then everybody drops off and try half in Google Meet. Yeah, which one is the better technology for that particular group. Good idea. Does everybody, do all of you have access to Google Meet? Yeah, I think it's free. Yes, I do. Okay, and it may be that that the Google Meet infrastructure is just better in Africa than the zoom infrastructure right. I truly don't know but I think it's that would be quite believable right it could be that they've just got better equipment there than zoom does. Good. Good. Thank you. Very good insight. Great. That's a really good point. Yeah, so schedule the first meeting to include both. So, now to reinforce that one of the comments from one of the mentors was, hey, sometimes audio was poor. And one of the things we need to remind mentors is please don't turn on your video camera. Because it makes the whole experience worse for those who are remote right those who who maybe already have a connection that isn't great using video now makes it even worse. So Mark, over here, I actually prefer zoom. I use them a lot and it's been working fine. So I think the challenge Cynthia had was just intelligence. And I think Google Hangouts, if we use it, we're not able to record. I apologize, I didn't quite catch that. So you were saying that Google Google Hangouts or Google Meet is better and I missed the part describing the further details. Could you say that again. I'm saying that over here, I use zoom and it works fine for me. Yes, it's definitely was Internet issues from Cynthia side. So it's not like zoom doesn't work in this part of the continent. And the limitation in using Google Meet is the fact that you may not be able to record. Yeah. Well, here in Zoom, we're able to record. Good, good point. And, and that's where. So your note was that in Google in Google Hangouts or Google Meet we may not be able to record the the nice thing there is that's that Meg, Kristen and I have access to a Google Meet account that can record. So we could overcome that because cloudbies provides us Google Meet so we could we could do that so very good thank you because I think I think recording the sessions has been helpful. I don't think anyone has had I know when I did a mentoring session with with one and for me it was very helpful to know I could record it and she could refer to it later. All right, so let me. Let me take some notes there. Okay, good. All right. So, next question. All right, so we had what could we do to reduce technical problems. How about a more open ended question. Are there other. What other problems would you would you like to what other problems would you like to have improved. And Cynthia mentioned more prompt reviews by by maintainers that that was sort of that's the kind of thing so what other improvements should we consider, or this is me being being rude again sorry Kristen did you have a question you would like to ask. Kind of kind of maybe a follow up comments that one about getting improved or reviews by maintainers. And it's like I try and remember maybe I know that we've made some announcements on the Jenkins channel that they're, you know that this was the tribute all this happening. But maybe we should, because some of the repositories like you know Mark, Meg and Angelique me, we don't really have commit access to, or we're not really the maintainers of that particular plugin. Maybe we should have done a. I think all I do the good job of this one for the JFrog plugin is like do a reach out specifically to the maintainers and say hey you know this is what's happening. There's going to be some full request made for you know some documentation we'd really appreciate you know you being able to look at it. And I think that might have helped speed along some reviews. Maybe that's something we can try to do a little bit more targeting a reach out to the plugins that we knew were going to have some improvements because unfortunately it's kind of actually one of the things about open source to right is sometimes it takes a little bit longer to get things merged. Because a lot of people are doing it you know in their free time or maybe you know they haven't looked at it in a little while so so it's the pace is a little bit slower than if you were working. You know as it as a full job or a full time job or people are looking to merge things right away so that is kind of a little bit of the give and take for open source that is a little bit slower. But maybe we can do a little bit more of a targeted effort to let people let the maintainers know that this is coming. Right, we could have used the maintainers to help to on source gathering, because I was one when we first went to write the new stuff it's like where do I get information and it's like, yeah, welcome to open source that can be interesting but because I think I forget which one there was one plug in that we'd identified as high priority because we get so many responses, but it turned out we couldn't write anybody who knew anything about it. And I think it was on India who was stuck there it's like, well, right. So we could have made sure that they, you know, even if if we missed a couple of the very top ones to get some that where we had active support. That's a great question though. The question. I noticed in the comments about using the get chat group versus slack. And that the people found the get channel sort of intimidating and we didn't really use it very much but a lot of these other people were not on the slack channel. Should we make sure that we get these other people on the slack channel or should we work a little bit more to get the mentally is comfortable using the get channel. Yeah, and I think, I think, well, so I opened that question to Esther to Cynthia and Tony, and I, I'm assuming that their preference is slack rather than get her. And I think that's because the slack user interface is a better user interface than getters is. Can can the three of you confirm that slack is preferred so long as we one of the mistakes we made here was I just just today invited Kristen to the slack channel where the mentors were talking mind you we've been a month doing this and I didn't invite Kristen so and then it's all good. It's all good. Well, and that was, and that was a terrible mistake but we had the same thing with one of the participants that I realized, oh I didn't invite her to the channel where we were having these conversations she could have benefited significantly by seeing the communication so so yes it was, that's a communication mistake right and communicate so clear communication channels and, and maybe what we would say is, and confirmation they are working. If we had done in one of the meetings if we done in the first meeting or the second meeting. Hey everybody, each of you needs to connect to slack and send me a message that shows that you've got access. We would have, we would have solved many problems with something as simple as that. Sorry, taking notes. All right. Kristen, any other questions you'd like to ask. Sure. So one of the things that I noticed is a recurring theme is that we have, sometimes in order to even figure out, you know the startup guides it's a lot of going outside of maybe the Jenkins official documentation. So my question is, did you find anything kind of out in your search that would be interesting and significant to pull in like to make sure it's documented in the official Jenkins documentation. So that, you know, maybe people in the future who are trying to do startup tasks aren't kind of all over like searching out and looking at stack overflow. Is there any gaps or that we're missing or any anything in particular if there's links or things that you found helpful to be helpful to see them you can send them on Slack or some remark directly put them in the document but I think that's my big question is, what are we missing, or what is it helpful to get you started. That's a good one. I like that. Okay, so what, what did you learn from other documentation that we should include in the standard documentation. I like that one a lot, and rough examples are even a good thing. On you, do you want to do are you willing to answer that question or share with us some of your insights and then we'll ask others. Sorry. So the question, the question was, what did you learn from other documentation like stack overflow or like reading blog posts that we should consider including in the standard documentation and that general topics is probably all we could ask for. The other documentations I used or I looked out to was was just because everything was practically new to me so I needed to read from here, read from this other source to compare and actually reduce what I'm looking for. So the documentation in Jenkins are okay, but then personally I needed to understand more about the plugins. That's why I needed to hear from other people that have used the plugin. I see. Okay, so what you what I think what you were saying is that your task was specific to a particular plugin and there was no avoiding that you were going to have to do research on that specific plugin. Yes, yes, yes. Right. And that and I think that's that's very practical of you because if we do all that research in advance, we we've done the whole project we've done most of the project so so that feels like, okay, I'm not sure that's available. Okay, good. That's true. That's a good that's a good point, but it, I guess, like, making sure that, you know, we weren't. It's that documentation, I guess, like you said saying mark that makes sense. Well, but but now now I think let's take the same question to to Esther and then to Cynthia because they may, they may have had a different experience. So Esther to you. Are there things that you discovered from other documentation that we should consider including in the standard Jenkins documentation. Let me see. I, I don't think I don't think so. I don't think so. Everything, everything that was that I found outside there was an example or two in the documentation I don't think so I think what I mostly looked out for was more examples more than just cases on stock overflow and other and other blogs on issues that people were facing and then looking at their own code, looking at their own pipelines and all that so I don't I don't think so. No. There's not like I think of at this moment but if I do think of one or like. Well, and you already said when you said examples and that feels like a place where we conceivably could have said hey here. I know we have for instance mega pointed us to the pipeline examples repository. And I'm not sure if it had the examples we were seeking, but it was a, it was an excellent resource that we could have included in the steps in the in the task to say hey here's some good samples. Right, and the stack information on each of these. There, I don't know. I mean there's I can almost see a project where somebody just track stack flow on these different steps and watches for some juice to come up because there was some really good stuff there. Right. Okay, good. Mr. So Cynthia, same question to you. As you had to learn from other documentation. Are there any things you'd say we should include that in the standard documentation. So I feel like examples would would have been better. Also, there are some terms that were being used and as a beginner I was like, Okay, what does this mean and that was making me go and search for like what is what what does that mean. So I don't know maybe trying to, you know, yeah, consider the beginners also were trying to understand what that maybe plugin is doing and making sure that the terms are the. Yeah the terms that are being used are like easy to understand for beginners. Yeah, I think that's it. Also like more description I think on what the plugin is doing. But that's for my side because I was trying to understand everything. So I had to like, go to look for articles that people have written to understand more on what they're doing. So, yeah. Excellent. So I really, you sort of caused me to light up to to get enthused about the thought because Megan I have in the past had conversations about glossaries and the Jenkins glossary where those terms are is not always obvious or readily accessible. What does the word pipeline actually mean in Jenkins right and what does job actually mean and what does, what does task mean and step, and each of those words has a relatively precise meaning that that you probably now understand but at the start you certainly didn't know that step means this and task means this other thing and argument very good thank you. Actually I think this so this is another place though if we give them a chance to take the self paste pipeline class, it would have put it in context because also that's always the problem with the glossary you don't necessarily see the flow. And, you know, maybe, maybe to take that theme of what if we've done a 30 minute or one hour introductory. Hey, here are the terms that we're going to be used or here. Here's the pipeline course in an hour. But I guess we've got, but we've got that in video form so what really what probably what we should have done is said, hey, before you arrive for day one, could you please watch this video and prepare questions about the video something like that. Good. Okay. Yeah, that would have been better. Very good. Okay. All right, other are there other questions that we would like to ask. See, I'm going to look through the retrospective feedback because there were some doing to. Oh, oh, yes. Okay, one observation was, did any of the three of you have difficulty because of a small amount of memory on your computer or a unique operating system you're using. Maybe we should check there part of me worries that it probably is common to have a computer with four gigabytes of memory. And that I worried. G is that enough, etc. So, so, I guess my question that I'm, I think we should hear from each of them is, were there hardware or equipment issues that we could have predicted and assisted. For instance, did did any of you try to use a Chromebook instead of using a Windows Linux or Mac or something like that. So on yin and did you have any hardware or equipment issues that we could have could have helped with or could have predicted in advance. Well, no, I used my work for me. Okay. All right, and Esther likewise for you were there. If I remember you had a you you reported challenges restarting Jenkins which in fact maybe may just be a Jenkins bug I'm not sure. Yeah, I had that issue, but then I started to restart Jenkins and the Jenkins.exe file so what one of I run that Jenkins.exe restarts it just restarted Jenkins so I didn't have that issue anymore. And then I think another issue that I had was logging into Jenkins. So when I tried to log in the first time we gave me this invalid logon error and I followed I tried to follow the online help me. They helped out in documentation because it was a link to the case I got anyone get that error so I was trying to follow it and then there was this setting that was missing in my laptop. I, I just have problems online usually missing and understand who I think it's a local security group or something it was missing so I had to run, I had to start the solution and then I found this back script online. And I run it on my system and I restarted and then the option popped up and so I was able to continue. Okay, and, and so there is a place where we probably should advise developers. So you were a Windows based developer. And you use the MSI to do an installation and we should probably guide developers that you that's that it's better for a developer on Windows to use the war file to do the installation rather than the MSI because of permission problems that come. Thank you. Alright, so guide developers on Windows and it go ahead. No, no, I was okay. I was to install. So there's a piece of the install experience, Megan Kristen and I do not spend the majority of our development time on on Windows I run on Windows a lot, but, but it's not my development platform so Windows to install from war. Not MSI. And the issue is permissions issues. Okay Cynthia same question to you were there hardware or you had mentioned internet issues were there other hardware or equipment issues that we might have predicted or helped you with. No, but I was going to say maybe adding. Because so I had an error where I needed to like set the environment variables like in the Java path. Maybe that would have been better to specify that in the, in the steps like in the task. So it may be another mentees might lose the same error might. Yeah. Good okay so in that case the tasks didn't have enough detail for you to be successful with the, with that the next step. Good okay. Very good thank you. Other questions. For me. I think, I think we're set, at least for me we're set with questions thanks for your feedback. You are welcome to continue providing feedback in the retrospective document. Encourage it. Thank you very much. Were we going to talk about what's next. We are. Yeah, so that's what I was going to go to see if you were about to hang up. Nope, nope, I was going to talk about what's next. Go ahead. Good questions. Yeah, so, so what happens. What happens to the remaining open pull requests right. And that's, I think that's a good question for what's, what's on what's next for us so let's talk through that. And let's take that as the first question I think what we need to do is more reviews of the open pull requests. If they haven't already been reviewed and approved. Mark, Oleg, Kristen and Meg persuade the maintainers to merge. And Angelique. Oh, and Angelique, right, right exactly. And then after merge. We watch. Watch that watch them or see that they are released. Now there's a step in here that that I like to do in addition to that, which is mark build private copies of the plugins with all pull requests merged include in his test image. The plugins are available to others. So for example, Esther has, I think, five or six pull requests submitted to the one she was working on or maybe a Cynthia one of the two, or, or Nina I know yours does with Artifactory. And the idea is what I'll do is I'll build all of those pull requests together into a single copy of the plugin, and put it in my test environment so that I'm using it. I'm using it out so I'm just using it regularly. That helps me persuade the writer persuade the maintainers, because I can say hey I'm using this I've started using it on this day, and it's behaving, behaving well in this way. So on unit does that provide you an answer to the what happens to the remaining pull requests or did you have more questions. That's okay that's fine thank you. So we've still got a number of pull requests left to merge and review so with the mentors will continue working on that. We'll have feedback on those discussions, and ultimately, the goal is to get them into the into the content and merged into the plugins and merged. In addition, I'd like to submit a blog post proposing to summarize the results. I'm, I'm intensely proud of what you've accomplished. I can't tell you how proud I am. Yes, we placed, we placed five people, and I think only two of you had previous Java experience. So, quite a, what a treat to see all the progress that you made and the ways that you added added to the Jenkins project, and I hope learn something yourself. So, yes. Yeah. Great. Okay. I'll submit that blog post. Look for a draft of the blog post probably even before tomorrow morning's closing session. I'd love to have your reviews on it. I don't, it may be Monday before actually get it published, but I'll try to get it written later today. All right. Yeah, that's fine. Thanks. Great. Oh, and I had several other points in terms of things that things that we will ask for next time will be more systematic about it right all sorts of things in terms of how to make this process work well. So, anything else we should discuss today before we conclude or Meg, Meg were there other things that you needed. No, just to say what a wonderful group this was I think it was fabulous. Oh, I know what I was going to say also for if anybody is interested in continuing the, should we give them the link to cloudies university mark. Oh, yes, yeah. It's a little late the self paced training is always there always available to anybody at no charge. Yeah, actually, and there are there are several self paced training courses. So I'll, I'll happily put those into the document. And, and you can choose because cloud bees offers several. The Linux Foundation offers one lambda testing offers one or more. There's several others that that if you're interested in them, you are welcome to use them. And to clarify this slack channel is staying open for the foreseeable future right. Correct, right I don't see any reason to close this this particular channel, if, if it goes idle, if we find it's not helping us, they may then close it but for now we're going to leave it open. Okay, yeah. Sorry Cynthia say that again. I was going to ask what if someone wants to be involved more on the technical side. So what can we do like so that means we have to take that course first. Yeah I'm not sure about the next step for that. No, if you want to be more involved, no course required, you're welcome to, you're welcome to take the course to help your skills but all you need to do is keep doing what you're doing, and, and that's that's great involvement already. I think is she asking if she wanted to do something other than continuing working on the steps reference. If she wanted to contribute to Jenkins. Other, is that right Cynthia. Yeah, like you to work on Jenkins but not the steps reference. Yeah, like the technical side, like more of Java and. Sure. So, so that's, let's put that in as a question because I think I think we've got some good answers so what if I want to be more involved in the technical details right and technical. So, so as an example Cynthia if you'd like to be involved in helping with the development of the Jenkins get plug in. I maintain that I would I would love to have extra help. If, and there are other maintainers like me, who are similarly interested in having people help them. So you could choose one that's interesting and ask that maintainer, may I help you. If you ask me the answer will be yes. If you, if you say I'm not interested yet. Go ahead Kristen. Also, like sometimes, if you're just looking around or there are sometimes problems inside of the Jenkins tier that are tagged as like newbie problems, or things that are easier to tackle. So if you look at some of the individual plugins, you can see that they have GitHub issues, they, some, some plugins use it it's again because it is open source week and Jenkins is very permissive, you, the individual it's up to the individual maintainers to say how they track their issues so it could be in one or the other. I think a lot of people are using GitHub issues now, but you can go there and then sometimes they're tagged with good for beginners and you can just kind of work on it and submit the patch, and that's a bit of pull request and that's a good way to get started as well. There's sometimes individual tools that need help to. So, review for you to ours, reviewing and testing other. Yeah, Mark. Yeah, have you all seen the resources that are on the Jenkins IO page for new contributors and that'd be interesting do you want to even share and show them. Yeah, that's a very good run so new. There are, there are office hours available I believe and right. Yeah, so let's hear I'll open that up and share it on screen so. Here we go right that's a really good point about the office hours mag two because like there's different special interest groups for different tasks so even if you go and you, you can just sit in the meeting and listen. If you don't want to feel like you want to say anything or just to kind of like learn about it and depending on what they're doing that meeting though they're talking about different problems, just to kind of get like to get started with figuring out what else is happening in Jenkins. And most people this is a really nice, most of them are very happy to have a newbie there who says could you tell me what you mean by that, and they'll happily explain it and bring you in so. Yeah, so, so here's the page that Meg was referencing earlier. This is the, what if I want to help more, and we have several different ideas where, if you'd like to help more here, then Kristen referenced this page. Let me bring it up. Let's see I need to. So Kristen referenced this page which is the friendly issues page. So in this table that you see here of core get plug in warnings and G each of these issues has been tagged as friendly for someone who is a first time contributor. They commonly require Java skills so it's assumed that you're interested in learning Java and willing to work with Java, but that's the kind of thing that's needed, or, and in the case of warnings and G it's also got some JavaScript in it. So, so those newbie friendly. These friendly issues, and I've embedded the link to that into the into the retrospective document. Then Kristen also mentioned friendly issues inside GitHub. And there you have to go to the individual thing but let's look at friendly issues on the Jenkins documentation site. So here we would look for see good first issue. So here is a set of documentation things that are good first issues and it's pretty common for plugins that are using GitHub to track issues that this good first issue is what they'll use to flag. This is a good choice for someone who's a first time contributor. Yes, there's something equivalent to that for non documentation. It is the same thing actually yeah so let's look at, let's look at let's take the Jenkins configuration as code plugin so let's go look at it so configuration as code. And this is one that uses GitHub issues. And now if we look here good first issue. Here are three good first issues one is rework the read me. Another one is create a developer guide and another one is clean up the obsolete terminology that's in the demonstrations in the documentation. So, does that illustrate well enough Meg. Yeah, I think I'm question for Cynthia and the others. Yeah, thank you. This was really helpful. Great. You are welcome in any area of thank you for this. Yeah, so let me put a link to that into our into those notes so that if you need to refer back to it later it's available. So it was. I've misplaced my notes. There we go. Got them. Okay. Thank you contributor page at there and then GitHub issues. Good first issue, like jcask. Good first issues. All right. And actually just thinking about this to another place you might be able to find good first issues is if you look at the Google suburb code project. They have those actually if you're interested next year unfortunately the period of submission and stuff has ended already for this year, but next summer if you're a student I'm not sure if any other students, but there's a chance to be able to speak in Google summer of code. But from those pages you can sometimes also get to good first issues or good, good ideas of things to help with. I'm also technical pieces, but yeah. Right. Good point. Every, we don't accept a project idea, unless it has. Right. Good first issues as one of its mandatory things that's included so just right. There might be a couple other ways you can see some technical tasks if you're looking for other things. Right. So here in the project ideas. There are some things in each idea. So, good, very good. Excellent. Anything else before we conclude for today. Okay. Hi, Henry. Yes. I just want to really really appreciate all the mentors for the time for your time. We had the mentorship, the corrections and everything like the journey was was worth it. And this experience is something I would really like to have again. Yeah. Because I was exposed. So many things I learned practically everything. My first time of contributing. And it was, it was so cool. So I really appreciate all of you. Thank you so much. Thank you so much. Well, thank you. Yes, sincerely. Agreed. What a treat it's been really truly thank you. Thank you to all of you. Wonderful. I hope we'll all be crossing paths with you again. Well, and one more reminder. I'm preparing a talk proposal for DevOps world. And would love to have and it will be remote this year so I would love to have the three of you if you're willing, be part of that talk. Well, I'll send you comments on, on how I think we should do it, etc. because I think it's, it's fun to have talks where you say hey, this is our experience and this is what went well and this is what didn't go well and so, so I will I will be sure that you're copied on that so you're aware of me proposing to have you join me as part of a talk. All right. I think that's it. Anything else before we conclude. Good for me. All right. It's been a very fun April. It has. It's been very, very busy. Thank you very much. I know we've got more pull requests to review. We've got more work to do. Thank you. Thank you. Thank you. Bye everybody. Bye bye everybody. Bye.