Jenkins Governance Meetings, 6 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Governance Meeting: May 06, 2020

Description

Recording of the Jenkins governance meeting:
* LTS baseline selection and 2.222.4 backporting
* Google Summer of Code updates
* Jenkins roadmap updates
* Jenkins is the Way initiative
* Jenkins Governance Roadmap and documentation items approvals
* Migration of governance docs to jenkins.io

Full agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o

A

Well, this is our regular Jenkins governance meeting. This is the second time we do it in the zone. Usually we do it in our C but testing other communication channels. Today, isn't my six and we have six contributors on the call. I'll share my screen to show the agenda okay, so we have a number of regular.

B

A

Including news- and they was a number for Provo requests regarding other programs, so I suggest we just go through the entire agenda unless there are other topics to be added.

A

Okay and the first item for us is healthiest baseline selection and working photos.

A

Would you like to speak about it.

C

Yeah sure why not so there's a pork, let me see if I can put it into the document. We have switched it a new approach lately. So there's a poor request link as soon as I find a way stinging try there. So there is a poor request when we have done all the back doors that are currently planned, for you know to be back ported in the in this line he's there.

C

A reception of folks seems to be good and just he's got some good points, I've adjusted that there's a couple of things that haven't been reported into the last one, therefore into the whole line. So this is something I'm happy with I, just notice that there are tests failing so I would have to look at that and see see where that goes. But this is something that I'm happy and there are peers to be a consensus about that.

C

So I suggest that we would check whether we are okay with what's in, what's out make the decision as a part of this document, and we can follow up, and you know iron now, the failing test for whatever reason and I guess we're I mean unless there are objections, I would be pushing it out as a release candidate tomorrow, I.

A

Think it's perfectly fine. If you get it fixed. Sorry, I didn't tell you yet, but it looks good overall, all the major changes which were marked I included and you don't have anything critical. Yes,.

C

I guess this is quite quite dense. So very briefly, there was quite of you know several isolated changes. They were mostly backported. There were the one with with the breadcrumbs and header, that's fairly recent, so it wasn't backported and there was also the part with basically everything around the read-only configuration screens that was backordered yeah. That's.

A

Great also, we have one fix, forgings configurations, code plugin, especially for users who align entries truly hooks.

A

We heated at least once in production, and we always the WebSockets fixes.

A

So thanks for doing that, we'll be deploying code. That is your my instance as soon as it's.

A

D

So my question was more related to the LTS LTS baseline selection. Well, Oliver is that that settled on to 235 the the backporting I think the process is working great. That feels really good to me and and delighted that Jessie detected the one gap that he found. That's really good back the LTS selection, you're, okay, with 2.2 35, or is that selection still process still in in play? Is that decision not yet final? All.

C

Right, that's a good point. We had a tendency to close this on on these meetings, so I'm, quite not sure if falling that or not yeah I suggest well now that in the mailing thread as we go, I guess it was suggested a couple of time. I just fail to actually do that so yeah I'm, okay, with the selection based on whatever discussion, ended last time.

A

From what I see in the developer male increased, everybody is basically on board, so it's either too low. The third to 34, 35 I, think that if you are also lucky that we can just say that it's a decision.

D

Yeah I've been and I've I've put to that to 35 into my environment for immediate test, trying to expose it to my normal use, assuming that it was going to be chosen, no surprises yet that I'll keep testing. I know.

E

I think 235 is much better than 234, because we have a fix for the warnings plug-in and the new you user interface. So it would be helpful if we have the 3 5 and not 3, for angry.

C

Yeah no objection, I mean one of the critical fixes in 35 definitely have to be back ported. The breadcrumbs 1 but ya know objects drumming.

A

Obviously you make the decision Oliver, it provides I'm not just about this decision. Roll with it.

C

So I decided that we go with 235 done. Oh I need to enjoy the feeling right. Well,.

A

I definitely enjoy that because yeah, we kind of finally communicate this decision and yeah thanks a lot for that.

A

Okay, anything else about the baseline and reporting I.

C

Think I'm done, except for that, so thank you very much for all like and Daniel. They both contributed a lot to the last update of the process, so it was very, very valuable. We provided after a couple of years, so that was definitely definitely good and basically everyone who puts time into testing and reviewing this poor request. So it's very appreciate. Amin, it turns out the single pair of eyes can make many mistakes, especially those are my eyes so this is. This is definitely crucial.

D

Yeah and I'm delighted with with the process you're using. Thank you very much. That's that's really great Oliver. Thank you.

C

Well, keeping the process going. Thank you guys. Yes, sir yeah, that was all from me, sir yeah.

