Jenkins Governance Meetings, 20 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Governance Meeting, May 20, 2020

Description

Recording of the regular Jenkins Governance meeting. We discussed the recent news and releases (Docker images, GitHub App Authentication, Read Only Permissions), Google Season of Docs participation, Cloud Native SIG restart, and Jenkins UI/UX Hackfest. We also approved support policies for Windows OS and for UI themes.

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

Governance meeting: https://www.jenkins.io/project/governance-meeting/

A

Well, welcome to the regular Jenkins governance meeting today is my face. We have several contributors on the call. My name is Alexander chef, Aaron, one Jenkins governance board members, so who is also doing this board? Member mark ways is at the communication officer and the mutation specialist top leader and much Genki Jackson is a little of the advocacy on atresia special interest group. So at this meeting we just discuss what happens in the project and make decisions on key items submitted by the contributors and the developers medically.

A

It's like voting for particular issues, etc, but the most of the discussions happen in the mailing list, and this is a section a session to just formalize these decisions.

A

Okay, if you know, want to know more about governance meetings, so that is a page on Jing desire agents, AO / project, / governance meeting, and you can find all the information there and you can also see the embedded document and by the way, here's our agenda. So we have a few topics for today and some good news about the projects in Jenkins. Also, my request for prevent wasn't for your heart. First repository your themes, support policy and Windows support policy.

A

So this is what we have now and if you want, the topic just feel free to put it to the agenda. So.

B

A

I will start from road map updates, so we have a work-in-progress public road map for the jingis project. There is a number of projects which are currently under active development, so you can see them here. It's actually quite least. We have somehow good news about these projects. So since the last meeting they were multiple updates. First of them a bit, we finally made their official docker images. So now it's Jenkins agent, Jenkins and boat and jenkees ssh agent. That is a blog post on genocide with a summary.

A

So it moves agent terminology cleanup project for world which we handle an unboxing outreach special interest group, then related topic, official Windows images. So now we have official Windows images for all the same agent repositories. We have continuous delivery process for them. We have releases and everyone is welcome to start using them, so they consider stays fully supported images and what we will talk a bit about what fully support means.

A

Okay, then, another major update that the project by Team, Jacob, alien-human, etc github about identification support. It was at least as preview one months ago, but now it's in a Jensen J. So you can just go to the Jenkins update Center install a new version of github range search, plug-in and get out in Turkishness github up, so you higher right limit user, independent out unification and from security, etc. So this is also an item on our roadmap. It's great to see that and also the reason going development in google Summer of Code.

A

Just today we have published a first video about proof of concept I've been developed by our student. So if you interested to go to the Jenkins YouTube and you can find it so this is this project and github check see a or Jenkins plug-in, and only maybe you would like to summarize the current progress all the way here. Yeah.

B

Of course it was a really nice meeting. Today we had a presentation of a prototype with which already does a lot of things. So I've now have a good feeling about that. There will be a good outcome of the project. Of course it's just a prototype and you know the code needs to be cleaned up, but we already have yeah kind of design document and we know a lot of steps. We should go forward and I think yeah. It will be a very successful project. Hopefully.

A

Fingers crossed it's really important to the jinx coming Indian, so yeah, thanks for working on that and yeah by the way. Once you have this major updates, please don't hesitate to be the project description.

A

We put a blog post for now, yeah.

B

Not now yet, or do you think just for the prototype or for why not if it helps to facilitate the feedback.

A

Okay, you can same for other projects, so apparently all people on this call I mentor, seeing one of jisub project or maybe multiple ones. So if you have a prototype or whatever, which would be should the showcase.

C

Please the sole so like as a topic on that theme. We've got an upcoming releases. They get plug-in that will include symbols for pipeline and some other stuff. Is that a viable blog topic? Why not? Okay, alright, so that that that would be one where I could blog about it. Great alright, thanks mm-hmm.

A

Well, any blog posts would be appreciated because again we want to share stories. We want to improvements about the project and, if it fit it, so the user experience thing yeah. You know what to do. We will talk about that later: okay, okay, so yeah another thing which is coming soon, hopefully the next week, please make sure to update in system repair mission. I have an action item to discuss. One would be the weekly release, so long story short.

A

We have a pull request which is needed to finalize this story and we need it for the next week for crowd, taste and jacket on, because system rate is really important. For users of configuration is cold, so there is a pull request from which is awaiting for reviews and more reviews who would be appreciated.

A

