Jenkins Governance Meetings, 2 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Governance Meeting, Jun 2, 2021

Description

Jenkins governance meeting June 2, 2021.

Topic included:
* Jenkins 2.289.1 release SHIPPED!
* Libera Chat Adoption
* Discourse PoC: community.jenkins.io
* Oleg Nenashev will join the CDF TOC as Jenkins project representative
* Jenkins Contributor Summit
* Jenkins Community Awards 2021 at cdCon
* DevOps World CFP is closed
* Roadmap Updates Review
* Deprecating ruby-runtime - next steps
* JEP process updates
* GitHub Issues for open governance projects/backlog
* Jenkins funding updates
* Approved: Open Sourcing the Friend of Jenkins plugin?
* Approved: Elastic Sponsorship for OpenTelemetry usage for community
* Reduced availability of Mark Waite & Mark’s roles in the community

A

Hello, hello uh today is uh june uh second, and we have a regular governance meeting, so we have a quite long agenda and, yes, we discussed that after the previous meeting, we will really glance through the news, no big discussions unless somebody wants to and our main focus will be actually to focus on topics where we can make a difference and where we needed discussion.

A

So the first item was jenkins: 2.2 89 one release is everything fine with it.

B

As far as I can tell yes, I haven't completed the checklist yet, but yes, it's delivered change. Log is visible. I think everything looks good, still need to check the logs just to be absolutely sure.

A

And this release is uh relatively stable, been compared to others, so there are not that many breaking changes, so hopefully it will be fine.

A

Okay, uh moving on uh liberal chat adoption, so we haven't announced it yet, but the fact that all our c channels I either terminated or moved to liberate chad. So I think that we will need to announce it soon but whomever uses hc. Please uh take a look at the mailing list because we have moved our community there.

C

We would do redirection, except apparently, redirections often will get the channel banned, so we're just being discreet to say hey by the way we moved.

A

Well, I can assume that our channels on freenode will be taken over anyway, so I don't worry too much. I am happy to just abandon them.

A

He's a willingness by the way yep.

D

Yeah, hey sorry about it. I completely lost the track of time. It's so bright. It doesn't feel like sorry.

A

Okay, so yeah liberal chat uh done thanks to everyone uh for pushing that, because it's quite important to move quickly. The next important thing is uh discourse proof of concept. Again, just heads up it it's happening and they it's already quite populated.

A

So there are categories there is structure set up. There is a site feedback, so if you want to try it out, go there provide feedback here and we can discuss it. So it's a proof of concept state. uh There is a mailing list where you can discuss more, but yeah. This course.

C

A

Available for evaluation.

C

I'll work with uh olivier to make sure we post now that it's get a github, so people can join.

A

And so it's yet to be decided what we will use in the end, but for now it's a github and well, it works pretty well. So then, next announcement is from mark that uh he will have reduced availability for the period up to eight weeks, so yeah. We will discuss later how we split the roles but yeah. If you haven't noticed that yes, there is a message from mark um same announcement, I will be joining the continuous delivery foundation um tlc.

A

So, as we discussed before, there is public statement on linkedin, which inherits the community statement we reviewed before. There are also some details about how I see this cdf talk, because I really see it as a representation of the jenkins community, not uh additional big boss or whatever quite opposite. So there are some proposals. uh If there is a meeting, we I'm happy to document this job, but right now it's waiting for feedback from anyone.

A

It will be effective july. 1St then jenkins, contributor summit. Everything is scheduled uh again called for any kind of participation because we need hosts. We need proposals and we need contributors to this event. I will be sending another message tomorrow uh to get more participation, but yeah. We will have summit one topic, which I announced separately, that we won't have a discussion about jenkins 3 unless another contributor takes it over, because I cannot hold to this discussion at the moment.

A

So yeah this is tbd and unless somebody steps up, I won't be able to host it.

A

um Yeah, that's quite unfortunate, but that's what we have junk is coming in towards again quick update, what's uh happening. So if you are in this list and all active contributors should be in this list, they can use level foundation did some magic. So you should have received notifications to your inbox and they using another uh following system, but it's also transferable world yeah poor right now, whatever yeah anyway just vote.

