 Hello everybody and welcome to the Jenkins Pipeline Authoring SIG. Today is Friday April 3rd. This is our weekly meeting. Welcome to everybody. I do see we have a few new people on the call. If you would like to introduce yourself, you're more than welcome. If not, that is okay. I'll give you a moment and if you'd like to introduce yourself. Hello everybody. My name is Jason. Well, I'm just starting to work with Jenkins. I'm pretty interested in knowing more about what this group is. Thank you very much, Jason. And welcome. We're awesome to have you. Super awesome. So thank you very, very much. With that, I am going to share my screen. I'm going to hope I do this right. Before we get started, I would like to let everybody know that this meeting is governed by the Jenkins Code of Conduct, which basically amounts to be nice to one another. Let's see. We'll go ahead and get started on the open items. So last week we did not meet because there was all kinds of things happening with myself and other people were busy. So we did not cover the roadmap that was drafted up. I would like to start off with covering the roadmap. And I have sharing it on my screen. This is kind of what I came up with and I started doing some of the initial initiatives. These are not hard initiatives. These dates are not hard dates. I just wanted to get something started and really open it up to the rest of the community to start to help set the sort of the roadmap for this particular SIG. I would also like to mention that the idea for creating this roadmap is to roll up into the JEP roadmap that was approved by Oleg and PRD. I don't have a link to that PR right off the top of my handy dandy interweb, but I think everybody may have a chance to have seen it. Is there any questions, any comments, any concerns? I think this is a fine start and we can always add things as we go. Right. I just wanted to get the format sort of up there, put sort of what the ideas would be. I put the GDSL on because I really do want to see that come to fruition from a sort of upkeep and maintain maintenance standpoint. But again, these are nothing that are hard. I know we've worked on the personas, the roadmaps and the documentation. So, again, this is just to get us started and feedback is welcome. What I do believe this document is open to everybody to comment. It is open edit ability to you, Liam. And the reason for that is just general safety. We don't want to have people come in and start messing around with things. Yeah, not to, not to be the gatekeepers. It's certainly not that. So with that, this is the roadmap. We can change it. We can add to it. We can take away. I just wanted to get something started there. I would like to, I don't want to set an artificial timeline on getting this completed, but I would like to put something out there to say, we'd like that we'd like to have this completed by X. What are your thoughts on that. I, this is Liam. I prefer that we actually sort of follow the lead from the overall roadmap, I think, which is, which doesn't have target dates. And the reason for that is I don't want to, for people to feel like this is that we are not succeeding if some specific date isn't hit. This is a volunteer organization. Things happen and like that means I think that it both sets an expectation that that may not be met and then also sort of it just might make make anyone doing the work feel less good about it if it doesn't get done on some schedule. I agree with that. I agree with that. So then maybe what we could do is is I can maybe I need to just take out these this whole timeline as far as I mean what we have is two main things right now three, three, four right then we're we're working our way through them. So I mean this is this is fine. I suspect that we're going to pull into the the overall roadmap or otherwise we can emulate it and or you know make it make a subversion of it. That would be great. You know what I think I can I can take that action item to sort of plagiarize it and then we can tailor it the way we need for for our SIG that probably will be a good good thing to do. I will take that action item. Okay, thank you. So there'll be another document coming before next meeting. Okay. So that takes care. Go ahead, Mark. I apologize. The Jenkins roadmap is live on Jenkins.io. It's admittedly still in draft, but the pull request was accepted. It's visible and being refined. I like the conversation we had in discussing the roadmap that maps of roads do not in general have dates on them. So my full support that maps of roads do not have dates. They don't need them. Right. Yeah. A map of a road talks about destinations and and possibly steps along the way to the destination but it doesn't really need or benefit particularly in a community project from having dates associated. So my full support to delete the dates across the top. Cool. Awesome. Okay. Thank you so much for taking care of that. Does anybody else have any input in regards to road maps getting rid of the dates, which I do fully support. It's artificial, but sometimes in my head I think like in the business side so I'm thinking we've got to we're working in a sprint and we've got to have dates and burn downs but I have to sometimes remember that's not the case for when we're dealing with open source. So I just sent to the docs mailing list and invitation for people to suggest Docs roadmap items as well and my intent there I propose to use a actually condorsed style voting technique, gather the ideas and then ask people to vote. You know, this, this feels like a great, a great effort as well and let's, let's encourage people the crucial thing for me as contributors are deeply profoundly highly valued. Overall, this is an amazing step forward for the community as a whole, because it's showing that we're, we're, we're all coming together and trying to drive us down a road. I like, I see where the motif is now, we're all trying to do that. And I think the beauty of all of that is everybody has a seat in the car to drive down that road or on your bike or you see why I'm going right so I'm trying to package that all up. Alrighty, so that takes care of road maps. Next on the list, we had there was I added these items in. I do not see. They may be here. No, I don't think so. Craig here so it. No, so for Craig, if you are watching the video, we are talking about the items that you wanted to be on the agenda. I would like to add something, which is an echo to what Oleg has stated that these, these type of bugs don't really fall under this sig. I do think that these are items that we can help maybe get looked at but I don't think they fall under this sig. I'm going to step back from that and let you, anyone else add anything that they may like to in regards to this. I'm, I'm, I have some to say but I'm waiting to see if anybody else has anything to point out here because I tend to talk so I'm. I also agree with Oleg so I that's I also don't have a lot to say. I will try and advocate for a perspective that I'm not sure that the perspective that I don't agree with which is these are pipeline bugs. And so I can see how it's how it's reasonable to want, want them at worked on, and to want to gain them greater visibility and to say well, this would be one place to get that kind of traction, right. But I don't, but as you said, I don't, I don't think that this is the venue since this is more would say that this, this group is more aspirational about where we're going and how we can help a larger community not work on individual specific technical bugs. There are already people doing that and the fact that their time is limited and that some bugs are not getting as much traction as anyone would like really there's no there's always more to be done and there's resources is not it's it's unfortunate but there it is right. Yeah. So, I think that well this may be I'm trying to how do I say this. Well, this may be a place that I, I think it would be good for this type of an issue, or issues in general that are related to a particular Jira would be better served in the getter channel. Through asynchronous communication, as opposed to this meeting because I agree this meeting is more of a larger, like how are we driving this initiative of pipeline authoring forward. Having said, if a, if a particular issue or person concerned about an issue feels that they're not getting the needed exposure to the to the issue, then maybe this could be a place that they bring that up to voice that concern. I don't necessarily think we are structured currently in such a way that we could help be a sounding board for that or get the help acting for a particular issue. I think I'm rambling and I apologize, but I mean, we're a group of experts so and members of the community so we can, we can help out direct people but that doesn't necessarily mean that, you know, the, the, one of them is more of a technical side the other one is actually maybe more in our, our wheelhouse, which is talking about adding a, adding a, improving the usability of pipeline by adding a link that will lint a pipeline, run the linter on a declarative pipeline to the web UI, for example. That is a very, very good suggestion. Yeah. So, yeah, I commented a little while ago on it's 52939. It's sort of a squash together issue that has like, we also, it was filed by Craig, actually, and so he said I want this and I also want to do a reload for this other larger technical issue which has been around for a long time is harder to do. So, that, so, but just getting a link, the link side of this is actually probably a reasonable thing that can, that we can do. I don't agree now for now, and anybody please jump in if you think wrong, but I think we can at least agree for now that a this is not this meeting is not the venue to address certain things like that. So, those things addressed, we can maybe say, you know, use the getter channel, and I think I also just to add to that I put in a PR, yesterday that PR was merged to update sort of the structure of our Jenkins.io for the pipeline offering to kind of state, hey, you got to use the getter channel for these things and make sure you've done your, you know, due diligence and research before coming, you know, there. And it really wasn't a change from what was already there it was more just a rewording. So, I think if it does anybody else have anything they'd like to add to this. I don't know what I did with my editing type mode. Much better. Okay, if nobody else has anything to add to this we will go ahead and move on. Okay, and the next item up is. Let me just, let me just, I'll just. Craig, if you're watching this later or if you're on the getter channel. We're happy to, you know, discuss this again just come back around just like it's one of those things where. It's like, well, you wanted to bring it up, we brought it up. We'd love, we'd love to have your, your view on it rather than any talk about it amongst ourselves. So, anyways, thanks. Thank you very much for that. Okay, moving on to the next thing we are going to talk about Jenkins Docsig seeking roadmap items. Mark you had brought that up. And I think that is awesome. I have some suggestions. So I think for anybody else that may not have been here when we were discussing that we're talking about, we're overall all there was a larger organizational roadmap put forward. And now each SIG is trying to do their roadmap to sort of roll up into that large organizational roll up. The Docsig is also doing the same thing. And they have, they're open for suggestions and contributions and items like that. Now I know we have talked a lot about previous meetings about the Docs and and how we'd like to see pipeline stuff sort of structured for that. So this is a great opportunity to be able to for anybody watching or anybody here. This is a great opportunity to be able to influence or have the ability to speak and add your value to other SIGs as well. So this is a link to the Docsig meeting notes in our meeting notes. Mark, would you like to add to anything about that. Just encourage people to freely be involved. I'm trying an experiment with this particular request. I'm going to gather suggestions for about a week and after about a week I'm going to put up a condorsed poll that will ask people to prioritize which things they want and then will. Those will take the top two or three and put those on the roadmap. We've had suggestions for Jenkins and Kubernetes for, hey, give me dramatic improvements to how Java 8 is described or the tuning of this or that. All sorts of interesting topics and areas. None of those things should be considered any way blocking or an impediment to the pipeline authoring SIG. You can create and contribute and add anywhere. I would definitely interested in the Jenkins and Kubernetes one. There's a lot more. A lot more coming up on that topic soon. So pay attention to that guaranteed you will see more about that. Does anybody else have any questions or comments concerns regarding the Jenkins Docsig seeking roadmap items. So where do we submit them. I'm looking. So right inside you could either send me email. You could propose some comments into that meetings into those meeting notes. Any of those is fine. You can send me a tweet. Okay, any of those is just great. Cool. Just checking. I've also brought up on my screen to share. Yeah, so scroll down. It's about it's item seven in that list. There you go. There we go roadmap ideas and you look just comment there. And my intent is to collect the ideas. Several of them have backing either email messages or Jira tickets that support and describe hey what is being requested. So that you can think about a little deeper than just the text that's there. Okay, that is awesome. I will do as soon as we're done with this meeting I'm going to go right to this link and add some stuff. Great. Thanks. Okay, so that takes it care of new items. We do have my action item that I will migrate and adapt to Jenkins IO roadmap for our SIG, I will have that ready by the next meeting. And so now we can go into open Q&A or open mic, whatever you want to call it. Does anybody have anything they wanted to discuss. Jason, just just checking in. If you guys had anything in order to bring up. No, actually, I just come here to learn some things. Okay. Great. I'd like to say one thing in regards to the new people joining that really warms the deepest parts of my heart to thank you for joining. Call a friend, bring a friend. I think it's awesome that community we're very inviting and this is the opportunity to not only get to learn, but also to be able to help affect some of the organizational changes that are happening. Thank you so, so much for joining. Please tell a friend and bring one. I was going to make some offbeat statement, but I'm not. It's cool. If nobody has anything else, we will go ahead and conclude this meeting. All right. I thank you everybody. Have a great Friday, great weekend. Be safe out there. Yeah, or in there. Yeah, in there. And if you're out there, six feet, you know, Yeah, all right. All right. Have a great weekend, everybody.