 This is great, I'm glad there's so many people that will be presenting, but yeah. Yeah, so and I can do an overview of Contribute Summit that I think is a worthwhile thing for us to discuss. There are still plenty of things that I think we need to discuss as specifics to docs. Things like, I think we need two sessions, one that suits the US West Coast. So late in the day, and one that suits Europe and Africa with the benefit that your time slot fits reasonably into the Europe and Africa time zone, because it's it would be about this time. So that we can fit Zenab's work schedule. The idea then, if we need a third session for Asia, it will probably be under the guide of the Chinese localization SIG, and Rick will lead that session and Rick's already agreed to be involved and to present and so. We've got the we've got his involvement, but that will focus of course on Chinese not on not on and probably be done in Chinese language, not not be focused on specifically documenting English language or multi language. All right. Yeah, so what I'm going to do is I'm going to start sharing my screen and let's go through topics and then. And then we'll, we'll go from there that way we're not just sharing a an empty screen. All right, so my screen here. And let's make it big enough to read. Okay, so. Okay, so what I've got is contributor summit is the crucial thing. There are some other topics that I think are worth noting. The progress should not drop off our list. Because I really do want to get scaling Kubernetes merged, but have been busy with other things we should also include Google season of docs. They've now they've launched a new program. It is a different thing and we'll we should discuss further than past years. I saw that there was a an email or a call for contributors already and I was like it's very interesting like already. Exactly yeah and that and that is impressive now. Xenob had a topic on mentoring for she codes Africa and I hadn't do we do I guess without her we probably don't get much benefit by talking about that. So the product from what that was like there's a link to the website where there's like a, they're writing something similar to Google. Summer of code where they're sponsoring women contributors to open source in Africa, which is really, really, really cool. And they're looking for open source organizations who might have topics or things that people can work on. Maybe something to look at as like a larger. I'm not really sure if that's like a document. Maybe it's not like really documentation but it might be worth it to look into encouraging people to are encouraging women who would be interested in that like to look at some of the things inside of Jenkins. So, okay, good. All right, any other topics that are hot on your that are on your list or should be on the agenda. Um, no, I just looked at I need to read the agenda from the day below. So it looks interesting. Yeah, sorry that it's complicated right with two office hours in a week it's like right. I can't just read the day the preceding notes I've got to go. Exactly. All right. Okay so first proposal then is cancel this meeting next week in preference to the contributor summit. We actually this will be happening this meeting would get be scheduled to happen after the summit, but by then I will probably completely burned out and unable to enable the function and therefore I propose we cancel. Do you object if we cancel this next week to persuade people to attend summit. That's fine with me. Okay. Great. All right. So, we've got summaries from the governing board and special interest groups already agreed so, for instance, Daniel Beck will talk on security. I'm going to be a better name on infrastructure. Tim Jacob on release. I'll talk about docs. Alyssa Tong has agreed to talk about events and advocacy. It will be three to five minutes we hope no one will spill much beyond that and I'll actually be fairly rigorous in holding us to that so that we don't burn up all of our time in the first session for status reports. Then we've got Rick with Chinese localization already confirmed. If there are several others that are confirmed as oh yes Cara de la Marc with Google summer of code and cloud native. And oh and me with platform so we have a full agenda for the first 90 minute segment and then a after the 90 minute segment we will have a 30 minute. 90 minute presentation segment will have a 30 minute organizing segment. And in that organizing segment the track leads will identify their participants and find a time. Find times that work for the participants. When I checked yesterday we had 30 plus registrations already yesterday. So Kristen I haven't seen your registration yet. So I would love to see that. All right. That's actually a good sign right because the people that I'm confident will be because I haven't seen Zenobs registration either. I haven't seen one from Mike McRoberts or from Vlad Silverman so our regular participants haven't registered so we're going to have more than the third more than the 30 registrations. By the time we're done with this. So that's that's good. And then documentation, I think the proposal was two tracks. One for Europe and Africa. One for Western US. And we'll just rely on East Coast US fitting reasonably into the Europe and Africa time. Then Chinese localization will cover another. We won't do the pipeline authoring segment I talked to Liam Newman about it and he's, he's not ready to do it and I'm not sure we don't have interest yet to do it. But we may combine security infrastructure and release into a single track called securing the delivery pipeline. Okay. That's an interesting topic and we've got several Olivier has agreed that he's willing to lead it if others aren't available. And I'm also checking with with other people to see that they're ready for that kind of a topic. Let's see so then in terms of on the documentation side some of the hot topics search for the dock site. And the plugin site is currently being invested by investigated by Gavin Morgan. So site site internal search. There's the Google summer of code project for rest API generation. Ultimately it will deliver something that's valuable to docs. So is of interest and docs inventory is the big initiative that I am trying to lead which is and categorization where we take what we have now. The current content including wiki and try to slot it into places in the book. Okay, place place it place the content into the book basically creating a table of contents for a book that a thing that does not exist yet which is the full collection of all the information and and the idea being that will help us detect. If there are gaps gaps in our definition of the sections. So let's call them chapters so we use book terminology detect overflows in in chapters. Hey if one chapter has 10,000 pages in another has three that that would indicate we've got too much information in one place and not another, those kind of things. And then that for me would already be a dramatic accomplishment as optional. The idea was prioritize sections for focus by our value or by our, our perception of which things would be most useful. Okay. Let's see. So, do you have any questions there in terms of those ideas around docs inventory and categorization. No, I do know we have the do, are we going to give us I actually kind of really know where this is, but like a status update on where we are with copying over. Like I know Gavin wrote that tool to be able to do plug in. Was it plug in documentation migration right right yeah that's that's a that's a very good thing to give a that should be included in the status report absolutely so the plug in migration plug in migration plug in docs migration status reports. Maybe what we should do is put, put that up in the, in the docs thing here because it's plug in migration status report. That's a great story, by the way, it's amazing the results we've achieved. Thanks to and then plug in site improvements that Gavin has done are just absolutely delightful. Exactly. Okay, so plug in migration status report wiki migration status report. All three of those I think are good, good components of the initial, the initial status report. Good. Okay. Then, let's see other. I think, I think, well, any other questions on on the documentation tracks for contributor summit. I thought I can go right now. Okay. Welcome Zenab. Hi. Great to have you here thanks for joining. Sorry, I'm late. We're delighted that you're here. That's wonderful. Thanks very much. Thank you. So we were just discussing Jenkins contributor summit next week and had agreement that we would cancel this meet this meeting. Let's see, am I sharing my screen Kristen. Yeah, yeah. So we'll cancel this meeting next week, so that we can be involved as much as possible in the contributor summit. And then we're reviewing what the content of my presentation will be. I've got three to five minutes during the first session to present a status report on dogs. Oh, right. And there's another one. And then we should probably in, in the next phase put Google season of docs plans and how we'll handle their, their, their new processes. Okay. So, Zenab, were there any topics that you wanted to be sure we got on the agenda today. I can talk about contributor summit for a very long and embarrassing amount of time, but there may be other things you want to be sure we address. Yeah, so in the last meeting I had with Kristen, I mentioned something about a program we're planning at Chico Africa and open source boots come. And I don't know if it is something Jenkins would like to be part of. So we're currently, the program is actually supposed to start in April. So we're looking for open source organizations that could sponsor and also mentor the participants for a period of four weeks in April. And so can you tell me more about what spawn what I think I understand what mentoring means it probably means coaching on code. Tell me what sponsoring means. Okay, sponsoring means providing funding that we use to pay the participants at the end of the bootcamp, because we intend to give participants a stipend of $500 or $1,000 sorry that's my head. There are about, I think $1,500 I'm not 100% sure, but we're planning on taking in 50 participants, and we plan to give the top 10 participants. We're going to be using the university nano degree courses. So the funds that we plan to that we hope to get from sponsors will be used in funding all this. So we have basically two sponsorship tiers. The individual and corporate individual is between 500 to $1,000. While the corporate tier, which is broken down into from growth platinum is from $1,000 and above. So yeah, that's just like summary. So, once an organization, if an organization chooses to sponsor, then we'll also advise that they mentor the participants they are sponsoring, but it's not compulsory that if the open source organization probably might not have the time or the resources to mentor the participant then we'll look for the open source organizations to mentor them. Okay, so I think you're you're already getting on to then the so sponsored. I think I got it captured correctly. The sponsors provide funding to that then will be used to pay the participants. And I assume the participants are there in Nigeria or is it multiple. Okay. Okay. Ladies, ladies all over Africa. Okay, and, and tell me more about how the, how would a sponsor transfer the funds to she codes Africa. So for instance, I may have an interested corporation that would want to participate but they'll need things like how do we transfer the funds, etc. So she could have currently has an account where we accept us the payments through cards. That's how we accept donations to she could have with her currently. So, if an organization chooses to sponsor I'll just send them into where they can make payment in the invoice. Great. I think it takes a one. It's not just USD. It takes a couple of other currencies, but I'm not really sure. Okay, great. But it but it does take, it does take donations in US dollars. Yes, it does. Great. And so starts in April. So you need to need the funding funding established by mid March by end of February. What's what's your timeline. So, I wouldn't really want to put so much pressure on you, especially considering the fact that I'm just raising this, though, it's because we've not been able to meet for a while and I wanted to mention this in person. So I, so I don't know as early as but preferably before mid March. So when we are making selections for the participants ending of March we know the number of participants we can take. So we don't take more than the available funding. Then also know the mentoring organizations that we participate in so we can use the requirements select participants. Good. Good. Okay. So, so the idea is at end of March you'll choose the participants to fund and you do that based on the amount of funds that are that are available. Okay, got it. And also the mentor mentorship availability. Okay, also need mentor available. Okay, good. Now and tell me more. So this is an open source boot camp. And so is the idea to introduce the participants to contributing to open source projects in specific ways like purely coding or is it okay to be contributing in documentation. Tell me tell me more about the the meaning of the words open source boot camp. Okay, so we wanted to be in all areas documentation design coding. We don't want to limit it to coding so we can have ladies from different tracks different fields be able to participate. Because that's the idea we're trying to promote that open source is beyond coding. So that's the first part. Then the second part is it's like we're trying to it's something like Google season of dogs, but not exactly the same in the sense that with duration shots are one, it's just for ladies in Africa alone to then the open source organization that wants to mentor would be required to fill a form, a project idea form. In that form, some of the information we require project details that the project the participant is going to be working on, then probably if maybe if it's a project that requires some skill level, maybe like requires proficiency in Java, then you kind of let us know the level of proficiency if it's a beginner intermediate or expert, things like that then the number of participants that you also be willing to mentor for that project, the details, things like that. So all these requirements are now what we used to select the participants at the end of the day so that number one the learning the time the participants we used to get familiar with the project will not be too long since the bootcamp period is short. That's one of the reasons why we are doing that. Very good. Okay, so. So project ideas submitted by the sponsoring organization so at least for for what I've seen with Google summer of code project ideas are wide ranging and can can be difficult to extract we've got I think seven or eight right now for Google summer of code as ideas we've had as many as 10 in the past, but not a lot more than that. And when you say four weeks so it'd be a four week project is that four weeks of the person working full time for weeks working 10 hours a week. What's your. Walk in full time. All right. So four weeks full time. For the, for the, the, the sponsored. What would you call it for the participant. And then assumes four weeks of I assume like twice a week mentoring. Yeah, twice a week mentoring exactly from the mentors. Okay. All right. So, um, yeah, I think then also at the end of the bootcamp. The mentors will feel like an evaluation of to evaluate the participants and the whole program. If there are ways we can improve, then also erase the participants so that it will and you'll be required to score the participants. This will enable us to be able to select the top 10 participants at the end of the day for the nano degree courses. And the score will also be based on how complete you feel the project is or how well the participant was able to work on the project and things like that. Yes, and the participants will also feel an evaluation of the open source organization mentors, things like that just tell us their overall experience work on the project report also just like summarize and let us know what they were able to work on during the four weeks and their experiences and things like that. So all this half forms that are ready so when it's time, we just send them to the open source organization for them to just see me. Great. All right, so for me the challenge here is the, the financial sponsorship piece, the Jenkins project available funds are quite limited but I may have a potential corporate sponsor that has more ready access to funds I can certainly let me do the following let me bring a. So, so when we talk about your two sponsorship tiers so the individual tier and the corporate tier, where would an open source project be considered in the corporate level or is there a different level that I didn't note. So, I'll share a doc with you that has full information. So, we have the individual tier, which is just $500 to $1000 that's one level, but under corporate we have bronze silver gold and platinum. So, bronze is from $1000 to, I think 2000, then and so on, and so forth to platinum that's $5000 and above. So an open source organization can choose to sponsor from any level. Okay, I see so open source. Does get a link to the doc right now and share with you. Great. Okay. There's also. There's also a site, I'll share the site with you also. Okay. Okay, so I'm going to you're okay if I put that link into the into the Google doc here. I like that name contribute on I'm going to steal that great word. Thank you. I'm sending the sites now. So, got it. Right. So, Zenab anything else you'd like to it feels like what what I would like to take as an action item personally is marked to check with friends at cloudies. See if they are willing to sponsor. I think it's worth checking other other potential sponsorships as well it seems like a great opportunity to, to consider it and I'll beg Kristen to chime in with her voice when I send the copy her on it so that she's aware that we're we're suggesting hey here's an opportunity and here's what what it would require. So, like some of the, like some of the women groups to and, but I just know of to see hopefully to kind of like pass that along. I don't know how if any if they were able to continue to other open source organization or other open source projects or other their companies that I did pass that information along to a couple other groups to. Yeah, good point. And we may want to discuss with Cara de la Marc. She's running a an organization somewhat like this in in and around London. I don't know if they're London experience I don't remember the name of the group she's running but it's something similar where a focused on getting people into tech and getting them, getting them, letting them experience it firsthand. Okay. I think I may have interrupted you. Was there something you wanted to tell us. Um, so I just wanted to mention another suggestion for projects. So other areas also that would like things around community management. So probably you wonder could help you manage your developer community or manage content maybe your social media accounts. Things like that maybe Jenkins presence in the community in the open source community at large, probably like a dev advocate or something. So give me some more more description there I think that sounds very interesting. I didn't have my volume quite loud enough so it was should could someone from she codes Africa assist with Jenkins advocacy is that what you're saying. No, so what I was saying is, say, if Jenkins decides to participate as a mentor position, the project idea, like a side code side documentation, other projects ideas could include dev advocacy or community management, probably managing Jenkins presence in the open source community at large, your social media presence, things like that. Also, I also project ideas that people could work on during the four weeks. Now I understand. Thank you. Okay, that's good. Alright, so it's, it's reinforcing reinforcing that there are many areas to contribute to open source that are not code. Exactly. Okay, good. Thank you. Okay, so, so it feels like what what I wonder should we maybe we ought to put this as a topic for discussion in the contributor summits advocacy segment. Because wouldn't this be an ideal place to bring to Alyssa Tong and to markie Jackson and others who are working on advocacy to say, Hey, here is here is a vehicle that could might be able to help with advocacy. And, and it's a place where we consider spending to support advocacy so agreed. Yeah. Yeah, so let me, let's. I think what I'm going to do, Z knob is I'm going to bring up the, the, let's see the contributor summit agenda draft, and I'm just going to put an entry into it for, I think I may already have a track for advocacy, if I don't. Nope, I don't. So let's create one, because it's a good Jenkins advocacy. I don't know who we will have lead, I would guess Alyssa Tong, or markie Jackson. But suggested topic seems like a hot one which would be she codes, Africa. It's a four week mentor mentoring program beginning in April. And that's where Z knob we would probably have you explain it to them in a session, talk to them about it. And, and so this was, let's call it mentoring. Yeah, so, and now I'm just going to take that out for now. And take. Okay, so this thing. It's target audience here is Jenkins contributor Jenkins users Jenkins administrators and potential. All right, so, so, at least for me that one's a candidate, if whether or not a track gets staffed will depend on interest, who's willing to attend the track and participate. So, I'll let you weigh your decisions on, hey, should you participate in that one and or others depending on your available time. Okay. Okay, so let me put a note there that added to the added to the contributor summit draft agenda. Is there more that we should be aware of with regard to the contributon to the she codes Africa effort. Oh, no, that's it. Okay, well that's exceptional thank you very much for sharing. That's really great. Thank you. So poll request progress, I still have not made my progress on scaling Jenkins on Kubernetes and probably won't for the next two weeks because of the contributor summit. My apologies will continue. Google sees docs is coming. You know, I was curious, are you interested in acting as a mentor. Are we, let me ask to this group the group of the three of us, are we willing to act as mentors for a new Google season of docs participant project. Sure. Go here as well. That's wondering. Oh, good point. I was wondering, is this going to be a shorter period of time like some of the changes that we've seen for Google summer of code. Is this like a another like a shorter. I think this one actually they made it longer and dramatically more flexible longer in the sense not of not of amount of hours expected but of duration and dramatically more flexible in that if I remember correctly. Google will give the money directly to the open source organization and the open source organization then pays the, the person that does the writing. Okay, so so it's, it's a different. It needs needs more investigation. More understanding because I don't know that the Jenkins project right now has the correct type of account to receive the payment from Google so I've got to investigate that with the governing board. Yeah. Okay, that's a good thing to bring up also. Maybe the contributor someone would be a good place to try to come up with some ideas. Right right exactly yes. Well and that for me fits in the, in the docs portion right we should be sure that that the docs is covered there in terms of summer of docs 2021 and show what what would it mean to participate. What are the requirements etc contributor summit topic. Good. Very good. Okay. Anything else on on either any of those topics. Nothing else for me. And I don't think I've got anything else. So it feels like we let's let's put it here let's put let me put a summary on this so she codes Africa. Contribute on and contributor summit and the summit. Okay, and we agreed we will cancel the 25th. Contributor summit. And so the next meeting where we'll actually meet is in March sometime and now I need to look at the calendar. So March the fourth. All right. I think that's it I'll archive the post the recording separately. I have to highlight to the two of you something we did in the last session in the in the US West Coast session. We added help to a pipeline plugin. And it was it we did it live and it was a lot of fun and we realized that that particular thing we were working on was especially challenging and needs a video recorded to show people this is how you do this and this is how it's it's actually pretty easy to do but you have to be aware this is how it's done. Right. Yeah. Because it's like adding any type of help text to anything inside of a Jenkins plugin right because it's following. Exactly except yeah the challenge here is I read I see a page here right I see the page. The complication for me was I see this page on. Oops not this page I see this page here the pipeline steps reference and I think oh okay this is just some ASCII Doc somewhere that I that I can go edit this directly. And oh here's this thing that I click this and it must be a page I can just edit I can improve this thing. No I have to go inside the plug in that contributes this thing. Yeah, I have to submit a pull request to that plug in which is really a cool hybrid between code and documentation, but it's an it's an atypical hybrid. So, so it was a it was a fun exercise. Right, I guess the positive thing here too is now that you've added that documentation not only will it show up on the page it will show up inside of Jenkins as help. Right, and that's, and that for me is the explanation it's like, look, publishing the documentation on a web page is is good but it's much better that it's inside the user's own Jenkins installation and and more and more people need to know that it's available there so this was fun. All right, anything else before we end. Okay thanks, and I will talk to you at the contributor summit. Thanks very much. All right, thanks y'all. Bye. Bye.