 So, welcome everyone to the Documentation Special Interest Group. Our agenda for today looks like this. See, Oleg, can you see my screen all right? Yeah, it works. It works. That's a great answer. I like that. Okay. Thanks. All right. Topics on our agenda for today include a review of previous action items, a Google summer of docs, retrospective action proposals was proposed, any community bridge was proposed as a topic, then I'd like to do a demo of the latest Jenkins.io improvements from Spinnock, Connexionary. A bunch of really cool changes that have been made. We've got docs, SIG infrastructure status report, the plug-in site, and then latest data on contributors to the site. Those are the topics that I wanted to be sure we covered. Are there other topics that need to be added to the agenda? No, I think it's fine. Okay. Yeah, maybe one, some bits about my topics. So regarding community bridge project status, actually I've performed status update one week ago, two weeks ago, the advocacy about RISC, and yeah, I've been waiting for recording to be published. So maybe it makes sense to review it together with stakeholders once the video is published because, yeah, otherwise I could do the same demo again if you want. So I think that's a good one. We should just, how about we give me an action item to link to the SIG, to that SIGs recording when it's available. Yeah, basically I can show it, just a second, I'm checking my login, yeah, I think I can download it. Okay. All right. That's great. If you'd be willing, that's wonderful. Let's take that then, we'll just capture that. Okay, I'll just show some bits. Okay. Yeah. All right, so then, great, all right. So let's go ahead then, on the action items, I've still got the action item open to submit the docs project ideas as a pull request. That's just a gathering exercise for me. I will get it done. Well, like on the Google Summer of Doc retrospective action proposals, I had not captured any notes, major notes, I think we intentionally deferred. If you wanted to defer again, how would you like to handle that one? Yeah, good question. So I think that I also need to go through the history, because I basically forgot what we agreed on. One of the action items is actually community, which we should be looking at below anyway. And other action items were really about having established software green teams and starting to do it in advance for something like that. Great. So let's add action item for me. I'll do it on my own, if you want. Sorry, I just forgot that the document is also open for me. Got it. Well, I did it. I need to practice adding action items. So thanks for letting me do that. That's great. Yeah. No worries. Oh, you just need to know all the personal emails of people. Right. Exactly. Okay. So then on to the community bridge topic. Yeah. So community bridge, I can probably just screen shape it and show what we have. Because... Let's see. And that means I need to stop sharing. There we go. You have... You should be able to share now. Yeah, I should be able. Okay. Do you see my screen? I do. Okay. So yeah, community bridge portal, what was going on and redirected me to a strange page. Yeah, community bridge is a portal deployed by Linux Foundation in order to help connecting various participants of open source projects, in particular people who are interested in mentorship, people who are interested to contribute, who are looking for mentors, and also company and individual sponsors who want to facilitate some projects. So basically it's a combination of project hosting portal and crowdfunding site. And yeah, this site has been started several months ago. It's still underactive with development. There is a number of projects which are already listed there. So you can see them here. But yeah, the most of the projects look pretty similar. So there are some projects which propose proposal or just propose to connect to the organization if you want to do something. And then yeah, the way for people to join Mentes and his, for example, information about the mentee funding. So here we can see that, for example, Hyperledger for this project, they have found funding for one mentor for one mentee, and they're looking for more and pretty much like a bed. So yeah, you may see that there are two different implementations. So one, for example, Hyperledger, they have one project hosting for the project. So for example, here, configuration for project management and construction or something like that. So it's one approach which is being used on the site. Another approach is just to have one project for the communities, which means that whoever joins, they're welcome to join. And yeah, right now there is no information for mentors, so there is no information for mentees. So yeah, this is the kind of stuff, but having this stuff is also important. And we have actually the same stuff for Jenkins somewhere, my projects, so it's listed on the list. So yeah, if you have Jenkins project, I just spent some time in order to create a stop. So here, again, you can see that we have no mentors list, I'm not sure why, because I'm listed as mentor, there is no mentors found, I'm not sure why, because if you follow the ether chart, one of our contributors actually applied as a mentee. But yeah, basically, this is what we have, so just a portal which offers, okay, if you want to contribute to Jenkins, feel free to reach out to us and we will see what we can do. What I was about proposing is to consider splitting multiple projects, for example, Jenkins documentation or so, so for example, yes, since we don't participate in Google season of dogs, we could have a dedicated project target, which targets Jenkins documentation. Another, yeah, or we could just make it more specific in the project. So yeah, for example, here, here it's now Jenkins or so, and yeah, so that's it. Yeah, setting up a program is pretty long, but if needed, we can do so. Or we can just, for example, attract more mentors here. For example, you mark, if you consider to be a mentor in some conditions, I can just invite you to this site. And so on, we can just review options and maybe kick off some kind of the program in the future. Great, so yes, I would like to be a mentor. And so mark.eroll.weight.gmail.com. Okay, something like that, I guess. So yeah, I'm just stating here as a mentor. And then theoretically, you will get an invitation to this portal. And yeah, so that's it. So regarding requirements, actually, I just set common requirements. So you may require a person to reach out to us to have conversation and to send us a kind of introductory letter, but that's it. So we don't have academic restrictions due to obvious reasons. And yep, that's it. Nice, okay. Yeah, so the tricky point about that is that I wasn't able to find any example of a working program on Community Bridge. So the site is under development, some students seem to work, but well, for example, for Google over the season of talks and for documentation special interest group, we could probably try putting several projects here. Or one of the projects is, for example, Jenkins. We can do Jenkins documentation. We can do Jenkins sex documentation if somebody wants to. And then we will have a set of projects. I wish we can later advertise, for example, by community channels or whatever. And now you indicated that there have been some surprises because it's currently the application itself, Community Bridge is actively being developed. Yeah, I'm not sure how actively, but there are just many gaps. Yeah, for example, we have application here. Oh good, okay. And that was one that was just recently discussed in Kitter. Okay. So that's why I don't think it's private because the application is here. I won't go inside, but yeah. So there is some application. There is a kind of cover letter here. So, for example, here we can probably do something in order to, yeah, for example, pending because. Right, okay. Something like that. And yeah, we will be working on the slide in order to get everything in place. And yeah, we can have more applications like that. Thank you. Thanks very much. All right, it looks very promising. Yeah, so I'm not sure how far this Community Bridge is going to go, but yeah, I think with the platform there, it's managed by Linux Foundation. And I believe it means that they mean business. So yeah, I think that we could try using this platform. Obviously, we have open issues, for example, about funding. Because yeah, you may see that there are current funding features there. But for us, these features are not accessible at the moment because in order to, yep, so yeah, there is some funding. So in order to get Jenkins here and to get this funding, we need to be a part of the core infrastructure project. Just a second. So core infrastructure. Yeah, core infrastructure initiative. So it's another program by Linux Foundation. Basically, it's an aggregation of various companies which try to push towards the system for core projects, including core open source projects. For example, there is a base program, which is designed specifically for open source communities in order to match criteria of core infrastructure and get the project listed on the list. So for example, there are some requirements, which we have already reviewed in this Jenkins security team. So it's not exactly trivial to get Jenkins in this project, but you may see that there is quite a list here. Right. Particularly having Jenkins as a part of core infrastructure project. Firstly, it's a pretty good quality metric. It's a pretty good thing for promotion for us. So yeah, I think it would be interesting if the project is ready to invest in. So this would be an extra level effort, and it would be project-wide across the large portion, or bigger portions of the Jenkins project you said security would have. Does this also have some requirements on infrastructure that we've got to do some safeguards against our current infra or? No, it's mostly about security processes. Okay. Yeah, there are some more stories in the list. I don't remember if you remember of security team, you may believe, or maybe not. I am not. I don't think I am anyway. Yeah, but yeah, basically there are some requirements there, which require strict review because Jenkins security processes are dependent in a different way. So for example, there are some expectations for disclosure time, and other things, which is fine, but we need to ensure that we comply with this process. So for us, funding is not available at the moment, and we would need to work on that in order to get that. And yeah, for example, one of our advantages is that currently the Jenkins Foundation offers diversity program, and other things, and they actually double funding for particular areas, etc. Okay, so yeah, that's what we have, but yeah, basically we need mentors, and we need people who would be interested in the area. Great, thank you. So enlisting mentors is something that shouldn't be too hard to do, inviting people. Excellent, thank you. Okay, so anything else? Any questions? Nothing, no other question for me. It looks very promising. Mm-hmm. Thanks again for that. So Oleg, you had mentioned that you might not be able to remain for the call. Thanks for that coverage on Community Bridge. So yeah, I can hang around, but yeah, there will be... So yeah, if you want to present these demos, I'm happy to listen. Okay, yeah, that was my next stop, because I wanted to highlight some really impressive work from Sprint Connectioning that he's done for the Jenkins.io site in the time period since the creation of the Dock SIG. It's... he's done really some quite nice infrastructure improvements. So for instance, social media pages, social media now includes images from the pages like this one, and here you go, this Jenkins need you came just because I shared a page on the... on... from the Jenkins.io site, thanks to his integration of OpenGraph and images. So if someone shares, if someone creates a new blog post, they can provide their own image that heightens the engagement of people in the social media community. And this particular one, let me highlight a specific feature of that particular blog post or that particular idol. So for me that was a... that's a very nice addition. Then he's also done some nice fixes in terms of the layout on the pages when we embed videos. It used to be that this Jenkins and Android page had a very poor layout for where the video clips were placed, fixed, looks much better now. In addition to that, he's had author pages. So if we want to see... let's take Oleg. We're going to look at everything Oleg has written, and here's his author page on the Jenkins.io site now, automatically generated, automatically maintained, shows all of the blog posts that were posted by him over time, and includes his biographical information. Same thing exists for Roman Rodriguez-Gill, for instance, and his... his contributions, recent contributions. So the author page has been a nice addition that Schbenek made to it. Those same author pages are also linked into our special interest group pages. So the DocsIG, for instance, lists a number of participants and members, and here if we look... oh, let's see. Rick is a participant, and if I click that link, it takes me to his author page. So... Rick highlights one problem, well, not a problem, because Rick has had Chinese symbols in his metadata. So before that, we had no problem, because we were showing GitHub ID by default. But when the change was applied, now we see his Chinese name and Chinese symbols. Personally, I have no problem with that because... But, yeah, there was some difference in behavior, and we've seen it for multiple people. Ah, okay, now is that something that needs a fix then, or is the new state acceptable? I think the new state is acceptable, and then we can polish it if needed. Great, excellent. Thank you, thanks for the insight. So the author pages, and then there have been accessibility improvements for people who are using screen navigation that may be visually impaired, for instance. So, for instance, on this page, tabbing now has behaviors that you might expect as you navigate through, hey, I can tab here, I can tab up and down, open a page by hitting Enter, tab in that page, I can cause that tab to move down. And so accessibility has been improved by virtue of tab navigation being better. Now, there's, again, still a work to be done in those areas. Always, we'll find new surprises. He also fixed the Blue Ocean page. It had a completely different styling than the other pages on the site, and so it was missing this block at the bottom that is standard on every other page we had that's now fixed. And the special interest group mailing lists are now automatically generated and placed onto the mailing list page. So this mailing list page lists the Jenkins user page, it lists jam pages, other discussion lists, and now at the bottom, the special interest group mailing list generated directly from the list of special interest groups that are maintained on the Jenkins.io site itself. So really nice additions from Spinnock, so grateful for what he's done for us. Any questions on that topic? No, thank you. Okay. Yeah, thanks for summarizing that, because I think it's something we should make regular and maybe even start doing some change logs and announcements for the Jenkins website. So similarly to what we are doing for this drafter, maybe we could apply some interest ratio components. So then, for example, once a month or so, we could just post a virtual release and highlight all contributions and maybe even talk about it in social media. Right, and I think those are all motivational things that help inspire people, hey, it's worth helping and show just how much progress we're making. I assume that one of the next upcoming places where we're going to see progress is on the plug-in site. Because we have a pending pull request that improves the plug-in site and lots of interesting discussions on the Gitter channel, or no, on the dev list, actually, about things that we can do to make the plug-in site better. So there is an improvement doc here where we're trying to capture some ideas and we've already got our first pull request that's proposing to improve the reliability of the scripts that generate the plug-in site. And what Spinnak noted was that he's decreased the failure rate from about 10% of pages failing to something down the order of 1% of pages failing to generate correctly. Yeah, one topic about the release site, I'm sure, am I audible now? So one problem is Jenkins IOS site nowadays that basically this site isn't really maintained. I mean, it has been originally developed for Jenkins to do zero, but it was three years ago already. Since other times, there was no active maintainers for this component, which impacted a lot of our efforts. But yeah, for example, now there is a developer-managed-pist thread from Graven about having GitHub releases on the website. So maybe we will be able to recover the effort. But last time I was checking whether it makes sense to do something about this site, I discovered that there is no nobody maintaining that and basically no interest to get the changes integrated by the infrastructure team. Yeah, and I think the pull request that Spinnak has submitted is one that I think I want to review. I know that Daniel Beck had commented on it. Hey, he's not sure when he'll be able to review it, but I think I'd like to review it, test drive it, and see if I could then use that test drive to propose to Daniel, hey, that's Merged, it's working well for me. But that's because I would love to have some improvements to the plugin site, but you're right, it needs, we're going to have people willing to do it. Thank you. So I don't have anything particularly to report on the DOC SIG Infrastructure Status Report. One item that is required for a special interest group is that it needs to report to the governance meeting, and the governance meetings lately haven't been happening, so I assume that that requirement will be lifted or I'll send it by email as a summary, or we'll rely on these meeting notes. Yeah, I think we should just send the summaries to the developer in case or maybe you're writing blog posts, for example, here you have a list of things we changed it on the Jenkins website, maybe even it's even blog postable, or you definitely worth sending it to the mailing list. Great, we'll do, let me put that as an action item for me. Thank you. So as a final item, I wanted to highlight some data on contributors to the site. I've been capturing this data and the Cloud Native Computing Foundation added the Jenkins.io DOC site to their Grafana-based data collection site where they're collecting various metrics and gathering them on open source projects, and one of the ones that we see here is, I can show it in the full context, is time from opened to merged. So how long does it take for a pull request to arrive in the queue on average and then be merged into the site? And what you see this is a 90-day view and what it shows us the middle line is that median time from open to merge and in the last 90 days we've had an improvement where we were at points earlier on the between 10, up to over 10 hours between submission and merge as the median. We've now decreased that to more like on the order of something over an hour. So for me, there's an improvement and this graph seems to indicate a real improvement. The CNCF site provides other metrics like this and there's a hyperlink in the graph if anyone is interested in taking a look at it. Now, does this tell the whole story? No, there aren't any software metrics that tell the whole story. So don't put too much credence into any specific measurement but it was fun to see that. In addition, we've got measurements that show we've got more contributors arriving over the last month. We've had additional authors contributing that hadn't contributed previously. So I think we're getting some growth and some development in the Jenkins.io site. Those were all the topics that I had for this meeting unless there are other topics all leg I'd propose we close the meeting. Oh sorry, there is no topics for me right now. Maybe what we could consider for the next meeting may be the joint meetings to be advocacy and outreach. SIG for example, but I'm not sure. It looks like half of the content here is actually about advocacy and outreach. So maybe we could do some collaboration there. Good idea, that's a good suggestion. I'm not sure that this meeting itself is being especially effective and so collaborating with the outreach SIG may be a much better result. Just give a brief summary there of progress. I don't want to disband. I think we're doing the right thing and we're getting the right results but the meeting itself doesn't seem to be helping with that objective. So I think that meeting is helpful but yeah the goal is to have more people on the call. And now since we don't do Google season of dogs and we don't have any full-time contributors documentation in the Jenkins community, it means that we either encourage people like Zbenek or other to participate and we get a set of people who participate or maybe just collaborate with other special individuals in order to again have more stakeholders here. Right, and that may be the that's a good point that other special interest groups might need just the benefit of a reminder. Hey, if you document what you've got or blog post about it, you can help your special interest group and the docs effort. Yeah, great. It's also a kind of meeting fatigue because you know with Google summer code etc. I have more than 10 community meetings every week, so yeah. Right, understandably. But thank you very much for your contribution. You're doing great things for us. Thank you, thank you. So I'm going to stop sharing and end the recording. Okay.