A

uh There are multiple jenkins contributors, so they also call for cdf contributors, so they will be appalled, friend, user companies and later so just vote and yeah divorce. World account for papers is closed. We've got quite a number of proposals, so it will take some time to process that. Please don't hold your breath to receive a final feedback on june 7 says it was announced, so the real date is to be determined. I would say it's rather end of june.

A

Okay, then, uh so we did all news in five minutes. Is it good enough?

A

Okay, great job.

E

A

Okay improvement. Next, the target do the anti-governance meeting is five minutes: okay, so yeah jinx roadmap updates. I just edited the regular item and again I failed to submit uh my roadmap items so yeah. It's shame on me.

A

One item we actually have to approve um at the moment is uh updating uh jenkins template engine uh to released because it has been released to the zero.

A

So are there any concerns about that, or should we just ship it so for that? Theoretically, we should be working synchronously.

A

So I assume that once we get three board member approvals, we can merge because the majority is reached but yeah we can do it like that as well.

C

I'll be honest, I don't know anything about gde, so I didn't review this.

A

So you have an opportunity to join a talk from steven to run at some point: okay uh yeah: where was I okay? Next time duplicating kruppy run time? So the main question is: what do we need to do is to push this topic forward because it seems to be a bit stalled. So, given I did a lot of work to prepare the announcement.

A

There was a lot of work by the team to update the jet, so I would really uh want to push this topic forward, but I'm not sure what is exactly our auction item there I'll keep pushing.

C

A

Is updated but yeah so fuji, but yeah there is a pull request from jc about uh removing j2p from stepler. I think uh in the current state we are clear to go because we are adopting stepler. It's approved and yeah jruby doesn't make much sense to maintain jenkins.

C

So this is an additional change to the earlier.

C

So, okay jep7, is the one that removes the ruby, runtime and jesse wanted to add stapler to that removal. Yeah.

A

Because, basically, it's just another cleanup of technical depth thinks templar, models is not fun and this coverage isn't from there either. But the.

C

Drop 7 isn't fully emerged. There are the updates to it.

A

um Updates so we have two updates. uh One is update from me where, basically, I uh try to follow up on your blog post and put uh data from your blog post there, yeah and here well, I'm waiting for feedback from daniel, and I guess from feedback from ukraine as well.

C

I was good with the changes I thought it. I had trouble following the jabs, but I thought it was only waiting on dang on now.

E

Whoops um I'll try to get this reviewed soon. uh Last few weeks have been weird uh if you're in europe- and you know what's going on in may uh I mean there are more days off than actual work days.

A

Yeah something like that. You should try russia, because uh the first 10 days of maybe your vacations or holidays or something yeah. It's a separate story. If you want to discuss politics, okay, uh yeah so anyway, it would be nice if we get it over the line, because again, uh lcs merch window is happening soon, and I think that we should uh announce this change in the upgrade guide.

A

Even if it's not clear, directly related to the drinker score, uh because yeah the impact can be quite massive uh or maybe not so we'd rather measure the earlier yeah once this jeff is updated. I'll.

C

Update the blog.

A

Post and we'll change the dates and everything yeah, I think well, this job mostly inherits your blog post, so yeah there should be no much difference.

A

So basically, approval from daniel is needed.

A

Okay, so another thing is job process update. Unfortunately, we don't have liam on the call but yeah a quick update, so yeah there is a pull request which is staged, which is almost ready to go. From my point of view. We basically rework how the jab work job process works, to simplify it. So we get rid of bdfl delegate role. We get rid of bdfl involvement uh in the job one process to answer graeme's question: we will keep bdfl or equivalent role. I had a meeting with kiki to just discuss his vision, for that.

A

I will follow up with the board separately, just to explain this vision and why you would keep a role but yeah from japan's standpoint. There will be no pediatric involvement and there will be no blockage for that.

D

C

You see my question what I don't know. I thought you said mike used to answer my question. I don't remember having a question or maybe it was.

A

