 Welcome. This is Jenkins documentation office hours. It is the 11th of March. Thanks for being here. So here are the topics that were on my list contributing to user experience was a question that's enough wanted to address the Sheikot Africa contribute on more details on it. I've got one action. The developers list. The website search was a topic we have last time I'd like to review it again. I don't have anything to say on Docs roadmap inventory and Docs structure, or the other topics that I have listed there so I'm going to just take those out. Any new topics that you'd like to add Zenab or Kristen any topics you'd like to add. None for me. Okay. All right, so then contributing to user experience so Zenab you'd asked about the, are there ways that contributors there from Sheikot Africa or elsewhere could contribute. So here is the user experience page and in particular down at the bottom of the page are the meeting agendas where you can see the notes from the meetings that have occurred in the past and commonly they also include a recording. So if they would like to see what kinds of topics the UX SIG discusses they can go and review the recordings and see oh okay this is what they're talking about then this and then this. I think has been the primary driver of a major enhancement that just arrived in Jenkins long term support that Jenkins long term support release just delivered this thing that includes the configuration for modernization all about the UI and it was took a long time to get it there and it's now shipping and has migration guides and hints so all sorts of cool things there. Uh huh, you bet. So recordings and and notes available from the page. Next topic was contribute on so we've discussed it in discussed in outreach SIG. Doc SIG and elsewhere and as far as I can tell we have agreement so cloud these plans to sponsor. I heard today that CDF is sponsoring as well CDF has actually send the phones. Good and and forms coming soon for the for the sponsorship from cloudbies I talked to Selena Glawick this morning. So so that's that's good. If you don't see those forms within say 24 hours. Zina please reach out to me. All right. Another candidate sponsor Broadcom. The question has been asked to their team but they haven't yet given an answer back to the to the Broadcom employee that I interact with so we've got hopes for others. Good luck on your recruiting. Thank you. Thank you so much. So, in the outreach SIG today, it was also reviewed and agreed on a proposed project idea, or at least the project idea was discussed. And, and so I can, I could talk briefly about that if that will help but that will be part of our submission. I have the responsibility to submit the organization. The mentoring organization application. So I'll do that. So that you should have that within 48 hours. Thank you. And the suggestion today was hey announce it to the developers list so I will do that as well. That's to encourage additional mentors. And Kristen Kristen is already agreed to be a mentor. It's nice to have. And make McRoberts has agreed to assist as well she's a training, a training author. And her work schedule is such that her work and personal schedule is such that she'll be available. Africa early morning hours. And Kristen and I are available Africa after working hours after you know so this time and a little earlier. So, I feel like we've, we're going in the right direction. And we'll keep you up to date as we go further. So, and yes I've still got this action item for the project ideas. If that the answers out there, in terms of computing resources, the project, whoops, the project ideas after the project idea that I'm working on needs a computer that can, that can compile Java. So that could be Windows, could be Linux, or Mac OS, or free BSD, or open BSD, those I know all work. And in terms of popularity I suspect Windows is the most popular there. They'll need to run Jenkins, which means they'll probably need, and need to experience it so likely think two to four gigabytes of memory. And you had said earlier that we need to put that into the application that's still correct right. Yes. Okay, good. Right. And required skills. Yes, I think we've got that. So any other any other questions from using up or you Kristen on she called Africa and the contributon. None for me. None for me either. Okay. Oh, sorry, I just thought of something. So, for the project ideas that Jenkins is submitting. I don't know, like how many, you know, I said, I mentioned earlier that form can take in three projects ideas. So my question is, first, how many projects ideas is Jenkins intending to submit. And secondly, say for instance, if you submit three project ideas, would Jenkins be able to handle it if she could accept all the project ideas or just one of them. Good question. And so that that's a, I'll describe what I think is going to happen it will depend on the response from the developer mailing list if we do more than that. So what I'm envisioning is we would, and I'm going to bring up my notes actually from the Jenkins outreach meeting because inside those notes, we've got a description of the project that way I don't have to retype it so just a minute while I go grab those notes. Okay. There it is. Okay, good. Yeah. So here come the agenda. Perfect. All right. So on my screen. And this meeting was also recorded so if there's any question we can always go back and look at the notes but here's what I had proposed so the project idea is that we will take pipelining, ask the, the people of the women there and sponsored by Sheikot Africa to create pipeline examples and pipeline help for popular Jenkins plugins in their use in pipeline. What that will do is give them direct experience creating pipelines and Jenkins, they may have previous no experience with Jenkins and so this will introduce them to Jenkins and what's a pipeline and how do you and then, then they will use those compile one or more of the plugins and use that then to write help that goes inside this plugin and therefore requires that they modify the plugin source code that they recompile it they tested inside Jenkins and then submit a pull request to that plugins repository to have that change included. That will give us examples in the pipeline step for steps reference it will give them the opportunity to have done Java compilation and to explore what it means to interact with Jenkins. The idea was we would put up to three of your contributors on the same project idea so that they could work together because this is, there are many, many places that need this. We think we could have me and Kristen and Meg coaching this group of three on this project idea. So that you've got three people assigned to the same concept but working in different specific plugins to achieve the objective. Now this is the first time Kristen seen this idea as well so Kristen you're welcome to object or say that's crazy Mark what were you thinking. I kind of like the idea of getting people having people work together but I don't know if that's like kind of what the project goals are. Because I know that for like Google summer code they're like you can't really have people working together but I mean that's software development right like we're supposed to collaborate. Usually not just a person working on their own. So I kind of like that idea of just working as a team. I think that some of the documentation can definitely be fixed for the, for the plugins but it's mostly and getting some examples would be very good I think that maybe they can even, there might even be a chance to update some of this like just or just to go through and make sure the pipeline documentation in general is okay. That's fine but there's definitely some examples of things like, I mean I had a question about like what you can do a certain library or like you're using a common library and I couldn't really find a good answer in the documentation. So like for example that's maybe some extra stuff we can add. So, I like it. Okay. All right so I'm at all I'm going to do is I'm going to copy this and paste it in here so that we've got it. Okay. So, you know, I think Kristen asked a very good question. Is it within the rules is within the boundaries of the Sheikot Africa contributon. If we put three people together on a on a single project idea, even knowing that each of them will have a dependent task they actually won't be dependent on one another. The thought was they, they however have the same general steps each will need to take as they achieve their as they accomplish their tasks, and therefore they'll be able to help each other. As they bump into problems or say oh I had this problem this thing would not behave the way I wanted, hoping that they can help one another in addition to getting help from the mentors. Yeah, so it's okay if you have more than one person working on one project idea, as long as they have distinct tasks, as you just mentioned, because you know at the end of the whole boot camp in April, you will be required to grade each of these participants individually, not by the project idea. It's important that, despite the fact that they are working on the same project idea you're able to access to assess each of them individually and their performance individually assess their performance individually, so you can grade them at the end of the day. Okay, well and, and my thought in terms of the individual I, I know. So this one right here the pipeline examples and pipeline help. I have lots of feedback in the documentation feedback, complaining about the absence of examples in very specific plugins where they say this plug in needs an example and this one does. My thought was since someone said that I could easily assemble a list of 10 or 15 or 20 plugins where these plugins have specifically been requested to have examples added. And if each of them took five, they would have independent tasks that are similar tasks but independent of each other. Yeah, that sounds great. Okay, good. Right. Now, in terms of getting them started with Jenkins because part of this will be, they'll have to get started with Jenkins right where I'm going to assume that most of them probably haven't used Jenkins before. And so I would assume we give them an introductory kit which says, please do this tutorial, please do this tutorial. Please try this experience. And when you've done those that will sign off check on that that part of it. Yeah. Yeah, that sounds good. Okay, great. All right, so that and I think that's part of the application process then so I'm expecting within the next 48 hours or so to have that ready to submit. Okay. Right. Now, one of the things that was asked in the advocacy session was, are there other. Are there other projects that we should be mentioning this to and I don't know a different topic. Okay. So, we'll we'll continue on this path. Any, any other guidance you want to give there's enough. No, I think that's it for me. But if you have any question you could always send me an email now reply. Excellent. All right, thank you. So the other topic I had was site search. I don't know if this is particularly relevant but for me it's been an interesting adventure. And I'd love to show it and talk about it and then we could decide if it's something we need to do, do further on here as a office hours but are there other topics you'd like to bring that have come to mind Zina. No. Okay, so then here, I'm going to show what Gavin Morgan has done in terms of an, quite an impressive piece of work with using the Algolia site site search engine so here is this, the plugin site with now using search provided by Algolia which is a search company. So they donate to open source projects. And so now I can ask questions like show me GitHub branch source and or show me, show me, let's see, a strategy plugin, and it finds strategy and strategies and a very elegant, nice improvement we used to have search that was our own indexes. He's improved it now to use these Algolia indexes. And as a result, we also get reports that tell us which search results have been which which search queries generated no results. So we've recently learned that a number of people are asking questions about this thing TFS, or team foundation server. And the answer is, we don't have anything to offer them right now, should we do something there. So the the experience has been really helpful. Well, now it gets better, because Algolia has also given us has also donated search for the Jenkins documentation site. So, Zina view of all people likely remember from your work on the Jenkins on Kubernetes documentation. No search up here well guess what there is now. Wow, and it has actually been fixed. Looks better now. Yes, and and works well. It is certainly we want to do more tuning we have more things to improve. But it works, and it shows things. Oh, whoops, now that's interesting. I have a bug. Shame on me. That's very interesting. Okay, so that was a bad sign just a minute while I record for myself what I did there. Okay, how did I do that. So look at the recording later that page that came up with undefined is indicates there's a bug in something that I need to fix. So excuse my showing you a bug live. So we've still got tuning to do here because one of the things we're finding is that that very often. Yes, very often what we see is the search results are biased towards answering with extension points. And extension points are just developer documentation, not interesting to typical users so on this and this sample of the five results that are shown only one of them is interesting to a typical user. So we need to find a way to turn down the priority of these extension points documents. We haven't found that yet but we got to learn from how to do that. Well, okay. And that was all that I had to show any other topics we need to discuss today. None for me. Okay, Kristen. No, I don't have anything. All right. Sorry, I wanted to ask a question. Actually, this is not related to it's about cloud bees. So I got an invitation to speak at an International Women's Day event for cloud bees from, I think, Stephanie or so. So I just want to confirm the name. Stephanie. And I think the last meeting we had was like last week and she was asking about speaker fee and something like that. So we had a kind of discussion so she sent me a mail today that they could work with the speaker fee or how cloud bees donate to Sheikot Africa. So I just wanted to confirm if this is has anything related to sponsoring contributor or this is different. I think I think they are distinct from each other. Yeah, because Selena Selena and I had that the conversation today she did mention that that they were having you speak separately and that there was a speaker fee but to me it those teams separate because they're what what it is is they're willing to pay you the fee or donate to Sheikot Africa but that's not, they're not coupled to each other. So, so their sponsorship of the contributon I believe is planned, whether or not they give you the speaker fee and I would suggest take the speaker fee directly don't have them donated to Sheikot Africa just because we want to encourage you to be a speaker. Thank you. I mean, if you feel oh you you're willing to donate it to Sheikot Africa that's your choice but for me I think in order to assure that you have the opportunity to speak and are compensated for speaking, you should accept the speaker fee. All right, thank you. Kristen does that seem reasonable to you am I am I off base. No I think I think you're right I think they're separate things. Don't say don't worry about combining those. Right. And I think, I think those kind of things are great. It's, it's a good chance for us to, for us to help the Sheikot Africa movement and your leadership of that movement. So those are both good things for us to help. Thank you. All right, I think that's it then. Let's call an end and I'll, I'll post the recording in an hour or two. All right. Thank you. Bye. Bye.