Jenkins Jenkins Contributor Summit, 23 Feb 2021

Previous Meeting

⏯

youtube image

►

From YouTube: 2021 02 23 Jenkins Contributor Summit - Opening Session

Description

Jenkins Contributor Summit opening session with Jenkins project status presentations from Jenkins board members and officers for Jenkins governance, Jenkins core, Jenkins security, Jenkins infrastructure, and Jenkins releases.

Presentations from special interest groups included user experience, platform, documentation, advocacy, and Chinese localization.

Presentations also included Google Summer of Code in the Jenkins project.

Slides are available at https://docs.google.com/presentation/d/1XZuFHcPP4FqtR9_bnSjhDDJMTZ1YYRbyelzt4iGz5oM/edit?usp=sharing

A

All right welcome everyone. This is the jenkins contributor summit 2021. This is our first experiment with doing this contributor summit online, and please note I consider this experiment and I hope you'll be patient with us as we work through what this experience is like in the past. Well, I'm going to share my screen and talk about why we're in this format etc.

A

Let's, let's just go ahead.

B

A

This is the jenkins contributor summit, we'll be running for two in two days: 23rd through the 25th, basically a 48-hour period where we're going to encourage people to be con act as contributors and help us understand the vision for where we want to go. um Today's session will last for about two hours. The intent is we'll have welcome and introduction that I'll provide. Then project related updates and team related updates, special interest group updates, and then we will take about the last 30 minutes slip into breakout rooms and schedule the tracks for this.

A

This summit there were specific tracks of interest and those specific tracks of interest. We would invite you to to enter into those breakout rooms work with the track leader to assure that you're you've found a time that worked for everyone to meet together and then hold those meetings sometime within the next two day period, so that for our conclusion on thursday, we have a ready summary of what came from those track meetings.

A

So now, why are we doing a contributor summit? Well, we need to gather jenkins contributors as the jenkins developers, people who test people who write jenkins administrators jenkins users. Many more of those who are actively willing to assist with jenkins in its development jenkins is used in over 250 000 installations worldwide.

A

It's widely used very popular and matters deeply to many organizations, both companies and open source organizations.

A

In this session, we'll review the the last 12 months of work, what things we've achieved and talk about what leaders believe we should do as the next in the next 12 months and then that will be discussed in more detail in the the various tracks that will meetings be meeting separately so schedule wise. We're now, in the opening session, we'll do 60 to 90 minutes of presentations from the jenkins board from jenkins officers and special interest groups, then we'll slip into breakout rooms where, in the breakout rooms, we no have the track.

A

Leaders seek to choose a time when that track could meet so that everyone can be part of the discussions that are held in that track meeting. We know that this is a 24 hour a day world.

A

I was just chatting with a colleague in india minutes ago, and that is this is a really bad time for that person in india. So we rely on you as track leaders and as participants in the track to find a meeting time that will work for you if most of your team members are in china meet during a time that works for beijing.

A

If most of your team members are in europe or in some part of the us meet at a time that works for them, it's also okay, to do multiple tracks, the document or multiple meetings of a track, the documentation.

A

Sig already knows we will do two track meetings, so we're going to do one meeting for the europe time zone and one meeting for the western u.s so that those track meetings will happen beginning today or whenever you negotiate through the start of the closing session on thursday anytime, in that 48 period, meet together, you're welcome to use zoom or jitsi or hangouts, whatever works well for you, the track leaders as assigned right now actually have access to the cdf zoom account that they can use that use.

A

Other systems, if you need to then in the closing session, we'll look forward to the track leaders presenting a summary of what the results are in the track and we'll look to see updated proposals submitted to the jenkins roadmap.

A

So let's do project and team updates now and I think now it's oleg it's yours.

C

Okay, I can do that. So do you want me to present myself or do you want to.

A

I was assuming it would be simpler for if I advance the slides and but if you would rather I can, I can give you control and we can let you share. What would you prefer.

A

Okay, let me I'll stop sharing and we'll. Have you share your screen, then yeah.

C

I usually jump between links so right, understood, host disabled participants.

A

Yeah, just a minute I'll allow you to share, I I was trying to be careful.

C

So no zombie right, please, okay, so this is my screen. I do thank you yeah. So just a quick update on jenkins governance um last year was actually quite busy. um In 2019 we had first elections, uh we expanded the jenkins governance board and we started pushing a few topics in the community, most notably streamlining some of the community processes and getting more people involved involved in maintenance roles, and they view several important changes.

C

Yeah. This list isn't prioritized. I will just go through that quickly, so one of the first items that we introduced a new jenkins public roadmap, which aggregates initiatives in various aspects of the projects like features, documentation, outreach programs, etc, etc. So in theory we wanted to put all major initiatives happening in the jenkins community on this list, so the potential users and contributors can discover them, and you can find a lot of uh topics there and one of uh subjects for this.

C

Event, and also for the junkies governance meeting tomorrow, is touch the reflection of the roadmap and to see what we are missing, especially in terms of near-term and future so items we want to do and we want to see in the project in a possible future. um Then we have graduated from the continuous level foundation.

C

Well, we're still a part of continuous debian foundation, but jenkins was the first project to create. As part of that, we changed our processes. We updated our code of conduct, we have achieved full compliance with current infrastructure initiative, requirements etc, and it was helped us to get some visibility and to get promotions by the continuous david foundation and yeah. We should keep working on that.

C

Other important change was technology cleanup and new code of conduct. Both of them happened in the beginning of the summer to address concerns raised by community members, and now we are more aligned uh terminology ongoing process and we look for contributors to get it over the line, uh but yeah still it's a significant change.

C

Then we've got a new funding. uh Page we've also got a page distant drinking adopters. So if you're interested, you can just go to the browser and find these pages so basically uh slash project, and you can find a lot of things here.

C

Basically, all this documentation has been created or moved and updated here during the last year. So um if you're interested to take a look and yeah.

D

C

But not least, we had 2020 elections and these elections, so we added two new board members, uh martin jackson and gary morgan. Do we have them on the call yeah, I guess not, uh but yeah? uh So currently we have uh five active board members and we can drive different initiatives in the community if needed, and so it helps to achieve the goals and also to facilitate particular topics which we would like to drive in the community.

C

So uh what's next uh for the board, actually, when we were doing uh 2020 elections, one of the questions was: uh what do you like to see in terms of junkies governance, sport activities and we got more than 40 responses, some of them your paragraph long? Some of them were showed, but there are three key items in the feedback there so, firstly, keep growing the community keep the community healthy help, new contributors to join, etc.