A

That's perfectly fine and yeah. You have six weeks until this LCS is out so more time for testing.

A

Okay, so next subject is google Summer of Code, so we have already discussed it at a couple of meetings, but we heard all the projects announced so this year we'll have seven projects six, they will focus on Jenkins, one new focus on Jenkins eggs, so Jenkins our products include custom, Jenkins distribution, build service. The topic we heavily discussed at the contributor summit in Brussels in February, then external Hilliard, instorage, continuation of power, plausible story stories, begin performance improvements, github checks, API for Jenkins plugins will who is Umberto, he's a big mentor in this project?

A

Also machine learning, plugins for data science and Windows services configuration support. So these are six projects. We have already added these six projects to the Jenkins roadmap, because all of them have been considered an important I'm, not sure whether their website has already been updated because I merged this change, maybe 15 minutes ago, apparently not but yeah. Once the build completes you do have for these items on the roadmap, as well as other projects like, for example, basically specification generated on future topics, because we would like to eventually help them.

A

So hopefully, by the end of this meeting, you have a new roadmap here and yeah. Today we had a welcome meeting Chris, oh uh JSOC students and mentors so I will publish a recording, 3090 and welcome to watch it. If you want to see more details, I.

A

Commence questions.

A

A

Guess not okay, then, let's go forward so roadmap a beat for road map yeah. This road map still hasn't been updated. Yet there were some look-and-feel improvements, I'm also working on I filter and call the story's content wise. We have edit G soccer stories to the road map. We have all submitted marketing and outreach programs. So, for example, here now we have new Jenkins online meetup platform, which is basically release Jenkins.

A

The way program which has been announced last week and you've already got a lot of stories, so police say if you would like to briefly share the status, it would be nice, so we have it later today in English right.

B

Okay thanks so like so just to give some context so last week we posted this blog to announce the initiative that we are collecting Jenkins user stories. So basically, in the past, we we there was some bad blogging or blogs.

B

That does not put Jenkins in a very good light, and so then the the thinking behind this initiative is that to combat that negativity, that we would showcase all the wonderful things that people are doing with Jenkins and the other thing we wanted to do was hoping that these stories will inspire people to you, know mimic or learn from these stories. So so that's the context of this this initiative, just so far before the preform rolled out this initiative.

B

We we worked on about 6 user stories and two case studies and since the release of this blog, which was last Wednesday so so far, we have received 20 new submissions, so 20 new user stories and then I think there's about another 20, that's still being in the works, but they haven't completed. So what we will do is take those stories, turn them into user stories and then for stories. That is really compelling. We want to turn them into an actual case study, so a user story is an abbreviated version of a case study.

B

So we want to continue this program for as long as we can so I'm. My plan is to keep this going for for this whole year and see what we can get, and then you know from that point on that: there's going to be a ton of good content that we can make available to the community, so we'll figure out what we will do next, but right now we just want to collect as many of these stories as possible.

B

So then that leads to Mark's question that the next question on the agenda is about the jumbotron, so I'll leave that to mark.

A

I think we can get there, maybe in a few minutes. So that's why we finished it. Obama thanks for the ovarium, so other thing we added is basically new online github platform. So basically it's tooling or Jinky, someone meetups I plan to post a blog post, but now we are capable of running well, basically, any number of meetups we can in support thanks for continuing dependents, delivery foundation for sponsorship, and we have already practiced this platform. This Jenkins from kubernetes online meetups. So we had to meetups is hundreds of participants and we plan another one.

A

Next Monday and we go have more meetups announcement, so these stories are completed or completed at least they're there. There is also a little bit and discussion about Jenkins UI, UX hackathon, so it also happens within the Jenkins is the way program. Well, at least we try to align because of the time frames over glob. We also be having a, but we need to Pacific user stories about user experience and also your changes and documentation improvements. So I think that it could be a good program.

A

So it's under the discussion tomorrow we will have a discussion and focus on outreach, dick making, but agenda. It goes well and yeah. There is a lot of other stories, but everything else has been added before and we applied to google season of dogs to southern trinket. So in one week we should have results at all bit and we are waiting I'll, try to the treasure the roadmap yeah.

A

So once gsok changes, I integrated to you, should have a lot of additional items here for tool and sherry simplification, section and right now it's biggest section I would say at the same time it's the most important one, because these people, what people expect from Jenkins. So if anybody has any ideas about projects and initiatives, we could add there. This submit your request, because it would be really helpful to go over this section right now. It should be around six seconds there obtained here: I didn't G soak.

A

Any questions comments.

B

F

