--- title: Introducing Canonical’s Open Documentation Academy description: tldr; Our Open Documentation Academy starts this week with our first weekly Documentation Office Hours on Friday 1st March 2024 at 16:00 UTC. Everyone is welcome! Keep reading, or see our forum post for more details and to leave questions. Many of us at Canonical wouldn’t be here if it wasn’t for Linux and open […] url: https://canonical.com/blog/introducing-canonicals-open-documentation-academy?format=md --- 1. [Blog](https://canonical.com/blog) 2. Article --- [Graham Morrison](https://canonical.com/blog/author/morrisong "More about Graham Morrison") 26 February 2024 # Introducing Canonical’s Open Documentation Academy [documentation](https://canonical.com/blog/tag/documentation) --- Share the article **tldr;** Our Open Documentation Academy starts this week with our first weekly **Documentation Office Hours** on Friday 1st March 2024 at 16:00 UTC. Everyone is welcome! Keep reading, or see our [forum post](https://discourse.ubuntu.com/t/documentation-office-hours/42771) for more details and to leave questions. Many of us at Canonical wouldn’t be here if it wasn’t for Linux and open source. Their availability and accessibility helped so many of us to get involved, wherever we were in the world. We didn’t need to ask for permission. Open and inclusive collaboration, and the sharing of ideas, remains the best way to develop software (and to do many other things!), but we also recognise that this “getting involved” step can be difficult. Where do you start? Who do you ask? What needs to be done? It shouldn’t be this difficult. Open source projects should be as open to new contributors as they are to critical bug fixes, because new contributors are the next generation of critical bug fixers. One of the problems is the lack of an established *Getting involved process*. At Canonical, this is something we can solve, and we want to help solve it together by inviting contributors to write documentation. Documentation is the circulatory system for a project. New features do not exist unless they’re documented. New users don’t exist unless they know where to start, and established users won’t stay unless they know what to stay for. But these requirements are also what makes documentation challenging, and for those of us into this kind of thing, ceaselessly fascinating. We’re in a fortunate position at Canonical because we now have a well-established team of technical authors who work across all of Canonical’s major projects, alongside a scattering of projects that haven’t even been announced yet, and we all work within a common framework called [Diátaxis](https://diataxis.fr/). Our own backgrounds vary hugely; from academic linguists and Linux industry veterans, to IT journalists, astro-physicists, teachers, developers and support engineers. From Brazil and Bangalore to Wales and New Zealand. We all very much want to help people become open source contributors by building an on-ramp process. It may take some time, and we will need to adapt, but this is exactly why we’ve started our **Open Documentation Academy**. Thanks to the wide range of open source projects that Canonical works on, from the Ubuntu Desktop and command line tools, to security, cloud orchestration and device provisioning,   we have a fantastic opportunity to help people make meaningful contributions to technologies they’re most excited about. Documentation is the ideal place to start making contributions for several reasons: * it’s how you learn about a project and its governance * no contribution is too small, or too big * documentation can always be improved * small changes can have massive impact and benefit so many people To help you get involved, the Open Documentation Academy provides a curated list of documentation tasks. Choose one, let us know, and get started. Tasks include testing and fixing tutorials, updating the outdated, restructuring large documents, and anything else you may want to suggest. Our list is growing, and a big part of the Documentation Academy will be ensuring there’s always a wide range of tasks available, across as many projects and technologies as possible. And of course, we’re here to help. We’ll guide you through your first contributions, provide advice on approaches, and help you build your confidence. **And it all starts this week!** If this sounds like something you might be interested in, here’s what to do next. Our [task list](https://github.com/canonical/open-documentation-academy/issues) is now open, and growing. Take a look, bookmark it, and see our [Getting started](https://discourse.ubuntu.com/t/getting-started/42769) guide for next steps. Join [our discussion forum](https://discourse.ubuntu.com/c/open-documentation-academy) on the Ubuntu Community Hub. Chat to us on [Matrix](https://matrix.to/#/#documentation:ubuntu.com), and [follow us on Fosstodon](https://fosstodon.org/@CanonicalDocumentation)! If you’d like to ask us questions outside of our public forums, feel free to email us at [docsacademy@canonical.com](mailto:docsacademy@canonical.com). Join our weekly **Documentation Office Hours** starting at 16:00 UTC on Friday 1st March 2024. Everyone is welcome to join, and our first one will introduce you to the Open Documentation Academy. Leave your questions beneath the forum post and we’ll answer them live. We’ll publish a recording of each office hours meeting a few days later. Links and comments can be found on the [forum post](https://discourse.ubuntu.com/t/documentation-office-hours/42771). Also, take a look at our official [Open Documentation Academy](https://canonical.com/documentation/open-documentation-academy) page. It covers a few more details on what we’re trying to achieve. Finally, subscribe to our [Documentation event calendar](https://calendar.google.com/calendar/u/0?cid=Y19mYTY4YzE5YWEwY2Y4YWE1ZWNkNzMyNjZmNmM0ZDllOTRhNTIwNTNjODc1ZjM2ZmQ3Y2MwNTQ0MzliOTIzZjMzQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20). We’ll expand our Documentation Office Hours schedule and add other events throughout the year. Thank you for reading, and good luck! [Get in touch Interested in running Ubuntu in your organization?](https://ubuntu.com/about/contact-us/form) ## Sign up for our newsletter Get the latest Canonical news and updates in your inbox. Work email: \*I agree to receive information about Canonical's products and services. By submitting this form, I confirm that I have read and agree to [Canonical's Privacy Policy](https://canonical.com/legal/dataprivacy). Sign up ## Share on --- ## Related posts [### A year of documentation-driven development](https://canonical.com/blog/a-year-of-documentation-driven-development) For many software teams, documentation is written after features are built and design decisions have already been made. When that happens, questions about how a feature is... [Yanisa Haley Scherber](https://canonical.com/blog/author/yanisa-hs) 17 February 2026 [### Documentation, development and design for technical authors](https://canonical.com/blog/documentation-development-and-design-for-technical-authors) Typically, a technical writer takes the product created by a development team, and writes the documentation that expresses the product to its users. At Canonical we take a... [Daniele Procida](https://canonical.com/blog/author/danieleprocida) 3 December 2024 [### Help us build better doc](https://canonical.com/blog/help-us-build-better-doc) We want you to join our Ubuntu circle, and help us document MAAS. More minds, more eyes, more hands make better doc. [Bill Wear](https://canonical.com/blog/author/billwear) 17 March 2023 [### Humans may be rational, or how to collect better documentation feedback with linguistic theory](https://canonical.com/blog/humans-may-be-rational-or-how-to-collect-better-documentation-feedback-with-linguistic-theory) Anyone who has ever built a product wants user feedback – and we in open source want it more than anyone else, and place higher demands on it than anyone else. However, this... [Teodora Mihoc](https://canonical.com/blog/author/tmihoc) 28 October 2022