Liam, okay, sorry yeah, it was in the millionth list, uh but yeah. We also get rid of uh uh second review role. So what it our current structure will be that uh they will be a champion or sponsoring sorry. Basically, a number of contributors who lead the effort. Then there is optional advisor basically for lesson, experience, contributors etc uh a person who helps uh to get a job through the process to provide stakeholder feedback if needed, etc, and we also have a reviewer role. But for the majority of use cases, review role.

A

Is junkies communities, slash open governance process discussion in the mailing list, consensus voting at the governance meeting if needed, and in some cases we can delegate it so if needed, but yeah, we basically align what happens with jabs with what happens with other decisions, and I think it's the best solution for now until we have technical steering committee or whatever entity to handle that separately,.

A

Does it work for everyone.

A

Elena daniel.

E

I have not had an opportunity to review this in detail. Sorry, okay,.

A

So if you could uh take a look later, it would be great. I think that we more or less reached consensus in the mailing list, so we need to agree with him how weird about particular part of this job, because I think it's good enough liam thinks that we need to reward it. So I will try to get it over the line just too many emergencies.

A

But my target is that by the next governance meeting we can merge it and make the process efficient effective, because what is our current state is that we have so many stalled jabs and once we know jab one, we can effectively press it with them so that we can either say that yeah they effectively emerged or we can defer them, but there will be no dependence on kiki's feedback to get it over. The line and yep kiki is busy with other topics, so we can uh our disturbing him for every job.

A

Okay sounds good thanks, oh like yeah, so then next topic github issues for open governance. uh So basically the idea the the proposal was for me that we have a lot of topics in our backlog.

A

uh Wishlist, etc, and currently, if you're a contributor who doesn't regularly participate in the governance meetings, it's difficult for you to understand uh what is cooking and where you can contribute so roadmap, even if it was updated, it's not enough for finding frame tasks and I thought that it would be nice to have a backlog somewhere uh so that everyone can could pick up the task. For example, let's say yeah jab one do some updates, for example, introduce change history in japs, or something like that.

A

So just these topics we could keep in the backlog we can discuss in github issues or elsewhere, and somebody could take them over. So it's not necessarily just a small group of people handling these governance matters.

A

Does it make sense to you yeah? I thought this was already approved.

A

I don't think we have a consensus to be honest uh because yeah daniel said he is rather against. I believe yeah. This nicely illustrates that the github repo model can be weird.

A

Daniel are you against that, or is it just a side note.

E

I do not think that the choice of tool is the correct one.

E

But that's about it. Increasing visibility is probably useful.

A

Yeah, one of the options is actually to try this course for this matter, because why not.

A

So I would rather be consistent about using uh jira issues, because jira issues do not really work like we discovered with events and with other topics, so yeah.

C

I don't think I don't think jira has visibility, we need for this kind of thing I mean I agree with daniel. Dira is better suited for this kind of thing. I just don't think anyone else will ever see the tickets like. Even when you look for like um good, first-time issues and hacktoberfest and all the contributors, it's just not visible enough, because people don't go there look for tickets, they just dump something in there and we have a billion and a half tickets and nobody looks there.

C

A

So, potentially we can move governance, ideas etc to this course and just close the topics when they finished uh the problem with that is that it might collide with a developer may increase, and at least for now my assumption that governance, discussions etc on general happened in the developer mailing list.

A

So that's why I was thinking that github issues might be better, but.

C

What do you think my my vote is go with github issues? I think it should go into um discourse, but I also would love to see like I'm hoping down the road that people like it enough. That discourse replaces all the mailing lists, because I want to see visibility. I don't want to have like 18 maleness that I have to be subscribed to. I want to be picking and choosing topics that I care about.

C

So yeah, I don't think we're at the point where we should say this should be in discourse, but I'm hoping down the road it will be yeah. Maybe.

E

So taking a step back, one of the potential problems I see is um this is yet another place where people post comments and discuss things and historically we had the dev list. For that isn't isn't what we need more like a road map for governance.

E

Discussions are happening.

A

So yeah, I agree with you daniel. We shouldn't use github issues for as a venue for discussions, it should be a backlog and we should create an issue template or whatever, which explicitly says that the discussion has to happen there uh in the mailing list, because I'm not ready to change this process as well. At the moment, we have a governance roadmap here, apart from it being dated it's something we need to improve.