Just just one question about.

F

Jenkins is the way energy, so I, guess mountainous lee jin-seok has seven projects inside including Jim Jenkins X and my understanding, GM Jenkins X started as a project for Jenkins, but yesterday there was a webinar by Jenkins X, my trainers they mentioned because nothing to Jenkins Jenkins explosion, so I wonder how it is a relationship where Jenkins x2 there Jenkins is the way. If there is a bogus story on Jenkins X will be included, Jenkins away.

B

Well, if there is a good story and a user story on Jenkins X, we'll definitely take it as well. You won't say no to that. Please.

A

It may be on different platform. This is subject for discussion of when it happens, but definitely if we get a story and you'll try to get it published somewhere.

A

I think we can just switch to Jenkins's the way then.

A

So I guess you have two items to discuss today is whether you put it on Jumbotron and whether you want to change it activity return so mark. Would you like to speak about the test? Sure.

D

So the the concept there is that, on the on Jake, the Jenkins dot IO site, we have a series of scrolling panels which appear right now: CD Foundation and then ji-suk 20/20, and then there's one more panel currently welcoming people to contribute the welcome to contribute and CDF panels are pretty much there all the time and should remain the G sock announcement fits very well for the timeline right now. Exactly what we'd like to do is add.

D

One more panel, which is an invitation to join Jenkins, is the way for people to submit their stories so instead of 3 panels, visibly there would be for one of the reasons for bringing it to governance. Is that that makes this. The initiative for Jenkins is the way very, very visible. We felt like the the governance board, should at least make a willing choice. Yes, this is a good thing to do.

E

Yes, I think it's a good idea. It makes it really with, for instance, everybody sees now what Jenkins can be used for. That's really a good idea. I think.

F

A

What do you think.

D

Yeah so plus one for me as well, Oleg and and I think Alissa had already expressed her +1 previously yeah.

B

A

So I'm just opening developer mining history go something back here so once from Tracy what Marquis but T's the new team so yeah! No once.

A

Yeah I would say that it's approved over somebody is against great.

D

So I'll go ahead: I've got a I've, got a double check that the pull request is safe and clean, and all those things there was a there was a correction that Tim Giacomin had detected needed to be made or that it might be possible. I took oh, let me do one double check on that before it gets merged.

A

Okay, thank you Mark and.

D

The way I'll confirm that I finished that is actually removed the on hold right now, it's it's labeled on hold to remind people, don't merge this until we get governance, approval, okay,.

A

So from there there.

D

Is one yeah it's inside the pull request.

A

Yep, don't make me pull requests on databases now, yeah just hold programs. So here's a current dirt for the Jumbotron. We can spin instructions. Users around the world showcasing how they build a new one and I've made in both software is Jenkins, and what about.

D

Yes, yes, you're right, then sorry I didn't cover everything. I just used I took the verbage from their side initially. So that's fair point. What about hard work? Good, so I will.

A

Start the new program about hardware, no Jenkins t-shirts right.

D

Clearly, clearly, Oleg is from the platform. Sig he's apparently had been involved with hardware before that's a good thing. Yeah.

A

And to cover the previous discussion, I may even dr. data cache, but.

D

Yes, yes, exactly yeah, we have two doctors in this in this meeting. That's great okay, yeah,.

A

So yeah thanks so much for doing that and let's keep it pushing another subject about Jenkins said the way again is Twitter. So if you look at our Twitter well, actually we're still using Jenkins to the 0yi image there. So.

F

A

This image is four years old, also like Jenkins so I guess it's definitely time to change the image to something and the proposal from ELISA was to use Jenkins and the way image there. So.

D

Oh like for the benefit of the people on the call, could you open the artwork page so that we could see the the image I want to be sure that that that people actually see the the image that's proposed, I think it's this one there. It is right.

D

Now one of the requests from the community was hey where's, the SVG version of this and I. Don't think we have an SVG. So if we need a high-resolution version, it is not as high resolution as some of the other SVG formatted versions that are there.

B

Mark I think I sent you a high-res version, yeah.

D

You said a high-res EPS EPS doesn't doesn't have the same attribute that SVG does that SVG is nearly infinitely scalable. It ok.

B

Let me ask for that.

A

Anyway, we don't need vector for Twitter: oh, we don't okay, great yeah, so we can be technically replaced by existing image. So it's rather amount of feedback.

A

No good shape opinions above it.

D

Yeah I'm, plus one for the replacement I, think it's a it's. A good update, yeah.

A

We could also add hashtag here, for example, Jenkins said the way on on the left account named, but yeah, it's again a matter of how visible this campaign should be.

