 Welcome, welcome, welcome. The date is July 3rd, 2020. This is the Jenkins pipeline authoring SIG meeting. This is our regular Friday meeting. We did not meet last week, and I forget why, but here we are. My name is Marky Jackson. I would like to remind everybody that we do have a Jenkins code of conduct, which recently has been updated, and we basically amounts to just be nice to one another. We don't want to have to kick anyone out. I am going to share, oh no, don't do that now. Let's see if it lets me do it. No. I cannot share my screen because I updated Zoom this morning, and now I have to log out, which would kick me out. So I will not share my screen, unfortunately, but I will read out the items that we are addressing today. And I will put a lazy link of, bless your heart, bless your heart. If everybody could just sign into the attendees list for the 3rd of July, I will put a lazy link to the doc in our Shazoon chat, and we will go ahead and get started. Open items from last meeting is none because we did not have a meeting last weekend. The first item up for discussion is we are talking, there will be a pipeline as Yammer Meetup. I am messing that name up, so I apologize if you are watching this recording. I will give you a Jenkins sticker or something. We will be doing a Meetup. I put the link to that Meetup. It would be good if we could attend, if you cannot. Don't worry about it. But this does have some items towards the, not only to our SIG, but it is also on the public roadmap. So it would be good to do that. Any questions, comments, concerns about the Meetup that was just posted this morning? Awesome. I will move on to the next item, which is roadmap. So we had to find items that we wanted to talk about or put items on the roadmap that we wanted to discuss. I know Steven, you are doing the templating engine, and you have put that on the roadmap. I am going to be doing, I believe, the IDE, so better syntax highlighting in the IDE, and I am going to start with VS code first. I have an issue. If there are other items that we would like to put on the roadmap, we really need to create Jira stories. So that was really about this. If you have not created a Jira story for something that you would like to put on the roadmap, please do so. Any questions about that? I think we probably need to figure out how we can go about breaking these down into actionable tasks. It would be nice if we could figure out a high-level epic per SIG meeting to give us some agenda for the next month or so. But I think it might be easier to start threads on either the developer mailing list or whatever so we can do this a little more asynchronously to see if we can engage more of the community. And then in these SIG meetings, maybe we can just go over the threads and start turning those into actionable tasks. But I think it has been in our backlog for a while to start turning these roadmap items. So I don't think the three of us on this call right now should try to decompose this, but maybe we can kick off some threads and then the next time we meet, review some of that conversation or something. I am making a note right now. I will all start off a thread for the IDE. If you want to start off one for the templating engine, we could just start getting the discussion and then I can go through and collect those for next meeting and add them to the agenda. We can do that. I'll take a look at the roadmap and all the items we have there and maybe I'll just create a thread for each. The items that we did have in the roadmap I took off because they were not well defined as all of the way Oleg has everything else on the roadmap really well defined and there's a story behind it. They were not really well defined. So the idea here is that I think we should start the thread and then start to really fill in the items in the Jira story to break it out because that's what we really need to do is A, have the discussion, start building out the task that you know link to the story and the story is in the roadmap and there's a full lineage of the way to see that. Okay, that makes sense. Okay, so I will start one on IDE and I will add a note here. Okay, is anybody else have any other questions in regards to that? Okay, too easy. We can move on to the next which is Google Season of Docs and Mark this was your item. Would you like to speak to it? Sure, this is a reminder that July 9th so just six days from now is the project proposal deadline for Google Season of Docs efforts. We've been accepted to Google Season of Docs. It's an invitation from Google funded by Google for technical writers to get involved with open source projects even if they've never had prior open source experience. We have right now six proposals received and Google approved us for one slot so we'll have one. We may ask for two. The crucial thing right now that we need is mentors and that's why I'm here is we're looking for mentors and reminding people that mentors need to be skilled in Jenkins. User skills, administrator skills, pipeline skills, they do not necessarily need to be skilled writers so we're looking for mentors. How many mentors do you have? We have two right now and we want two per project as a follow-on to Google Season of Docs. We hope to also run a community bridge documentation project so we would reuse those same reuse a new set of any extra mentors on the community bridge project. So that's really all I had was a shameless plug encouraging people to come help us as mentors. The time commitment is significant. It really is four to eight hours a week for a period of 10 weeks so don't underestimate the time commitment in offering to become a mentor and that's it for me. Thanks, Marky, for letting me take the time. You are most welcome. Have you put anything out to the mailing list like sort of call to after you Africa? Well to the Docs mailing list, to the user mailing list, no to the Docs mailing list and the Dev mailing list and as we get closer I'll put additional requests out. I'll probably also start targeting very specific people based on topics we have in the proposals because some of the proposals are focused on a specific area where we may need a unique set of skills. Okay, are you open to having, I have a particular person in mind but this person does not know Jenkins but is a experienced technical writer or does that probably doesn't help? You really need a mentor that has more Jenkins experience. Yeah so the mentoring role really needs people with Jenkins experience. The writing being done by the person who is the writer the writer actually does not specifically need Jenkins experience that's what we rely on the mentors for. So the mentoring task is really a Jenkins skilled person not a writing skilled person. Okay awesome, okay that settles that. Okay, anything else in regards to the Google Season of Docs? Nothing for me, thanks for asking. Awesome, well that is it for the end of the items to discuss. Does anybody have any open items they would like to discuss? Not on the agenda. 15 minute meeting, it's like a stand-up I like it. Awesome, well if nobody has anything else we will conclude this meeting and give you back 45 minutes of your pre-4th of July weekend. Everybody be safe, be happy. Remember if you're lighting fireworks, hand sanitizer, and fireworks, go together just saying. Cheers everybody have a great weekend. Thanks everyone, bye.