 Okay. Welcome everyone. It's docs office hours. And we are being recorded. Please remember we have the Jenkins community code of conduct. I'm going to go ahead and share my screen and let's take a look at the agenda and put things on to it that we need. Okay. So all I had put for today was question and answer. Oleg and I went through a series of questions and answers. This morning in. Oh no, yesterday morning in docs office hours, Europe time. And what we did is we put the answers into the notes here. So we can review those and be sure that the questions we had on Monday are adequately addressed here. So that was the, that was the topic that I had was be sure that we follow up on the 29 June questions. Are there any other topics you would like to include Jonathan? No one. Okay. So let's, let's walk through the questions and be sure that we've got a combined understanding. So what. Let's see. We, I confirmed with Oleg and he, I talked in more depth about community bridge. And community bridge very much is on his mind and he's actively seeking funding to do in addition to Google season of docs, a community bridge project. Now, one of his concerns is that we've got to be sure we have enough mentors in the, in the Jenkins community to ready to support a community bridge writer. So, so that's in addition to the funding, we've got to have mentors who are willing then. So any question there, Jonathan. I think we're going to have an hour. Let me think you, you showed us the mentor issue. So for example, next year I will most participate, but the next year I believe the help you in the Jenkins project. I know more, I will be no more about Jenkins. So maybe next year I participate as mentor. That would be and that would be exceptional. We've realized that the most precious thing that we can receive in terms of people's contribution is their time. And mentoring Google season of docs, we're expecting will take roughly the same kind of effort that is required for Google summer of code. And that's from four to eight hours per week. And so we want to be very clear to the mentors. This is what you're agreeing to do for a period of 10 weeks. It'll be a great result that comes from it, but you need to understand that it's, it's not. This is not a trivial amount of time that you're going to contribute. Yeah. I believe that. So he is my friends too. All right. So then reminder on the timeline, July nine. So we're six days away from the application deadline. Recommended to submit on July eight so that you're absolutely sure it made it on time. Then from July nine to July 31. The Jenkins organization will review the, the final proposals and select them. And then they'll send their selection onto Google. So at, at July 31. The selections will not be announced. They go to Google. Google reviews the proposals. And then August 16 Google will announce the selected projects. Oleg agreed with my answer from last from Monday. Can an inexperienced technical writer be part of Google season of docs. An inexperienced as in no Jenkins experience. Absolutely. Not a problem. Inexperienced as in no technical writing experience. Yes. But it's a little more challenging. So, and he, he refined my answer. Said it's focused on technical writers who are interested in working on open source. So in terms of status report on proposal reviews. Proposal first proposal reviews are done. So. Done as of. As of July, I think I finished July two. And so, and I'll, I'll visit visit the comments again to see if, see how they're going. But if you have, if you have submitted a proposal and haven't received feedback from me, I left at least some comment on every single proposal. So if you have a proposal and I didn't do feedback, that means I'm not aware of your proposal. I need to see it. Any questions there, Jonathan. Yeah. And it's about my proposal. And you sent a comment. Asking for an application about the term I use a task force. It's not a normal term to you. So it, it. I make, I make miss. I, I clarify to you. And that, that answer. Make sense. Right now. Okay. I think so. Yeah, I will double check. I haven't been through the reviews today has been focused on fixing a bug in, in blue ocean and a bug in other places. So I will, I will do a review just to be sure that I've seen it, but I saw your comment. About that was explaining and it seemed reasonable to me. Yeah. It's a car. Like a sprint, a finding sprint to put all your efforts to do something fast and well done. Okay. Okay. All right. So then. The question on long running project. So long running project after the discussion with Oleg, he confirmed that long running project is a decision from the person proposing the project. They are saying, Hey, I would like to do this work over the course of about six months instead of 10 weeks. It's also asking for the mentoring organization to assign mentors for the entire six months. So yes, it's both. And if the project proposal does not say it is a long running project, we will assume it is not based on what we read in the timeline. Then are there shortcomings for long running projects? Our, our answer was not that are specific to the nature of long running projects. They are an option. They are neither advised nor discouraged. You could, if you, if it fits for your needs, we can support either type. And this one application should specify if it wants to be long running. So the question was, can a project proposal specify alternatives? Yes, you could say, Hey, here's it described as a, as a regular project, or here's it described as a long running, I would think the projects are quite different regular versus long running. And to use your, your sprint metaphor, Jonathan, the way Oleg described it, he was assuming that a regular length progress will be a regular length project will be more intense than a long running project that it's, it's a higher intensity of effort for that 10 week period than the comparable effort spread across six months. Okay. And then the question was, we had one about, hey, what if things change like environments, or we really, we learned something and realized, Hey, this is this needs a completely different way of approaching it. Oleg and I talked through several different scenarios. And he first immediately acknowledged adaptation is allowed and accepted even, I'd say embraced, right? It's, it's welcomed. Who do we inform of changes and that depends on the type of change. So minor changes stay right inside the project team. No one needs to be notified outside the project team. So the mentors and the writer. Significant changes should be notified to the organization admin. So in this case, I think it's Oleg and Markey. So that they can help if they need to. That's so for example, if we change dramatically the delivery deliverables what we're going to create, or when we'll have them available, or if we're adjusting mentors. So if we realize, Hey, one of the mentors is unable to help. We need to bring another one on or we add two more. We tell the org admins because they need to record some things at Google about who our mentors are. Any questions there, Jonathan? Just one, it's about the, my proposal. I, my proposal, I, I write that to me, great it 100 pages inside the first 10 weeks. All right. So I'm afraid maybe. I, I, I actually is 100 page. So maybe 80, 18, 80 or 70 pages. For example, it's that the problem is I can't ask, I just 100 pages. So I would, I would significantly reduce that. That estimate number of pages to do. It would be wonder if we could wonderful if we could do that. But typically. There is a. I would guess it's on average one or two days in total of effort for a writer to make the transition of plug in documentation from, from outside of the code to inside the code. And that's, yeah, it's not that that's a contiguous one or two days it's rather the initial extract extract submit a preliminary pull request watch the build. Oh, whoops, this had a problem that had a problem started to make the repairs. I think that the two PRs in our experience month, and each migration takes me 16 hours, 16 hours. And because I need to prepare the lab, take screenshots and right, they could translate the week and send it. So, how do you think about I change the number for 250. And if you can achieve more and there's no problem. Absolutely, I would even say, if you let's see a 10 week project if you said 40, because the the assumption is that the writer is only working from 10 to 20 hours per week. Yeah, and if you're only working 10 to 20 hours a week. If you say 40 that's still actually quite a large number for 10 weeks that says you're doing for a week, which means you must have become much faster at the end. Because in the beginning, I'd assume you'll spend one or two days, what, eight or 16 hours per per migration, therefore you're only get two or three in the first few weeks, and then hopefully you become more fluid at it and oh I can do them faster. Okay, so I changed it for 40. Thank you for being. Yeah, so then we had, we had, we did have an up, we did have the mentor meeting. I had a conversation with me and Oleg and Kristen whetstone this morning went well. We discussed various proposals we looked at, okay, are there are the questions we need to ask and felt like we were comfortable understanding things. So, that that was a positive we've, we've got the right people. Now on your question Jonathan, they were delighted to answer the question could a technical writer act as a mentor. Yes, if you have Jenkins knowledge. So that's that's really encouraging. And then there was the timeline that we talked. Oh right and this is this was for. Oh yes, we, we done this and done met Friday, July three 2020. Jonathan, any other questions. No, no questions. I guess we achieved all requirements. And I love meeting with them. Great. Excellent. Well, and thank you so much for so much for your involvement and your contribution is so so wonderful delighted with the progress you're doing. Thank you very much. Jonathan, did I spell your last name correctly, I think I got it right. Right. Okay, say that again how do I pronounce it morai morais morais okay so the s is is sounded the s on the end actually is sounded. It's not like the French where it would be, it would be silent, it's morais. Portuguese, it's a Portuguese, each letter has his own sound. So it's a massive pronunciation. Okay, so, so it's Portuguese then is closer to phonetic, like Italian is. Yeah, distinct from the French where I regularly just drop letters off the end of French words assuming that that's not pronounced it. Don't drop it at nothing. They'll drop. Great. All right. And the H after the J is does that that gives it the, the, the J sound the jaw sound. The H was saying this type and my mother registered my name in the country. And there is no H but someone put there, no one see it so for that. Okay, so that so it's, it would have typically been j o n a t a n. Ah, very good. Okay, that's, I thought, oh, maybe there's a secret because in the Italian, an H after a after a let's see an H. H has a very special H after the letter C will harden the C, whereas a vowel after the letter C will soften it. Yeah, the H, the after some types of letter has itself, but not about no one knows how after the J. God. All right. Excellent. All right, well, if no other questions I propose we call it done. And I will post the recording of the note and the notes are in the document. I would like to say thank you to you and Maggie and all of you from Jenks organization. I chose Jenkins because it's, in my opinion, all the other organizations in Google Doc season are not so organized as you. They have no periodic meetings has no documentation and this with the big size and the quality you keep running. So congratulations for this. Nice work and thank you for receiving me with so much attention. Well, and thank you for joining. I'm sure it's daunting. We love having international contributors. It's amazing, particularly you from Brazil, it makes me so proud. Yes, we've got someone from Brazil who's helping our project that is that is a great thing so we appreciate you very much. So, thank you. All right, we will have office hours again on Monday. And if we see you then great. Thanks very much. Okay, thank you. Bye.