Future never end11/9/2022 ![]() To succeed, we will need to do the right thing in each of them. Our transformation project will take place across four distinct concerns in documentation. It’s going to affect the work of teams and individuals right across the company. This project will change the way that nearly everyone who works at Canonical thinks and talks about and approaches documentation. We hope that the standards, discipline and values we assert this way will spill out from Canonical, into our wider community, and will make a difference to our industry as a whole. It has already started, and will become part of the fundamental Canonical discipline of making software. This is a permanent, on-going commitment. They are values that we want to become known for. ![]() These are the values that we stand for, that we will express in our work. We want it to be the best it possibly can be.īy “best” we mean documentation that above all else understands, respects, reflects and serves its users’ needs. Our aim is to create and maintain technical documentation and documentation practice that will represent a standard of excellence in the industry. We have embarked on a comprehensive, long-term project to transform documentation. We need to do it according to a plan that will give us the unity and coherence we seek, and will sustain it into the future. We need to create and maintain software documentation, deliberately and systematically. Even producing better documentation isn’t enough. We know that merely valuing documentation is not enough to take us where we want to go. ![]() We want to do better for our documentation users – this is how we’re going to do it. We’ve been able to create unified and coherent software product lines, but we’ve been less successful doing the same for documentation. ![]() Our software spans a range from single-purpose command-line tools to vertical ecosystems composed of dozens of discrete component products, created by dozens of independent engineering and product teams. One thing that has made it difficult at Canonical is the complexity of our engineering, product and services portfolio. We’ve understood the importance of this for some time, but actually finding a way to express those values in our practice is less easy. It’s a way we demonstrate how we value each other – including how we value you. Our software documentation is part of how we talk to each other – our users, our colleagues, our community. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |