Jenkins Governance Meetings, 19 May 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Governance Meeting, May 19, 2021

Description

At this meeting we discussed the recent news: 2.289.1 Release Candidate, GSoC 2021, moving budget out of SPI, CDF TOC nomination, and issues with Freenode IRC. We also had a roadmap review, discussed the JEP process changes, terminology updates and Inclusive Naming Initiative membership. Then we approved officially adopting Stapler as a subproject.

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

A

Hello, hello today is may 19th and we have a regular governance meeting as we announced in the developer mailing list. We have a quite agenda for today, so we have some news. We have a roadmap updates review, though no all topics have been submitted and I'm guilty of guilty of not submitting my request and then jenkins. Jab process updates technology updates, with many duplicating ruby runtime to determine what are the next steps adopting step there. I think it have issues of opening governance, frontal junkies, revamp, plug-in end-of-life policy. As you may guess.

A

We will unlikely reach these topics but yeah, let's start and see what we did.

A

Okay, so yeah news. So the first and most important news. We've had google summer of quota announcements this year we will have five projects. uh I mean five jenkins project. There is also one project focused on spinnaker, so projects. We have cloud events plugin for jenkins differentials, binding agencies, remote informatory, with parameters most likely, maybe open telemetry. We will still discuss that security with the data for jenkins, coordinate, separator and semantic versioning, which is also subject for remain from what accurate in the child.

A

But yeah so what it means we have five quite important projects. Three are rather focused on jenkins in the cloud. One is magic version which is required for sdlc stories. I mean securing changes, delivery pipelines, we discussed at the previous contributor summit and git credentials yeah. Well, it's a must have because it is used to imagine every jenkins instance and yeah, it's quite important, especially again usable prosecuted trends, so improving credentials binding. I think it would be important in addition to the plugin. So these are topics. Today we had a kickoff meeting for community bonding.

A

You had something like and participants there for them. Your students, um then yeah at least still also publish recording, but so far so good. We will also start at retrospective asynchronously because yeah there are some topics to discuss, uh as always: there's some struggles etc, but yeah overall, it seems to be good and yeah. You start community bonding, so we encourage everyone to help students if they reach out in the community. Please welcome the students and yeah if any of them is watching.

A

Welcome to the jenkins community. Another great update is that we got multiple good applications which we were unable to accept.

A

So right now, I'm looking into alternatives and if I find something I might come up with a budget request for this summer of autumn period, so that we could run a program on our fx mentorship, because here we had several uh project ideas, which are quite important, but we should be unable to accept due to various reasons so just uh to show you what we have from the least automatic specification specification generator for sdpi again, if not this year, um custom rankings distribution service again, not this year, or at least not the ca in jsok, but it would be awesome to actually get it to the operational point.

A

uh Then plugin installation manager improve once uh click on uh bypass. They said for jenkins. All of these topics are quite important, so if we could have a program, it would be nice.

A

But right now it's just heads up, because I have nothing concrete to ask for, and I still have an action item to actually.

A

Send an update about our budget and maybe one important topic, so we will have to move out of spi because yeah we discussed use spi uh yeah. The original problem with that was that we can use this pi treasury as long as we need when we're discussing 50 in 2018, but as long as we need, and basically two years of transition, etc.

A

So three years of transition. So basically I asked it would. Rather, if we migrate, so there is no strict need to migrate tomorrow. There are some action items on the ranking governance board, but yeah. I think that we will need to go to lfx crowdfunding.

A

um I still have an action item to add other board members to lfx crowdfunding management, so so that it's not a bottleneck and after that yeah you can initiate the transition.

A

And another action item is to actually send a budget report, um but yeah right now on our accounts. We have something like 14 000 dollars from them. uh Almost eight thousand uh gsoc, I mean money we received as g-shock uh stipends to organizations.

A

So yeah it's not like. We have insane amount of money, but yeah we have never fundraised and if needed, we could try.

A

Fundraising: okay, any questions concerns or shouldn't you move on.

A

Okay, then cdf talk termination updates so last minute that I will be the nominee from the jenkins community. So basically, after that uh there was a need to uh submit a nomination statement. I shared this statement with the governance board and with the developer mailing list. I got some feedback addressed to that and that they submitted before the deadline.

A

So again now it's submitted. uh You can find a statement somewhere in the developer's mailing list, but yeah. We are waiting for the process to be announced and on the related news, cdf has just announced general member seats. I mean this year. Two seats in the talk will be left from one general members and if you know a contributor from a general remember, you can eliminate them.

A

So you can find this here technical oversight committee under a description for usability, but basically any number of general member of cdf any employer can be eliminated. So if you want consider doing.

A

This so basically what it would allow is increasing uh volume of uh jenkins users and contributors, and this is cdf talk but yeah. Let's see how it goes.

A

Okay, moving on.

A

So right hand has released that release candidate for the next lcs baseline. It's a non-standard developer, my linkedin again, everyone is welcome to test it and provide feedback. Again. We have open questions about how we promote release. It is better to facilitate feedback but yeah the release is there, so, hopefully somebody tests that and provides feedback.

A

Any comments about this release.

B

It's pretty straightforward. Is there any uh things we're concerned about in general,.

A

In this release, so there was a patch which we had to revert because yeah there was a in mozilla firefox, which they implemented that they developed. So daniel has more details about that. I believe.

C

I mean the original patch has been in weekly releases for a few months now, but only fairly recently was discovered that it caused the regression, mostly in html unit, and I think in the testing, for that it was also revealed that either the new patch or already my patch mark, you will know that also coast caused problems with form submissions being blocked. It may already have been in my patch.

C

D

Was already in in your patch and the dealt the revert has healed it and the the change from thomas uh thomas grenier de la tour also seems to have healed it. So we've got a potential fix, so we've won, we've got the revert and that's in the 2.289.1 release candidate. I've confirmed it and we've got to propose address the problem that firefox brings.

D

Also that's pushed up as a candidate needs, more reviews still or at least I think that was what you would ask for daniel was please. Could we get more more eyes to review this particular change.

C

Right yeah, that was when I thought it would go into the weekly. I don't know what the current status is right, but yesterday it was, you know, fairly late changes in the pull request. I think we'll just take care of it. It would be nice to have the new patch already in point one. It doesn't sit right with me to revert something- that's been in the weekly for quite a long time, but it is what it is.

D

Yeah for me, it was important to revert it from the weekly because of how embarrassed I am that I didn't detect, didn't detect sooner the problem and chase it down. So I was aware I had a problem. I thought it was forms conforms modernization. I was wrong. It wasn't forms modernization for once that blocked a uh a submit so yeah at least.

A

You tried to crush that, and thanks a lot for that, and thanks a lot that everyone who stabilized that so and anyway, the scope isn't that big in terms of back parts, the scope in terms of features we bring from weekly is also not terribly big, because we didn't have major breaking changes, so we have table studies, etc in the previous lcs baseline and things like ruby, runtime, etc. We haven't merged it in time, so yeah this release is relatively safe.

D

Yes, I haven't created the changelog yet, and I hope to do that over the course of the next multiple days.

E

I'm not the best one to talk about this, this impact, but I know that um we are. We have been seeing some failures on the pr 5206, which is jenkins 6902 about ssh hd bump from what does the 7 to 2.6, and it seems to break a few things, and so I just like a few seconds ago mark this regression. I think uh correct me if I'm wrong, but yeah yeah, I'm not absolutely sure I didn't have the time to dig into it, but yeah, I'm not exactly sure.

C

E

Was not mentioned more by people as a regression. It seems to be one.

C

If you look at the pr itself.

E

One person said that he had to she or he had to go back to the 2 283 before the 84 to get back to normal, so yeah. We are still assessing the impact and what is possible on on cloud b side but yeah. I'm not sure what is the last radius on this one right now. It seems to be annoying at least.

A

Oh- and that was so that's why we have at least candidates, because we still have two weeks to make adjustments.

E

Exactly I mean my point is that I'm not really fully sure yet, but I was about pointing that I didn't earlier today. uh I should have done that under the pr pinging you know uh typically um team and and reihan uh to see what they think about backboarding this one.

E

Well, no, but probably actually, there's no fixing yet. But you know thinking about uh well making fun for potential coding.

F

A

F

A

F

Yeah, that seems to be they had an evaluation in jira.

F

No no yeah yeah. I just looked at this yesterday, so uh yeah. I think it's it does seem to be a regression. I think just affecting people using rsa keys only and it looks like it's best fixed by just updating sshd again they've published the tag that has the fix that doesn't seem to be on central, so maybe it's still being held up in release candidate status somewhere, I'm not sure.

A

Yes, so I mean sshd, they have a process with voting so similarly to apache.

F

A

So it may be something like one week before the release and before the station actually released, and if something is needed, you can drop a message to the developer man at least so I mean sshd has another remaining list and you can ask to facilitate, or we can stage it uh on our local infrastructure. If it's really needed.

F

Yeah I mean it might make sense to revert this in the lts branch. I don't know, maybe.

A

A

Yeah, thanks all so anything else about the release.

A

Candy, okay, let's move on then it's 20 minutes and we still haven't finished news. uh So yeah click update. So we have been in contact with amazon to renew our sponsorship for aws. We've been quite successful about that. The jenkins board, olivier mark inc and daniel, I believe as well, maybe not but yeah. So what currently happens?

A

We have um agreement from aws to consider to continue sponsorship, but there is still open concerns about how our infrastructure is organized, because um our amazon account is still owned by cloudbees and last time we had issues with that, because yeah.

A

On aws, not the best, but so we discussed uh our options and we are good to would rather proceed with detaching jenkins entirely to the new account and initiate the transition to cdf, so that we could do basically what we did with microsoft and transaction before, and we could uh close this topic all together so right now, uh this is spanking.

B

I think the big win there is that the club, because cloud views owns it only cloud b's employees were able to access it and if we get it migrated, then they've the entire info team can manage it if they want. Yes, that's right.

G

But on the other side, I want to add something quite important. um This means that we now this once we move that account to the cdf, we'll have to pay attention to the sponsoring, because in the past, when I mean club is, was paying for that account when we needed, which was quite useful and so once we move that account to the cdf.

G

um No, I don't I mean I don't know yet how it will work, because we have a limit of 10 000 per month that you can spend on infrastructure, so we'll have to pay attention about the cost of data that account as well, and we may have to reduce our infrastructure, because we already when we moved azure account to the cdf we had to reduce from 20k per month to 10k and part of the workload was moved to the amazon accounts um last year. That account was sponsored by amazon.

G

um The sponsoring is renewed this year, but yeah these accounts run critical services of the project.

A

Yeah, so we will need to monitor that and we also need to have someone connected as a credit card. Hopefully it will be the continuous delivery foundation. I raised the ticket to the cdf. I have meetings with tracy tomorrow um and then this cdf talk on tuesday and I will see what we can do but yeah right now.

A

We just started that that we have ultimately given this right until we move and detach it completely from cloud base, it will be difficult to have community contributions there in terms of management.

B

I do know that damien has reached out to dessert ocean. I think I'm going to add the board and olivier to that thread so that, but that might help keep your costs down too. If we can spread out sponsorship for more clouds.

G

Yeah, that would be nice because then we reduce the risk uh on the one I mean once once one one cloud provider or remove the sponsoring that just reduce the risk there keep.

A

In mind to my maintenance cost, because maintaining multi-cloud setup is not exactly cheap and you also have limited bandwidth infrastructure.

B

But even if it's just like uh the spinning up the cia jenkins machines, that will reduce cost because you won't need as many of them on one cloud and that less maintenance than critical infrastructure in kubernetes clouds and stuff.

G

That's that's a difficult balance to find because monitoring the costs also take time and send ending and communicate with all the people to find ways to reduce the cost, also daytime so um but yeah. Otherwise, that's a really great news. Sorry.

A

What if we had infinite money.

G

Like what we had to what we used to have with azure for four years, yeah.

A

It's like yeah, you go somewhere and you get hapless. You enter. Show me the money submit done.

A

G

But yeah otherwise, with our mother account. That's really nice because that's quite I mean okay, that's something anyway. It was.

A

Quick heads up, but yeah we are working on that. So the next topic is from daniel about trouble with freenode irc speak.

C

About that um yeah, so um this kind of exploded today um our irc channels, are on the freenode irc network, which is sort of hosting quite a bunch of open source projects. I think linux, some linux distributions uh php all of their irc channels on this network, and it looks like there's been kind of a.

C

I mean it's described as a hostile takeover of the network um where previous, where the previous admins are being forced to hand over access to the infrastructure, and I mean I provided some links in the the notes, and it basically uh has this page that only comes up with uh links to basically the two points of view um about a dozen or so volunteer staff uh have resigned today um and it's difficult to say. What's going on, really it's just something we probably should be aware of.

C

Those staff who have resigned are starting a new irc network and, of course, if we need to migrate elsewhere, we may be able to consider other options as well. In addition, all these alternatives to irc um just you know something to keep in mind. I hope that there will be a clearer picture over the next few days and weeks.

C

um Perhaps we can look at what are other projects with perhaps a larger stuff that can deal with drama like this decide to do or not to do and do something similar.

A

Yeah, so there is the list here and here: projects that are over the white number projects amounts and saying that they would be moving so whether they really would it's.

B

Yet to be seen I mean to that note. I think it's the same as when microsoft took over github, everyone was quick to jump ship and then some people did and some people didn't. I think the only real concerns are our private issues, our private channels, which, as daniel pointed out, are not heavily used anyways.

B

A

The rest can really channel uh uh thinking. Security is located in private rc, channel yeah, and if you go over the security we also have um running, which has considerable access to our github. What was that.

B

Well, I didn't hear what you said: the what has.

A

Access to um the jenkins said c board. Yes, so if you want a disaster scenario with somebody exploiting access to this boat through three note uh access and wiping out our repository.

C

Doesn't have destructive commands.

A

I already renamed jenkins cs jinx repository once.

C

Yes, renaming a repo is not destructive or like um the only destructive action that exists is deleting a jira component and moving the issues elsewhere. Everything else is non-destructive.

B

So I think what I was trying to say is: I think this is a high priority issue, but, as daniel pointed out until a little bit of the dust settles a bit, I think it's a little premature to say: hey we're, jumping ship to this or that or what other thing um the only ones that were critical were assert.

B

I think search shouldn't. I don't know.

A

So you can theoretically just delete or move to another channel because, to be honest, outside mailing crystal, there is not that much activity in the chat now at least right.

C

Most of the activity takes place in jira. The cert general hasn't been really active recently, perhaps something for us to be mindful that uh from now on, um we probably should move uh private direct chats.

C

uh I think the queries I think uh they are called an irc uh elsewhere.

B

I also don't think you should have those, but uh okay, so uh on the high level. My vote is, is still gitter. It's a matrix just centralized on that, but I think we need to spend time to investigate and make a decision. But I would like to you know, as a recurring topic for me, is to standardize our thing because we're a little bit everywhere, we're spread out very thin all over the places yeah. Maybe it's something.

A

We really need to discuss so regardless of free node, but you have to know is another cool collection, and since we have progress with this course, uh maybe it's something we could actually try. Moving forward.

C

This course is this replacement, not the chat, replacement.

A

Yeah yeah, but uh for many our awkwardest jenkins, it's basically when I bought for the majority of users.

B

It's still worth investigating, even if we you know, I agree, though I don't think this course replaces chat. But if you have.

A

Rc, you have guitars, we have slack now in many sub projects and cdf, so maybe getting rid of one of them is possible.

G

Yeah but yeah, but there is a difference because in the case of rc um except I mean we already use github by default in most of the projects, and we only have rsc for jenkins infrastructure.

G

Drink exhausting as well, I think.

G

I mean that's only concern a small group of people, so if, if tomorrow we decide to move to a different rc channel or use something else, it's not like if we have to move the committee from the jenkins guitar channel to somewhere else. The jenkins channel on irc is still pretty big yeah different yeah, but you always have people staying on our rc.

G

Whatever you do and- and I mean I don't see it as an issue- if people want to stay in the junk internet just to discuss and ask questions as long as other people answer questions, I mean it's not officially the the main communication channel anyway.

B

But it is listed and that's my point is we should be very clear on saying this is where people will be there available to help out if people do it other places, that's fine, but we should be clear on this. Is the official complaint I.

G

Thought that we officially moved to guitar for the uh we didn't.

A

So we basically said that uh whatever works, then the yeah, the current state of the pia, will coming in so many channels, so consolidating them doesn't seem like the worst idea because, for example, this course could replace some million lists and I believe some chats, because many chats actually operate in the q and a mode and this course is quite good for kunai.

A

So yeah, let's see it's just on the topic we need to resolve now, unless somebody wants to drive with it.

C

Yeah, can we can we please move on? We are already past half uh you.

A

Agree so any closing courses on that?

A

No okay, so for roadmap updates, we have several open pull requests. um Actually, we have only two requests which are related to roadmap content. We can take a look at them quickly because again I haven't submitted my pull request. I was trying planning to do so. One update is from caro on behalf on cloud native c, so they are basically what they are called native cloud events support it's a gsoft project this year and I believe that we have a consensus, that's reasonable to have then the restrict on the client plug-in.

A

So this one is a bit more complicated because we already have two entries on the roadmap about tipton and, to be honest, I'm not exactly sure what is the difference and your color is not here today, so for tips on. We already have um what you have clicked on pipeline, build steps which was basically plug-in alpha and the currently you can move it to done and we have taken the different pipelines, execution engine which was making a jink's pipeline pluggable in terms of pipeline execution engine and making a picked on a first-class citizen.

A

Well, it's technically possible not yet to be decided but yeah. The idea was like that. So the question is whether we want to add another topic for dicton, because he basically duplicates this one, but it is another.

A

B

B

I'm not sure what your ass is like. It sounds reasonable to me.

A

So yeah, if you had that we will have basically three different items, each of them would overlap with each other, so it might be a bit complicated, yeah.

D

So I think, oh like what you said is that the techcon tecton pipelines build step is in fact the tecton client plug-in yeah there we go so isn't that really saying that the thing that she added for tekton client plug-in is already there. Maybe we need to rephrase it to be techton client plug-in um rather than.

A

D

Pipelines build steps- I I don't know if that would have helped her realize it was not. It was. It was a duplicate because it seems to be a duplicate. I don't, I don't see us adding duplicate entries into the roadmap as a benefit right now, yeah and um so.

A

There is update roadmap, so we have updated it after we discussed the elasticity meeting and right now. These features do not seem to be important enough to be put as separate roadmap entries, so maybe I'll just take action icon to remove this part to play and replace the item. We.

D

Right so because, for me, tech client plug-in is is more explicit than the teclon tecton pipeline, build step just for my benefit, but I'm okay either way just creating this roadmap item. There was no.

A

Client plugin got.

D

A

Thank you. So it was a bit uh a while ago, but yeah it's basically what we have started. Okay and the next is the docs and platform roadmap of this. Maybe you would like to speak about that.

D

Yeah, so in the february 2021 contributor summit we had ad site search was one of the items listed. I believe it's done and released for both the plug-in site and for jenkins.I for www.jenkins.io and jenkins on kubernetes.

D

We started it and we've got another person who's working on it now during our docs office hours, asia and australia time. So I think those are reasonable updates.

A

Yeah, speaking of that, will we need to create lfx mentorship for this.

D

Right now, the person is doing it without lfx mentorship, but we would like to like to consider that for some time in the future, I think our our idea was september-ish that we would consider doing a sponsored program.

D

Right and sorry, the embarrassment for she code, africa- is it's already done, but we had agreed in february as as part of the presentation that it should be on the roadmap. This is me doing it much belated.

A

Much problems with it, so any objections.

A

Okay, so all of it is straightforward, so we can just say that okay and you need to spend more time on refining the roadmap, because it's a bit dated, we still have some items from february contributor summit. We didn't put there, we have another one, I'm covering one and yeah together this mark. We also have a talk about how we did the public drinks road map at city corn. So I guess we under hook to update this roadmap before we record.

B

um Forgoing feature: is there a reason that those roadmap items are not tagged for the board? The prs.

A

For both champions you mean.

B

I don't, I don't think I've seen yeah, I'm just like. We have auto reviewer andre zayo. That says this is a board and this gets assigned to board right yeah. I guess.

A

It has broken at some point because I believe that could owners will configure uh to review this, but you're right that now it doesn't happen.

B

Yeah, so I think that I mean I don't think this needs to be discussed like the roadmap.

A

I don't necessarily need to be in this meeting yeah again, you can assign it to me, or anyone can submit one line to request.

A

um Yeah, so I think that we have agreement. I will follow up because apparently I'm I'm not locked in from firefox, uh I don't yeah. I was testing this candidate from firefox, so yeah. Let's move on so jenkins job process updates. So there is a long discussion.

A

Basically, we agreed on the most of the things I believe. So there is a pull request submitted, which addresses the agreements. We had a few iterations with liam about how things should be awarded, etc, but I think that basically it's ready to go so there are a few important changes, so we agree on terminology on these, so instead of we will use champion.

A

So basically somebody who drives the initiative without the practical changes in uh how it accurates so yeah. We also replace the review process. So we introduce jenkins communities as an entity represented by our open governance process, so yeah, it's basically what we have for discussion in the millionaires, consensus building and voting for the governance meeting if needed, or if there is strong consensus, not even spending time on the meetings and yeah. Basically, the idea that this approach replaced bba failure would be the effect delegate, which was the biggest bottleneck in all our current chips.

A

We also introduced advisor role, so the role of advisor is basically provide. Consulting. This role is optional, so it's basically how sponsor works in java jabs. So it's an experienced contributor who just helps the job to happen. If somebody less experienced, they is willing to submit a jab and go through the process, but it's optional. So basically we reduce uh variable bfl delegate. We remove bdfl as a decision-making entity and be it optional advisor, but yeah optional.

A

For example, if jc is the most popular author of jeff's and if jcs admits another job, then I believe jesse wouldn't need an advisor to deliver on that.

A

And also yeah, there is open question about what we do with bdfl in general, because yeah, basically bdfl, was only used as a karma in uh one and well personally was rather against introducing the default pro from the very beginning.

A

It was, I think, in python, community, etc. Now, I'm even more against about having this role uh but yeah right now we haven't received this response from kiki, whether he would like to step down as bdf, so that we move for.

A

Is just getting rid of one of the rules which does nothing so question two board members and two contributors who work with the job process? Does it say, look same to you at the moment it was mostly collaboration between me jesse and liam.

A

Thank you. Any feedback is welcome.

D

I need to do a more detailed review like I. I would like to to review it to think about it, because I need to submit the jeff to proposing java 11 as default.

A

So yeah another important item that since we have asynchronous process, so we can build the consensus and give the restaurant consensus so that we are fine. We agreed that we would have seven days review period after call for final feedback, so that if nobody shows up we just merged, so we that's seven days in the process for any job acceptance, even if there is strong consensus but we'll take in our current situation when jobs stay around for months and years without actually being assigned to believer delegate, I think that it will be net improvement.

A

So if you have any other ideas how to ensure that everyone had an opportunity to voice their opinion. Please comment in the discussion, but yeah right now. I just try to do it in this way.

A

Yeah tell me how to update so there is spending threat. uh There is one open questions. What are we doing with historical change involves, and uh there was splitting opinions, because some people think that we should clean them up. Some people think that we should keep them so from people on the call. Are there any strong opinions.

C

Yes, but I don't think it makes sense to go into detail here.

A

So everyone please go to the mailing list and comment.

B

Yeah eric, I recommend you on the list.

A

All right uh yeah, let's do so yeah proving the remaining terms. We still have a number of open jumps. Basically, we didn't do much progress about that over the past two weeks. It's still something on my letters but uh yeah. There is nothing to appropriate. Now. We still have terms like check this controller, but in such a way we need more feedback before we accept it so again just moving on, but this topic is why we definitely need to back in the original ideas, because none of these terms seem to be good at the moment.

A