C

It was one of the biggest areas of feedback, then drive for pc changes and modernization, also a lot of feedback and they diversify jenkins beyond ci cd. They were surprisingly many answers uh proposing that so jinx is an automation server, but historically a lot of complications. uh Only within ci cd, but it's nice to see that uh people want to see other areas as well beyond that uh there were also a lot of positive feedback and the requests to organize more events written jenkins world conference.

C

Maybe we should do that as a junkies user conference who knows but yeah. These are key items. uh What we also have on our roadmap in the to-do list, so we have uh contributor onboarding. We need to import individual contributors and company contributors. We need to facilitate jenkins roadmap and there are a number of formula items which we need to address at the governance board. So first agency's enhancement proposal process needs to be reworked.

C

Currently it doesn't work because it was intended and um it becomes an obstacle for those who try to create the jibs and at the same time we cannot appoint people to the process, because this process doesn't help to deliver changes and build consensus around them. So we will need to work on that. Then.

C

Finally, jenkins trademark has been transferred to the linux foundation. It's just update from the last week and what it means for us so that we as a genius project need to perform updates, including jenkins website. Well, all jenkins websites, also our cla here- also our documentation.

C

So there will be a lot of activities required that there are also other programs like friend of jenkins, which are not quite active at the moment and uh yep. It's just a uh top of the list and of course there are many other items we need to think about when it comes to governance um on the road. Now.

C

Currently, we don't have much things, but I believe that we still have um a technical steering committee here, which is slightly aligned with process revamp, and there was also a lot of discussions about user advisor report over past months. So maybe we should also put it on the list so that we can also start working with users, maybe as a part of continuous delivery foundation, efforts with user console or independently.

C

But this is items which are currently on the radars and if you have any other proposals, if you would like to see any additional changes, we have a governance meeting tomorrow and they suggest to use it to discuss. What's next in governance and what are the requirements.

C

Okay, any questions comments.

C

Okay, so if you think that I talk too much, then yeah link is called so yeah. This is funny yeah, okay, so the junk score was uh quite active in the past year. So historically jenkins score was rather a set of extensibility features, like extension points, some basic frameworks, etc, and historically there were not so many features being delivered and the junk is called directly this year.

C

It slightly changed because the baby of projects, specifically targeting uh features provided by gentilescore and underlying frameworks, uh the key highlight is your ux rebound will be many changes in different uh focuses. Lately we will have a uxc update uh but yeah. Basically, they will local and feel improvements, so they have new controls. uh There was a better support from the themes introduced and a dark theme for jenkins, and there was major revamp of plugin manager.

C

I guess two revamps by now um also called configuration management etc, and there is upcoming change related to table studies, continuing duration and uh many other, smaller accessibility and your ux topics. So if you use jenkins, you may have noticed that the web interface changed a lot over the past year.

C

When then, for users of configurations code, there is no support of read-only configuration ui so that you can configure everything, that's called, but still access uh information. That is managed permission which provides permission set, so you can have managers in addition to full admins in google summer, of course introduced external fingerprint storage, and there is also new windows installer again, it's not all new features, it's just uh one top ones from the changelogs and there we also some changes which are not that public facing, but which are really important for the project.

C

The first, of course, is security. There will be a lot of security hardening and fixes around the jenkins core. There are many advisories this year. Again, it will be discussed later in depends, um and another important highlight that this year there was major updates in terms of technical depth and dependencies.

C

There were many topics like sg security, extreme, which we were afraid to touch for years, but this year we finally did it so extreme jquery screen security.

C

Also we enable dependable- and they do dozens of library updates uh within the project. uh It helps with security scans. It also uh helps uh this functionality and allows to keep project up to date. So thanks to everyone who contributed and yeah it's great that we the rest of this topic, also we removed about insurance dependencies, which is also a good thing, and another important effort is good quality and smells.

C

So there is a number of contributors who work on various static analysis, shifting apps idea warnings, performance, optimizations, and although these efforts do not always get to change logs, some efforts are too minor. Some are also the refactoring, but actually they they also help to keep the code bias code be up to date and thanks to all contributors, I put some names on the list. But firstly, this list is not complete and.

C

If I missed something, sorry, someone um and if for yeah, hopefully we will finally have a list of contributors directly in the change logs, like we planned at some point: uh okay, okay, uh there will be some changes in the maintenance, so, firstly, we finally got release automation for lcs and weekly releases, so there is no new release: automation, infrastructure. We share, builds tests and sense and ships releases it's a major enhancement compared to the city in 2019, then we've got a new release officer team jacob.

C

uh We also onboarded a number of new main call maintainers so that there are more people who have technicians who can review and immerse changes thanks hello to everyone who does it on the regular basis.

C

We currently maintain around six pull requests in the open state. It's an improvement compared to previous years, and we merged a few dozen school requests every week. So yeah, it's a good balance for now, and uh now this dependable, uh such a many of these pull request, actually artificial ones. So it improves the situation. Then, of course, current infrastructure initiative compliance.

C

So now our maintenance policies and documentation and security policies- all of them, are like aligned with the linux foundation requirements, and they are also documented so that users can discover these policies and potentially tell unbox uh additional opportunities like security analysis, funding and yeah depend upon. We talked about it preview, but finally, dependable is also part of the jiggy score.

C

C

Now we can update dependencies in a much more relaxed state than it used to do to be before when every update was manual.

C

Okay, what's next, uh basically there will be new lcs soon and there was a blog post by mark about changes upcoming in this release and one specific change which we need to highlight once and once again is configuration ui tablespace.

C

So if you use complex configurations, please take a look at the current weekly releases or have the release candidate and try them out to see whether your plugins are compatible and if not, please report issues, because this is a compatibility breaking change. We know about many plugins affected and be interested to stabilize it as much as possible before the general availability of the lcs baseline and securing the jk's delivery pipeline will be a separate uh track, which we will be discussing any kind of security issues with our built infrastructure and delivery infrastructure.

C

And I guess so that's it about what's next, because there is no other specific initiatives plans for the junk score at the moment and if you see any major initiative missing, let's discuss it during the summit.

D

A

Thanks so much thanks very much so oleg, maybe you'd be willing to continue driving for this piece daniel. I was going to drive for for daniel, but since you're already on the on shared screen, why don't you just go ahead and bring this up and we'll let daniel take the next voice daniel. Thank you very much, daniel our jenkins security officer.

E

Thanks mark uh thanks olek for driving next slide, please um so 2020 has been quite a busy year, as uh many past years have been for uh jenkins uh and jenkins security and the jenkins security team. So to get the stats out of the way.