A

It's not really suitable for fine grained items and github pictures could be used for fine grained items.

E

Okay, so um how about this github issues? But nobody gets to comment. All items are locked, then it's basically the road map kind of thing in the github presentation, and there are references where, where the discussion should be happening.

C

So on that note, uh one of the reasons why oleg was proposing this was so that he could get help on some of the tasks he's been doing if they're locked nobody can say. I want to take this item well,.

A

You can figure it out uh because if there is a link to discussion somewhere, okay.

C

Yeah yeah, okay, so everything we put in there should have a male in this topic to start with or something.

A

Yeah in theory, or below uh topics which have associated discussion; okay, because.

C

Yeah that negates my concern that or not negates, but uh columns must the conservative I'm happy with them being locked as long as there is a link to where you should be discussing them, and I don't care how where we discuss it, but so.

A

So yeah github issues for backlog, not for discussion and yeah default behavior.

A

Locked issues with the links.

E

Yeah or maybe we can just say discussions elsewhere, and if people, uh if comments trickle in then, we can always start locking things to prevent that off-topic discussion. So it it. It shouldn't feel unwelcoming, which is kind of a drawback of locking things.

A

uh Okay, no discussion uh address somehow by issue templates, maybe even bots, if we need uh later but because yeah there are bots for something like that.

A

A

A

uh Find a lot to lock issues when needed.

A

Then okay, does it make sense.

C

I'm happy with it.

A

Danielle mark evelina.

D

No, it makes sense to me, I I think, having it as issues. You know those locked backlog items is going to make it easier for everyone to browse through them and then yeah. The discussion have happened where it needs to that that that sounds good.

A

Yeah plus one for me, okay, then all plus ones, um yeah. One question about uh the license for this repository.

A

uh Should we just take creative comments, or should we invent something else, because I wanted to use the same repository, for example, to dump a backup of uh governance, meeting conversations we had in a free node, uh and things like that, so I would foresee that we use this repository for other topics uh where we're basically too lazy to put it on the jenkins io, but we can still use it first for it as a repository for some cases, and we, if we ever decided to adopt hakumdi, for example, for meeting nodes, then we can also use this repository to start the meeting nodes.

A

C

Like to finish one proposal before we start another proposal, because I think we have an issue with that right now, so I I do agree, though that's a good idea, but I I don't want to. I want to get the governance backlog running before we start adding new things to it. I agreed and.

A

Yeah then question who would like to prototype this repository.

C

I guess I can.

A

Do you want to do that.

C

No, but if someone has to do it, I am probably free right now well you're doing.

A

This course, which is also important but yeah. If you want to take that, thank you, I can take it yeah. I don't think it's a really big task.

A

So gavin is going to be jenkins communications channels officer soon.

C

It's not uncommon for that to happen for me, so yeah.

A

Okay, well, thank you for handling that okay. So then moving on is funding. I have some news so yeah we have this uh funding discussion, which was quite old. I had to recover that due to a few reasons, so, first of the reasons spi would like us to move our budgets and treasury as elsewhere, because when we agreed that we would spend money eventually and run out of them and the topic is closed.

A

Nobody expected the transition from the cdf to take two years, so they would be interested if we move out and our only destination at the moment is lfx crowdfunding.

A

We kind of agreed on that and I do not think it's a problem. The problem was with expensive fibergland because um originally, when I reached out to the lfx support team, they said that there is no way to actually support multiple uh people who would have be approving requests.

A

So I came up with a proposal like let's do some backstop like treasury role, who would approve that and we maximize community efforts. So it's not a single person bottleneck. So there is a long discussion about how we do that. I think we reached a consensus with only at least maybe this given as well but yeah the main thing. There is actually the linux foundation funder workaround, so they can at all five board members uh as reviewers.

A

So my question to you: do we want to implement this treasurer role, documentation as a separate, or do we just update what was written there and that's it without formal treasurer.

C

I don't have a strong opinion about this. I I kind of don't want to have discussion like the mailing. The mailing list discussion was happening and then, if we're going to jump to the meeting, I it's hard to go back. Like I yeah, I don't know uh whatever I am supporting. Whatever is the least effort for us.

