Jenkins Governance Meetings, 22 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Governance and Roadmap meeting, April 22, 2020

Description

On April 22 we had a first Jenkins Roadmap meeting. Oleg Nenashev presented the current state of the roadmap, and we discussed how to improve its representation for Jenkins users and potential contributors. Then we had a regular governance meeting, now in Zoom instead of usual #jenkins-meeting IRC. Topics: participating in Google Season of Docs, 2019 project summary report to SPI, logo usage approvals.

References:
* Agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.a2go1uljjpsp
* Public roadmap draft: https://jenkins.io/project/roadmap/
* Governance meeting: https://jenkins.io/project/governance-meeting/

A

Hello, welcome to our first online uh jenkins governance meeting uh today is april 2 2nd. Usually we do governance meetings using jenkins meeting rc chat, but today we have special agenda and we decided to try out using zoom and video calls for that.

A

Similarly, to how we organize jenkins special interest group meetings today we have several topics for the agenda, so let's discussion of jenkins roadmap as we agreed at the previous governance meeting, who would like to officially call it a first roadmap meeting and to discuss public roadmap for the junkies project, then we have a topic about the google season of docs application reports to software in public interest. It's our umbrella organization at the moment, and also request to use jenkins logo.

A

So these are all topics we have on the list and if you have something else, please don't hesitate thread it in at the bottom.

A

Okay, let's start from jenkins roadmap, I could do a quick introduction.

A

So, historically, jenkins project didn't have any specific roadmap or explicit plans how it would evolve. I firstly it's because of how jinx communities are organized with the community driven project, so basically the project evolves in the directions where you have contributors, but in the recent years we started self-organizing in the community, so we introduced special interest groups.

A

We introduced uh subprojects, and uh now we actually do a lot of current immediate effort in the project, even although it evolves in the same way and one of the usual requests from jenkins users, especially from big companies using jenkins and vendors who built products on the top of jenkins, was to have a kind of roadmap which would show where the community evolves, which areas we focus and where we facilitate contributions.

A

So I think that it's a good time to discuss that during the contributor summit in brussels, uh we had around 20 contributors there, and this topic was widely supported.

A

So I went ahead and drafted a jenkins enhancement proposal which would document that old map process, so it basically makes jenkins roadmap, firstly public, so everything is public, including the data, including process. Everyone is welcome to participate, everything happens through open channels and also it's community driven. So basically we do not force roadmap or, whatever is, let's say, jenkins, governance, board or governance meeting.

A

But instead of that, uh we delegate that uh two entities within the projects, including plugin maintenance teams, special interest groups, sub projects and actually, whatever other entities we have in within the community and the ecosystem. So this is the idea uh there is a lot of documentation here, after which we could go, and we also have a proof of concept which has been developed over the past weeks.

A

So one month ago we had a governance meeting and then we approved publishing roadmap as a draft state, and I can show you how it looks like so. We already start determining out to various entities and we collected a lot of feedback about items that they would like to focus.

A

So if you take a look at this list, you can see that there is a lot of items all over again some. I all these items are quite big and we try to put a big initiators on the table because we want to facilitate contributions.

A

uh We wanted this efforts to be major, but still there is a lot of them and likely we will get more once this roadmap is socialized because we haven't done any promotion yet except developer mailing list, and we know that not all plugin maintainers really follow developer managers, but still we have quite a good number of items so how this roadmap is organized at the moment again, everything is a subject to change and that's why we have this meeting and future meetings to collect feedback and to adjust so instead of grouping them just by entity.

A

Let's see platform special interest group or pipeline or rank you try to focu group it by use cases.

A

uh So, for example, uh before that we had a job management, but now there is pipeline authoring and development tools, so developing pipelines, engineering console tool and service integration, so then user in experience and interface, so not exactly new features, but also you know that user experience is really important and it's one of the top items when we collect feedback about jenkins and if we go down, we start hitting arrays, which are rather focusing uh jenkins administrators.

A

So we put end users first, then we have administrators. So here we have management and administration, including agencies, configurations code, including other changes like remoting our websockets. So this is for administrators, also a specific section for cloud platforms. It's mostly kubernetes cloud providers and other things yeah. We know that uh cloud native special interest group and jenkins is dormant.