B

So plus one for me as well and like I, said I'm hoping for us to continue to collect stories till the end of this year. I.

A

Don't think that we will keep this image until the end of the year, but yeah, maybe one months or so would be reasonable.

A

Would appreciate my penis and.

D

I agree wholeheartedly that it's time to replace that avatar image with something else, I like your notion of one month one month on Jenkins, is the way and then we could revert it even to something simpler or to the regular Jenkins logo. Yeah.

A

I think it's local by default, unless you have something else right.

D

Jenkins 2.0 is a while ago we're a nice long live project, but that's that's a long time ago. Okay,.

A

So I, just only ever that stain in this story, but yeah so at least some marker plus one right. Yes,.

D

A

E

Opinions I don't use Twitter, but I'm. Okay with it.

A

A

F

Oliver, should we wait for your feedback.

C

Oops I, muted, sorry, yeah I, like the idea. Okay,.

A

So I guess we have a decision now. Do we have something? Are they male increased.

A

It went to advocacy and outreach so also, plus one from Markie here.

A

It's alright I guess it's approved so.

A

We for one month so one problem: he is about the implementation, because currently the account is managed by Taylor. I have access, for example, to TweetDeck, so I can post tweets same for mark for Markie for tracing, but we need someone to really change the logo. So I guess it would be your ISA who is about to reach out.

B

A

Thank you do so anything else about changes of the way. That's.

B

A

Okay, thank you. So I have subject about governance roadmap. I started submitting some poor request. For example, here I put suggestion to it: well, obviously, 720 dominoes but and officer elections to the roadmap. They have to do it according to our process and at the second item I suggest, to put to the agenda to natrum is core infrastructure initiative compliance. So core infrastructure initiative is a.

A

Just say can tell it's a it's just a security certification, which is suggested by Linux Foundation and he's delivered a foundation active and adopt so that so what core infrastructure initiative, membership unlocks? Firstly, access to targeted as my security sponsorship programs, like security audit, etc also access to tools and, moreover, currently becomes a part of continues. Aw foundation, maths, the requirements to graduate the city of project, so I think, would be a good thing for us to be officially certified as core infrastructure initiative.

A

There is someone information about these best practices or pledge program which defines the requirements, and that was also the carbon certification. I started an experiment in January, so we are currently at 88% of the checklist.

A

So there are two major areas with me to address first list to introduce Jamie Scott triage team, which makes sense in any case and which was one of the flops at our respectively. Had two CS in the previous baseline and another is security, but we mostly need the security team to clean up the question over there and to ensure that we also because I didn't really spend too much time on this section. So we are close to completion my opinion and it would be really beneficial to the project.

A

So I would suggest target to the roadmap.

A

What everyone on the fine with it? Yes,.

D

First one for me.

A

So we have plus one from Alex only Oliver. Do you think it's.

E

Okay, yes, I'm, plus one.

C

Yes, sir I'm practically involved with your roadmap discussion, so I guess I will abstain for this one mm-hmm.

A

Yes, oh, there is a no impact on the LCS process in my CIA certification, I'd only William, sorry.

B

This appreciation, which.

A

Make our priority as for Sean okay. So if everyone agrees we'll just measure that also there are other pull requests, one is about both directions and other one has a code of conduct candidate, which is not really really it and how both directions. Basically, it's just restriction and called the page and some working so again, everybody is fine. This public quest I suggest to take a look at synchronous game. Sometime. I would like to not sure that it was just the preparation for the volume up as well, so.

A

I think it's for synchronous review so that we didn't spend too much time in the link.

A

Okay, that is no question. It's about the roadmap and the second eye.

A

Victoire governs the communication.

B

Sounds good okay,.

A

So we have two pages: actually they have a little more pages, but the red magic ones which are currently on weekend on his approved trademark usage, and here, for example, we have basically a history of previous approvals and this history is not complete because, for example, one months ago, I asked for trademark is approval for Jenkins row and I can actually edit here, because it's a protected page and at the time when we agreed that I would follow up and to see how we could move it to jang seong. It's basically today's agenda topic.

A

Another similar page is commercial support, which is companies providing for those kinds of commercial support for Jenkins. Again, this page, probably it's not protected, but I think it's something which would make sense to move to the changes on your website, maybe after some cleanup.

A

So in order to do that, we need to have a process. How do you manage that? Because gentes is basically a shared resource last week as a part of drinks, I love copy editors are important. We created an element in our guide and this might even write explicitly. The commands work is the ownership structure and all documents are under the project explicitly managed by the government spot.

A