A

C

A

By the way, uh gary and evelina did you receive notifications from expensify? I did yes, so you have access to the system.

A

I think that it's uh enough to press it.

A

Okay, so what it means that somebody has to initiate a money transfer. I can just do that because I did the previous one. So I think that we just move for all the remaining money to crowdfunding and then we basically end up with just one location so that everything becomes more simple.

A

Okay, so treasure roll I will put on hold for now. I still need to update the jab, but I think that, right now we don't have to introduce the official role.

C

Yeah, I don't think we have enough expenses or any expenses that we really have to worry about it. Yet.

A

Well, I wish we had some expenses because we get the donations, so we should spend them because it's the best way to appreciate uh the donations we receive yeah. I've had about some projects having hundreds of thousands of dollars on use donations, so I don't think it's really appropriate without mentioning the names uh and yeah. In our case, we should really be close to net zero yeah, but that's a fitter problem yep I agree so I will initiate the transfer so that we basically close spi as soon as possible.

A

A treasure roll put on hold one question and again we'll say that, let's finish uh what we started, uh so I think tbd.

C

Yeah, so we have sponsors.

A

C

Specific case, I don't think we should have more ways to accept sponsorship that we're not spending. I think we should start figuring out how to spend it before we start asking for.

A

Well, I have something like uh I have to pick here confirming budget for the effects mentioned the communication project. We also have ideas about tecton, client and few other items like rest, api, yeah, but yeah. I just didn't- have time to come up with proposal for review, yeah, okay, so tbd. For now we have some action items. That's good uh yeah, one uh moving home, yeah, okay friend of jenkins. So where do we stand now? uh We agreed that we killed the program. So basically it's officially dead.

A

If you go to donate, I guess to donate here, so you can see that friend of jenkins yeah thanks uh to gavin for adjusting courting so right now, yep, we don't provide anything and we intend to somehow provide recognition without any explicit commitment.

A

How we do that it's yet to be figured out, but a friend of friend of jenkins is officially dead as a program, but I would suggest to go a few day and to open source the plugin so that everyone can install that if they wish my estimation that it would take one hour or so the benefit that homer is interested. They can install this plugin and it will have a link to put jinxio participate, so in theory it can lead to some traffic.

A

In theory, it can help us to facilitate contributions and yeah in practice. Why not.

C

Yeah in practice, why not, I don't think the whole point of it was you install it on a server and then there's a link for you to donate, but you've already donated to get the plugin so yeah? It was a weird.

A

Well, it was just wasn't open source because yes, shipping ancient plugin with whatever crop inside, and I can assure you it's ancient uh because I have access to the code.

A

We all do yeah and the another benefit for us that if we update this plugin and release a major version that we can, we will be able to get rid of the previous versions on the user instances. If any and they will.

C

Eventually update, it makes way more sense for it to be used on public installs, not uh private, hidden installs, so yeah, I'm in favor of open sourcing it I'm not sure we necessarily need to release it. But, as you said, you know we might as well release it and anyone could install it. Then yeah.

A

It's no problem with releasing yeah.

A

Why not so is there anyone fun that, finally, that we just released it and close the topic.

E

A

Okay, does anyone want to play with that, or I can do that?

A

I have a to-do item to write some code, sometimes so yeah. Maybe it will be a good thing.

C

uh The only thing to me is is, I think it should go through the hosting process, not so that it has to get approved just so that everything gets done properly, because we've had some issues where reposts have been created randomly in the past and then other pieces aren't in place. So.

A

Yeah, I agree. I agree. I will still need to rework it first before even submitting for hosting, because when daniel sees a plugin using 1.396, I guess hosting won't be approved.

E

Luckily, I'm not involved, but uh it wouldn't be approved, even if I don't reject it. Okay,.

A

Yeah anyway, so we have a few topics left, so my suggestion would be to drag mark's topic to the bottom, so we finished these discussions and then we spent all the remaining time to check. What is the transition plan is finding with everyone.

A