E

First, we delivered 19 jenkins security, advisories, five jenkins, core security updates, fixing, 19 vulnerabilities and in terms of plugins, we announced 200 vulnerabilities in about 150 plugins of which two-thirds uh had fixes, which means about one-third of the vulnerabilities that we announced were in plugins that are unmaintained or whose maintainers were otherwise not.

E

We were unable to contact, and in that case, as you surely know, we published the advisory and set up the warning to inform the administrators about that.

E

Last year, we've late last year, we've started the trial run of using codeql a recently uh by github acquired technology for security scans.

E

The problem that we've always had in the past with security scans, is that a lot of the things that we do in jenkins are fairly unusual, for example using the stapler web framework, so other security scanners always often didn't have really useful results and, with the custom rules that we wrote for this for jenkins-specific problems, we've been able to identify several vulnerabilities in plug-ins that we fixed and, of course the idea is to expand that even further sonic already mentioned, we updated some dependencies in core, most notably uh extreme and um replacing a segi security with spring security.

E

Those are not immediately useful for for for security, but this limits risk. If we're tracking the upstream project and their releases more closely, we will not have uh substantial problems when a vulnerability is discovered if you're on a really outdated release, um so that indirectly also benefits security. Of course, uh two steps forward, one step. Back. uh Last friday, we delivered the security update for recent jenkins weekly releases, because this update of spring security introduced the security vulnerability.

E

um Oleg you're still sharing your screen.

C

Yeah, I was just showing the security.

E

Yeah, so this only affects the jenkins weekly releases, because uh previously published lts releases do not yet have spring security, but will, in a few weeks on the ui ux side for security, we made the security warnings more visible in the plugin manager inside jenkins, which allows administrators to more easily understand which updates relate to which security issues they want to fix, and, finally, the most exciting entry in this list. Unfortunately, you will not be able to tell is the internal tool improvements.

E

So the jenkins security team is a very small team and we publish quite a lot of security. Advisories help maintainers, deliver security updates and we've massively improved our internal automation over the last year for advisory authoring for delivering updates for um merging security fixes into jenkins.

E

Obviously very little of that is visible to the outside, but you may already have seen the new jenkins security logo or avatar. That is also on the slide on the right uh in the commit history of the early january, core security update. That is, the avatar of our release for our security bot.

E

uh Please next slide.

E

So, what's next, obviously we're going to continue delivering security, fixes security advisories to inform administrators that they need to keep their software updated.

E

But beyond that, we want to improve the developer tooling, to make it easier for maintainers to keep their plugins secured and to do the right thing in the first place in particular, making the jenkins security scan based on codeql available publicly and to roll it out to all jenkins plugins, uh hosted in the jenkins project, um then securing the jenkins delivery pipeline. This is kind of a theme of this condition summit, we're all about automation, but maintainers release uh plugins from their laptops.

E

That's not quite uh where we want to be so.

E

There has been a lot of automation, work in the past uh by olivier vernon and others to automate the core releases and jesse glick has done some work, uh gotten started with it to automate the releases of jenkins plugins, and ideally, we will be able to take that developer laptop out of the equation entirely.

E

And um finally, uh we want to get more people involved, uh more contributors involved in jenkins security. Now um it's! I cannot just make everyone who asks nicely of a full member of the security team with access to information about unresolved security vulnerabilities in a variety of components.

E

But, as I hopefully demonstrated, not everything is just fixing security issues. There are a lot of ways for people to contribute to jenkins security, to the ecosystem, uh to the documentation to the ui ux of security, even if they don't have access to the poison cabinet, and so, if this is something that interests you just let me know and we'll figure this out. Thank you.

A

Thanks daniel next up is olivier, verneen.

F

He sounds like he's my round next, please.

F

So basically, I want to. I want to start with that. um Basically last year has been tough in terms of um service stability, uh service outages, but we also drastically improve the reliability on other services.

F

So the reason why I want to mention this here is: we had a few issues with the service that you rely on, which help us to identify gaps, gaps we had in our processes, so we drastically improve on the monitoring. We just drastically improve our process around managing infrastructure um and yeah. That's that's basically come with um increasing the jk server project. Basically, can you go to the next slide?

F

Please? So I I can't really I mean I don't really have one way to either to to highlight how um the infrastructure is used, because um we run many different websites, but this one is just google analytics google analytics. That shows you, the traffic we had on the main website, chinkistrail and, as you can see here, we have users from everywhere in the world um and the traffic increased by 30 percent.

F

So if you know, if you understand, what's happening on the main website, just imagine what happened on tierra the plugin site, the update center and many many other services. So that's what I mean by we had a few scalability issues to keep up with the demands. um But overall, I think in terms of reliability. The last year has been really great. um Can you move to the next slide? Please um so, basically the main areas that we work on over the last year. So we already mentioned the release environment.

F

um So we now have a secure way um to trigger a release. The community can see when we do a release. What's the output, so obviously it increased the feedback loops. If something goes wrong, um so it has been used since april. We also worked a lot on the mira infrastructure, so the mirror infrastructure are the services that people use each time they want to update a plug-in. They want to install the shaking score or whatever. So we had a lot of scalability issues in the past um and it's now getting way better.

F

We work as well on documentation. We may create jira to um to the linux foundation, so that was also a major initiatives. So the idea is, we don't have to maintain that service anymore, so we don't care about version, update and so on. So that's that was something really great. That happened over the past year, which helped us focusing on other services and something major that happened as well was cost cutting, um because we have to to keep.

F

We have to keep control on the way we spend we're spending our money in the jenkins effort, but I mentioned that in one in the coming slides. So next, please.

F

Next slide, yep thanks. um So just something that I want to highlight is the number of contributions done to the jenkins infra project. So people um I mean we had quite a lot of contributors. um Some are just recommendations.

F

Some are specifically like public communities or whatever, but basically we had a lot of traction um in the project. We we had a really stable um amount of weekly meetings with, on average, three to five people attending each time. So I mean that was a really great idea. A.

C

F

Year in terms of contributions specifically to the jenkins surfer project, um something also that I like to see in this graph is how the contributor shifted from um contributing from the united states to europe. um I mean from from my point of view, it's definitely easier to connect with the people, but yeah.

F

Please next slide this next. um Something that I mean I don't often share is how much the jenkins infra project costs and basically, what happened over the past year. Something really specific to us is we don't have a credit card, um so we don't really have a budget. So when we want to bring more services to the community, we have to find sponsoring, um which is great when we have sponsors, but obviously sponsors are coming goes, and sometimes we also have to make choices about. um What are the services that we can keep?