A

I have a long standing uh action item to recover there, but still we have some items which we discussed before and which I put attentively on the roadmap, and hopefully we will have more details and for more classic platforms. We have platform c and thanks to all platforms contributors, we actually have a lot of items here.

A

So it's a java support windows, support a lot of roadmap items for official docker images for different platforms, because there is a high interest to run jenkins somewhere outside the linux, docker images and thanks a lot to all contributors, and then we also have documentation, though maybe we should move the documentation high because it focuses users uh yeah, let's discuss it later and after that we also have project internal stuff, so what it means first infrastructure. So infrastructure is a backbone of jenkins organization and a lot of changes are visible.

A

For example, recently we immigrated plug-in site to a static website. Then, just a few days ago, thanks to olivier, we also moved it to fast lead, cdn and now just loads immediately, which helps users, and there is a lot of other infrastructure items which are mission critical to the project, and we want to highlight them on the roadmap, then plug in developer tools, again important for jenkins developers, important for the future of our project and also community marketing outreach, including all programs.

A

We participate in like dual summer of code community bridge also, we drive aging terminology cleanup within this special interest group, so we have meetups recently with the name docker images, but there is a lot of such topics which is currently here, but maybe we should move it to up to documentation and last but not least, jenkins governance. So, for example, here the item for public roadmap.

A

So this how it looks from user perspective again, it may look that it's already packed, um and this is a topic to discuss, because we actually still have color dimension here, which we didn't use or currently colors uh basically represent the status, but instead of that, we could use them for additional grouping and we also could basically discuss any other topic about the layout. So everything is subject to change.

A

How is the backhand implemented? So originally, the roadmap was inspired by blue ocean roadmap, which was hosted on jacqueline's io website for a few years. Currently, it's removed. Blossom roadmap was implemented uh using json data files and javascript, which was loading with json files and showing them.

A

But after a few iterations, we actually switched to another approach, so this entire roadmap is basically implemented using more classic website technology, so it's mostly hummel- and this harmony here just gets data from my yaml file, like in the jenkins io repository. So basically we have open data. Everyone can access this file and download this for whatever their own processing needs and yeah. This file has full contribution history, so everything presented on the roadmap is basically supplied by this file.

A

Yeah, it's getting quite long call over there.

A

Okay, so this is what we have with the roadmap now again, any feedback is appreciated, and my plan for this roadmap is to actually get more items, more feedback and maybe within one month or so, we discuss publishing. It is a final version if everyone is happy with what we've got by that moment, but it's not an immediate thing. I do not expect us to approve it as a final mod today. That's for sure, and I don't think it's ready.

B

I think just add something on this roadmap. I think it's really great. Can you hear me? Yes, yeah awesome. um I think it's really great and it's really important for the project, but something that I would I would maybe try to advise is. um I think the different components should be updated by the different uh leaders. um So I think it's really important that, for example, there are some points for the infrastructure and yeah. This is something that we should all do like.

B

Be sure that it's always up to date, because I don't think it should be the rule of you or one single person to be sure that all the different components are it.

A

Yeah so regard speaking of that we have jab 14, which basically documents all the process, and there is also an item for road map items like maintenance, so for maintenance. Firstly, we expect the initiative side, meters and managers to actually keep the roadmap up to date. Again, if you want to update it, you just submit a pull request against this yaml file when it gets reviewed. We also go to all automation.

A

So when you submit a change, it automatically requests reviews from governance, board members and attacks accordingly, but basically this roadmap can be updated at any moment, but by any contributor, assuming it gets approvals and reviews. You also have a roadmap review meeting documented in the job, but it's a rather a regular scrap. Let's say I guess monthly under the document or maybe even less often, uh we should be using just for additional adjustments and maybe for defining future things, but not for runtime or status.

B

Updates, I don't. I don't know what you think about that, but maybe it would be interesting to specify the dates uh next to each uh category. So, for example, let's say the documentation. um If I mean if we know that the documentation category was updated over the last week, some months, um it can already give a good sign, uh and on the other side, if we see that, for example, the infrastructure was not updated for months. uh Maybe someone should either be the person or maybe take some ownership there, because um yeah.

