 Welcome to the documentation special interest group meeting September 25 2020. Let's review the agenda, and then we'll go through it. So first report on previous action items. Then Hacktoberfest preparation as a topic. Google season of docs as a topic. Office hours results. Data on contributors and contributions. We'll work through each of those topics and then conclude the meeting. So no, nothing to report on the action item regarding GitHub apps and plugins that use them, and nothing expected for several months, most likely. Not a not an issue and not a problem for the project. In terms of Hacktoberfest preparation. One through October 31 is Hacktoberfest sponsored by digital ocean. Last year we had really great results multiple meetups and good sessions great contributions. This year we're expecting a little bit less, but we're trying to, to staff up and be ready for it. So we've, we've created a set of GitHub issues. Thanks to Jonathan Marise for that. And those issues now need to be triaged so that they can be assigned some of them anyway the good first issue label makes what we do by triaging is we allow a second person to review the issue before we put it in front of someone who is a first time contributor to assure that the first time contributor will understand what they should do in order to resolve the issue. Some of the issues are more complicated, we wouldn't want to dissuade or disappoint a first time contributor by giving them an issue that's really out of reach of a first time contributor. We will likely propose a Hacktoberfest docs meetup during to help hold during the month of October so that we can review how people can contribute to docs Jonathan Marise. Vlad Silverman and I are willing to host that and we'll, we'll highlight some of the progress that's being made some of the easy ways that there are to contribute to Jenkins through documentation. And we've also got a proposed idea on how to do terminology updates, and how to allow that to be a Hacktoberfest approach. So what we think we could do is count the occurrences of the, the offending terminology in this case master in the sub trees of Jenkins.io so there are pieces that may be in one part of the tree like system or another part I can using or various places like that and create GitHub issues for a portion of those sub trees based on a reasonable count of the offending word in the sub tree. The idea is that we don't want to create a single monster issue that would require someone to make many, many, many changes rather let's create several smaller issues with assigned subsets. If those people can work on the subset, take it up, complete it, submit the pull request and go on. We don't want the subsets to be a change of a single word in a single file, but rather some reasonable size set, and the size of reasonable remains to be seen by doing the triage exercise. So we're creating those we'd still like someone else to review the issue to decide if it's a valid good first issue and if it is then we'll assign the good first issue labeled to it. Now, we've only got about six days before we start October fast so this is a place where we're time limited on what we can do we hope to get this done within the next few days. And the option item that was suggested was a hacktoberfest Hall of Fame. We had this kind of Hall of Fame for the Jenkins UI hack fest, and it was exceptional. It made things work smooth it helped us highlight who was contributing how they were contributing. Unfortunately, it doesn't look like we're going to have the capacity to create this hackfest repository this time. I mean, Jonathan is investigating it, but I'm a little worried that the issue efforts are more crucial than having the repository to track. Next topic, Google season of dogs, Zenab Abu Bakad has been approved and is now working on documenting Jenkins and Kubernetes or Jenkins on Kubernetes. So that documentation progress is going forward she's actually sent out a draft and is inviting people's review of her draft. We encourage those who are part of the docs to help with that review is welcome to offer review and feedback. Kristen, what's done and I have the lead on that as mentors along with Markey Jackson. Thank you for the help all around there. We're also holding weekly docs office hours. We've actually got them scheduled twice weekly. And with that twice weekly schedule, we regularly have four of us that attend the Monday office hours and meeting notes there remind us of how we're making progress. And a portion of that has been identifying and finding ways to make progress on the wiki conversion. We have quite a number of pages still active in the wiki, even though the wiki has now been read only for almost a full year. And so this wiki conversion process is helping us move content from the wiki and place it into logical and sensible locations with good review on Jenkins.io. We also coordinated the Jenkins 2.249 to 1 LTS testing in the docs. Special thanks to Vlad for his help with that Thursday office hours we found are rarely used since they're on demand. That's not a problem. Just be aware that many times we will list them as on demand and when no one appears we don't hold them. It's not an issue. In terms of our progress and data on contributors and contributions. We now have 121 issues open and 111 closed. That is a significant jump from a month ago. Thanks to Jonathan's creation of a number of issues in preparation for October fast. It's, it's not an indication of degraded quality or anything like that. It's just a hint that there's still lots and lots of work to do. On the time from PR submission to engagement. Here on this graph what you see on the green line is the 85th percentile of time from the initial submission of a pull request to first involvement from a non author on that pull request. What you see across this two year span is that for the last six or seven months we've consistently kept our kept our 85th percentile value below one day, but just barely below one day that's much better than we used to have, but still could use some You'll see in the last in the most recent data period that we actually brought that down to less than 16 hours for the 85th percentile. It's good positive progress. The time from open to merge is not showing as positive a progress because we've got quite a number of pull requests that are languishing in the backlog that were submitted as part of the hackfest needs significant provisions but have not been revised. This one we really do need to improve. Then contributors for the last month. We're about the same number of contributors and number of merged pull request this month as we had last month. So we're not we're not showing growth in terms of our documentation contributions, but we're also not showing a loss. We do have 28 open pull requests and have closed about 30 or 40 in the last month. Thanks everyone for documentation contributions.