F

um Not every sponsors provides us, so we have different kind of sponsors, those who just provide us services for free- um and we don't know how much we are spending. So an example of that is reporter jenkins, here.org, sponsored by g frog. um It's a quite a critical component of our infra infrastructure, but I mean we have no insight of how much we would have to pay for that machine.

F

But on the other side we have sponsors that just gave us credits which allow us to spend the credit the way we want to spend it, um and so that's that's where this number come from. um I just look at every cloud: every account that we have how we are spending the money and basically it helps us to identify um if it's worthwhile to use more of a specific service um to identify other different kind of sponsor and so on.

F

So if you look at the left uh diagrams, those are a percentage of the 200 000 dollars spent over the last year. But obviously this is the minimum number because, as I said, datadog ibmg for a page or duty offer us services that we don't have to pay, and so we don't have any insight on how much we would have to pay for those. um And so what happened? When we don't have a sponsor anymore, um then the cdf um paid the bill. um It's it's like um the last solution.

F

uh So it's really nice, but on long term we have to increase that that numbers, and so over the last year we went from spending 20 20k per month on the azure account to less than 10k 10 000.

F

So right now in terms of our objective, it's fine, but it also says that we cannot easily increase the usage, so we have to find other options um to increase. um I mean to increase the the number of machines um in the future, um so yeah right now we have 40 percent of that that's money which is sponsored, and then we have to find solution for the rest. Next next slide, please so the way.

F

The way I want to finish this is it's quite difficult to to define a roadmap for the jenkins infra, because we are usually I mean we even depend on um provider that we have sponsors that we have and um the ecosystem the way it evolves. But the main main ideas here is to keep working on sponsoring. um We are definitely looking for sponsors who can sponsor us for years.

F

um The reason for that is because take time to migrate between cloud vendors um and that energy could be spent somewhere else than just me, creating between cloud vendors. So if you have any ideas of suggestions that would be really nice.

F

Another major area that I think we will have to work is the plug-in release environment um if we have to put something in place, so we already mentioned that we have an environment for releasing jenkins car. We may have to put in place something for the plugin ecosystem as well, which has different needs. um So this is something that I would like to work in the coming year.

F

um I want to mention confidence. So over the past year, we spent quite a lot of time migrating the documentation from conference to either the jenkins ie website or on the plugin site. um That confluence machine is still something that we have to maintain, um and ideally, I would like to see it moving um to say go as far as we can, so I think it would be nice to to focus on what's missing, to stop that service. Definitely um we have some work to do on the update center.

F

um Not the service itself, um but where it's running so we have some cleanup to do in the amazon accounts and so that service is running on that on the amazon account. So we we have. I mean we it's a critical component to our infrastructure um and so yeah. We cannot. We cannot easily modify the way it's deploy and manage. So um that's something that we'll have to clearly look at and finally yeah. We have a few maintenance tasks that happen every year.

F

um This time, I think we'll have to focus on the better from codes um to just do some updates. We wrote those codes uh years ago, and so now um it will be soon some time to to update that so yeah that that's all for me any questions I mean the roadmap is not something fixed. So if you want to work on something particularly um yeah feel free to to make suggestions, we we have a roadmap, but I mean it changed depending on the needs.

B

Thanks olivier, oh, like let's.

A

Go to the next slide, then. Thank you very much so tim jacom, our jenkins release officer next topic. Tim go ahead.

G

Hey everyone um next slide cool, um so yeah last year was the year that we finally got core release, automation, working, which is um basically completely automated, um building, um building testing and deploying and releasing the jenkins wars to the to the world, um and so we think it was in june. Julyish weekly release was completed and we started doing weekly releases, um and so that's all completely hands-off triggered automatically every tuesday um at around 10 30 a.m.

G

Utc, I think roughly then um and yeah, so that's completely hands off, um and then we have lts and security releases as well. um So that's a huge um it's a huge milestone for the jenkins project. Previously um kosike had to release every single version of jenkins back from the very first 12 until whichever version it was that we stopped at, and I think he had it semi-automated, but it sometimes failed and if he wasn't around it could take a while and a huge huge benefit as we can now.

G

If there's something seriously wrong in an existing version, we can quickly release a new one um and there's a number of contributors that are able to trigger a release.

G

So you have taken over the release officer, mostly just trying to make sure it's not centralized, grow the team a bit and get other people involved and sort of started that off with some documentation of the full entwined, lts release, process and developed a checklist and we're trying to, um and some marks helped out on. The last couple of releases- and I think it's been quite good so mark was coordinating some of the 2.263 lts releases next slide.

G

Cool, so what's next in releases, um so you heard quite a few lines there. The only line that we don't have automated and are still running on my machine is the lts release candidate builds, which I really would like to get off my machine.

G

So some progress was made last year, but we weren't didn't get it fully working, um so we just yeah. We need to finish off that part, um so jesse's plug and release automation has already been talked about, um but it's quite good and there's a few plugins using it already and there's documentation on jingles to io, for how you can change your plugin over to using it.

G

I'm not sure what that line was mark chapters in there more dependency management. Automation I mean. Does the jenkins bot the jenkins plug and bomb is going well um and it's getting widely used and it's in the archetypes for every new plugin that gets created, um and so I talked about the build test deployment of the jenkins release earlier, there's more than that. That goes on.

G

um There's things things like change log and some testing, that's done outside of the jenkins core process, and so there's a number of manual steps that are done, especially for lts releases.

G

The weekly release manual checklist is a lot shorter, but the lts one has quite a lot on it um and there's a number of things that we can be done to automate that even yesterday, gareth just did a pull request, which should help, which is automatically updating the lts version in the helm chart, um and it says the public community helm chart um but yeah there's a number of areas where that would be useful to just automatically update um and so put a few ideas out there for anyone who wants to get involved and help out, but basically pretty much every step in the lts checklist is up for automation.

G

Ideally it's very hands-off and just happens as much as possible.

G

That's it for me.

A

Thanks, so the the special interest groups are the next topic um oleg. If you want to go to the next slide. ah Yes, felix. Could you take us on the user experience.

H

Yeah, definitely thank you mark uh hi everybody. um Can you go to the next one? Please.

H

um So 2020 uh I'm happy to say that it has been a rather big year regarding ui changes. uh I started with the latest one, which is table studio for configuration uis. So almost a year ago, josh zarev approached the uxc asking for help driving this his already year old vr.

H

