Jenkins Governance Meetings, 15 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Governance Meeting, Jul 15, 2020

Description

Recording of the regular Jenkins Governance meeting on Jul 15, 2020. At this meeting we finalized the list of terms for the terminology updates voting, signed off publishing of the Jenkins Roadmap, approved changes to the downloads page, and discussed the CDF graduation status. Full agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o

More info about the Governance Meeting: https://www.jenkins.io/project/governance-meeting/

A

Hello, uh welcome to the gents governance meeting today is july. 15Th uh you have uh alexa. Will you have around me on the call? So it's the middle of july and everything is quite uh slow with these.

A

Let's take a look at our agenda, so regarding news, one major update that we have uh jenkins code of conduct upgraded from version of contributor component 1.3 to 1 to 2.0, so it included a lot of changes, and here we approved it at the previous governance meeting. But now everything is in place and published on our website.

A

So this is a code of conduct you should refer to. It includes uh several major changes, including our pledge, our standards and also some changes in the reporting flow. For example, now cd foundation is a second level of escalation. uh We also added a line about the regulation of uh board members so that there is a path for reporting that somebody is concerned, and they will also minor updates here and there, but generally there was strong as a consensus about accepting this code of conduct. So hopefully everything is a key.

A

Now alex heavily participated in this story. We also did some reviews, so I don't think there are many questions about that, but yeah.

B

Thanks for doing that, oleg.

A

Happy to do that and thanks to all the reviewers, because, okay, we had something like 60 viewers and the main pull request, also a lot of figures and code of conduct, changelog changes, etc. So thanks a lot any other news which was mentioning. Oh, there is a security release today.

A

So if you are interested in drinking security, we have just released a version with a lot of xss changes in the jenkins core, so you can find it here and please take a look, because some of these vulnerabilities are high severity ones, so actually pretty much. All of them are high severity ones. So it's definitely a good time to upgrade.

A

Okay, any other news.

A

Okay, so the next topic is terminology of these. When we stopped at the last meeting, we agreed that we need to select a ton of 10 items.

A

I guess the agenda for today is still staggering on this. Top 10 items and unblock mark is so that we can start voting. What do you think.

B

Yeah and I don't I don't even necessarily think we need 10 specifically, I mean we talked about 10, but if there aren't 10 good candidates.

C

B

I think we just need to select the number of good candidates and I really like the um the recommendation we kind of look at it um in terms of like those sentences like likely mentioned. I think that was helpful uh to me at least so. um Do you have the the document um that we had all the options in or do you want to bring up the email from the governance board just.

A

Just a second, so we have a google doc with all options um and yeah. If you placed in the discussion from the governance board, I think it would.

A

So I will just add it to the top.

A

A

A

Up alex, would you place the options here.

B

Yeah I'll put them in there.

B

I have that document open so.

B

By the way, I um I someone sent a request to tyler for an interview about this, for I don't remember which website and I did a little bit of an interview with them about kind of our progress and reasons and stuff like that. So I'll provide that article when it comes out.

A

Yeah, I guess it went through press contacts right.

B

A

I was actually thinking whether it makes sense to just replace these press contacts just by jenkins governor's board email but yeah. I'm not.

A

A

Anyway, it's a bit out of topic, but yeah anyway, thanks a lot for doing the interview.

A

A

Let's know when it's published.

A

So there agreed to use a professional term.

A

Which is easily localizable to other languages? This is our criteria right.

B

What's that sorry.

A

So we agreed that we need a professional term uh which could be easily localized to another interest rate. Yes, basically, the criteria we consider.

B

And this is kind of the list, basically paired down from what we had what I originally posted in the board: governance board mail, removing the ones that were not kind of professional, as you mentioned.

B

So there are only nine items here actually, but these are kind of the ones that were the ones that kind of removed anything that had kind of language barrier in terms of um translating, as well as things that didn't sound quote. Unquote. Professional.

A

And we also removed the server and host right in the last list.

B

Yeah, so we remove those just because it can be confusing. If you say jenkins server, is that the physical server versus the um you know that sort of thing, so we kind of remove those. For that reason,.

A

Yeah, I would have voted for servers still, but it makes a lot of sense.

B

So I'm I'm myself, I'm leaning towards um either primary or controller, but that's just my own personal opinion.

B

So I think we can roll these over if we're in agreement on these set of options, we can roll these over to mark to set up the um the public poll.

A

A

One question about uh primary: so it's just primary or primary node.

B