Okay, so elastic sponsorship, open telemetry, so basically syria reached out to the community and offered that we could. Oh, it was actually diamond. So there is elastic apm um and there is interest to improve our own monitoring within the system, including jenkins instances and other components.

A

So the idea that we would use open, telemetry and open telemetry is being widely adopted at the moment and, for example, in gsoc for remote monitoring, we will be also integrating with open telemetry.

A

uh So that is a good engine and the open telemetry is just supplier of the data. So we need something to actually process this data to visualize etc, and the proposal from damien syria, the company, is to use apm.

A

uh So there are other opportunities like parameters. Tunnels, if you want or a pm, is more size, ish solution, so that we don't have to maintain anything on our own and yeah. The question is whether we want to at least explore this option as a prototype.

C

I don't think it's a board issue, a governance issue but sure.

A

Well, so technically it's sponsorship well accepting uh uh this donation, so you know at some point it may.

B

A

Cancelled et cetera, so I would rather prefer it to be a open governance process, definitely not governance board because well, whomever joins this meeting kind of vote.

C

Yeah, I'm I I think it's a good thing and you know any anytime any company, uh sponsors or donates to us. We can highlight you and especially if this data is public, because I would love to see that we can say hey look. This is open telemetry. This is the data we're getting. This is how you can see it. It's a good use case, I'm fine with that. I am, as the mailing has pointed out, I'm not fine with it being on infra or anything else that has sensitive data on it.

C

But after that it sounds cool and since ci.

A

Is a showcase all our instances except c and casio contain potentially private data.

A

Which contains, let's say more or less public data yeah, um because it's not really trusted in our current design yeah and we have uh intro ci trusted, ci, search, ci and release so for more jenkins instances and all of them contain sensitive information, yeah, so yeah. Basically, what you say that uh allowing it.

C

Well, the original proposal said infra and I'm I was like no, but someone else brought that up. First, so yeah.

A

Yeah, I'm also minus one for intro.

A

So who has a different opinion.

E

So the one thing that I would like to note here and I missed the conversation that happened on the dev list, is I mean we are allowing the infra team or enabling the infra team to choose to do this right, we're not deciding on their behalf that this is what will happen.

C

Yes, it was proposed by infra team.

E

A

Okay, in that case yeah sure so, basically, infra officer can make these decisions taking our current decision making process well, uh yeah, so infra officer he's eligible to represent the jinx community on all the sponsorship. Conversations and yeah even freddie makes the decisions for us. It's just additional level of approval, I believe which doesn't hurt to discuss in public, because we can get contributors to open, telemetry and other components.

A

So I totally support this approach.

A

Okay, moving on then yep uh like plug-in end-of-life policy, so we don't have basel on the call. Are we ready to proceed with this topic.

E

I think it's a little ongoing, um just the scope of what we should be doing is very unclear. I don't think I don't know what this uh meeting would.

E

What we could accomplish in this meeting other than you know, point out. This discussion is happening uh and uh everyone interested should look into it and uh participate, but otherwise um there's there's no consensus.

C

I do agree with bazel's notes. At the end, though, there is a lot of proposals for a lot of process, and that makes me concerned that nothing will get done.

A

Well, it'll, be we get things done here and there so yeah right now. There is rather explosion of different uh initiatives here and there we probably should be more conscious, but at the same time this particular thing has been a problem for us for a long time, because every time when I have to initiate two week timeout for a plugin which has been touched last time five years ago. I am not very happy about that because over two weeks we lose some of uh potential maintainers who just give up or forget yeah.

A

So I would like to get this topic over the line, but yeah. I understand the concern that we have too many uh topics say in parallel.

C

Oh no, uh I didn't. I didn't mean that uh in basil's last post in the mailing list he was talking about, there are too many proposals for too much processes like automated tasks that are going to you know trigger our end of life, stuff and all the other stuff. I agree with him on that. It's getting a little bit out of control that we're not actually figuring out uh minimum requirements before we're.

A

Dealing with all this, so there are two parts: firstly, is the policy.

A

Second, is automation for this policy yeah, because what we really need is to have this policy, even if we don't apply it always, but we apply it when needed. This is perfectly fine for us, yeah and.

C