A

So currently we can do that at the governance meeting. So just by doing scrap we can take a look and the activities of which items seem to be installed. Of course, there is a magic feature there like blame, not to blame somebody but uh to see when the things we updated.

A

So we can technically check it from the website.

A

Yeah, if needed, we could split it to separate files etc, but I thought that at least for initial implementation, it would be better to keep everything okay in a single place.

B

Yeah, I also think I'm also in favor to have everything in one fight.

C

So olivia your your desire there was to see which which items in the roadmap might not have had recent activity, but isn't isn't the measure of activity really not so much an entry in this file as it is project activity somewhere else? That's behind this thing. This is if, if, for instance, we don't update a particular row record in this file, I'm not sure we've gained as much, but if we fail to make progress on some something that we thought was on the road map with its back end efforts.

C

That seems like a more interesting piece of data. I'm not is, or is that, have I misunderstood your idea.

B

My my id is not not more like um we yeah it's more like um if you are a contributor. If you want to understand, if something is working, we need a way to know um um if some help is needed in that specific area, and so, for example, if you see that there are, I mean, for example, a specific category is not updated anymore.

B

Maybe it seems that the person who was working on that was maybe working on something else, so maybe delay whatever, and maybe it would be interesting not not to blame that person, but just to say hey can I help you and see how we can move this this category forward, and maybe that's yeah, it's more like it's. It's not really in the idea of blaming on someone but more um to see if someone can help and how to identify um that.

A

It's open source, there is no blame, life happens. What happens? Yeah covet 19 also happens like we know now. uh So yes have to predict anyone anything. I hear.

A

Firstly, many roadmap items actually tied to subprojects or seeks so, for example, here if we talk about infrastructure, there is a weekly infrastructure meeting and it would be great if infrastructure team, just uh some time, let's say every month, to take a look at the roadmap and do stuff on their own, so that we don't need governance meeting for that. Obviously it becomes a bit more complicated when it comes, let's say to features, because what is the weakness of the current roadmap?

A

It's quite shallow in terms of features being delivered by two users, because we have a lot of infrastructure thing. Packaging thing, but features are being developed in plugins features are less coordinated at the moment, especially user facing ones. So once we facilitated the cross, plugin eca system ask contributors to do something related to plugins. So, for example, I put promotion support for pipeline jobs.

A

If you're familiar with this story, it has been around for three years. It's not only in future. Right now it's also in my personal hall of shame uh so but yeah there might be such items, but we are still interested to collect them. uh We are especially interested to collect ones which are in current and near-term, because these ones what uh what is moving the project now, so we understand the concern, but I think that current job can address it. Okay,.

A

So any other feedback comments.

A

But now I have a few questions to you: should I put them in the doc, so first question to you is: do you think that the current categorization is fine or do we need to rework it somehow.

D

I think it's fine at this stage, since it's something that's just kind of getting started, it might need to be updated in the future, but I think it's good for now.

E

Me too, I second, that is our third thought as well.

A

Okay, thank you so yeah. We might more uh add a bit more uh content here. So today I sent a message to the gsoc public mailing list about the gsoc project ids, because apparently the most of our project ideas we have on the table here, uh do qualifiers potential remote items and the current stated that we have some project ideas on the map, but not all of them. So maybe I'll just do another bulk update and there is a lot of features there which we could highlight.

A

But let's see I still. If you have something in mind, if you work on a particular plugin or an area which is not listed, please let us know just comment in the developer mailing list or submit a pull request. So we can edit and second question to you is about uh relations, because current file basically has one category and all initiatives are grouped by this category, but we already hit cases where this approach isn't the best one.

A

So, for example, there is pipeline authoring and they have pipeline documentation in the roadmap for the future, but at the same time I should go to the documentation pretty much. The same for kubernetes documentation because it should go to cloud native seek problem.

A

So my question is whether we would like to support multiple categories or whether we would like to keep things simple.

E

I personally would like to see just keep it simple, at least for the first, this first iteration, I think more. What I would want to see is this get out to the public faster, and I think the way it is now is really good. We can.

