Jenkins Documentation Office Hours, 2 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Google Season of Docs office hours, Jul 2, 2020

Description

Recording of the Google Season of Docs office hours on Jul 02, 2020. Mark Waite and Oleg Nenashev discuss open questions from potential Google Season of Docs mentees.

A

I need to refer back to something: okay,.

B

So, yes, that the recording and it's just G sort of sauce, we have four people on the call and right now we are planning to process agenda and lots of words from the previous meeting led by mark and after that, just which another organizational part. Okay. So next question was: should Collins for mining projects.

A

Right right, so google season of docks has two concepts: regular length and a long-running project. The question is: are there any any negatives for someone proposing a long-running project.

B

So now a long-running project is basically to, firstly, it implies somewhat relaxed schedule so which means so that, what's highlighted here, like schedules, easily yeah, that's true harder to predict here is it really depends on how planning has organized how Kim cut rate, because there is no practical difference here in a shot and intensive project and long intensive project.

B

It really depends on how they teams played and for the next question for the next bullet about could be more valuable. Yes, they could but yeah why they could be more valuable. Firstly, yeah you may choose one client project and work much mounded than expected, so for one client project here you can deliver among these keys.

B

What is advice to not of basically it's your personal choice, and it's definitely not expected that you take one Quran in project and keep working forty hours per week on that.

B

At the same time, it may be more variable because there is more opportunities to get feedback, because you can submit something for review and submit something to the community. Sometimes review cycles are quite long, as you may have experienced from dusit applications.

B

Sorry about that, but yeah what may happen in open source because yeah the project is driven by volunteers. A lot of mentors are volunteers in this case, and it means that sometimes responses might be delayed for mentors. We didn't expect into the active phase, but if you are out reached why the community again there might be so long-running project, basically allows you to be that and it allows to review cycles. If you want to do any kind of service at rate may be more convenient.

B

If you talk about special risks. Well, yep along the timeline along, there are more risks of various events like whatever like covert 19 confinement version 2, and so so you need to keep it in mind at the same time, yeah one training project that provides you more flexibility. They react to the things, though I'm not sure how flexible is Google in terms of google season of dogs, deadlines or JSOC deadlines, at least I believe, with smallest the same for G's G's odd, but if there is really emergency, etc.

B

Of course, Google is open to discuss options, especially in the case of jay sauter, when there is a low number of mania speaking in the project, so they might be more portunities, so I provided some hints, but generally a long-running project is neither advice to know. Discouraged is just another option and it's basically up to you to decide what would you prefer in terms of availability, the case of the Jenks project, even if you can accommodate, was short-term projects and long-term projects.

B

So it really depends on you.

A

Alright, thank you. So then, could a project proposal specify the alternatives?

A

I want to irregular, or, if allowed I want to do long running as part of the project plan, or should they the the one of the question, is: how should they frame it if they think they've got a long-running plod project or something that might be both might be one or the other in.

B

Their place or application, we expect a plan and I believe that they have to explicitly specify, but it's a long-running project or not in the application. I might be wrong about that, but if you have a preference, do this mention it in your project schedule, because faucet may also require some adjustments on the mentorship side, etc. For example, Christmas break and other things which air may get in the equation and just having information about the plan in advance would be preferable.

B

But again one great term or shorter term project doesn't make a difference in terms of affiliation because amount of time I expected to be spent on the project is approximately the same.

A

Thank you now how to deal with. How do we adapt to changing changing things we learned during the project, etc?.

A

B

In a googol season of dogs, the approaches exactly similar to Google's Summer of Code as long as the inventors are. Finally, the progress. The organization is fine with the project, so it means that deviations may happen in each cases. Even significant changes over subject to make happen, though it's not something we would really want to do, but yeah I think might happen. For example, you apply to work on. What's the documentation, immigration, you provide a list of plugins and we know that basically, there is continuous migration of plugins and becoming so.

B

It means that you, you submit your proposal now. You know August, that would say we are accepted, but by the beginning, in September they might be contributors who address. Let's say half of your scope.

B

It may happen and we expect the teams to adjust based on social scenarios and it's not a problem. It happens everywhere. It happens, a real war, it happens in open source everywhere. Change of plan is a part of the plan, just make sure that you communicate with Mantle's and do a gentle decision on that great ok. So what are the limitations of changes? So?

B

Yep my not changes. We should do not to change deliverables, it's not the problem if major deliverables change and then, of course, it's a subject for discussion. These managers.

A