I think at a minimum we can do it just for people wanting to take over. So like that. You said the if a plug-in hasn't been released in five years and someone's like hey, I like to take over that to me, is one of the few cases that we should have a much simpler policy for.

A

Exactly and once we have this policy whomever wants to do some according exercise and implement automation for this policy. They are welcome to proceed if they want, but we will have policy in place and unblock contributors.

C

Yeah, so I agree with daniel. I think this should kind of stay in the mail list for now and then we can, if governance needs to step in as a final person, that's fine, but I don't think right now. Government needs to dictate this policy.

A

Yeah but yeah there is a consensus that we want, a policy which should help.

C

Maintain us maintainers users, everyone is going to want a better, more clear policy about this.

E

Yeah, I agree, I I think there's there is a good solution uh to the problem, uh but I believe we have not yet found it so yeah.

C

Or we just go yolo and delete everything. That's more than five years old.

C

A

Year, once okay, so this is something we will definitely have to vote on when somebody writes a jab, but for now we need to unblock puzzles so that there is clear uh consensus about what to be put in this jab and once we have that yeah, I think we will be able to vote because yeah if one year many of my plugins will go to adoption- and probably I deserve that, but yeah it's something to discuss separately.

A

Okay, yep, uh then yeah. We have one topic, left uh mark's roles in the community so mark. Would you like to take over this discussion and maybe screen share?

A

What's your preference, I can.

B

To make meeting notes, if, if you well I'm happy to share- or you can just share the uh the note that I sent to the uh okay.

A

I can uh screenshare then yeah, if you prefer, but yeah, then I'm not making much meeting notes. You know.

B

Oh all right! Well so good point, maybe it maybe it is better that I screenshare.

A

Whatever I think we can start.

C

I don't think there's a lot of notes for this. One anyways.

B

Okay yeah, so the the most we've got well. The issue is: I'm going out currently scheduled june, 9th to donate a kidney and I'll be out for two weeks from my employment and as much as eight weeks from the jenkins project. uh We would like somebody else to help, and um these are opportunities for people to help. There are two different presentations here. One was in this developer list. Another was in the docs list and I think the the two places that need more help.

B

We've got a volunteer for on this page. The jenkins docker images.

B

We've got a volunteer for scribe for ux meeting, we've got a volunteer, we don't have a volunteer for platform sig yet, and I've got a volunteer for mentor google summer of code project, so it feels like that one is doing. Okay, um the dev tasks are not causing me yeah platform. Sig doesn't have and there's a meeting this friday so and I won't be able to run it.

A

Yeah, so I could probably take over platform seek well again uh for a while, because yeah I was the one who started that for me. The problem that I cannot do it on fridays.

B

So right- and that makes sense so that that's that one- I may just send a cancellation message for this week's meeting and we'll will allow that it will happen later with, as volunteers are available,.

A

So yeah, for me, the interest is java 17, because I wanted to tinker with it anyway, and maybe team jacqueline would be also interested to proceed right.

A

Yeah, if not so in any case, it will be a reduction of the meeting frequency, maybe once per two weeks or one month and yeah. So the main objective would be to just get docker images initiatives.

A

I also have occasional blog post for arm to publish because well they created it due to other reasons, but actually there is some good content to be reused, so yeah. I think that arm support is something we need to put on the roadmap for platform seek, but yeah and dockers, I'm also formerly a maintainer, so I'm pretty bad maintainer for docker images but yeah. I can also keep flights on these topics and I will look for someone to continue so, but your mark don't have to worry about that.

B

The the other hot topic here is actually on docs and it's in the it's in the docs list. Not here. The topic is the changelog for jenkins releases, and what I had proposed was that we would have um a new contributor help with the weekly change log and we got our first weekly change log submitted by that new contributor this last week. So was really delighted and he'll. Do it again next next week as well, so dhiraj singh jorda has been willing to do it and he's doing the weekly with my tutoring.

B

The bigger challenge is the lts change log, but my thought there was. We just accept that the release lead. We asked them to write the change log for 2.289.2 and 2.289.3, and I intend to be back in time to do than the september major the dot one yeah.

A