Yes, here extend the system with an extended rate for agents, so actually what I'm going to do I'm going to ask for maintenance about having police, not on Tuesday, as we discussed now, but maybe on Monday or even earlier, so that we start testing that there were three contributors already tested. That and I think that we could learn that so yeah I'm about asking for such deviation, but I think it's really important for the project. So the.

C

Idea, then, would be system. Reid would be in a weekly build even be at the launch of the hack first yeah.

A

We have an event scheduled to Tuesday, about system, permissions system, etc, and by this time it would be awesome to have it and the Jing is victim. Well, as assuming that merge conditions are passed but actually be passed even now, I prefer that I just moved it back to review, because I wanted to just a bit more but I'm happy just that the official measure condom so that we could integrate it tomorrow.

A

A

So sorry, for such detour about uncommon changes and ongoing changes, but I think it would be useful if we cover it a bit at these meetings and if you feel that we should read focus on other stories, just watch these cartons.

A

Okay, next important news, we have been asserted to Google season of dogs. This is our first-ever gain, G sod- and actually this is a second year of Google Docs at all what it means to the project. We will have a technical writer working on the project from September to December or maybe even one day, if it's a long-running project and it's a good habit, you need to improve particular area of documentation.

A

We have a number of project ideas published here, for example just in the immigration and update documentation and documenting changes on kubernetes, recognizing user documentation and probably extended in bed and also creating new solution pages. So this is the project IDs we have now and if anyone is interested to submit more project ideas, please do so thanks to mark for submitting newbie friendly issues etc, so that students can try contributing something.

A

Apparently, actually we got a number of public question coming from potential mentees in this program, so you've got nine hundred ways right, mark dejoy, soap and Counting, so we already get some contributions and obviously variant facility bit. So if you have any project ideas, please submit them. So we have one months until technical writer applications start so by the time it would be great. You have all projects in place.

A

Okay, so another quick update is cloud native special interest group, so it has been dormant for one year we had a long discussion at the edge. Inc is contributor summit in Brussels in February a in January, and there was a consensus. But yes, we wanted to recover that. Yesterday we had a first kickoff meeting with those who joined the meeting, so we had around eight contributors there and we agreed to place it on this cover.

A

So major change is important for the project that we rather switch focus to user stories, so it means plugins within the C&C effluence keep managing Jenkins and kubernetes Jenkins on five providers and other things you can see in the list.

A

We still want to work on architectural changes, but architectural changes would be rather scoped to form or to focus on delivering user features, because before that, thus it was highly focused on architecture or cloud native Jenkins and yeah personally, I'm, not sure whether you really need a cloud native Jenkins or we need web friendly Jenkins and while foraging is for me it's also a really good goal for this seek.

A

Okay, if you're interested there is a recording that there are meeting notes starting from June, we will have regular sessions, but basically it's back and it will be a big pages.

A

Okay and yeah other important update is Jenkins, UI UX hard-pressed. So if you have participated in any community meeting over past two weeks, you may have heard about that because we discuss it almost everywhere, but yeah. The idea that we run a one-week hot first, specifically focusing on improving changes, user experience and it's about user interface, documentation about stories leaking tutorials, providing guidelines so that users can easily use Jenkins and easily they can find the information. So right now we have three tracks. So it's user interface, it's user documentation and spread what we spread.

A

The word I need to submit the pull request to fix that, but you just shine whatever stories, including leveraging the Jenkins the way program we have started two weeks ago, I wish was approved at the governance meeting so yep. That's the plan currently realigning Colombo of events. So there is a draft. We have already published a few of these events. Others will be published by Friday and hopefully it will be a great event where we will have many tributes joining right.

A

Now we have 50 address VP's in our registration form and we have around 80 address VP's to the opening Meetup I personally I have no idea how many and she deserves to be a bit in total, but yeah our hope is to have around 15. So let's see any comments about that, any questions.

A

C

So, like the the gathering, the contributors work, the repository that you proposed I think that's later in the agenda, isn't yeah. We can just switch to the detection. Okay,.

A

Okay, so one of the challenges for us in this head, fest that it includes not only code contributions like submitting requests. That part is easy, but it also in contributions, for example, reviews user experience, testing and also spread the world, including submitting stories posting about Jing is etc. So we need the mansion which would allow us to record these contributions as a part of discussions, we discussed multiple ways to do it. One of the ways was to just have a Google Doc, where everybody would be able to record contributions.

A

