 Society Droid Trout the Way with the OpenSack Foundation and the Newton Design series and we're welcoming Lana Brunnelly back for another cycle as PTL of the Docs project. Lana, would you tell us a little bit about yourself? Sure, I'm Lana. I'm the documentation PTL for Newton. I work for Rackspace. I'm leading a team of technical writers here in Australia. I've been working on open sec documentation since Icehouse and I've been the PTL since Liberty but I've been an open source technical writer for about a decade now. Great, and tell us more about the Docs project. So the Docs project cuts across all of OpenStack. We're a horizontal project. We provide end-user documentation on the docs.openstack.org site and we know now that two-thirds of OpenStack users refer to Docs at least weekly with about one-fifth of users looking at the site daily. So it's a really big audience. Yeah, it's fantastic numbers that we saw from Docs and Docs use in the user survey. Tell us about what those hot topics were in Austin as your team were discussing what issues to solve. Sure, so we had two main hot topics. The first one was about increasing our support for teams who want to include information about their products in the official docs. It's been a big conversation for some time now through the last cycle. The big tent has really changed the way we look at projects and we want to ensure we're supporting each product team in the best way. The second topic was really more about processes and governance. We've made some strides ahead in this area during the previous cycles. So now it's about betting those processes down and ensuring everyone understands how we're working. Thank you. So what are some of the user needs? You're starting to talk a little bit about those with hot topics. What is your team thinking about the user needs? So the main one really came down to the installation guide. Because of the way the big tent changes have affected things and it's changed the way projects go about joining the OpenStack ecosystem. So Foundation obviously have an increased focus on ensuring new projects have sufficient documentation, which is great. But that meant that we needed to change our approach to documenting the installation of an OpenStack cloud. There's no right way to install a cloud and there's certainly no right set of components you should be installing when you do it. But we have a small documentation team, we have a seemingly endless parade of new components that require documentation. So we were actually faced with a really big technical challenge and everyone had some kind of skin in the game. So that was kind of tough for us. The second problem we wanted to solve was about providing some more guidance to developers and other OpenStack contributors, especially with these big tent changes, talking about how the docs team works and to make the inner workings of the docs team a little less inscrutable than they were before. Well, we appreciate it. And what can we look forward to in Newton in terms of new features or enhancements in docs? So I've got three top priorities. First of all, we're going to create the infrastructure to allow projects to write their own installation docs in their repo and then publish them seamlessly to the docs.openstack.org front page. So this means that projects have responsibility for their own docs, but the docs team will provide assistance in the form of templates and infrastructure support. And that means that we're ensuring that all projects are treated as first class citizens within the ecosystem. Secondly, the existing installation guide, as it is, will change focus. It's going to be more about an installation tutorial, giving people a highly opinionated and completely manual installation method to learn the ropes, but it's not for installing a production cloud. So thanks to the user survey, we can safely say that most production clouds are installed using some kind of automated tool. So having manual installation instructions is useful as a training tool, but it's not really for a real world scenario. So the third thing we have is a really a fairly long laundry list of other things that needed to be done. It all ended up focusing mostly on streamlining some of our processes, being clearer about the way we operate, consolidating guides that had for obscure historical reasons, being in their own repos and bringing those back into our main repo, and just general editing and tidying up, of course, which happens every cycle. Well, those sound like very ambitious, but important goals. Very ambitious. One last question for you, which I know can be a bit of a conundrum for documentation, which is we try to connect the dots on the product workgroup between the different projects by emphasizing five themes, which are scalability, resiliency, manageability, modularity and interoperability. And so tell us from your perspective, what is documentation particularly trying to solve for? So last time we did this interview, I mentioned that Docs had a focus on manageability. So that was for the Metaka release. And we were aiming at working more effectively and efficiently, sorry, with a focus on collaboration. So for Newton, while manageability themes are still really present, the focus is actually on scalability. And we're making our documentation efforts scale out to represent a much greater proportion of products, contributors, operators and users. From empowering projects to write their own documentation with our support to making processes simpler to find and understand to ensuring our documentation is accurate, up to date and effective. It's going to be actually a really exciting cycle, I think. Well, thank you so much for all of the contributions that you and the full documentation team provide to getting Newton ready to rock and roll. Great talking to you. And we'll see you in Barcelona. Lovely. Thank you so much, Heidi.