um Just primary.

A

You'll be using this primary.

B

A

C

I think these terms, like primary or main, are really hard for other languages.

B

C

Because they are more used as adjectives, um for instance in germany,.

C

Okay, but we will see it in the vote, so I think it's okay to have them here and let everybody vote.

A

Yeah so important thing that we select one of these options, so there would not be option 10, which we selected reviewing the loads.

B

Now we did, we did make it kind of um well. We we tried to make it clear that um this is just inputs to the governance board and even the if the. If the top voted item, it doesn't mean that that necessarily will become the name right. It's just inputs, so we that that's something to think about too is if the top voted item is something that we feel still doesn't um meet the criteria that we want because of language translation type things, then we can still pick something else from the list.

B

It's just to kind of get a view of what the community is is thinking or would be clear to the community.

A

And we use every single transferable load so that, if option one is not selected, then option two will uh take adjusted hours anyway.

A

Okay, I think this is a good list and we can just agree on that.

B

Yeah, I'm good with.

B

A

Okay, we'll just.

A

A

A

A

So anything called else in terms of job. This topic.

A

B

A

Okay, then, I think we could move on.

B

I'll send that list to mark just so he has their information.

A

Great thank you, so I guess it means that we would start voting earlier than next week, because yeah mark is off right now, but yeah. I think there is no hurry.

A

And we still need to prepare an announcement somewhere, I'm not sure did we agree to do it in social media on the developer, mailing list.

C

A

Yeah so we've had a discussion uh at the last meeting, but I don't remember whether we had a consensus there.

C

Yeah, I don't remember that we talked about exactly.

C

A

C

It's good to have it on the mailing list. Okay,.

B

So I probably built the user and developer mailing list.

B

Okay, that way reaches a wider range of people.

A

I'm sure that too many people are using everything user mailing list. Well, there is a decent amount of reads, but yeah.

A

A

So basically, user developer and maybe some signaling keys, not sure.

A

But yeah we can start from that many keys. If you feel that we want to do more to have more votes, you can expand the outreach.

A

So no blog and no social media.

A

So, okay, let's move on um jenkins david duration report, so quick updates. We have completed the checklist and during the completion, actually we made significant updates in our documentation. So, for example, a code of conduct was updated, as we already discussed. We also created a new page, which lists adopters.

A

Using the information we have got through jenkins is the way and if you want to add your company, please just submit a pull request. Everything this uh configuration is called now. Documentation is called and yeah. There are guidelines which you can follow if you want to add yourself to the list.

A

um So what else do we have? We have recommended the weekly releases, apparently before that we had no documentation for weeklies at all, so there was some circuit knowledge and discussions in the mailing list, but now we have guidelines here. Plus there is maintainer guide, which was also slightly updated to document the weekly release process, so yeah we got some documentation and what else yeah? Basically everything was also referenced from our landing page, which was quite shallow on details before that.

A

So now there is just a bit more information um this, along with our cdf radiation checklist, basically allowed us to say that we are compliant with all requirements defined by cdf for graduated projects. So if you open this google doc reference in the mailing list, you can see that yeah everything is passed. There are details attached to the right which expand uh our response and private information. uh What uh exactly is passed later? We likely need to convert it to another form, so it's but yeah.

A

The form is yet to be provided by cdf, and this forum is okay to start the reviews. So if somebody wants uh to contribute and wants uh to expand these descriptions, uh please just submit a proposal. uh You have anyone can send just changes in this document and we can keep improving it until the cdf uh technical other side committee meeting on july 21st.

A

So it's tuesday next week, this will at this meeting there was, there will be a review of our application. I'm not sure what would be exactly the process. My plan is to just join. The meeting. Can answer questions maybe presented this document a bit, I'm not sure alex. Do you plan to join.

B

Yeah, I would like to.

B

It just depends on my my work schedule if I'll be able to.

A

Yeah, so it should be something like 3pm utc.

B

Okay, so I'm yeah, I should be able to do that.

B

Where is, is there a calendar item that I can that could be downloaded to add to my.

A

uh I believe I referenced it somewhere. Okay,.

B

I'll look in the email, that's fine!.

A

Yeah so, based on the discussion, we sent a message to review and yeah. Everyone is welcome to join the meeting so the meeting player inside here.

A

So basically they have a second.

A

Yeah agenda, I believe.

C

It's on the 21st.

A

C

Yeah, that's my wife's birthday. No time.

A

Well, it's a really good reason so yeah, so it's city of top meeting and here sailing. If you want to join.

A

Okay, uh so that guess that's all uh for cdf radiation. I think that everything is in pretty good shape there and it helped us stop improve our own documentation, so we can move on with that. My only concern is about.

A

Our governance speech, because, to be honest, this governance speech is really outdated, so I was thinking about partially rewriting it so, for example, just to show a few examples. So our philosophy- yes, it's okay license is a key contributor license agreement. It's inherently updated on its own, but it's a separate problem.

A

Then what we have trademark here trademark is okay,.

A

The attribution is okay, then there are some items here which basically came from my very first generation of jenkins wiki, which was also a drinking society. At that point and some changes, some things just need to be updated, though we update it irregularly but, for example, you just scroll down the rest reference to rc no detail same for main keys, or it should denote the references at the proper link.

A

Also, for example, we reference wiki, we reference, jinx and jenkins without reference and other services, etc, etc. So in general, it's a generally it's a key, but yeah some facelift would make sense.

A

So this is something I would like to do until the the talk meeting next week, but I believe this is the last thing I would be doing for our documentation. There.

A

So do we need any special process for updating this page, or is it fine to just have a simple majority.

C

I think it's just a good put in a pull request, or what do you think yeah.

A

Anyway, I don't want to change anything in principle, so rather sleep and clean up all the text.

A

Okay, so anything else. What's about the serial nudition uh one thing which was mentioning tomorrow, we will have advocacy analysis meeting and uh my understanding that we will be discussing uh marketing uh for project graduation there, because cdf uh wants uh to do a lot of promotion on their side, and I guess on the jenkins side, we would also like to publish a blog post or something like that.

A

So I will add a combination of these efforts to the tomorrow's message.

A

A

So there is a plan to us some webinars, some podcasts etc more details to come soon, but here we will be definitely taking it through the mailing keys so that we can get more contributors participating in these.

A

A

Any questions comments about that.

A

So for that I will definitely send a summary because right now, I also don't have all the details of what would be expected with cdf plans to achieve so. Let's just wait and see.

A

Okay, so accord infrastructure initiative, so it's slightly related to graduation as well, because it's also part of the graduation requirements uh passing a current infrastructure initiative checklist, although, according to clarification by cdf cdf, is fine with our current 80 percent.

A

So we don't uh really block it by current transaction initiative, but we have two main sections which still need to be finished. One is about uh quality, so there is. I mean there are two items. uh Sorry, it's about quality about reporting, so we must acknowledge uh a majority of buck. Reports should respond to majority of our fees.

A

So this is what we are trying to address with the trash tim and jenkins, and recently we have integrated a full request. So now, if you go to the maintainer guide now we have the community documentation about issue triage and the recommendations of how to do that and how to work with reporters.

A

What is actually objective uh for a triage team, but there is still one major problem: we need to have 18 so likely. I will be organizing something to do knowledge, transfer or whatever for the next week or just some discussion again, I'm not sure how many contributors you would be able to uh get there, especially during the summer vacation break, but at least we could kickstart this effort so that there is some more offline content available to potential contributors.

A

So this is what we have for issue triage and the second part we have on the list is security, so for security we actually have a lot of items. To answer, and for that I submitted a draft to the security team. Then we had a few cycles of reviews and now it waits for final approval by daniel uh who's, the security officer. So once it's approved, we can actually close uh all these action items as completed at least my current understanding.

A

We are compliant with the requirements and taking a little bit from the security team, um it should be a keys.

A

So once we do that, once we do the triage team, we will get to a bit more than 100 percent uh and yeah. I believe that we will be able uh to see that this effort is also completed and in the future, what it allows us. We can, uh for example, ask linux foundation and nci members for funding, let's say security, audit for the jenkins project and many other items, because cia is a widely funded funded program. I usually just a lot in security.

A

If you can apply, it could be helpful for us.

A

Okay- and you can.

A

B

Do you um do you have a list of people who have kind of um volunteered for that triosh team so far, and is that a big enough list or do we need to continue to kind of poke people and ask them if they're, if they'd like to help okay.

A

Let's see also, we have a number of responses in the mailing list, so okay, so this should be my necro post. Oh it's here so after that we got number of responses, so uh me plus five responses there.

A

So, theoretically we could form a team. All these five participants could dedicate some time- let's say a few hours very well per month- let's see but yeah again at least we can start documenting that and facilitating contributions by obviously and lately, if needed. We can also do a lot of automation using rc board and whatever, because here we can have canned responses and whatever to learn to help maintainers.