E

C

And so I'm I'm more the other direction that I would like multiple categories, but I'm prone to agree with marky that I'm not sure there's enough benefit to delay making this available in favor of adding this support for multiple categories. This is already intensely valuable in focusing my efforts, helping me to think more clearly, so multi-category won't won't dramatically improve that.

A

Okay, so in the worst keys, we'll just uh make a break uh change in the yamaha file, I mean yeah. I didn't expect anyone to really consume this file anytime soon,.

A

Key things, another thing is about coloring, so firstly thanks a lot to spinning kaneshney who actually helped me to fix coloring there, because original uh things were terrible and actually it also has cool mobile. You know so it's one of the only uh on our pages, which look good on the mobile now on the website.

A

We need to have more, but the question about coloring again: does anyone want to try something else with categorization so, for example, special color for documentation, special color for features so breathing, because this coloring looks uh great, but basically it's inherited from blue ocean and it doesn't create anything on its own.

A

No additional value.

B

Would it be nice, would it be nice to specified the sig or is it a system, because it's the right now, the different category I mean I'm just an id, but maybe it would be nice to have to know which seek is working on that specific component. So we know which meeting to attend.

A

Yeah, so right now it might be a bit tricky because it really depends on which item you click some groups. They have explicit links. uh Well, uh you can see that there is a description. There are descriptions. There are links for all items again we are still cleaning it up, because the original version was just a brain down. Then, after all the discussions, we added more and more links, but theoretically many items already reference, something where you can get contacts.

A

Also. There is metadata like this one, which is currently not represented on the layout, but it's in my to-do list, so there will be some links to this channel. So when you go here, let's say your user experience. You will see a additional pop-up here which will link you to the channels etc and for items yeah again. It really depends. For example, here you will go to jira um for some items, let's say like the documentation or platform c to be created, uh landing pages right on the sick pages.

A

So, for example, here, if you go to let's say cloud native java support here, you went on the platform seek page and on the platforms page here you can find the contacts yeah. This experience is also not that good and some items just reference jabs.

A

So here, for example, if you click you'll, go to the jenkins enhancement proposal and all our our format for jenkins enhancement proposals presumes that there is discussions to metadata but yeah again, your mileage may vary depending on the item. You click.

A

So if you want to have unified experience for that, I totally support that and I open the suggestions.

C

So, just to be sure, I'm understanding. So the idea there is I'm, I I'm a new arrival contributor and I would like to help with modernized, mirror, mirror infrastructure or with user guide improvements, and so the idea that olivier was proposing was some way of when I click on that thing of my interest that it takes me to a way to reach out to others which, which I think go like you were saying. The chat channels was is an example of how to reach others about that topic.

B

Yeah, basically, that was what I was suggesting, so I I mean an easy way, because the jenkins community is quite big.

B

You have a lot of different initiatives and- and it's not always it- it's not always easy to know if you are supposed to go on guitar if you're supposed to know an rc and on whatever, and so I was just suggesting that if you want to participate, I just click here and then you have all the information um you have to know how you can help, basically how we can have more information about that specific components.

A

Yeah one thing we could do actually to support drop down for companies, so, for example, you get something to the left. You click on that and you get a list of potential items like contacts project description.

A

Whatever else we add, and we can actually traverse these links, so you don't have to put everything uh to the uh yaml file, for example, how we do it for json project ideas uh just to show an example because for project ids again we hit the same problem. Each project idea right on the project has its own communication channels uh and some communication channels are in guitar some mercy. Some slack.

A

And here, if you take a look, there are links. So, for example, here you can see that uh there is mailing list which points to platform sheet. There is chat which points to guitar for git plugin, and there is meetings which links to gsoc so how it's handled. Actually there is some metadata injected in the project idea and we just uh traverse this metadata. We support inheritance.

A

So, for example, here you can see the digital is defined here explicitly, but the rest of the channels they actually come from platform signification and regarding meetings, I guess there is a boxing wire because it should point at the platforms meetings.

A

But yeah so theoretically I could implement something like that. So we support seek or project reference and then a website builder just restores all the.

A

