Are you looking for some slightly different books about open source to read? Ones that aren’t technical or which don’t delve into the technology? If that’s the case, I have three books for you:
Ours to Hack and to Own — These days, it seems that the technology that we buy or use isn’t ours. Someone else controls it, or the tightly restrict how we can use it. We’re often at the mercy of large corporations which have a grip on what we see and read and hear. Is there way to take back some semblance of control? That solution could be platform co-operatives, which are the focus of the book Ours to Hack and to Own.
The book collects 40 essays about platform co-operatives, and how we can use them to promote more openness with the systems and services we use and rely upon. You can my review of the book at Opensource.com to learn more about Ours to Hack and to Own.
The Open Schoolhouse — A few years ago, I interviewed Charlie Reisinger for Opensource.com and was both impressed and moved by the work he and his team had done to introduce open source to the Penn Manor school district in Pennsylvania. In 2016, Charlie decided to pull his thoughts and experiences, and those of the staff and students works with, into a book. The result is The Open Schoolhouse.
It’s an inspiring book, not only from the angle of open source triumphing but also how open source has changed lives. Charlie tells a number of stories about how the shift to open source not only saved the Penn Manor school district a lot of money, but also helped a number of students find themselves and to achieve beyond their own expectations.
The Cabbage Tree Method — The goal of this book is simple: to introduce a method of developing open source software that puts the people who will use the software at the centre of the design process. Yes, via the Cabbage Tree Method, people will actually control the design of what they’ll use.
That sounds chaotic, but it’s not. The Cabbage Tree Method, as Adam Hyde explains, is about communicating and collaborating with the user at the centre of the process. That collaboration is led and guided by a facilitator, and the folks crafting the code will know exactly what the users want and need when they start coding.