Another way is was to have spreadsheet in Google, for my is basically the same, but I actually suggest a bit more sophisticated way is having a separate repository where everybody would be able to set me in their contributions, and this is what I propose here now.

A

So I'll briefly show it to you how it looks like right now, so other is a UI harvest page. Basically, it's just implemented in a week Mindy, and it has some advantages being compared to the form, because we invited contributors to submit information about the equation says get heart issues. So, for example, here I can submit URL enhancement, bug fix or whatever event and basically for each contribution.

A

We ask participants to summarize what they've done share some links to share screenshots if possible, and if we, if we submit, if you just said Satish's, then what we will do will total so them we will include them to the list of contributors. So you can see it right here. We are using all the contributors, it's a default. Well, it's pretty popular engine which allows tracking tribution, so we will be putting them there. Also.

A

We can aggregate this information, for example, for daily summaries weekly summaries, and we can use that to generate reports when the harvest is over. So that's why I propose using such maybe a bit more sophisticated engine, but it will be hopefully more efficient in terms of collecting information.

C

So, just to reiterate, all I need to do as a participant in the hackfest is submit an issue to this repository and record and use one of the templates. That's there to describe my contribution and that will have recorded that yes, I'm attempting to contribute yeah.

A

So, for example, recently improved yeah.

A

Do I improve dogs on irrigation in part on Gingka, say.

A

So yeah, for example, I, can just link my pull request. I want to do that because I need some time to find it, but what I can do here? I can just take a screenshot of the new bar I created yeah I'm, just showing it in Y just to show how is it implemented?

A

I mean just user documentation. Then some requests.

A

And navigation bar yeah now it doesn't take three pages.

A

It's still difficult to navigate on a mobile. You are you, but this day is better yep and use. Your dog sections can be easily found, so yeah. Basically a report such contribution.

A

Ok, here how it looks like and after that, then somebody who reviews that what we will do will use the board because yeah I forgot the command, but it's easy as that.

A

So somebody reduce my pull request at something like that like for documentation, so I will cheat a bit because I haven't submitted documentation to request as a part of this hackathon, but please be sure I will do right. Oh okay, I just asked the pod to said.

A

Did the page, and here there is a pull request which basically it's documentation to the table and that's it so right now it has been a date only to the metadata button. When I they will be incremental requests which will update this patient all set documentation, I think here. So it's a widely used engine and open source and I think that hackathon is a good opening.

A

Try it out, I will all set welcome both today we let other boats which summarize these issues and create daily reports again yeah, together with Marquis we've been at the Jessup mentor summit in Minich this autumn last autumn, and they at least two sections which were related to community boards and promoting that so I have a bunch of thousand yeah all the use it ISM as my playground. Yet, for you agree that it's a good approach for sharing Ravens I would love to help on that. I have notes as well.

A

Okay, so, basically, what I'm asking here is is everybody? Is everybody fine in his hosting? So there were something like seven plus ones and we developed a mailing list. So will.

C

It host in does it matter whether it's hosted in Jenkins, infra or Jenkins CI. Does the organization which hosted matter I.

A

Would prefer to hosted in Jenkins CI because they have admin access, so I can basically hug things. Okay,.

C

But that switch me just great is that does that slow down any linking of pull requests into it? They just hyperlink into them with a pasted, hyperlink and that's efficient. They don't have to use the github link to pull request facility.

A

Excuse me: well, it doesn't really matter because github pull request facility or works across organizations. Oh my gosh, oh okay, good! Alright! So yes, how it impacts, for example, team mentions, but to be honest, I'm, not sure why we would need that I will probably create a team for the viewers. Organizers whomever wants to help is updating this website.

A

C

It okay! So then, ultimately, this readme page will represent when it's when, as we get towards the end of the week, the readme will have on at pictures of all the people who have contributed so we're left, 50 or 60 people as contributors there exactly nice.

A

So, let's my plan and everything cuz mobiles, automated so yeah as long as you don't have someone who uses strange, github, profile, etc, it will be easy okay, so if you're fine I will just move it because I need it for the commentation update anyway,.

A

A

Junkie, sherry.

B

A

Okay, I will kick survey team access later, so I will create a new team word.

A

Something happened, I still do this and how things work sometimes we're there. But okay. So now it's fostered on my pinky I gotta move the projects and okay so yeah it will keep passion quit, but I think that it's a good start. So, thanks for your time on that and yeah at least we've got it published.

A

So any questions or should we move on then from.

C

A

A