Team has been working especially and has been working really really hard on it. So thank you tim. It's! It's coming after much work on community vlogging after much a bit of pain, it's coming, it's happening, it's been released in weeks, or maybe I think it's really big. I think it's a nice step for accessibility and a good improvement overall.

H

We expect some problems, though, and we are monitoring the back reports. Of course there will be backgrounds, um he's saving improvements. um A year ago, the uxc started with the with some list of items we wanted to improve, which were heavy and having a footer typography hyperlinks buttons stable stuff.

H

So we achieved all of the of those issues all of those items except the iconography, which, thankfully tim I will talk about it after all, uh the thing is, I I think in my opinion, it definitely has a more modern look at the field and these styling changes also brought again my team. Oh most of many of these are writing. ah It's a possibility to improve theming and team created a dark theme and I think they daniel created a solarize thing, which I'm a very big fan of so.

I

D

There's that there's.

H

A there's, the uh thing manager themes are incubated and they will may break with updates. So there's that, but you can try them out in plugin plugin manager, which has been watch improved as well by mustered by daniel and yeah. uh Now there there's categorization uh with some nice levels for for for each flying, there's a more much more performance search.

H

Exception available that pretty good stuff there's also read-only configuration apis for users without permission. It's it's really handy and jquery was upgraded across the whole plugin ecosystem. There was on several several cves uh razer regarding the versions which jquery used in jekyll's ecosystem, so we did a strip across the james ecosystem and we updated many unsecured jquery instances or we did remove them when possible by the way regarding a safe version of jquery is rudy hafner's, plugin, jquery, 3 api, that's updated to a secure version.

H

Next, one please, and what's coming next icon improvements, uh I think jackman just created a pr. I will try to edit these lights after this. If you remember, please don't remind me of this. He uh to change iconography! It's it's going to be a big topic on this new lds cycle. In the jungle year cycle. We are starting small, with mostly with.

H

Weather icons and they build status indicators. We encourage everybody to try them out and progressively. We can expect that everybody is welcome to contribute the new icon updates. There are lots of icons that need to be changed and it's a huge effort and it's here and we need more developers and designers to be involved uh this eu. This ui is an area where we certainly need community contributions so, and we welcome everybody. We will help every every every animal new contributed out.

H

Everybody is welcome to. We appreciate the new contributions here. So next one please.

H

So next one please blue ocean. We have talked about blue ocean before the status is, and there is no new development on blue ocean. um We travis, we still monitor it, for security, for security issues and defects. Those will be addressed and any any important community contribution will be reviewed on marches first.

H

D

H

uh And I think this is it right?

H

Okay, thank you. Thank you. Everybody.

B

A

Felix so platform sig next topic- uh oleg next slide, please so in 2020 we we cemented the support for java 11. we've upgraded our docker images to use debian, 10, centos 8 alpine 312 to use latest versions of the jdk, both for 8 and 11, and we now get proposed image upgrades from dependable. We like that very much we've added additional experimental docker images, including the the open j9 support for system, 390, mainframes, um interesting and fun. Things continue in the platform.

A

Next next slide. Oh, like.

A

Oh dear, did I get the what's next slide? I apologize apparently the what next slide is the same thing. That's just wrong. Sorry, everybody we've got more work to do on docker image maintenance. We've got lots of work to do around how we handle and improve the experience for users of our docker images, and we've got lots of interest in the in the world in general about arm yeah. Next next topic is grado like I must have made a mistake on the slide. I apologize.

A

That's we'll we'll be grateful that the platform topic is brief. Documentation sig, likewise, should be brief. Next slide, there uh delighted with the work from gavin mogan and from oleg on helping us get plug-in documentation migrated we are now at over. 50 percent of plugins have migrated their documentation to github. Congratulations. Thank you plug-in authors. Thank you, documentation. Authors znob was our jenkins on kubernetes author for google season of docs and did a great job there, mentored by kristen whetstone by me and by others great experience.

A

Thank you very much to google for funding that the wiki migration project is progressing slowly and we are having successful documentation office hours twice a week with regular attendees, both from the european side and zinab in africa and from the us west coast. Thanks very much next slide.

A

What's next in documentation, the crucial things are, we need site search for jenkins.io and we've got an active project right now that gavin mogan is running to improve the plug-in site search.

A

In addition, we'd like to join google season of docs 2021, like we did in 2020 it's a different program this year, we'll need to look at it. A little more carefully understand how to approach it, but we think we can. We can join it and have benefit from it.

A

We've also got a new initiative from zenob, proposing that the jenkins project proposed project ideas to she code, africa, chico africa is a an initiative zenob's a member of this group that attempts to assist women in africa in becoming more involved in technology, and we look forward to this we're going to plan for it. It's an upcoming event in april and, yes, we need to improve our contributor onboarding experience both for chico to africa and for other contributors as they arrive.

A

A next slide like, I think, that's it for documentation. Oh no, no, we've got other concepts. Sorry, we want to inventory the current documentation on jenkins.io, the wiki and other locations and then proposed destinations. One of the weaknesses we have is we've got an awful lot of content on the wiki that is outdated or partially outdated needs a needs, a place to be put on jenkins.io and that place needs to be carefully considered and thought about as we structure it. We also would love to include continue our efforts on changelog automation.

A

Right now. The change logs for core releases are generated with tooling, but hand curated and we'd like to consider. How can we improve and further refine that and that's it for documentation? Oh, like next slide,.

A

Alyssa, would you like to take on advocacy and outreach.

J

Yes, hi everybody, um so next slide, oh like please, so in 2020, the advocacy and outreach sig ruled out a few fun outreach programs with the goal to promote and bring jenkins in good light. So one program that we did was called jenkins is the way, so this basically is an initiative to collect document and share how users uses jenkins we've documented their challenges, their goals and their results.

J

And then we publish this on a website dedicated to all these stories and which is jenkins is the way dot io that you see there, the industries that we were able to capture these stories includes just to mention a few health care: financial services, gaming travel, science and, of course, we received over hundreds of submissions and of those just last year alone, we published 70 users stories and user stories are an abbreviated version of a case study.

J

We also published six case studies, five testimonial videos which can be found on the home page they're, oleg um yeah, thank you and then we published one ebook and sent out over 200 um jenkins is the way t-shirts.

J

Again, the link is jenkin. Jenkins is the way dot io all right next slide.

J

Oleg another. um Another fun item that we pushed out last year was a cartoon video. That explains why jenkins is powerful and flexible tool for cicd, and we once we pushed this out and it attracted over 14 000 views within about three months next slide.

J

