 I'm Mark Wake. Welcome to the Jenkins Documentation Special Interest Group. Today, wanted to do a brief summary of our progress in the last two weeks over the Jenkins documentation. So first topic, previous action items. The DOC SIG pull request has been submitted and the blog post has been created. I have one action item open that the DOC's project ideas need to be included in a pull request. We've also got a new page in our Jira site that provides a dashboard for website bugs and we've made good progress on those website bugs thanks to that Jira page. So the page looks like this, shows on the left unresolved status on the bottom left and website unresolved as a filter on the right. Thanks very much to Rodek Antoniak for creating that page. Beautiful work. Welcome, Kristen. So we've got John Haas blog post is done and or rather the contributing DOC for Jenkins X is done and participants have begun reviewing pull requests. Grateful for help from Rodek, from Meg McRoberts and others. Oleg's also completed the mentor instructions as a pull request to Jenkins.io. Kristen, were there any topics that you wanted to add to the agenda today? Okay, so we've got action proposals that we would like to cover. We'll take these another week or another two weeks, two weeks from now. Oleg is unable to attend today. Likewise for the Community Grid status report, in terms of the DOC SIG infrastructure status report, JEP4 progress is on track, looks good. There are a few items left to do. We will continue reporting at least once a month to the Jenkins governance project. Website bug reports have been reviewed and we've made really good progress on clearing them up, tidying them up. We can really use help from other team members in the DOC SIG to review those bug reports and especially identify ones that are newly friendly. We've got another topic here on the plug-in site, reviewing strengths and weaknesses. We'll defer this for another two weeks. And then I wanted to take some time here today to talk about prioritizing our documentation effort with data. So one of the things that had been created a year or two ago was a page feedback mechanism for pages on the Jenkins IOS site. And we've now got results. So the pages most voted not helpful are the Jenkins Pipeline Git step, is the maintainer of that plug-in. Shame on me, that's one to work on. The Hello World tour and the environment tour. Those Git plug-in, I think I understand, that particular step is syntactic sugar and should be pointed to checkout. But Hello World and environment are both intentionally structured to help students, help readers get benefit, and yet they have strong no votes. The scanning page is empty. So getting not helpful on an empty page is no shock. The build step is exceedingly complicated. And so strong no votes there, no surprise, that's a project idea we should probably put in. The nodes page is also empty. So for me, that page feedback results gives us some hints of possible project ideas that we can put into the system. We'll capture those in an upcoming pull request to Jenkins.io and put each of them in there as an idea of someplace that could be approved. Now I've got some really good news. Let's look at the graph here. In the last month, we've dramatically increased both the number of contributors and the number of contributions to the Jenkins.io site. We've also had some significantly positive contributions from in the area of social media helps that make our pages more attractive when presented through social media. So when there's a Twitter link now, for instance, there'll be a picture associated with it that will be included in the Twitter feed. Oleg indicates there's more work we can do to further improve that, but this is a nice step in just the two or four weeks since we started the documentation special interest group. As another positive, our open pull request count has dropped dramatically. We've resolved many, many pull requests. We're under 10 and have been under 10 open pull requests for three or four weeks now. So thanks very much to those doing pull reviews of pull requests. There are some other surprises here, which in the data, which I didn't quite understand, but Hyde would like to highlight. The second highest referring site to our GitHub repository for Jenkins.io is actually Wilson Maher's blog. And he's got a page or a set of pages there that are Jenkins tutorials. They are more frequently referring to the source code of this Jenkins.io site than Jenkins.io itself does. Very impressive that he's got so many visitors and I'm not sure what we can learn from that, but I think it's worth studying. That concludes the topics that I had. Kristen, were there any things that you wanted to report on? No, not really, but I did notice when you were talking about the pages that were not as helpful, two of them are part of a, or could be related to a sub-project that would be fixing the pipeline steps documentation, which is something that we have looked to have as a Google summer code project, or it could be like a season of docs project eventually, but yeah, there's like a lot that could be done there to improve that. Excellent, and so you say that was, I missed it because of my having my audio configured page. Which of the pages was it? Sorry, so the one that says the build step, that's a good step. So see, they're part of the steps auto generation. So there's some work that could be done there. So it's interesting. I agree with you about the Hello World Tour and the environment tour. It's interesting that they, is there a way that we can see more about why they said it wasn't helpful or is it just kind of, it wasn't? There isn't, all they provide is a yes, it's helpful or no, it's not, and that's even then opt in for them as a participant. So they don't get a feedback form, it's just, hey, helpful or not. Gotcha, okay, because I was like, because it could be different for other, for certain people might find, this one little piece helpful or it's just like, it's all not helpful. But no, I'm glad that this is here to even get the feedback in the first place so we know what we can start addressing. Right, and that was my thrill, is I'm ecstatic that we've got the feedback. A little embarrassed that the plugin I maintain is the top of the list, but. It's all good. I think some of the parts of that is that it's just difficult to figure out what's going on in general with the plugin steps. And it's so much easier to just have the pipeline or the auto generation or the snippet generator inside the Jenkins itself. It's a lot easier to see what's going on there, but. Right, yeah, that's, and that's, so I'm delighted. This was the work originally of Jattles Gaskell. I believe it was almost two years ago that he did this initiative and I'm really thrilled that it's still gathering the data and we can use the data. I find it interesting, it's another piece of data that I haven't yet extracted is how many pages got votes at all. Aggregate total because that may hint which pages are most heavily viewed. And we could then decide, oh, we should focus some energy on the pages that are most often viewed. The empty pages, yeah, that's, we should fix those because that's a cool place to do some writing. Right. All right, great. Well, that concludes the topics that I had. Anything else from you, Kristen, then? No, not really. All right, well, let's conclude this meeting then. Thanks very much. I'll archive the recording of the meeting and we will meet again in two weeks. Thank you. All right, thanks.