So for change locks in general, I think it's a matter of jenkins core maintenance team. It's not a matter of the documentation, seek, though yeah admit there is overlap, but the team jacob is still here. Release lead will so for that one! It's rihanna and this process is over thanks a lot to rihanna. We will find someone for the two and we will be able to coordinate change logs so whether it will be the same release, lead or another contributor, but we can figure it out.

A

So I don't think that it's something massive on your shoulders at the moment mark because.

C

A

C

I think it should be the responsibility of the release lead to have it done, but not necessarily do the work. So whoever is the release. Lead should be the one that's pushing. Whoever gets the release notes done.

B

Yeah no debate there. What the challenge is that the dot one ra change log requires a lot more judgment than the dot, 2.3, etc, and a lot more judgment than the weekly change log.

A

But that one is done next, that one will be september and all of us hope for that by september you will be back mark right, so yeah. I think it's not a problem.

B

At the moment, yeah the the way you've described the release, lead expectation is already how it's working right already reached out to me and said mark. Will you do 2.289.1's change log, and I did so absolutely that that is a very workable condition.

A

uh So yeah for the rest, uh do we have any other areas which you haven't handed over yet so, for example, git plugin.

B

So I've got we've got three maintainers who are handling the get plug-in bobby sandal, olivier lami and ramon leon. So I'm comfortable with get plug-in and get client plug-in. Welcome.

A

uh Yeah so yeah, another topic I'm would be concerned about is jenkins, io copy, editing, bandwidth and those social media went right because so for copied. I think right now. It's mostly team, jack comp and me and mark so without marker you'll have less time for social media. It's basically just me at the moment and again it would be nice to have someone else. So maybe I will cooperate with elisa to get more involvement in this effort, but again it's a areas where you would be happy to get more contributions anyway.

A

Right so so yeah for that, I am just raising a flag that yeah likely. We will feel the reduced bandwidth if you don't uh get more contributors, but yeah I'll spend some time. Looking for contributors and yeah, you may have noticed that currently we have memcans uh yeah. I know that it's a terrible use case, but yeah now it's memcan says code.

A

So right now, if you want to post mems, you can just submit pull request and we can adopt it uh to jenkins twitter account if you want, uh so that we move all the contribution process to github so that they will be know. This wacky reviews in guitar chat somewhere and instead of that, whoever wants to see a tweet, they you've got to submit a pull request and we can automate it for blocks, etc. So that again, eventually automate not right, not immediately, so that at least that dummy pull requests which can be copy edited.

C

Yeah- and I added a I mean on that note- I added a show off a category to discourse, so hopefully we can have people in a less formal way, show off things they're talking about which will lead to social media blog posts. So I mean it's a little longer term goal, but it should help with content.

A

Yeah, I agree and, moreover, with content contributions, because right now, for example, for linkedin for its infinite queue we can create, because for linkedin general recommendations to have one first post per day, we have much higher traffic and twitter. So it's usually it's something to post every day.

A

If somebody is available to post it, which is a bigger challenge at the moment for twitter for twitter, we should just encourage the community, because we have so many things happening here and there and if somebody was just posting a tweet so that we could repost that done, we have a lot of content already so yeah.

A

There are not so many contributors doing that, but yeah when you release a plugin when you submit a couple requests or when somebody submits couple requests to your uh plugin, and you can just appreciate this contribution.

A

All of this traffic actually helps yeah and we will be happy to basically repost it, but somebody needs to be a creator. First.

C

Yep so hopefully that'll improve. I don't think it necessarily has to improve now, but yeah.

A

Okay, so any other topics uh any other responsibilities of mark we missed. So I definitely platform leveler plugin, but yeah we will survive somehow. I guess yeah, muted,.

B

Yes, I think, I think, we'll all the other plug-ins I maintain everyone will be just fine without new releases of them. Yeah and.

A

Yeah, you can uh grant daniel blanket approval to really see if there is a security method, so I usually do it. When I go to a break yeah, I think it should be enough.

A

So no other topics- and we can finish on time then so next meeting june 16th thanks everyone and yeah. I think it was a better place uh today in terms of discussions.

E

Well done oleg thank you.

A

Thank you. Okay, thanks all bye.

A