We also teamed up with comet strip to create jenkins comic, just to give some humor uh to a day in the life of a developer, automation and mr jenkins, and we also try to relate it to you, know the stuff that's taking place at the moment.

J

The programs that we were rolling out so like the jenkins graduation uh with cdf and then jenkins, is the way theme on the right hand, side there next slide, please so the events that uh we were we had a presence at in 2020 includes foster scale devops world cdcon and we participated in the hacktoberfest citycon. No sorry devops world was the largest event that we attended last year with over 20 000 registrants next slide, please.

J

So what is next? For this year, we've completed the online fosdem event. Earlier this month we will have a presence at cdcon which is taking place in june, so in case anyone is interested in speaking at the conference. The cfp is open until march 5th.

J

This will be a virtual event and then devops world will also be a virtual event which is taking place in september. uh This is the largest jenkins event of the year. There will be lots of jenkins content and expertise, so please keep an eye out for the cfp if you're, if you're interested in speaking and that will be available sometime beginning of march um as for jenkins, is the way outreach. We will continue with this program in 2021.

J

uh We want to continue to collect more stories. Specifically, we want stories from the open source foundations that are using jenkins. So if you know of anyone who are in this space, please reach out to me and we like to write, write up stories about them, how they're using jenkins within their foundations, and lastly, we we would love to do an education outreach. Basically, this is a program that will allow for college students to learn and adopt jenkins as part of their college curriculum.

J

If anyone is interested in building this program, please reach out to me via the advocacy and outreach sig. That's it for me.

C

Thank you and the next is google summer of code.

K

Great google summer of code next slide, please.

K

This is our fifth year for the jenkins project to participate in google summer of code. um We're very excited about it. Last year was an amazing year. We had seven projects all completed successfully. Really great work was done, so that was a very fun and there were over 40 participants. So it was a very large gsoc participation.

K

We have weekly office hours for gsoc, please do join um I've, put a link to the events calendar and then you, you will find the time you said they're on wednesdays, at uh 1400 utc.

K

So tomorrow everyone is welcome, jump on find out more about gsoc how you can get involved either as a student, a mentor um we have. We have our projects listed, but uh even though our gsoc application is submitted, we are still open for project proposals. So if you have um an idea, you can uh feel free to to bring it up at gsac office hours and and or pr or repo, uh for where the project listings are. Thank you for so these are the projects we have now.

K

All of the draft project ideas um are will be moved to accepted, and that's that that will be done very very very shortly. um We would like more mentors. We've had a lot of mentors step forward, so thank you so much to all of our mentors and all those who have suggested project ideas having more mentors is always welcome.

K

This year, gsoc is going to be slightly less coding hours than usual. Usually it's 350 coding hours this year will be 175 coding hours. So what that means is there may very well be slightly less like say, code reviews required from mentors, but we do want students to have a really good experience, so we do want to support them fully, which means that we still need loads and loads of mentors, and we don't want to over overwhelm you as a mentor, so the more mentors we have, the more the work is spread out.

K

The more support students get. So this is what we're looking for. um We can go into the next page, and this is just a shout out to all the our gsoc 2020 projects which we're super proud of. Please go read more about them: they're they're awesome. So thank you to everyone who was involved in this initiative last year, because it was a huge success next page and these were awesome students who um contributed to jenkins last year as part of g suck. So thank you very much to our students.

K

It's quite quite an honor for us to have all these students participate and um become involved in the community, and you know we we um giuseok is its own project and in and of itself it's a great body of work and we're really happy to be involved in it.

K

But it is always um very validating and we're always very excited when, when students continue to be involved in the jenkins project, so just quick shout out for sladen, who was um a gsoc student last year, did a fantastic job, and this year has come back and volunteering to mentor on three of our listed g-suck project ideas.

K

K

So these are our project ideas, just quick um which link through to their listings on our website. Just quick, quick note on slate and volunteering three times for three three projects uh to mentor on. For this summer, if you do so that doesn't necessarily mean we expect you to mentor on all three projects. If students pick them up and they go forward as gsac projects, you know we will work out your your schedule, but um the mentors should put their names down for any of the project. Ideas that interest them.

K

So you it's not a commitment, it's a statement of interest and engagement. um These are the ones that we have so far. Seven of them. We have a potential eighth one in the pipeline, which is very cool. uh I was pinged last week saying: oh, you know, you've submitted the g-suck application, but I have an idea. That's come to me. Can I still submit it to the website? The answer to that question is yes.

K

These project ideas are fantastic for applying to google summer of code, so they actually form the basis of our organizational application to google summer of code, so they are essential to us. Thank you to everyone who has submitted them, um but but we can still accept more project ideas. Now, um okay, next page.

K

Okay, great so, we've applied to uh google summer of code this year, it's a little bit different as part of the continuous delivery foundation um and we're really part of we're really excited to be part of the cdf's gsoc org, because it's already enabling us to benefit from uh being part of the continuous delivery foundation.

K

For example, I've already been having conversations um with the folks of the continuous delivery foundation, who are organizing cdcon, which is their conference, and we will likely have our google summer of code students be able to give little updates at that conference, which is pretty cool to speak at a conference when you're still a student and participating in google summer of code. So that's really nice. The other really nice thing is uh it's become that much more natural for us to? um I guess, work and mentor between projects. So we have one of our project.

K

Ideas is the tactile. Client is increased, work being done on the checkdown client plug-in for jenkins, and it's very likely fingers crossed that we will have some tactile folks, also mentoring on that, which I think is a really cool collaboration between projects and will benefit the students in other ways. um This is nice. Is that uh being so much part of the continuous delivery foundation?

K

We can get more resources to students or have have grabbed sort of, like other unofficial mentors and get them a little more um access to resources. For example, one of our um projects is on cloud events, um a cloud events plugin for jenkins, and there is a cloud events sig at the cdf, so we're very much encouraging interested students, as well as those mentors to engage with that sake, and you will learn a lot more that way and be able to ask those questions. So that's that's quite nice, okay.

K

So I briefly mentioned before: gsoc has a shorter coding phase this year, 175 hours versus the the usual the more usual uh former way of 350 hours, and there will only be two review periods instead of the usual three, but uh we're still very excited for students to have a great summer and contribute to jenkins and get involved with open source and join our community. So this should be very, very, very good, good summer um again, additional mention uh mentors.

K

Please sign up more the merrier same with project ideas and uh last there are a few links there for joining our gsoc office hours every single week. You can drop in and out of them, and ask your questions and find out more about the projects, those links to our gsoc meeting notes and blog post on call for mentors how to how to sign your name up. Also, there's information on that post on how to propose project ideas so yeah. We we hope to uh hear more from you is the short of that. So.