Links bonus points for newbie friendly issues, but yeah. It's maybe a big ask.

A

Okay, so if it helps I'll try to implement it,.

B

Yeah I mean, if you have some time for that yeah I think, would be useful.

A

I definitely have some time to finish world map this year. For me, it's one of the most important items.

E

A

So anything else about the.

F

Roadmap uh alec: uh this is my first meeting and so I'm just trying to clarify some some issues about this, not issues but questions about this roadmap. uh There is current released categories and my understanding right now that if there is no background in the current, it is not a button and if there is like green in release, for instance, if there is green background, it is a button which is clickable, I understand. Is it correct.

A

No, it's not correct, actually, all of that uh uh buttons well not actually buttons. It's just uh whatever gives combination with a lot of css around that, but yeah you can see that there are some metadata so, for example, pop-up description again it comes from the yaml file. The results are hyperlink, but the behavior really depends on which data is supplied through yaml, so coloring is just status, so release the green in progress, a yellow, et cetera, et cetera, but it's just status coloring. It doesn't represent any content in the moment.

C

Thank you so vlad did that address your question.

F

uh Yes, I was a little bit uh confused about released and current uh categories because I thought that uh well released. It means it's current, but I guess it is like uh all these categories define, I guess, the progress, how we're moving from left to right.

B

Yeah but yeah, but release mean it's done done where so, it's more like you read from right to left.

A

Yeah, so status is also documented in a yaml file, and in so we are basically releasing that initiative is completed. There might be still some follow-up items to be completed, but largely it's delivered, for example, plug-in site, it's largely delivered, but yeah. We know that there are things to be improved, uh even major things like cdn, but in principle this feature was available to users and it was really worked well and the same for others, but yeah these statuses again. They suggested jenkins enhancement proposal so formally at the current state.

A

They are not slated in stone and if anyone wants to change them, please do that.

A

You can just suggest a change in the job or you can submit a pull request against the jab with your suggest changes and we can adjust. So everything right now can be changed.

A

That's why we keep this job as a in the draft state and yeah thanks a lot to alex earl, because he is now officially a bdfl delegate in this job, so alex will be doing final approval for.

F

D

A

Okay, so yeah, basically this summary of status. We are using horizons again, because common feedback about roadmaps is whether you commit uh on delivery dates now in the community. We don't commit and deliver these, and we don't really commit on delivery at all, uh because that's how open source projects work, but instead of that, we set up some horizons, which are also a big blogger.

A

C

I still, I still remind people that maps of roads do not generally have dates on them. They just don't.

A

uh It's a subject for long holy words.

A

Especially for particular people, but yeah whatever, okay, any other questions comments, or should we move.

A

On sounds good: okay, thanks all for your feedback and again anything you have in mind. Please uh comment in the mailing list so that we can incorporate these suggestions and uh I noted the action items thanks a lot for your feedback, olivia.

A

Okay, so we have something like 20 minutes left, but a lot of topics should be more simple, so google season of docs mark. Would you like to summarize it or.

C

Do that I would yeah so google season of docs is a project sponsored by google, where they encourage professional technical writers experienced skilled technical writers, who may not have any experience in an open source community to assist the open source community by becoming contributors to open source projects this year. Their plan is that they will host 50 slots for technical writers to assist open source projects in designated selected themes and projects for those open source organizations.

C

Examples well the jenkins project or the freebsd foundation, or others like it, have specific conceptual things that they would like to have a multi-month effort with a skilled, professional working on their project. Now these professional technical writers may not have experience with git or with open source workflows, and so there's growth for the the writer and growth for the the open source project did that? Did that give a good enough description there? Oleg? Are there things that you would like to add?

C

Yeah, definitely.

A

So thanks a lot uh one thing to mention that google season of dogs is generally a long trying program being compared to g-shock, because yeah fork, it means g-shock, never ends, but uh for students for mentors it's several months uh in the case of g-sort, it's uh much longer time frame. So there are long running projects which are up to nine months. There are short projects, but again the full cycle day is more than six months, and actually it's quite good for the community, because well in jenkins project we definitely would benefit from better documentation.

A