So the next question is about themes, support policy and again is related to the hug fest, because one of the items we put there right now is support of the dark theme, and why do they that would be in just to have other things updated to have better market place for themes, another topics which are currently and they drop the Google Doc.

A

So in order to do that, we needed an official support policy for themes, because the Urich see when we were discussing this topic, maybe a lot of concerns about how we align things support policy miss they need to evolve, Jenkins UI.

A

So there was a political for me which is based on the deafness discussion, so a better devilís discussion, and guess we got a bunch of first ones, not only we got one from Tobias, who is the making it of simple themes longing, so it's a key field back for us, then yeah. There was this pull request.

A

Actually, I didn't intend to have it rushed before the meeting, but I forgot to put on hold, but yeah just I still want to discuss it here and officially sign it off, because the policy is basically that we don't provide banner. We don't provide compatibility for themes so.

A

It means that we can break the themes by UI updates, which is must-have for roadmap. They will have stories like UI overhaul and definitely it's not something which could be reversed without breaking changes in layout structure, etc. So various page and right, yeah, we'll just show the current fashion since it got much I it's to be them managing.

A

So it's here things for user interface, so yeah this policy includes two beats. One is link. Is themes are provided disease without any warranty just taken from MIT license? Why explains why we need that guidance? How to report it and best practices for developers, so this is my world was proposed and the mailing list and sent off just a user bit of text. So my question to the governance meeting: are we finding with that being host disease? Or would we like to review it? We approve it may be diverted.

B

It's just fine so in this time just nurtured, but it is already merged, but right, yeah, sorry and.

C

I worry that I clearly approve. I merged it. So, yes, absolutely it's! My little post a post, merge approval, yeah, sorry about that.

A

Well, not what I said no worries at all. It's my mistake: I didn't mark it up proper accordingly and the mark was totally right to merge it because it's within a user documentation. So let's copy the editor, who makes the decision whether we merge it or not, and I'm not sure whether it was a good idea to put policy in documentation, but yeah just decided wait until we have some big formal. Why not?

A

But okay, if everyone agrees, we can just.

A

Move toward it, so I will probably make some updates during the hot fest and this pages, but it works. Okay. The next topic is a bit more interesting is about our windows, support policy, so jenkins project is 15 years old and during this 15 years, basically, we had no windows support policy at all well and for what it was. We still don't have linux support policy or support policy father any other system.

A

So the theory behind it that if you're able from support Java version, most likely jenkees will work- and this is a good theory, but we have a lot of native code, Jana Jana. We also have Windows service, repair and other components so.

A

It's not guaranteed that changes will work on any platform and this policy basically suggests change which documents the support levels we want to have. This is what we discussed in the developer mailing list right now. There is no conclusive decision there, where whether we measure this document or not, because yeah so we'll check what we have there. So we have some positive comments about having policies in general, but you know approvals and the level of permanent list for this particular request.

A

We have approvals from mark from team J comp and translating about the policy and suggestively discussed at the meeting and to see whether we need to got a motion back or whether we can publish a day's version and iterate if needed and.

C

I think we should publish, publish in iterate I, think it's it's adequate and beyond. So it's it's a really great policy. They have. Even if we did know iteration it describes levels of support and which things were actively testing, which we aren't.

A

So there are some follow-ups which will come up today and which worth noting, for example, currently we bundled net framework to do it. Zero binaries, for example, for Windows OS wrapper. We want to go to photo zero. Basically, it means dropping support for Windows XP service pack, 3 and so on. I'm, not sure whether it's that import in 2020, but it's a big technical depth for the project, a twenty20. If you look at the code, we have a lot of branches.

A

Tall same books come to google Summer of Code project, because there is no llamo parsing libraries, which would support that net framework to the zero at the moment. So we want to move forward and basically block compatibility of some Windows versions yeah and our support policies. Basically level one is just latest supported: versions of 64-bit and aversions, which we put in docket. Images, which is currently not latest, could have explicit and level two is whatever is supported by Microsoft, which is 64-bit level.

A

Three eats everything else, so it's no longer support versions of 64-bit platforms, 32-bit platforms, basically all other exotic, well exotic questions example: I spent I think I forgot part of my career working with Windows, Embedded and Jing. This works there, but I'm not sure whether we are ready to support it, especially since we have no practical way to fix issues at the moment and to test that so I put it to tier 3 same for preview releases same for wine, artists and other windows.

A