Great excellent and then the who do we inform I had assumed that we only have to do formal notification to Google if someone were actually abandoning their project if they, if they had been accepted. As I later said, I have a personal emergency. I simply cannot continue, but other than that changes don't have to be notified to Google. We just go ahead and accept the flexibility ourselves.

B

Yes, yeah just clarify how we approach JSOC and how you approach I believe, but again, all minor changes. They happen on the project teams. Still we expect teams to notify orchid means in the case of significant changes. So let's say if you change order, the delivery, etc. It's totally on the project, but if you change the scope significantly it's better to identify or hide means so that they know about that, and if you have to change every significant.

B

So, for example, you want to create bernetta documentation and, let's say Google calls kubernetes and you agreed to work on docker documentation. So this changes likely need discussion and like heads up to Google, they obviously have provided the keys, which is unlikely to happen, but just to provide you an idea. So such a drastic scale changes again a basically organizational decision but means to prefer to notify Google Kim about that. Because, again you something goes wrong. If we have to fail the project, this communication transparency may help both sides. So.

A

So one that I may have made a mistake on a google Summer of Code if we're adding a mentor or a mentor changes that should go to the orchid means always right. Yes, because what.

B

That means and to do, updates on the website, etc.

A

Okay, sorry I! Don't do that yeah.

B

So we eight separate things but okay, so it's orchid means its changes in the deliverables. If needed and for example, we if there are a long, an availability period. So during google season of dogs, you're also expected to take vacations breaks. But let's say, if you are going on a one-week vacation is better to send heads up to orchid means, because we may need to do some communications and the better that we know in advance that you know.

A

They're, oh one last question: I think I got the answer right, but the question was: can a technical writer act as a mentor if they were not accepted as a writer? So let's say we have someone who submits proposal in one of many and we select only a few of those and the others say: hey I still want to be involved, can I could I switch and become a mentor, and my assumption was, if you know Jenkins and are willing to mentor, you could potentially be a mentor in this case right.

B

Yeah, so there is no limitation on that as far as I can tell yep, also as we discussed at the previous documentation, SiC meeting, we consider doing additional community bridge projects for documentation in Google Docs and, in this case very different there wanting a such limitation for sure and it might build an option for you to apply to community bridge. It's that great and recommendation and.

A

We had discussed community bridge actually on in the Monday office hours, so that's great I just took a tour of the site. I gave a brief overview. Excellent. Thank you, yeah that covered all the questions that there were on the the meeting from last Monday. Thank you. Okay,.

B

So yeah regarding the rest, July announced he's added wine applications, Oh July, 8th but yeah. So we have a bit lesser than one week, so I can be asked who mentor successor to focus on? Are we giving the proposals? I spent some time straight on there and thanks to mark for doing that, we use almost every proposal by now and yet we basically encourage readers to review proposals and also to peer reviews if your interest in the project etc.

B

We hope that we'll be able to produce all this list gain. If you don't receive feedback, please don't hesitate to pink participants, because sometimes we don't provide the feedback before so the proposal looks so good, so yeah there would be some minor things to discuss, but overall we have enough information to run to this proposal. Sometimes we don't provide feedback, because basically we are just overall reservists, so just you don't receive it can. Can you excuse my yeah if you don't ever see feedback? Just these.

A

Fingers yeah so as far as I can tell I have reviewed all the proposals that I've detected mm-hmm. That means, if someone was expecting my review and got no comments, I missed their proposal, and so so I would I. At least person would be very grateful if someone says hey Mark, you said you'd remove reviewed everyone. You made no comments on mine. I made a comment on some minor thing, at least on everyone that I reviewed. So so, if, if there's a proposal that I've missed reviewing, please ping me in the docs channel.

A

Send me email, beginner yeah, yet on the docs mailing list. Any one of those is great.

B

Okay, that's perfectly fine with me and if I don't probably feel, but just think because it was out for a while, but I am catching up with all my Inbox I just have two thousand and four hundred emails. Deportes.

B

Let's sum it up like yeah,.

B

Okay, so ready guys, so that's it for today. Other questions.

B

So I will do this meeting next week as well, but yeah lessons learned that this slot is not suitable for tech writers. So if we organize meetings after the acceptance of projects will be a different time slot and right well and what about the night slit, yeah.

A

I was I was amazed that we had. We had people in the Monday afternoon. My time call from West Africa, so so they were calling in at 10:00 p.m. their time, and it seemed to work better for them, so that yeah, that's okay, yeah.

B

If you employ professional sound where the problem this time is not video, maybe for Asian Pacific region, but original Pacific region at the same time, that was not so many applicants for J SOT current row last year, so statistics whatever alright, thank so like yeah. Thank you, Tom and yeah I'll probably show the recording tonight.