We facilitated a lot of contributors to documentation over past years, thanks to and past months, thanks to plugin documentation, migration project jenkins, iowa enhancement.

A

So what I reported in 2019 report, we had more than almost 200 contributors to documentation, but still we could use a lot of educated effort and for us it's a good opportunity and yeah I'm just stretching page. You can see that there is a lot of different open source organizations participating and they have a lot of success stories for json.

A

So personally, I think that it would be great to participate, but we have a problem because we need orca means we need mentors to run a project. But again, as mark said, there are only 50 ones. So it means that we need one mentorship, mentoring, team. We probably need one or academy, so it's not like jsoc, where we scale and we invite dozens of contributors to participate, but still they need some commitments to get this project running.

A

And this is why I put it on the roadmap because sorry on the governance meeting, because there is a thread, but in this thread right now we don't have consensus, we don't have orcadmin.

A

There are people who are interested to be mentors potentially, but there are some potential project ideas and we need to decide whether we want to push this effort or not, and we need to decide timely because the deadline is may 4th.

C

Right and we will we will discuss further in the docsig meeting this friday, but but you're right, I don't feel like I've personally got the capacity to act as an org admin, I'm open to be persuaded otherwise, but with google summer of code and other activities, I'm feeling pretty.

A

Feels loaded similar to me, I am ready to dedicate some time in order to create a landing page. So, for example, what we have in jsoc project via jsoc, so we have um basically a json documentation site our sub site within uh genki scion, where we have our own guidelines, our own lending information fermenters for students. Also, we have a listing of project ids which are presented.

A

uh I can create lightweight version of that for google, seasonal docs under the umbrella of dogs seek, but regarding maintaining the program, I'm not ready to do it alone. So if there is somebody who is willing to participate as a work admin and who would be interested to mentor particular documentation, projects, for example, becoming a junkies and kubernetes or just a work of solution pages, like we discussed a couple of days ago that our solution pages are really bad, we could improve them a lot, but we need people working on that.

A

So if there is somebody who is interested uh to work on these projects and who likely- who is also a native speaker, or at least a much better english speaker than me, because all gist of documentation should be in english- it's a strong decision by jesus. But it's only about english. It's not a legalization!

A

So if there are contributors for interest to consider that I'm ready to help this get into the framework on the website.

F

I would be interested to participate, but I am not a native speaker.

A

So question to you a lot: would you be interested to participate as a mentor or as a participant, because.

F

I I would say uh for the beginning: I would be interested to participate as a participant, because I'm not sure what are responsibilities of the matter and yeah.

C

Which is already already.

A

Quite encouraging, because so the correct terminology for json right.

C

Okay, yeah, I think that's correct yep.

A

So yeah for me, it's a past time.

A

Your audio isn't that good.

C

Your audio is still breaking up sladen.

C

A

Yes, sladen was interested to participate.

A

So anyone else.

C

So I could, I could spend oh, like I think, part time as a mentor. The challenge is, I don't think I can be a an org admin. I just I don't have the capacity for that.

C

For instance, I'm I'm reviewing vlad's recent contribution and I'm delighted it's really it's marvelous, it's wonderful! What he's done uh that? That kind of role works great for me, org admin feels more than I can take on. Okay,.

A

Yeah I'll see what the facilitate another part-time work admin, because I guess we still need two 4g sort.

A

And if I find someone we could kick it off.

B

But what's the current deadline for this.

C

May 4 so we've got about two weeks: okay,.

A

But it's two weeks to get the application uh submitted to or have a website in place. So last year we applied, but basically we applied with google doc link and this yeah since json accepts only 50 projects, and last year there were more than 200 applications. Obviously doc. We are not accepted so yeah this yeah. We definitely need something better.

A

If we even want to try.

G

Yeah is the audio better. Now, yes much great, I switched on to my mobile, so yeah. So as I was saying, I would be interested to participate as a participant, but if the team doesn't have any, I mean if it's difficult, for uh I mean as an organization to uh get mentors, I would be interested in participating as a mentor as well. So I don't know I mean it's, uh it's a bit of a confusion, um but.

C

G

I would be willing to contribute in any in any way I mean if there are enough mentors, I could participate, but if there aren't enough mentos and um I would love to participate as a mentor.

