 Welcome, it's Jenkins documentation office hours. It's the seventh day of April 2022. Great to have have everyone here and topics that I've got on the agenda news using crowded enterprise for localization Alex you and I spent some time on that. We had a question from Elizabeth on sponsored internships, and then we've started the she quote Africa contribute on and there are some topics about docs that I'd like to go over here and have invited a number of people to attend. Right now we've got, we've got peace with us, and I'm hoping that others will join as we proceed with the call. Any other topics that we need to add to the agenda, Alex any topics that you need to add beyond what are noted here. Okay. Welcome Elizabeth we've got a topic for sponsored internships on the agenda. I assume that that's good enough. Are there others that you need to discuss. We need to bring today. You're muted Elizabeth. Good evening. None from my end for now. Okay, great. All right, so then I'd propose let's take these topics in order and let's go ahead we'll add more topics if the time if time allows and we need them. So we released a new version of Jenkins on Wednesday. It's a long term support release. It'll be about a month before the next long term support release. And thanks very much to everyone involved change login upgrade guide or link there. Next topic then using crowd in enterprise so Alex, how was it how is it going and and what should our next step be etc. I think we have set up the platform level of plug in very well. I think you didn't encounter more issues with that did you know no no well so no issues. No issues for me at all it. It worked. I was able to integrate the changes. I think we did have the action still to decide if, if we want to approve something today right is that because I had seen a poll request and had approved it merged it I have not released the latest pull request but had released an earlier one. So I've still got an Italian translation that's not yet approved one small piece. And it looks like all the German are approved so they've been merged as far as I know is that correct as far as you understand Alex. Yes, that's fine. Okay, this week or last week I translated the last drinks and approved them earlier this week. And I think you already delivered this PR. Okay, so and we can see that here in the poll request so there is. Let's see it would show it as me actually being the committer right new translations here we go. That's you. Actually me but that's you. Right right that the misleading thing there is because it's using my credentials it is submits the poll request as me even though it's your work. Okay, good. All right. Okay so so for me that feels like. Italian still needs to be approved. And that's a task that I know how to do. Alex what do you recommend for next step so I could use it more plugins that I think I understand how to do or we could at least try it. Are there, we could demonstrate in an online meetup. We could propose wider adoption by email what what do you recommend next. We could propose something for an online meetup because writing it out and in the email group, Google thing would be a bit tedious and likely doesn't bring that much attention to it that I would like to have on it. Good. Okay, I like that and online meetups it's been a while since we had one so this is a great excuse to host one. Okay. I think we could do some demonstration to sum up what we did in the docs offer sessions on the online meetup to roughly go over crowded from a user perspective and leave out the technical aspect. Like how integration in the tank and see our organization would work. Right. Okay so so now in terms of how do we so I've, you've taken me through very, very patiently getting this registered. If, if there were 20 or 30 plug in maintainers who wanted to do this, or Jenkins, or even eventually Jenkins core. Would we need to have them be tutored by you as well or is there some more general purpose thing we should be doing. I think that the tutorial in itself has a tour and guide, if you have noticed that on the initial login. But I think it would also be better that I maybe with you can guide people through it. So people have someone to talk to if they have questions instead of relying on the documentation might make things easier to understand to get used to. Good. Okay. All right. So let's let's I've got an example group. Would it be worth. I've got an example group of a bunch of people who helped with French translations during October Fest 2021. That might be a good excuse for hey let's gather them together possibly even for a meetup, get someone from that group to join the English language meetup and then maybe they host one in French language of on their own. Yeah, for example. Okay. All right so an online meetup. Would you be okay if I propose that and put you as the primary presenter with me as an additional presenter and we'll do it together. Yeah, that would work out. Great. All right. Okay so that I can do. Now, in terms of, of the, how does the experience work would we continue using intellectual sites, or would we go to a different location, how would, how would the experience be for the Jenkins project in as we get larger and larger. I think one of the sites is my personal crowd and enterprise organization. I mean, I don't mind having a few Jenkins projects here, but in the long run, it doesn't make much sense having them on my instance just to carry them over on the Jenkins CI instance. Okay, if you would want to do that, we could request an open source license from current enterprise and use that for further demonstration purposes. And that would be, I hope, likely the solution we would use in the long run. We would request an open source license. And then, and that would then they then host, they would host something like okay so you have intellectual sites that crowd in dot com this might be Jenkins dot crowd in dot com or something else that crowd in. Yeah, for example, but try to enterprise support CNM records so we could easily point it to somewhere else. Oh, oh, okay. Okay, so so conceptually it could actually, they would still host it but it could be translations dot Jenkins dot IO or something like that or crowd in dot Jenkins dot IO. For example, yeah. Okay, good. All right. I don't know when you want to when you want to set set the online meetup up, but maybe we could request the license before and have a demonstration thing right in Jenkins. I think that would be the better approach instead of relying on my instance. Good. All right. So, so if we, if we better if we get the open source license, then establish the, the site and use that in the demonstration. I think doing the online meter because integrate one of your plugins or reintegrated design library that has fairly easy translation strings, right on the Jenkins CI or Jenkins crowd and instance. Well and design library is a great choice because we've got a very obvious place weekly dot CI dot Jenkins dot IO to show it to people. Yeah, and it's using continuous delivery so every time something merges a new plugin a new plugin is released so we get very fast fast iteration on the translation strings. Yeah, good. Okay. I think it might might justify us begging Tim Jacob to include Tim in the demo so that he could so that he could do the merge, and we could show live yes here's the merge. Oh and here it is released and congratulations now it will be available on see weekly dot CI in 24 hours, something like that. So one note on the open source license. Last time I had to request one. I had to do it as organization administrator. So it would be likely someone, what has to be someone from the governance board, I guess, which happens to be me so that's a good, good thing. Okay, so organization, and, and certainly it's a, that's a conversation for me and the board to have right they, they may have other requirements for open source licenses they may say you must be this or that. And we have to evaluate if we meet their criteria. Good. Taking it, I've taken a look over it. I think we meet the criteria quite well. All right, well Alex that's, thank you very much for that I think I am going to go ahead and add some more plugins as my time allows just because I want some more experience with it. But also I'll propose the online meetup. And if by next week. I haven't proposed it will talk about it in Docs office hours to remind me. All right. And let's assume I'm going to assume. I'm going to have six weeks from now, let's let's say four plus weeks from now, because I'm busy with other things right now and it's going to be a little tough to get all the things organized. Yeah, for the final date. Certainly some time to set up our Jenkins instance so I think for six weeks are fine. Okay, great. All right. Excellent. All right. Thanks Alex, any other topics on this one before we go on to other topics on the agenda. Not from my side. Okay, thank you. Elizabeth next topic was sponsored internships, and I'm sorry that I'm not able to help with them at this time I just don't have the capacity I've looked at it. I don't think it's a financial thing as much as it is my capacity to submit the proposals and manage them. That's fine. Thank you. Yeah, my wealth and thank you for asking. Thank you very much and thank you for the the boot camps that you're running and the you're seeking for internships that's really wonderful. Thank you. Okay, next topic was, and it looks like we've got Catherine and, and we've got Catherine and peace are both here so so that's that's at least two. Let's talk to she called Africa contribute on then for a few moments. So the she called Africa contribute on has started started April 5. And we've got project plan links here on community Jenkins.io. There are three projects were running inclusive naming. Let's see peace you are assigned to which of those sorry I've got a look inclusive naming. Oh good so you and you and Catherine are both assigned to inclusive naming very good okay so we can focus our conversation today on that project. Very good excellent. Oh and it's right here I should have read down below here we go. Catherine are both on the inclusive naming project very good. Alright, so. So, what we've, what we've got there, what we wanted to do today is meet one another, introduce each other, say hello, and then talk about startup activities to get ready to do that. And for inclusive naming. I think what we could talk about is. Oops, now my fingers. How to divide us. How to divide the work, the work between the participants. So that you don't trample on each other as you're doing doing research and I'll talk about some ideas there. So I've got some startup ideas, and then I think the most crucial one is how to divide the work. Would that be okay for you piece and for you Catherine. Yeah, that would be okay. Okay great well so then let's, let's have you introduce yourselves and so peace why don't you go first tell us something about yourself. I would love Catherine to go first because her name says we'd see. Sorry, I'm not very good at alphabetical sorting. It's obvious. My name is peace look out for. I'm in Nigeria. And I'm actually a technical right. Who loves coding. I love everything about coding and I'm, I came to learn more about coding documentation and test API testing. And our house I also want to know more about contributing to open source. That was why I am that that was why I applied for the contributor and I'm so happy to be a thank you very much. Great, thank you peace and delighted to have you here and lots, lots to do Catherine would you like to introduce yourself. Yeah, I'm Catherine hero, currently based in Nairobi, Kenya. And I'm glad to be here I, I was looking for to join contribution and I'm kind of content developer, technical writer and front end developer and technical writer. Yeah, so I joined contribute on because I've been curious about open source. And I figured since I already have skills in technical writing, then learning about documentation would be a great would be a great way to start contributing to open source project. So I'm looking forward to learning a lot. Excellent. Thank you. Thanks very much. All right, so the inclusive let's let what I'd say let's take next is let's look at some of the start up start up activities that peace and Catherine will both need to do as part of getting started and getting ready to help with inclusive naming. The inclusive naming project is trying to to replace less inclusive terminology in the Jenkins projects strings and software and documentation, like master slave whitelist blacklist with more inclusive terminology controller agents include lists deny lists, those kind of things. So, so it's a it's a hybrid of software and writing and the hybrid nature of it makes it interesting because we need the help to make those changes and part of the help is finding where to make those changes and checking that the changes make sense and are workable. So, all of them have certain startup activities. One is for instance, you need to download Jenkins and download Java 11, and then use Java 11 to start your own local copy of Jenkins. This runs on it works on Windows, Linux, Mac OS. It runs on hardware that says small as it actually can run on a Raspberry Pi. It's a little bit constrained memory wise on a Raspberry Pi but but certainly on a Windows computer with two or four gigabytes of memory it should be just great. You'll use that to get some initial experience you could do tutorials you could try your own experiments the idea is just become familiar with it then you stop it and when you need to run it you start it again the same way and it will remember what you did. Another part that you need to do is you need to create yourself a GitHub account and please record it in this spreadsheet under the GitHub GitHub ID column. Because the GitHub ID column helps me know how to identify you when you're on GitHub. So add it here and you may have to add it as a comment I don't know if giving if I've given you right permission to it. So just be sure that you've, you've added that when you've got your GitHub account. Then you need to create a get pod.io account. And the reason for this. Many times. Okay, and we have to note that it was last year's experience that taught us this. We use get pod.io because some frequently contributors don't have a big enough machine to do documentation writing on their own computer. You could ask Xenob who's with us right now about her experience two years ago in Google season of docs when we gave her the impossible task of running, running on a Windows computer with very small, small space and it turned out it just didn't work well for her she had all sorts of heroic efforts she had to do didn't you Xenob. Yeah, that's that's very correct mark. So it was a lot. I had to install a virtual machine on my PC to be able to run Jenkins that I like to install. I was trying to use. I think it was the BSL something, but I was having issues. So, so many issues just kept popping up I just had to opt for a VM on Ubuntu VM. I was able to run it for is is really, really great like compared to all that stress, because for me I was able to set up GitHub in I think less than 10 to 15 minutes. It's it's pretty pretty straightforward. You don't have to get out of your browser. You can operate the IDE from your browser you don't have to install anything on your PC. I knew what I was setting it up so compared to my experience three years ago. This is so much better. Thank you. Thanks very much and there is a link here to a video tutorial on how to do that. It's actually documentation office hours from earlier this year, where John Mark Mason showed people how to do it so you'll you can watch this video, follow the steps that are in this video and it will have you configured and running able to see that. And if you have questions, ask them on Slack, we're happy to answer questions. Okay, so we've got those three, three steps, download and run Jenkins create a GitHub account and create a get pod.io account that Catherine and and piece both need to do. Then the next topic is this one. This is one where I want to actually consult with you Catherine and with you piece to see, would this idea that I've got of how to do it be workable for you. So, so this is the part where we sort of start asking I need to ask you some questions and offer some ideas. What I was thinking of doing is mark create a spreadsheet of Jenkins core and plugins. And then you'll sort by number of plugin installations. And then each person. So, peace. And Catherine enter their name next to a plugin when they are starting on that plugin. You clone that plug in you clone that the source code of that plug in. Then what you'll do is search for problem strings in HTML, replace them because HTML is just text text files. It's jelly, and it's mostly replace them Java, and there it's more like sometimes replace them. And this is where you'll have to you'll have an experience of working through what it means to deal with each of these kinds of strings and we'll take you through those. And after you've searched for one you may submit a pull request commit them and submit a pull request. When we get to jelly. It's, it's more complicated, because you have to compile them test them commit them and pull requests. Now that's an awful lot of detail for welcome first step one oh one for the very first step. And Catherine, are you okay with the idea of using a spreadsheet to help separate who does what. Yeah, I think that's a great idea. And if anything comes up later I think we'd be able to make changes as we start. But I think that this plan already works for starters. Okay, great. Thanks Catherine so peace what about you do you think that will be okay for you. Oh, we just lost peace okay so we'll have to check with peace later. So, Zina, based on your experience, does that seem like a workable process or is there something that we should, we should adjust there. No, I think it actually works. It works. The only thing is for them to remember to keep updating the sheets so that there is no conflict because if you start working on a plugin and we don't update the sheets someone can pick it up so it's very very important while it's really good it's good and get really messy if people are not updating it. Good. Good point. Yes, very good. Just to add on what Zainab has said, maybe we could agree on a number of plugins we can start working on. Then we assign the person who is going to work on them before we start so that no conflict as we proceed. That's a good idea, pre assign an initial set of plugins to to each person, right, and say okay you take these you take these, and when you've run out of those. When you're finished with those, then you could start putting your name yourself that's a very good idea I like that. Okay, that makes sense. Yeah. I think that's something I could do I did that. I did that last year, and it didn't seem harmful when I did it. So let's, I think that's worth trying good. Okay, any other recommendations. Okay, so that's it. Great comes up I can always send you a message on Slack. All right and peace is does this seem to you like it will be okay that creating a spreadsheet of Jenkins core and plugins and then having having the two of you assigned to rows of that spreadsheet so that you'd be assigned a set of plugins would that be okay with you. Yes, I think it's okay with me. Great. Okay. Now, now one of the risks here is and it's it's part of the challenge of open source is there's no promise that we'll get reviews of the poll requests. We have to ask for them right so and and we'll do that. So it's, it's just part of the nature of open source that we will submit poll requests, we intend for them to be valuable and usable and, but we can't guarantee that they will be merged that's we'll keep working on it. We certainly will attempt to use my influence to persuade people to maintain them are to to merge them and to review them and we'll do that as best we can. So that that feels like a good process then the next piece for me I think would be planning how we're going to meet regularly to be sure we get you started successfully and and which pieces will work well for you. Since the people we've got here today are related to inclusive naming is would Monday afternoon your time be okay, or would is is late evening better for you, what what times of what times work better I assume you've got regular jobs and so you're probably not available during your working day. So do you want is evening okay your time, or is there there another time. Okay, so for Catherine evening is okay. Great. And peace, how about you. Well, I feel even is okay this by this time the time we started today. All right, so this gives us so start time of Docs office hours was okay for you. Good. All right. That's very good because that that avoids most of my meetings during the day by being at this time. So, so Catherine, if we were to meet at this time on Monday, or on Tuesday, would that be workable for you. Yeah, that's fine. Okay. And, and peace. Same question for you would that be okay. Yes, it's great. All right. So let's just plan that I will, I will set the calendar agenda calendar item. Mark to schedule the calendar item. And with both of your permission, I will send you an invitation to your Gmail account from that calendar item that means though that your Gmail email address will be visible, or maybe visible in the calendar, are you okay with that. Yes. Okay, Mark invite both to the meeting. Okay, great. And I would also like to invite our project manager to the meeting. She is. Oh dear, I have to get nafisa GMO. She may not be able to attend but I'm going to invite her anyway because she'll be helping me assure that we do these things successfully. Great. We will plan for that then. Thank you. Yeah, if you are also going to be working on spreadsheet, I think it's a bit great for her to be involved in that process. She's probably doing some work on the spreadsheet and monitoring it, monitoring the progress on that. Exactly. That's what I was thinking as well. I think that Zina is that is that that's something where we can have her help. She can also help us with seeing how the data is going. We may have her do things like track which pull requests have been submitted and how they're, how they're progressing just because that way we let peace and Catherine focus on doing the work and nafisa can worry about tracking and how, how are we progressing. Yeah, exactly. Great. All right. That covered all the topics that I wanted to deal with on the inclusive naming project. I'll send those invites. I've got to meet separately with nafisa about the project manager because tomorrow we want to do a blog post. So peace and Catherine I think I've got both of your pictures correct is that right. Yeah, I'm going to pull in the slide deck. I think I've got it here. Where did I put that slide deck. I just wanted to have one more chance for you to tell me yes it's okay. Here we go social media covers this one. So here is the image I've got GMO GMOs. That backwards don't I isn't that's her first me. Oh, I'll have to check with her. So Catherine you're okay with your photo. In peace you're okay with yours. Yes. Great. Thank you. All right. Mark, I wanted to erase something you mirror. I don't know if miracle reached out to you. She dropped out to say she had to drop out of the program due to an emergency she had a home or something. Oh, oh, okay, thank you know I wasn't aware of that but knowing that she has to drop out I'll just take her off the list and if that's okay. Yes. Great. All right, done. Thank you. Let me let me have a better better layout as well. Excellent. Thanks. Okay. I think we covered the topics that I wanted today. Any, any other topics we need to go over. I just wanted to ask a question. I remember we spoke about I think I raised some time ago about by weekly sections want to be having where want to address different topics. So I was wondering if you'll be open to speaking at one of the session about github, because I know you're a pro at github, maybe give some tips on how they can use github to contribute to their various project is not going to be for just Jenkins contributors, but contributors within all the organization so yeah. Sure, sure, I'd be happy to do that you let me know. So and I apologize for my poor poor late linguistic skills. Does biweekly mean two times a week or every two weeks. Every two weeks. Okay, thank you so I admit it I'm an English speaker but I never remember which of those it is so that's every two weeks right. Alex no grinning at that comment that's that's cheating that's totally cheating. He is a German speaker and he knows it better than I do I'm sure. I'm not correct, but I know that what I'm trying to say is every two weeks, I'm also correct. Okay, so I would be happy to talk about github and do a question and answer session absolutely happy to talk about using github to contribute to open source. Yes, so the first session is supposed to happen on the 23rd of this month. It's on a Saturday. Okay. So we're thinking of doing it say sometime around the evening of Saturday. That's evening Nigerian time. So I don't know if that will work for you. It will that would be that let me double check my calendar but you said the 21st. 23rd. Okay, so 23rd on my personal calendar is open. That would be fine. Okay, so Saturday. Saturday, April 23 evening Nigeria time. Yeah, Africa time. Okay. Africa is too big a place Nigeria time. Okay, great. All right. I would I would propose to talk about the web user interface. And the command line because those are the two things that I found very helpful and here we'll talk about pull requests and templates. And, and then reviewing changes and CI job checks and continuous integration jobs. I can talk about those. All right. Thank you. I'm just going to come back to this note later and take out this content and just use it to create something before then. Sure, you bet. All right, thank you. Great. Let's see what are some other things like that for King repository. Oh, yeah, those kinds of things great updating repository. Great. All right. Any other topics we should discuss today. None from me. One point with the license. Oops. Yeah. Would you request one or bring it up in the next governance meeting. I'll start the question even before that so I will start an email thread with the governance board. After I've, after I've checked their terms and conditions. So if the license terms are easy, then at meeting I see nothing that causes me any red flag. I'll just ask the board for permission. Yeah, I think it's like 10 or 12 points. Yeah, major and possibly give grant me manager access on it that would make the demonstration much easier. If that would be possible, that would be quite nice. That makes I think that makes good very good sense. That makes very, very good sense since I think you're the most experienced person we have on it. Great. Okay. Anything else on the crowd in topic, Alex. No, think we got everything covered here. Okay, so Zina, you may have missed the early part. Alex has taken us through a way of doing translation into other languages, much, much easier than we've done it before. So for people who speak French or in Alex's case German or in my case some limited Italian. We can, we can do the translation process into those other languages much easier, thanks to open source donations from this company crowd and enterprise that provides tools to do this. All right. I think we're done for today then a record a copy of the recording will be placed on community Jenkins.io within the next 24 to 48 hours. Thanks everyone for being part of the session. Talk to you on Monday, Elizabeth and peace. See you then.