A

B

I just wanted to make sure there was enough people to help out with the effort. So it looks like that's a pretty good amount and a lot of them have good experience in debugging issues. So should work.

A

Yeah right, yeah and actually yeah just dumped metrics.

A

So even now, even if you take crude metrics for responses for jenkins core, I created some dashboards etc, and there you you can see that over the last year, which is a cia requirement, we have received 491 battery ports engine score and for them I have only only 214 unresolved tissues and what I was able uh to see. The majority of these unresolved fishes actually got the first response, though, with our current general setup. I cannot automate it and create a dashboard for that, but yeah.

A

Even with these crude numbers, we are kind of compliant with the majority requirement in cia, because majority is more than fifty percent right.

A

uh For his it's a bit worse but yeah, I think we can get here easily.

A

So I'm a bit optimistic there, but yeah again. It still requires a lot of uh effort to get it actually working. We got the core maintainers team uh operational uh this year. So now we have a lot of people who contribute to reviews uh and integration of full requests.

A

So maybe you could also do some bits for triage.

A

Okay, does it answer your question alex.

B

Yeah, thank you.

A

uh Thank you too,.

A

Okay, another process issue. um I made an update for the downloads page. Basically, it's a follow-up on old discussion. I guess in the platform or maybe the governance meeting so on our current downloads page. It actually includes just seconds here.

A

So our current page includes a long header there and after that we have listing of uh distributions. So there are a few issues on this page or one issue that this header again moves to the bottom, as well as these paragraphs etc, but also there are some more concerning issues. For example, here we have a mix of third-party and official packages, for example, our main official packages were so what is just in the bottom of the list.

A

Documents on the top windows is on the bottom again, so I would like to actually get these packages sorted and also. I would like to move for deployment toy usually to the bottom, because deployment to asia again is not official package. It's a custom distribution being built by a microsoft, azure team, so um I submitted the pull request which refactors this page so that it becomes firstly shorter and secondly, it aligns pages, and it also actually provides some guidelines which we are updated before and the deployment the plant junk is in the public cloud.

A

It's just a section in the bottom and yeah right now: the inputs only deploy to asia and later we could get. For example, google instances open shift instances or whatever.

A

If you decide to do so, I didn't touch it in this book request. I just uh retained the existing content, but I think that principle we could extend it.

B

Is the deploy to azure? Does that um allow you to specify which jenkins version when you're doing it, or is it just the um uh like the lts version or.

A

I guess it's only lcs version, okay, so I'm not locked in in my azure account, so I cannot uh show yeah. uh I guess it's on the lcs and uh since uh and usually this releases some of the cardinality. So what it means is that this releases might be delayed. For example, in the case of security releases.

B

I was just wondering because previously the deployed azure was directly under the lts stuff, so it's kind of um so you could tell that it was lts, but I don't. I don't think that matters. I think it's fine the way it is um because.

C

B

Long as um or if there was a way that you could see which version on that um marketplace, page, which we don't probably have control over at all,.

A

Yeah, this was basically optimistic because we don't know yeah, okay, so, for example, we just released this version a few hours ago and yeah on the on our plugins on our site. We already said that it's 2.235.2, but I bet it's not really a case.

B

Okay, so I think it's good that it doesn't have a specific version then so yeah I like that.

A

Okay, so yeah. Basically, I just wanted to get approval because it's a sensitive page, which is basically one of the most visited for jenkins.

A

So if you're fine with that, I would like to just uh ask for all to nudge it yeah.

B

It looks good to me, I think I I think I gave approval, maybe not.

A

No, you didn't ah so what I will do. I will ask for your reviews and if you approve that I will nurture it. Okay.

A

Okay, I think that it's ready to go and it's not that drastic, but at least some improvement.

A

Also, it was mentioning that this page doesn't really work on my bio.

A

I I'm not really sure why you would you use it on mobile, but if you do like that, so what you can see there that basically uh all the content shifts a bit so, for example, they deployed so you have long term weekly and then there is a mix of different types in there. So it's not critical but not ideal as well.

A

B

All right, you have my approval on the pr.

A

Great okay and the last so should we move on.

A

Okay, so yeah jenkins roadmap, so for roadmap uh last friday we had a contributor meetup, so the video and slides are already available. Basically, this meetup, I represented the public world map and public roadmap process. I got some additional feedback, but generally the roadmap remained the same.

A