So my suggestion would be to say that this maintainer guide is enough to say that the resources protected well enough and that we can adjust all these various teaching Sao without inventing new repositories and other things.

A

So my proposal will be basically to move for these pages to Genki sale so that they would appear under the project section here now we have governance documentation. Their code of conduct is both elections and also some team descriptions. For example, first name team is documented here right now, just because I didn't find a better place and I suggest to become of trademark information. There.

D

So what do you think about it? I think I think it's the right approach, I think it's comparable level of import of value that we need those pages on Jenkins that I own and we need them under control of the governance board and I. Think using the the code owners technique that you've used on Jenkins at I/o is sufficient and gives us a good history. Yes,.

A

Oh speaking of kodamas, we have both. One is basically github. We have katanas and if there is any page within the project, scope governance both will be automatically deploys that so that we will get notifications so that if there is a pull request suggest also, we have etcetera. So all public press which go against governance, the communication again they will have governance label assigned to them. So you can subscribe to this label. So you can just have a query and accessibility request.

D

Are you aware of any cases where we've got a governance document or leg? That's not explicitly a governance document on Jenkins that I? Oh, that's, not explicitly controlled by code owners.

A

Well, if we discover such a document, we don't just add it yeah, okay,.

D

Good so so there's a process if, if there's a gap detected, we just insert it into this definition. File yeah.

A

This process is quite simple: just submit a pull request. Great okay, thank you yeah, so.

A

Yeah I just wanted to keep the things simple. So if everybody is fine with it, I will just put the documentation there.

A

B

Think it's a good idea, it's a plus one, but that's after four! So for the support page Oh like that, that's after we update that right. Well,.

D

Part of the transition is to bring it in and update it in the transition process. I will assume you know like. We can't alter the existing read only thing on wiki Jenkins that I already.

A

So commercial support, theoretically I and all of you have access to that. Maybe marques William well, because we got advance access to Jing this week as a part of flagging the communication immigration story, but common contributors don't have access to this page. So, for example, if let's say forest technologies well, this company doesn't really exist anymore. It was acquired if they want to modify the stage. They cannot right.

A

So yeah by moving to Jenkins I, will be basically and make it possible again to at least submit a days. Maybe we need to build this page from scratch, because voila I know for sure that some companies around that some companies would be willing to update about some of them. I have no idea.

A

We could at least start that process.

A

And for me, a trademark user probably is more important.

A

In other world holes you.

E

Just sleep with one years.

A

So I will just submit a pull request then and theyíve. There are modes, for example, from Alex Harold, and we can call that the decision has main so I also target three. Both number approvals.

A

A

Actually, that's it from the agenda so again same question as we've had before.

A

Do you feel that this for Monte is okay or whether we do we want to switch back to our set I.

E

Like it see you at least Wow a couple of people, I never seen so Oliver, for instance, I, never seen so it's really nice to see.

C

Ya, fortunately, for me we beat harder to do. It is owned on a regular basis, but I guess I see the shift towards diverse. You know, I think channels for at least DD areas where I'm active, so yeah I probably won't be able to attend as often but not that much uncover inside anyway.

A

So we can try to make this call even more synchronous, I believe that it still makes sense to have regular meetings. Just although some discussions in Cup was celebrating means in the giantess project, but you should know for decision-making no thousand channels as much as possible.

C

Oh yeah I wasn't objecting to that. What I was referring to specifically was the obvious baseline selection and under reviewing of the changes which we essentially sort of moved out of these meetings, unless those especially right and and.

D

That the healthiest baseline selection, using its current process, doesn't if I remember correctly, doesn't actually have to come to buffer government's. It's it's entirely. Your call Oliver and that's great, so you don't actually have to be here for that. That's I just brought it here, because you let benefit that you're. Here thanks. Oh yeah,.

C

For sure, it's sorry did it's just a hobby that haven't vanished, yet we've been doing it for years this way and we change the process and even ice able to follow it. So that's where we are.

A

Continuously change the processes now so and hopefully be improved overrode, so yeah thanks a lot for joining the LT has changes so I think that it's perfectly fine to do. You can sync mode and effective discussions in the mailing list out. I'm perfectly fine is how it happens, okay, but it would be great to communicate the digital decision to the developer mailing list, because some users start asking what is a big decision on the Wednesday.

A

Historically, we announced it on Thursday if we could communicate the great.

A

Anything else to discuss today.

A

So the next meeting is May 20th, I, guess nothing. Crew is really working. This meeting from happening on this date, so I think we can just keep the usual schedule.

A

Then, thank so for time.

A

Charles Thank.

B

C

Thank you guys.