A

Thanks kara next.

C

Yeah there was a question in the chat about: are these projects only for young students or how young are the students being targeted.

K

That that too, actually this is really interesting that you suck for this year. um Gsog is, I guess traditionally, is how you would say it. It's been for for students who are involved in computer science programs so that it's for actual students um and and I think the age cutoff may have been 25, but uh in general it was for students. I managed to read those links in the blog post on the exact criteria this year that criteria that has really opened up in a nice way.

K

So you just have to have been a student on sort of an uh an official coding program, so it opens up jake gsoc to students who were engaged in boot camps recently, just graduated from boot camps. So that's quite uh nice. Actually I.

C

Like that, broadening.

K

Of the potential base.

C

One thing which was mentioning that it's not only for coding specialities, it's for any official student, including phd students, so well, it was always like that. But you know they had an official programs, because this year not everybody was able to access education because of covet disruption.

K

Yes- and that is one of the reasons they're also having the shortened time frame, it's just an acknowledgement that um yeah our lives have been disrupted this year.

A

Okay, thanks very much kara. Thank you. Thank you, so um rick who would normally present this material is probably asleep right now, so just be aware that the chinese localization sig is very active, they continue to translate the the product. They continue to translate change logs. They continue to make progress there and rick has been coordinating wonderfully.

A

There is a chinese localization sig track identified, likely meeting during working hours for the chinese teams next slide. Oleg.

B

K

Cloud, nato say: okay, great, uh we have a weekly cloud native sake, there's um a link in this slide for for all those who would like to join it's on fridays, at 1400 utc um during the client of sig. We discuss sort of initiatives and projects that are in that space of making jenkins more uh cloud-native work better on different cloud platforms um and different things. The three projects we are discussing, the most right now are all are all actually they've uh become proposed, gsoc project ideas which I'm very excited about.

K

So we have the kubernetes operator for jenkins, which um there's actually more than one um kubernetes operator for jenkins within the wider jenkins community. But um this is the one that's been contributed by virtus labs and they are volunteering to mentor for jutsoc as well what they would like, what the proposal for just and what we're discussing actually in the cloud native sig is um having greater security feature for for this uh plug-in, and the idea is that actually, um there are warnings that are given for different plug-ins.

K

If there's a security concern and what this will, what the gsoc project enables is that the students would um write a check essentially so that the users um could decide which plugins they would like to install whether or not their warnings when using the kubernetes operator for jenkins, but but in general, we in the cloud native sig, we we discuss all sorts of things kubernetes and cloud native vis-a-vis jenkins, the other two projects which are getting a lot of.

K

um I guess air time during the cloud native stick right now are the text and client plugin, which again is um an aspect of that has formed a gsoc proposal and the cloud events plugin. The cloud events plugin is super exciting, because right now, um jenkins doesn't really have a way. It's not it's. It's not discoverable for cloud event and that's kind of a shame, because the cloud events are being used for interoperability, between tools between ci cd tools and even possibly, between platforms.

K

So it is quite nice to be able to make cloud events um discoverable and subscribeable. So that's a really cool initiative in terms of greater interoperability, but but these are just like a smattering of kind of ideas, of what we talk about in the cloud native sake, you're more than welcome to bring your own proposals of how you think jenkins can be more cloud native or what you would like to see or if you would like to help with any of these initiatives.

K

We would love to see you at the cloud native meeting um again a link to the events calendar. So you can add it to your calendar and we have meeting recordings and meeting molds. So we look forward to seeing you there.

A

Thanks cara, thank you very much. Next slide. Oleg.

D

A

All right so here I'm going to actually stop the sharing. uh I if I remember right, yeah there we go um so now. The the session, the intent we'd like to take now is to take your time to have you join the breakout rooms that are interesting to you. You can. You can choose to navigate from one breakout room to another. I've made some preliminary assignments. Please do not consider those preliminary assignments as a mandate that you're only allowed to investigate that topic.

A

Many of you had provided a a list of which topics were interesting to you. I've attached you to those lists. Most of you will go first to the securing jenkins delivery pipeline session, led by oleg several will be in the cloud native session, led by cara and there's just one or two in the documentation session that I've got I'm going to open the rooms now, hoping that your experience with the breakout rooms will be positive and let's get those tracks scheduled so that you know when you'll be meeting rooms are opening.

A

All right so now you should be navigating away, except those of you that I did not assign to a room so andrew, uh roman and runesha. uh Is there a particular one that you uh chris, I thought I had assigned you one. Oh.

B

Oh you've been in the cloud natives.

A

Oh okay, so then let's you should be able to move on your own, but I can certainly move you to cloud native there. You go yeah.

I

And I'm trying to move myself.

H

I see now yeah I I know how to do it mark thanks.

A

Big big win: okay and russia. Is there a particular track that that is most of interest to you?

A

Oh you're, muted,.

D

Sorry I was on mute. I wanted to go to the securing jenkins delivery pipeline breakout. Oh.

A

Good, okay, so I'm gonna I'll do the assign for you, then, because sometimes the ui is complicated. It should prompt you. Would you like to join or some such.

A

Thing and fedex is there a particular session you would like to join, or would you rather, if you would be willing to act, sit here at the top level watching for people and possibly chatting to me? That would be great, because then I could join some of the other rooms and not have to be the top level.

A

C

D

Hi I'm leaving as well.

C

C

Okay, so yeah, I will uh do that for well, while I create the meetings etc.

C

If you have any questions or comments related to jenkins, just link them up, so we can have a user this time for whatever informal.

D

B

A

So so I see people back in the in the main, that's good! If you would like to join other sessions, what you do is join their breakout room and negotiate with them for their the time to attend their track. That track.

C

So one item: I started a google doc which can be used for notes for the tracks uh but yeah it was at hog, so I'm not sure whether they will be using it or not. But for our track. Everything today.

A

Excellent, thank you thanks very much, and what I was thinking is. I should probably get the scheduled track meeting times and send the announce an announcement to all of the registered participants of each track scheduled meeting time. So did the did cloud native decide on a time when everyone would meet together in the next two days.

C

I guess you need to ask cloud native.

A

I'm sorry I'm asking the right cloud. I did your track. I'm sorry.

C

No, no, no utc on thursday.

B

Okay, great all right.

C

Yeah, the junk is calendar already.

A

Perfect, oh, that's a good point. I will do the same thing. I should have thought of that excellent. Yes,.

B

A