So yeah, maybe documentation, see if we could help mark. If there is something like.

A

Oh yeah daniel says that everyone needs to review review his prs. You mean the junk score once right.

C

I mean all of my pr's, but in this context yes.

A

Oh yeah so just request the reviews from everyone on this scope. I think that it would be fair and yeah. Let's try to get it over the line, because yeah terminology club is definitely something we would like to progress until the next lcs design cut off in mid-july or late july. Actually, but yeah we could push these changes forward. It would be great we discussed, participating in how commit push event on may 29th in the managed to gain this focus on terminology, but taking the activity at the moment.

A

It seems that we won't participate in this officially. So maybe it's a question to but east and for now, but yeah right now it doesn't seem that we have organizers to run this.

A

Event, this is a commit uh push thread somewhere here, but it's the 29th. So it's a saturday and yeah that I guess everyone has other things to do on saturday.

A

A

A

Okay, so let's just try to get this over the line, uh so yeah request from included naming initiative about help with naming included, naming marketing promotion, so several of our contributors have jointly. They included me in inclusive naming initiative, including the slack meetings, because you might have seen that there is a lot of cool requests happening right now in jenkins, so just to share some insights.

A

There call this message sometime or in cleaning top and also there are other contributors. So I created terminology cleanup project just that there is input request and you can see that we have almost 70 reasonable requests, so yeah and people participate. So I think that taking our history and decisions we made in august, it would be nice if we could uh participate in and help with the name initiated at the moment. We are looking for some more reports, promotion and maybe having an interview with jenkins project representative, so I think that always reasonable.

A

I wonder whether anyone would like to be such a representative.

B

I I just don't, have the bandwidth to take on anything more right now.

G

And I think we should identify someone outside this group.

A

So I was thinking about just uh inviting alexa since he was doing leading the effort this summer and he is an author of uh still blog post, so if alex would be available, I think it would be great, but again I'm not sure this is availability. These days and alexa.

A

Yeah, I also have a lot of things on my plate same for mark, I believe, for the it's also university season, etc. uh Davilino is also busy from what I know she doesn't apologize. She can join with this meeting so yeah. Maybe we might actually must actually send a public call, but I think that it would be important for us to participate in some extent to some extent.

A

Okay and separate related topic is actually about efficient journey, the included naming initiative for the project community, so just so, there is inclusive payment uh just to provide something, but it was basically started by cncf and a few other com funding companies.

A

um So yes, ncf is the main facilitator now so priyanka sharma is uh gm and cncf, and also one of leaders of this project. Also, you know many of you know stephen augustus. He is also one of co-founders and many other active contributors ibm both of them like janky's contributors, red heart and what they have. They have related projects like conscious language, including terminology by kubernetes, et cetera, so we can easily just add jenkins, there paging his community or whatever.

A

So this looks straightforward and I think that we could do that. We also need to uh we'll meet with the landing endpoints. We have some inadvocation, but I think that um aggregating this content would be still very beneficial to rank, is coming in, regardless of us participating in the initiative officially.

A

So what do you think about that? Would it make sense for us to join this lease, etc?.

B

I, and always I'm always worried about taking on more responsibility without finishing the stuff we already started.

G

I'm same with giving if we can find someone else, we can drive that that thing. That would be really great, but we I mean we already currently I'm driving.

A

The naming I mean this is so after marquis and alex stepped down. I inherited it so by basically about the implementation. It was better than me doing all this like work.

A

It's another question about visibility, whether you want to happen. It's not a big big deal in terms of time.

B

At the moment, I would personally like to pass. I mean I think it's a good thing to do, but I am so concerned about how many projects we have half started, and I don't want to advertise the fact that it's like get people saying, hey, look jenkins is starting this progress. I'd rather say, hey, we've done this progress and then added to the list.

D

Well, but but isn't this one see I'm the other direction with this one, because this is a project we've already started and all it's doing is providing another link to our our terminology update. So I I don't this particular one. I don't think adds any significant burden to us that we don't already have.

G

So my my I'm just wondering if we could maybe reach out to one of the people who helped with the room with the naming renaming. So maybe one of those people can step up and help on that initiative.