A

Yeah thanks uh a lot for suggestion. One thing we need we need to clarify is about potential conflicts with jsoc, because yeah you should apply to jsoc as a student, so there is a lot of hidden stones uh there uh and yeah suggest uh we discussed it uh after may, 4th.

G

Yeah no, no, no issues but till then I would still love to help you on the landing page. Okay, let me know if you need help. Yeah cheers guys.

A

Okay, thank you.

A

Okay, so yeah uh take a look but.

E

A

Like you can put me down.

E

For you can put me down for a part-time uh or gadman.

A

E

I can I can help you with that.

A

Okay, then, we actually have a team so yeah. If everyone is fine, I'm willing to give it a try.

C

Yeah, so the just to be sure that the scoping is clear in this one: it's we accept that at most we would take on one mentee.

C

uh We wouldn't want more than that, and we would frame that around a project to improve the documentation in some valuable way.

A

And that's why we have jenkins roadmap, because we already have prioritized projects in different areas which are related to documentation and we use you can use these outreach programs to facilitate these projects pretty much like we do with gsoc project ideas, though there was no roadmap at that point, but all project ideas we had they're really available to the community and to the junkies future.

A

So we can actually convert some of these documentation projects et cetera to project ideas.

C

That's it in terms of roadmap, then, for instance, there are some topics that I think are are smaller, for instance, than jenkins on kubernetes on this picture is, for me a massive but highly valuable, likewise administrator guide, but but I think there could be smaller things, the solution, page rework which it would be okay for that to be on the roadmap. Oleg, are you envisioning that that would be roadmap world map worthy, or is that too.

A

Small for you to envision that, because if we talk about solution pages, I believe that it's not really that small effort. So right now you have uh yeah. So there is solutions page. It looks awesome again thanks to zbinx, because there was a pull request couple of days ago. But if you click inside.

C

Right, there's almost no content and it's varying quality. Yes,.

A

Yeah, so I think we need to rework everything. We also need to put more solution pages because yeah, there are some items, but these items uh strangely, because the other technology ones which are really important to have but also use case ones like, for example, continuous delivery. But the results only continue there. What we do with that, how we group that, maybe how we add additional tools, because we have the bucket server thanks to contributors, they added that you could have the same for github, for example, or we could have the same.

A

Let's say for static analysis tools for security scanning tools and so on. So this effort may become a topic for multiple jsons.

C

Great okay, so it is a good fit. Thank you. Yep.

A

So, if you want to add it to the roadmap, just do that. Okay, I think it would be available.

A

Okay, so the next topic, which is quite small, is about uh another report to spi so just to share some context. uh There was a request from sbi to share several.

A

Paragraphs of what jenkins did in the previous years, we have already created the draft and submitted it for a year. So my question to governance, board members and all other contributors is whether you're fine with the current wording.

A

Basically, it's a short summary of what we have in the new year, blog post, which we published, so it just tries to condense it to a smaller format.

A

If everyone is fine, I would just ship it to spie so that they can include that in their annual report.

A

Yes, good good.

C

For me, I, like it.

D

Yeah plus one for.

F

Me it's very impressive.

A

Okay, so uh yeah. If anybody has some uh blank white, I will wait till tomorrow. Let's say morning: u.s time zone.

A

And if not, I will, if there is no feedback, I will submit the current version.

B

Morning, u.s time zone boat, which which side of the us 2 pm.

A

A

uh Yes and actually submitted by home, so you can just say jenkins, project jenkins contributors, whatever usually so. There is an example of a sphere report where they put usually names, but they would rather prefer to keep a project entity instead, but yeah as others prefer. I can do whatever.

C

For me, the jenkins governance board would be a great a great choice, but if you would prefer individual, your name is also honorable. You, you created the vast majority of that content, so that'd be great.

D

A

So jenkins, boss, tommy or something else like advocacy and outreach.

D

I think you should say your name and then put your title as part of the jenkins board.

A

Yeah, almost in favor of.

A

That doesn't have no preference.

D

Good yep looks good.

A

Okay, thank you so yeah, again, 2 pm uh last minute feedback and then I will ship it.