So one of the others was we were having a conversation in in events and advocacy wondering how how we assure there the times that were working best for them looked like they were relatively late in the day um for you. So we may need to do two sessions for events and advocacy or accept that hey, we won't be able to have everybody who wants to attend every session. That's okay,.

D

D

B

So, oh like, if, if it would be okay.

A

uh I would any suggestions on how we might do uh gather people's insights, should I just send email to all of the people that registered saying hey share your retrospective on it. What could we do better? What what should we do differently if we ever do this.

C

Again, that kind of thing: well, if you do it again, it's better to start from introducing uh rules of engagement in the beginning, so that everybody knows the way to put notes et cetera before they split now what you can send a follow-up message, firstly, to track leaders, then, once you get all the information put it to the calendar and send another email with a summary to basically everyone who registered or just pointed them to the calendar, good, very good. Thank you right now, yeah! So, second, I will share the screen.

C

They see it yeah. So do yes yeah! This is my calendar.

C

So the easiest way you can just point people to this page, because here you can see that what we have planned by now is gcask office hours, I'm not sure whether they will happen or not, but they sell coffees hours. So they will happen ranked governance meeting. It will happen, securing jenkins pipeline and contributors.

C

So basically you can just point to people here and they can find this information perfect.

A

Good, I like that, and that's that's easy for me to do, and the docs track has already agreed on the two times that they want to meet. So I can put that into the end of the calendar. The the events and advocacy has agreed on a time as well good, excellent.

C

Okay, so what we will need, so we want the sessions to be recorded right.

A

uh Yes, prefer it if the facility they use doesn't record, but in in the case where we're using zoom. Yes, we should record.

C

Yeah, I'm not sure whether all uh leaders have access to jenkins zone.

A

I know that cara does. I know that you do, and I know that I do so. I think that covers- and I don't know on alyssa, but I intend to join the events in advocacy.

A

Oh good, okay, great so we've got, we've got what we need, then excellent. Okay,.

C

C

Where it's so slow.

F

And I'm sure that andrew as well or at least you can.

I

I'm sorry I've been only listening with happening or what was that.

A

He was just making a joke andrew that you, you probably also have access to the to the cdf zoom account as needed.

I

I'm sure I know the right people to be able to get said access, but I do not directly, in fact I'm I don't even have a paid account.

D

A

Yeah actually, oh, like you're, showing the right pattern. I need to go ahead. I'm going to go ahead and schedule the zoom meetings for the for the others, the other, the tracks that we've already got agreement on and get those published, get those ready to be published to the calendar.

C

Well, it's not a pattern, it's just while we're here and waiting for somebody to maybe join ask questions. Why not right yeah, okay and here it becomes difficult because it's 12 p.m. Right! No new.

C

D

C

D

D

C

Okay should be good.

C

Enough, so are there any other topics to discuss.

A

I am not aware of any so I've got the docs track, the europe and africa docs track.

A

Box track scheduled now invite there and I'll put it into the jenkins calendar shortly.

A

Okay, I'm gonna have to shorten it. 30 minutes.

B

A

And oleg in terms of of safety, is it okay for me to embed the the uh the the zoom link into the jenkins calendar? I assume it is, but I don't. I always have to check to be sure that.

C

Oh, that's totally safe, okay,.

B

So the general.

C

B

I

I wouldn't say it's totally safe. However. However, um it's hard not to do something where you embed the password honestly for an open source kind of thing.

I

If you expect people to just kind of join the issue you have you run into, is there's still the potential for zumba means because of it right.

A

C

There is some risk, but yeah. We are not uk cabinet of ministers and uh yeah until we don't post it on twitter and whatever commonly we are safe.

I

Commonly, I wouldn't say, we're totally safe um the lfn uh tack and was it the tag yeah, the technical advisory board uh committee for all of the lfn project actually had somebody zoom bomb them once, um and it was apparently really bad.

I

Like they joined and they just started, dropping all sorts of nasty, I wasn't on the call, but uh yeah they actually brought a psychologist to help people with that. One.

B

A

And and we'll we're trying to avoid that, with with within reason, yep.

B

I

No, I get it, but you got to do what you got to do.

A

Oleg can you can you see that I posted the docs track onto the.

A

It's right right before the the governance meeting in the jenkins calendar and then I've got another one to add, which is.

A

After oh, oh right, I have to show my own calendar to see when okay, good.

B

F

F

F

Did you mention that there were one session about chicago africa.

A

What was your question about? Chica africa.

F

I was just mooring if you said that there was a session about chicago africa or not.

A

So it will actually happen during the dox track of the contributor summit tomorrow, so so that one is, is yeah, definitely and we'll have we'll have zenob share we're going to have to do some planning around that because they need project ideas and I've got a few that I've started, but but we need more project ideas and we're also looking for corporate sponsors.

A

So if you know any corporations that would like to sponsor chico africa, the sponsorship is one thousand two thousand or three thousand. If I remember up to five thousand for their very sponsorship levels, I've already asked a certain company that employs me. So don't bother asking that company. I've already asked them.

A

All right west coast.

B

C

Okay sponsorship, so we have some uh money emerging discovers right now, not that much.

B

Okay, so that well and and so that.

A

I thought that the jenkins project's key contribution would be project ideas, but if we have funds is that something I should bring to the governance board? Oleg as a as a possible or.

C

Well, to be honest, I don't think that uh one open source organization was sponsoring another. One is.

B

A

See that's relatively unhealthy sponsorship should come from companies that makes sense yeah.

C

Well, it's technically doable, but in such case we can host the community breach of electric projects under our umbrella right.

A

Okay, so now I apologize, I have a hard stop in two minutes. I could assign someone else as the host if you would like to continue- or we just accept that this will end.

F

It's still funny as well.

A

All right thanks everyone. Thank you very, very much. I'm going to go ahead and close all the rooms. There will be grumbling and flinching about well yeah, I'm going to close all the rooms so that they come back.

D

C

B

A

Olivier. Thank you very much, andrew thanks for joining daniel as well. Thank you. Thank you.

B

A

A

Forgive the ending of the of the breakout rooms. I know you're in the middle of conversations. You really did not want to interrupt, but I have a meeting that stops in one starts in one minute that I have to leave for sorry.

K

Thank you very much mark and I will um see the cloud native group tomorrow.

A

All right thanks everybody thank you again for joining I'll, send out separate email to everyone that registered that I have email addresses for asking for your insights and suggestions of what we should do to make this better next time what things went. Well, what things went poorly, etc, we'll basically invite you to do an online retrospective.

A

Thank you thank you for participating and see you. Thank you.

J

A

Mark the next meeting is two days from now.