A

Yeah, it's a valid approach so and yeah. Currently we work with several contributors and so through the.

A

Created some tools for discovering um terminology on screenshots, then we have some stories to share about governance, how we approach the decision making in a big project. So just by sharing experience, we already contribute to this initiative and I don't think that there will be a big cover head and but yeah. I understand given spawn as well and if you could find someone who would take leadership, maybe.

A

Let's see so I guess for that we again need public call and yeah the same for cdf. So for cdf for the results list of members, I will be bringing up uh our cdf joining because.

A

Of and terminologically not on that project, so for spf it makes sense to join this list and for cdf it's actually free because yeah, yes,.

A

Non-Profit, it's free, so maybe cdf will join and maybe we will also get some help from staff marketing team in terms of promotion and benefits. Related communications.

A

I don't want to have jenkins as a short case of inclusive naming cleanup, because, firstly, we are quite better than whoever may clean up my humble opinion, but at the same time we are working on that. So I think that being represented there would make sense.

A

Okay, anything else about that.

A

Here we are closing time should we just vote on an adopting step that has a sub project, because it seemed to quite straightforward.

B

I thought I was already done so I'm on board with adopting yeah.

D

Plus one from me, plus one to vote on it and plus one for me that to vote to approve.

G

Does that mean that you would move the stop luggage repository to the jenkins cio organization or we keep the stapler under the stapler organization? It's to.

A

Be decided, but the janky's governance would apply there officially and yeah. Currently, it's daniel and jc, as stephen had means so jca is already on board. I believe that daniel hasn't voted.

C

So I mean it makes sense too. I mean it makes sense to integrate stapler into the jenkins project. uh If kk is okay. With that, I don't have a strong opinion on keeping the orcs separate. uh We could do it fairly cleanly by by just keeping the orcs separate, and you know adding a few more contributors as admins and then we're done um plus. But if we keep the org, we need to throw out a bunch of folks who haven't contributed in the last decade um because uh it seems weird to have these.

C

You know old accounts around. That's.

A

So what we will be definitely doing is moving idea, stepler plugin, because I believe we have a consensus about uh renaming this to jenkins plugin, because nobody else uses uh step that enough to really need a integration with intelligent idea, and for that I believe you have a consensus on the mailing list unless somebody is opposed.

A

The same happened to using netbeans plugin advanced plugin is already within the gengxie github organization, so basically they will be under the junkies here, roof or whatever happens, but here for step there. I think that the moving repositories rather implementation detail.

A

uh So but yes definitely anyway, it goes to a kind of arctic part of our sub projects. I mean, as discussed in the military. I don't think that we should recommend uh for using outside jenkins um so well. Basically, it will be just our heritage and, as jesus said, there is no practical way we would ever remove scepter from jenkins so yeah. I guess it's a small coding exercise for anyone. If you want to try but yeah, so I think it would be natural if we just take it over. I feature.

E

A

So just uh then you'll listen. You think that kikis are probably a must right, because kiki belongs to these contributors, who haven't contributed for a while to step up.

C

I mean it's kind of his project in a sense. If, if I were, if I were the men of a repo in koski's namespace, I would move it out there without his approval either, and this is not that dissimilar to me. Okay, I.

A

Agree so I'll try to get exclusive approval from kiki.

A

So yeah we're losing people. So do you want to press it with other topics or do you want to shut down for now.

G

I think we can shut down for now.

A

Yes, so what do we have duplicate improvement runtime, just let's try to get the progress in the mailing list because it feels like jeff is almost done. uh Blog post is almost done, so we should rather push it forward.

A

Github is just here we can keep discussing it from the coming, but I don't think that there are blockers for experimenting and we are friends of jenkins. There is no harder at all for that and again, we can discuss in the magnetism again. I don't know why policies question deserve this event meeting.

A

So thanks everyone and yeah thanks again for your time. Maybe we didn't need to switch to weekly meetings or whatever, but yeah. Hopefully you won't be have so many topics say in the next two weeks.

A

Yeah last but not least, don't forget about contributor summit and if.

E

A

Ideas about agenda topic strikes. Please comment there.

G

A