A

Okay and the image usage request. So we have five minutes left right because zoom icons uh close the time the clock on my windows panel. So that's.

C

A

It takes so long, sorry, okay, so there is a request from chrisor. um Actually he forwarded the request from somebody else, because chris is a press contact, so he received an email and he forwarded that and they want to actually request permission to use jenkins logo in whatever configuration panel so usually, which we don't care too much.

A

So what we have? Okay, it's a broken hyperlink. So we have a bunch of logos. Actually we have more than that, but and we still encourage contributors to submit the, but it takes a while. But what is the interesting part about that that all loggers listed here they actually listed their under creative commons license 3.0.

A

So technically, all these slogans can be freely reused, modified, etc. But there is a caveat there, because all these slogans should have a.

A

Reference should include attribution to the jenkins project. I am according to the license, but historically we didn't care about that at all and, to be honest, I don't see a particular reason to care, especially for junkies logo, which is pretty recognizable without any additional attributions.

A

D

A

I'm a plus one.

D

Yeah, I think we should just approve it. I mean it says here that it can be used under creative commons, so yeah as long as they follow the license. I think it's fine.

C

Yeah plus one from me, that's this one as well and not.

B

C

One I thought that the answer there was, I like the answer from daniel beck. That said that, as far as he could my interpretation of his answer was they can use it without even asking for immersion. This is not a trademark usage which which really requires formal governance. Approval right. This is something different than using the trademark.

A

A

I think we just approve that just in case but yeah. I think.

A

Whatever, okay and other topics, so two minutes.

E

I have to I have to drop. I have a hard stop for another meeting.

A

Okay, yeah thanks for participation, marquee yeah uh other next meeting. I guess it will happen in two weeks as usual,.

D

I had one quick thing, oh like, if that's all right, so I just wanted to uh kudos to the release team uh having released the first, get it on the public, recording uh the the first release into the new release environment. So a couple of them actually, so that was that was pretty awesome. Just wanna give kudos to those guys they did awesome.

B

And I can't wait for the next one.

A

Actually, it's a good thing to do so at the seek meetings and project meetings. We start from news section, so maybe we should try to start doing the uh it also the governor's meetings so just to highlight such major achievements.

A

Okay, but yeah really congrats uh to all involved and especially to olivier because see it was uh something like two years effort. uh It required a lot of different changes across the project and it's great.

B

I think that ticket is even older. I mean the epic. uh I think I should just close the ep for now once the weekly for the automatically did yeah, but um I think they typically are it's very old yep.

A

Yeah, I guess when I joined the project in 2012, it was already actively discussed at that time. I'm not sure whether we had a ticket but yeah anyway.

A

uh So how do we do the next meeting, like that in zoom or like before, in irc.

D

uh Zoom works pretty well. I think um I think irc works pretty well too, so I guess it's. Maybe if there are specific topics that we um would do well with an actual voice or video communication, maybe we go towards zoom. If there are things that are just like uh needing approvals, maybe that's an irc meeting.

D

I don't know I'm good either way.

C

Yeah for me this this meeting this this meeting in rsc would have been a complete disaster. Zoom for these topics was crucial. um I I'd like alex's idea. If agenda motivates it, we should use zoom I'd, also be fine if we use zoom all the time, I have no problem with zoom. I like this. The interaction.

B

Person personally personally, I like to have this kind of meeting versus having those in rc, because I find those I mean, I find this kind of meeting. um I mean I'm less distracted, at least so it's easier to just stay focused on the meeting and be sure that okay, I will just follow what the discussion where on hours, it's easy to work on something else. So but yeah, that's a personal opinion.

A

Okay, so my proposal, we wait for gender items, so everyone is welcome to submit agenda items and maybe several days before the meeting we decide whether we do zomo or c and uh yeah we've.

G

A

A new zoom account, so we will be working on granting permissions uh to board members, sick leaders etc, so they can host zoom meetings on their own like they used to do with hangouts on air a couple of years ago, so we will restart this experience for everyone.

A

Okay, okay, thanks all uh thanks a lot for your time, thanks for coming thanks, everyone.

G

A

F

F