 Welcome, welcome, welcome to the Jenkins Pipeline Authoring SIG meeting for Friday, April 24th, 2020. The world is still in shambles. I hope everybody is safe. I hope you are well. My name is Marky Jackson. I am one of the SIG leads for the Pipeline Authoring SIG. Before we get this started, I would like to say that the, this SIG is governed by the Jenkins Code of Conduct, which essentially boils down to just be nice to one another. Don't be a jerk and I won't have to kick you out. With that being said, welcome everybody again. This is the most people we have ever had in this meeting. And I don't know whether to cry, which I won't do on camera, or to start laughing and think somebody's trying to punk me. Liam, I am going to, as we always do, turn it over to you. I believe I can make you the host. With the most, which I have now done. Okay, okay. The doc has been updated for today's, for everybody that's joining. I do have to leave at 920 for a work related meeting. We think that this may be a short meeting. And with that, if everybody can just add their name to the attendees list in the doc, I have dropped the link to the doc in the getter channel. I will drop a lazy link into the chat here as well. If you could just add your name there, that'd be awesome. Yep. Okay. And. And I'm gentlemen. I am sharing that document on the screen now. I don't know whether or not it automatically comes up or what. There it is. So, yeah. Welcome everyone. Open items for the, for a day. Why don't we. Get started. Multi job. All. Where did we get this? Oh, right. I did not. Everybody needed to read this document. I can say I've read it. Okay. I have not. Would you like to talk about it at all? Essentially, this is a proposal that's being put forth. By, I forget who it was. I want to say it was Steven Foster. And he is actually put a super awesome proposal together. I would like to talk about it in terms of. A roadmap item. It is super solid. I think that this could be a roadmap item. What I was hoping for. And I will ask that we can table this until next week's meeting. Sure. Because I would like Steven to be here to actually talk. Talk about it. Right. Yeah. I don't want to butcher any. Yeah. So we're just going to start with the next one. John's like a plan. The same thing for the Jira queries. I, what I need to do is actually add a label for like pipeline authoring that we can use. And also. And throw some, some issues in there. Let's see here. Markey. What's the meeting. You want to talk about. Meeting Cadence, you want to talk about? First of all, just to go up one back to the JIRA query. I did create that roadmap. Thank you, Oleg, for helping me with that creation. And we did link a few tickets in there, but we can definitely still use the query. As far as the Meeting Cadence is concerned, I have sent the email to the SIG mailing list. I got no feedback. I have a pending body of work on my local environment to submit the PR. I have not done that yet. The PR will be to update the Cadence that the last Friday of every month will be a meeting where we will go over roadmap items and do sort of a stand-up style. This is what I've worked on. See where we are with those given items. I have not done that PR. I will have that PR in some point this weekend. I already have it written. I just got to find the time to actually pull the trigger on it, which I have not done. That's my status. I'll do it this weekend. OK, cool. I'm looking at the pipeline PR that you put up on the... Yeah, if you scroll to the bottom, you'll see a link to it there. The actual PR. That's the actual PR. And now these items are now on the official Jenkins roadmap. OK, Doki. Excellent. We will need to do some edits. For example, pipeline was Yamal first version was released today. And I think we need to move it to current at least. Yeah. We tend to discuss the meeting next week on Thursday. During the last time slot for EMEA meetings for pipeline ordering. And if anyone wants to participate, just let us know. And for the rest, some scrap is still needed. And I guess there is still a mission I can to create summaries for these projects on the pipeline ordering seek page. Is that correct, Mark? That's correct. I can also, while I'm doing the PR, I will do the PR to move the pipeline as Yamal into current. I'll add that to my PR. OK. Before it escapes me, I saw a pipeline documentation. I feel like I saw something on the Twitter verse somewhere that the Google Summer of Docs is coming around. Do we want to consider submitting something to Google Summer of Docs as part of the pipeline authoring? Thank you. I don't think we should be missing a deadline. Oh, legs like, don't threaten me with a good time. Yeah, so actually, we had a Google, sorry, documentation seek meeting today. And I briefly presented what we have now. I will just put a page to the agenda. Long, convenient read. Everyone is welcome to submit a political request and the proposed projects there. And we are really open to any ideas, especially since JSoT is not the only way to facilitate documentation. We also have October 1st. We also have community breach and other areas. So if you have a project which you would like to propose and document, it would be a great step to start. And then I'm happy to edit any way you want. Mm-hmm. And there we go. Relief. Cool. Thank you. So, Steven, while you were talking about Google Season of Docs, is it something you would consider to be a mentor there, assuming that it's about pipeline or maybe even specifically about libraries, and so forth? So that's a great question. I think that as part of this SIG and the charter, we've had conversations before about documentation. I think we should maybe set aside that we have a longer meeting. When is the deadline for submitting proposals for that? I think we probably want to figure out what a reasonable MVP is for what our ideas are for documentation improvement as part of this SIG and propose that as the idea for Summer of Docs. I certainly have plenty of other ideas around templating and stuff, but I think specifically to this meeting, we should try to capture some of our ideas for the pipeline authoring in general for submission. Yeah, so our deadline for application submission is May 4th. So what does this date means? On this date, we submit application to Google and Google starts processing this application. The deadline for technical writer applications would be something mid-July, if I recall the timeline correctly, it's linked from the JSOD page. So it would be a hard deadline to submit your project. Obviously, earlier you do that, higher chances that you will get an applicant. And if you could at least summarize something by May 4th, it would also help us and increase our chances of being accepted because a number of interested mentors, a number of project ideas, use that criteria when applications have been selected. So if we're gonna talk about it, if we're gonna make a submission, we need to do it probably next week. We need to figure it out. Okay, next week is the deadline? Well, because if the deadline is May 4th, then our next meeting is a week away and then the May 4th is right before the meeting after that. So we're gonna have to talk about it soon. How do we feel about next week's meeting potentially being drafting this submission? I think it's a lot easier to make sure it gets done if we all just crank it out as part of the meeting, talk about what our idea is, and just get it done. Sounds good to me. Sounds good to me. Yeah, fine with me. So just to clarify, Google's Season of Talks is a bit more relaxed than Google's Season of Code. So we still have a project ideas page, but there you just put an abstract, let's say one paragraph describing your project idea and link to your own materials like a pipeline authoring stick where you provide more details. So yeah, it's perfectly fine, though I don't think it requires a massive brainstorming to be submitted, but if you do it, if you scrap existing tasks, it will be a great improvement for the project in general. Okay. That makes sense to me. Let me see, what else did I do there? Mark, you can feel free to actually put your comments into things, you don't have to like, you put a little comment on the side here somewhere and I don't know where it went. It was a comment that didn't need to be in the body of the doc. I'm not shy about putting it in the body of the doc if I think it'll help. Okay, cool, just making sure you know. All right. So let's see, that's what we have on the schedule. Yeah, that's all, actually all we have. And I think that's a fair time to make this a short meeting. I think we're all kind of, several of us that are under time constraints or pressures. Before we, if we could just spend just a couple of minutes and this is optional, if you'd like, for any of the people that are new here, I do see we have a lot of new people and I would like you to get a chance to give your introduction about yourselves, who you are, and again, that is totally optional. Do not feel obligated to have to do that. No. Okay. And I consider that as a new comment. Vlad, if you're talking, we can't actually hear you, you're muted. Sorry for that. I'm one of the newcomers here and this is my first kind of online video meeting for this group. I had been in Silicon Valley for a while, for about 30 years, well, about five years, I would say, working with Jenkins, very interested in technology and what it can be done with this and continuous integration, continuous deployment, delivery, and it's amazing too and would like to contribute as much as I can to different projects that we have, guys. And I'm really interested in this. Thanks. Thank you very much, very much, Vlad. I see you doing a lot of work in the community lately and it's very, very welcomed and greatly appreciated. Last one. Anyone else? Me, it's Jason. Hello, everybody. Well, I've been working with Jenkins for more or less for one year. I reached out to you because finding more information about necessity we have in your company, well, finally we found your rule and I wanted to know more about the roadmap of Jenkins itself. Basically, my search was about testing of pipelines and well, that I'm very interested in if I can contribute in anything else would be great. Cool. Welcome. Excellent. Anyone else? Well, with that, I welcome all of the new people. We hope to see you again next Friday. I think this is a meeting record for us. On two levels, the most participants in the fastest meeting we've ever had. Yeah. Well, if nobody has anything else, I'd like to tell everyone have a great weekend, be safe, be healthy, and we'll see you online and next week. Excellent. Looking forward to it. Thanks, everyone. Thank you, everybody. Thank you. Thank you. Bye, bye, bye.