It gay imitations I have no idea where the junk is worst yeah. To be honest, but I definitely know that it works with cygwin again. It's not something I wish to further support, but yeah whatever, and we the level 4 would be unsupported so things which we definitely don't support. So it's Windows XP, although there and well there is a typer open all webinar service pack, 3 then I put Windows Phone, just an education edge case example, and basically any other Windows platforms before 270.

A

C

No, no windows, the visto support not now not ever.

A

Wow it's up for discussion, but with the current policy it actually to be still.

A

303, so I still need to fix the spelling commit before margin, but in principle this is what I support and for mobile ones to improve. This policy welcome to fly from special interest group, even welcome to solutions.

A

Okay, so what do you think about merging that.

D

Assuming that they fix diapers I'm, a plus-one I did not comment on this PR because I, don't know enough about Windows I didn't I sort of it's a non-binding +1. If you will.

C

I'm plus one I think I think it's the right thing to do and I can see I promise to continue using windows and making sure that it keeps working.

B

Okay Lee: what do you think yeah for me? Is a plus one I, don't use windows, but I think it's a good thing to have it working, because a lot of my students are using windows and they would be happy if they can use Jenkins awareness.

A

Josh you just urgent in the middle of the meeting. But if you want to comment.

E

Give me a moment to try and find the document that you're walking out. Okay.

A

A

Let's chart this chart: okay,.

D

B

B

Think I need to bring my son to bed so goodbye and smelly this time. Bye thanks.

A

A

Yeah I think we are closing down mothers.

A

A

We use that okay, so do we have any other topics for today, I.

D

Don't have anything none for.

A

Me, okay, so the next meeting credit. Yes, it would be as usual, so it's something quite June 3rd. Maybe this.

C

Again, right, 2 3.

A

Don't forget about anything happening on this daily, so I think you just schedule it is this again I'm, not sure whether it will be assumed or our scene. So let's see I prefer them on my own, but there might be contributors, corporate or IRC.

A

Okay yeah. Thank you. Would you like to finish up the discussion here.

E

Sure I mean I'm I looked through it in the preview. It seems fine I.

E

Sometimes I wear Windows hat, sometimes I, don't my current Jenkins in the environment does not but I definitely deal with Windows the overall. It seems reasonable.

E

It's the idea that, right now, you have zero documentation as to what you support exactly.

A

So we look really improving this documentation. For example, we just updated web browser documentation. When are we working on 11 support? We created support policy for Java, but operating systems is still a very incognito falls.

C

Future future document will be will include, dark or will future additional pull. Requests will try to talk about darker in a similar way.

E

E

Yeah, so I lost one little comment in the github there's one line, which is a little weird. Well, either the : poem clone windows, I, don't know what it's trying to do.

E

You mean this plugin yeah like is is is following called window-sash slaves, a proper name of a thing or is it yeah? So it's.

A

A mock from this macro will basically, it is off to this website: ah okay, yeah, so yeah. This is a special keys. There's a happy maintained of this plug-in I would say that I see no real use case for that on modern windows versions and just configuring. This plugin to be working there since Windows fashions, would be a good challenge.

A

But yes, since its, they decided to reference it. Okay,.

E

E

We know where I've talked about slaves, but masters is still the canonical term for the other side yeah. So we really.

A

Named agents so now there is no slaves, there are agents right. We have a project in our roadmap to finish at the cleanup, because there is still a lot of things to do, but we just discussed renaming dr. agents before that we renamed stage built agents plugin. So these were two major issues, but still a lot of minor things here and there.

A

It's here there is just a link to the epic ok for masters to terminology so person. They don't have strong opinions. I know that Marquis has so I think we could put it on the roadmap name to something like Jenkins server or whatever, but yeah right now. There is no specific point of it. Okay,.

E

So, as a general thing, we at my employer are in the process of moving away from Jenkins. This is a slight disclaimer, but I'm always help happy to help out with terminology and things. So when you guys do get around to it, please feel free to ping me I'm sure I'll still be reachable. Ok, great.

A

E

Ya, I'm should I mark an approve in.

A

The PR earth: well, if you see it's funny, I feel free to just approve so well. Basically, all pull requests and drinks project open for comments. So all.

E

Right I'm happy with it. Thank.

A

You for taking the time to find that thanks for your feedback, okay, so my next steps there I will fix a few typos and then hopefully we'll measure them way tomorrow after the platform, sick, making.

A

Okay, now that's so this is regards to agenda and thanks everyone for your time, yep I will publish the recording soon. Thank.

D

You I'll see you online okay,.

A

D

All right, Cheers.