So over last few days I submitted a few patches so, for example, a patch to the jenkins enhancement proposal, thanks uh to leave for reviewing that so now, jinx enhancement proposal is totally aligned with the current roadmap stage.

A

um Just second, it's here job 14., but it's more. It was mostly about updating status, definitions and list of statuses and updating how roadmap works, because it's uh it has greatly changed since the last version. So this job, I think it's formally related to publishing.

A

Well, basically, it's alex, uh who made who makes the final decision but yeah personally, I think that it's ready for the final review and approval.

B

Yeah, I agree, um so do I just uh merge it or what is the approval process? I'm clear with that.

A

So the approval process is that somebody submits a pull request. So what you need to do you need, for this repository, create a branch, and then there is a script in jab which sets the jab status so set the job status.

A

And since it's a protest jab you will need to send the status to active. Okay, though some jobs actually use accepted, I'm not 100 sure. What's the difference, I need to read the jab on my own. I mean one uh but yeah. Basically, the draft needs to be converted to one of these stage: states.

A

Okay and then you just submit the pull, request, changes and that's it.

B

Okay, I will do that.

A

A

Are you fine with publishing that.

C

Yes, it's good.

A

Okay and yeah, another question is actually about common pull requests, so I have a few submitted so support for archiving roadmap and also some content edits which are waiting for reviews.

A

So would you like to get it integrated to get them integrated before forming us of the job, or is it trying to do testing.

B

um I think it's fine either way.

A

So supports archiving basically gives us an opportunity to move all completed through the map items and withdrawn once to a new file which is archive yaml.

A

Basically, it's not displayed in the web interface, it's just linked from the bottom, so that if you're interested you can go there and yeah. I don't think it's worth spending time on creating visualization for that, but we could do that and actually that's all it does.

A

And for the rest, here we have plugin management. Ui improvements is actually one feedback from the recent online meetup, because I was going to the presentation and somebody said that hey one of your items doesn't have a proper link because your plugin management, uh your improvements, had no documentation, so it had no link there and it was just redirecting to the roadmap itself. So what I really did, I just added the definition on the uxc page and the edit the link, so it's compliant with jeff again.

A

Only another thing we also follow up to the same feedback is a pipe pipeline altering roadmap. A few items listed on the future also have no link, so they just extended the code a bit so that if there is no link provided, we just reference uh initiative, link. Sorry, a critical link, usually references, the special interest group or to something else. At least it helps to narrow down the contacts.

A

So these are three pending pull requests and the last one is basically just saying that it's a subject removing disclaimers, etc. So this will dimensional uh only after the job is accepted and.

C

A

So yeah, sorry for the pull request spam but yeah.

A

I hope these are the last ones which are required to at least have the roadmap in the ready-to-go state and then again it's not the final stage because we will be doing updates incrementally and I think we could schedule an official roadmap meeting to august so maybe or maybe even september. What do you think.

B

um I would say september might be good, just because august is gonna, be busy with uh people going back to school in certain places and stuff and trying to figure that out in terms of kids, at least here in the u.s.

B

So if we can wait till september, that might be nice. Otherwise, although it may impact people in september as well. So I guess it's. Whoever has the least amount of impact.

A

So I guess it means after august 15th, because I guess in the united states and europe it's mostly august 15th.

B

Yeah, that's pretty close to ours. Our official date is august 5th, but um so maybe late august or middle of august would be the best.

A

A

So again, then we can just discuss the data, maybe at the next governor's meeting, so no harder with that, but yeah. I would also wait a bit before that and again we still can uh facilitate feedback from seeks etc. To add more roadmap items. Oh it's! Actually it's also already quite full, but yeah. We can highlight more initiatives.

A

For example, we will have a presentation uh at the cloud native seek about the tecton trigger plugin, so, for example, for cloud platforms I would like.

A

I would like to split this item to two, because there is a configure, plugin and also a ticked on pipeline engine as a pipeline extension which we discussed, which is a completely different item with completely different scope and which will definitely remain in the future.

A

So any comments, questions on the roadmap.

B

Oh, it looks really nice. I I've heard a lot of really good comments about it from people so nice, nice work and thank you.

A

Thank you. Let's keep pushing that.

A

Okay, so I think that's it uh for today, so if it's possible, would you be able to stay for a few minutes uh after the recording, yeah, okay, so yeah thanks all for participating in the meeting and see the next one? I guess it will be in two weeks july 29th. So next changes yeah? Okay, thanks so.