 Welcome to Docs Office Hours. It is the 4th of March 2021. So topics I had on my list included Contribute View Summit retrospective, Sheikot Africa Contributon, Google Season of Docs, Google Summer of Code, and Docs Roadmap and I think that last one we should just accept we won't touch it this, this session. Any other agenda topics that you'd like to put on the list. Okay, cool. So, survey was sent, sent for the contributor summit. Please be sure that you reply to respond to that survey, even if you didn't attend if you registered you should have received the survey and non attendance is is actually an important piece of data. Any comments that either of you wanted to offer directly here outside a survey or otherwise. Okay, great. Next topic then, Sheikot Africa Contributon. So, Zina, let's see, ideas are being collected. I'll, I'll gather them. I think I think I'm going to make this office hour session, the, the gathering place until we submit a poll request. I've got background noise that I need to fix. Sorry about that. Okay, so. All right, so we need to prepare a poll request to Jenkins.io proposing the Sheikot Africa project ideas. Any concerns there or questions or worries. No, just that I just wanted to point out that really appreciated if we could kind of like conclude this before the 19th of March, because that's when the participant application is going to end so that we can use this in selecting the participants that are going to participate in the bootcamp first be able to meet up with the first timeline. Okay, that makes sense. So I assume we'll continue discussing each week so our next checkpoint will be the 11th a week from today and and we should have it ready then invisible. Thank you. Great. All right. So, and then let's see the Jenkins project application to Sheikot Africa. Oleg has shown a very good model for us is how to do that. Mark draft answers to the survey publish them for review before we ever submit the survey for the answers to the questions. We publish them for review, then invite others to review and comment proposed application. It helps because then we use this to align with others will do the same thing with Google season of docs. Next topic on computing resources so Zina you mentioned that in the project ideas application we can describe their hey if we're if we're inviting them to do something that's documentation centered we can ask for someone with Linux, so that we don't put them through the experience you had of initially wrestling with Windows development that just wasn't really ready to do. Is it really common that the applicants would have access to Linux. That's another thing I can't really see. Okay, but I know Windows is more popular. I don't know, but I just know that most people have interact interacted with actually using Windows PC. So I can't really say but then again, even if you are to end up selecting someone to use a Windows using a Windows PC to work on documentation, I'll be happy to work with them, you know, in trying to set up their Windows PC to work documentation. Great. All right, just knowing that Windows computers are more common in Africa than Linux is already a good thing so that we we bias towards projects that can be done comfortably on on Windows like for instance the terminology cleanup because it's a Java compilation process can be done very confidently on Windows. Same with the pipeline examples. Good. Okay. All right, anything else you want to guide us on there on the contributon application. No, I think that aside information on projects, probably like a description, you really need to put in like a description of the project say if you're talking about you know, maybe like a description of what is about something like that. Probably if you have somewhere on Jenkins.Ivo that like you mentioned you're going to open a full request so you link to a page like that would be useful in the would be useful in the application form. Another usefulness of this information is at the end of the day, we plan to put everything on the program website like all the available mentoring organizations and the project. So that's where the description will be useful because we plan to put it there. Then also links to join forums that will be useful for anyone working on a particular project or working on the Jenkins project forums that you can join if you need help and things like that. Then also mentor information for projects. Then also a number of participants. Each project, see if you want one participant for each project also. Yeah. Okay, that you highlight a point for me number of participants per project. Some of these projects are in fact, they could in fact be done parallel if a team were willing to work together. And Kristen, maybe you should sanity check me just to be sure here but my thinking was, for instance, pipeline examples, or terminology cleanup might be a thing where a team of three or four contributors might gather together in a mentoring session with one or two mentors where we could actually get more contributors than mentors in the meeting and and be coaching them where they each take a different subset of plugins to work on. Do you think that have you have you seen anything like that done before do you think it could work. I haven't seen it but I think being able to kind of have a common time to do activities would be helpful. Maybe that'd be able to feel like the more the merrier. And be able to have everybody together. That way it's mentors or sorry the contributors can help each other, and it may not be as important to have so many mentors sitting on the same, the same place. Like that. Yeah, I think that might be an easier way to get people to help to. So, and I think that's, at least for me that that sounds, it sounds like it would be an interesting experience. A lot of contributors to assist one another, not just rely on, oh, I'm the lone person working on this project and my mentors are half a world away on a different continent. So, one of the reasons why another reason why we choose to have this set of things, you know, considering that we have a short timeline. So, probably my happy project that might be much for one person or one person might not be able to create that whole timeline. So having multiple people working on that project would kind of like you'll be able to accomplish more, you'll be able to support each other and you necessarily don't need to have more mentors when it's just probably one meeting or two meetings twice a week with all the mentees at the same time. And, and do you think that's I see since there's there agreeing to work full time on it. I think it's safe for us to assume that they can therefore adjust their schedules to meet. Good. Very good. Okay, super so that that is a that is an aspect that I had not considered thanks. Okay. I'm trying to check the phone. Sorry, you were, I missed that Zina we were trying to check. Yeah, I'm going through the phone. There's any additional information that I forgot to. Great. Okay. All right, anything else then on she code Africa, contribute on. Okay. All right, Google season of docs. Oh, wait a sec. I've got one more topic to add to the agenda. I'm going to take it in now I'm going to insert one site search. I have to show this plugins and dogs. In the in the contributor summit, one of the things that was listed as a roadmap item for the, the project was to support site search. So searching within the Jenkins site, and we've had plug in search for a while using a relatively complicated search interface that we've done ourselves. We've been using Algolia, and their search system makes the site the search is quick and tunable and we get all sorts of interesting metrics from them. And is really pleased with the results here. Now it gets even better is that now if I go to the Jenkins pages. There's also a search. And, and again this is offered to the to the Jenkins project by Algolia no charge. So we now have search. Now we need we need a little bit of, you can see that the layout isn't quite right and so we'd love to have additional tuning, but this only just arrived this morning. So, so we're really quite pleased it looks it looks good. It looks usable and, and now look it even fits its sizes down to 640 by 480 screen and still works. So it's, we're very, very pleased. So just FYI. If you're interested, it's, it may be a place that we might consider as a possible project idea. My guess is, it's probably not well suited to Sheikot Africa because there are a number of complications hiding in the structure of the site. But glad that site search is working, both enabled visible. There's more to tune and adjust to for for layout for content for search effectiveness, and we're working on next topic then Google season of docs. This is one where project ideas from the Jenkins project and I assume what we'll do is use the Sheikot Africa ideas process to gather ideas for larger scale projects in the in the in Jenkins. And at the mark prepare the poll request for GSOC 2021 Oleg has confirmed that we have the ability to handle the financial processing that we need. There were some relatively minor limits that he described in the governance meeting last, last day or two ago, looks good. Any questions on Google season of docs. Mentor recruiting will be the same challenge there although mentor recruiting for this one because the projects don't start for quite a while mentor recruiting is feels to me less crucial. If I remember right the writing starts in June. We've got some time to time to gather. Let me double check just to be sure. Accepted Doc Delva Oh no, I take it back to technical provider hiring deadline is May 17. So in May we'll start it so yep we're going to have to do some mentor recruiting as well. Anything else there. Nothing else. Google summer of code so the pipeline steps docs generator project idea which is a coding activity that directly helps documentation has been added Oleg's also done a nice improvement to this you fixed a number of mistakes I made in the initial submission, and it's looking much better. That's a that's a great, great result. So, Kristen you're still okay with being a potential mentor for this on the assumption that you'll only only mentor one, not we wouldn't have you mentor more than one. Sure. I think the big thing for me is like there needs to be more than one mentor for project. Yes, that's a big catch I like there needs to be more than one person responsible for helping to do all this stuff because that's not a fun experience. Absolutely absolutely well and and with the world of coven 19 I absolutely don't want us to sign up for something that has only one mentor right that's that's just too risk right right. Okay, good. We do have another one related to this the rest API when that that feels to me like almost a springboard or piggyback on this same concept. So we've got two projects that are related to Google Summer of Code 2021 and a direct impact on on documentation improvements there's this. There was it automated special the automatic specification generator for Jenkins rest API that looked like it could very much use the same techniques as. Yeah, I think it's going to come down from I think it's going to be very similar like the beginning part to generate to get the information is going to be the same it's just how it's how the information is exported or like what you're doing after you basically assemble the list of all the plugins. Right. Okay, let's see so also already includes rest API doc generator into that. Anything else on Google Summer of Code. Okay, and I don't have any progress to report on the docs roadmap inventory. I've got to do the, I've still got contributed some of things I've got to do to get the roadmap updated on Jenkins.io. It will probably be several weeks before that makes any substantial progress. Any other topics before we close for the day. None for me. All right, thanks to both of you. Recording will be posted probably within the next hour or so day or two at most. Great.