Jenkins Pipeline Authoring, 3 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Pipeline-Authoring SIG Weekly Meeting for 20200703

Description

In this meeting we discussed the following:
- Upcoming pipeline as YAML meeting
- Roadmap items
- GSoD call to action

A

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. Lastly, and I forget why but oh well, here we are, my name is Mark E Jackson I would like to remind everybody that we do have a Jenkins code of conduct, which recently has been updated and are we basically amounts to just be nice to one another? Who don't want to have to kick anyone else? uh I am going to ship Oh No.

A

See if it lets me do it, 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 it I will put a lazy link off 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 dock in our shizune chat.

A

And we will go ahead and get started open items from last meeting is none because we did not have a meeting last weekend. ah The first item up for discussion is, we are talking. There will be a pipeline as llaman meet up by I would talk and I mess in the name of so I apologize. If you're watching this recording I'll give you it. Thank you I'll give you a Jenkins sticker or something I will be doing a meet-up I put the link to that Meetup.

A

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 save, but it is also on the public road map. So it would be good to do that. Any questions comments concerns about the meetup that was just posted this morning.

A

Awesome I will move on to the next item, which is road map. So we had to find items that we wanted to talk about or items on the road map that we wanted to discuss. I know Stephen, you are doing the templating engine and you've put that on the road map. I am going to be doing I believe the the IDE so the better syntax highlighting in the IDE and I'm gonna start with vs code. First I have an issue.

A

If there are other items that we'd like to put on the road map, we really need to create JIRA stories, so that was really about. This is, if you have not created a juror story for something that you'd like to put road map. Please do so any questions about that. So.

B

We I think we probably need to figure out how we can go about breaking these down into like actionable tasks right side yeah. It would be nice if we could figure out a high level ethic per cig meeting to give us some some agenda for the next month or so, but with I think it might be easier to start threads and 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.

B

Maybe we can just go over the threads and start turning those into actionable tasks. I think it's been in our backlog for a while to start turning.

C

B

Items so I, don't I, don't think the three of us on this call right now should to try to decompose this. So maybe we can kick off some threads and then the next time we meet review some of that conversation or something.

A

Making a note right now, I will all start off with red 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 that.

B

We can do that I'll.

A

B

And I'll take a look at the roadmap and all the items we have there and maybe I'll just like create all.

A

Right take it among the items that we did have in the roadmap. I took off because they were not well defined as all of the way Oh like has everything else on the roadmap really well defined and there's a story behind it.

A

Those were, they were not really well defined. So the idea here is is that I think we should start the thread and then start to really fill in the items in the road. That's getting me into JIRA story to break it out, because that's what we really need to do is a have. The discussion start building out the tasks that you know linked to the story and the story is in the roadmap and there's a full lineage of of the way. This feedback.

B

Okay, that make up okay.

A

Okay, so I will start one on IDE and.

A

A

Add a note here.

A

Okay, does anybody else have any other questions in regards to that.

A

Okay, easy we can move on to the next, which is google season of docs and mark. This is your item. Would you like to speak to it sure.

C

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 we will have one. We may ask for two.

C

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 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.

B

For any mentors, do you have.

C

We have two right now and we want to 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.

C

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 ten weeks. So don't underestimate the time commitment in offering to become a mentor.

C

And that's it for me, thanks Marquis for letting me take the time you.

A

Are most welcome? Have you put anything out to the mailing list like I haven't sort of called after yeah, okay, I? Well,.

C

To the docs mailing list to the user mailing list, note the doctors 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 in the proposals, because some of the proposals are focused on a specific area where we may need a unique set of skills.

C

A

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.

C

So the mentoring role really needs people with Jenkins experience, the writing on it 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 milk reading task is really a Jenkins skilled person, not a writing skilled person. Okay, awesome, okay, that.

A

Settles that okay, anything else in regards to the google season of Docs, nothing.

C

For me, thanks for asking awesome.

A

Welp, that is it for the end of the four items to discuss. Does anybody have any open items they would like to discuss not on the agenda.

A

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 fourth of July weekend, everybody be safe, be happy! Remember if you're lighting, fireworks hand, sanitizer and fireworks to come, go together. Just saying cheers: everybody have a great weekend, Thanks.

B