Regarding process, all of the FLOSSmanuals books are perpetually works in progress. Every book is constantly being updated. Some are more relevant to update than others. This is not a software focused book, so it isn’t as relevant to update, but there is much that could be added. Think of it like writing a book in a code versioning system: if you introduce a bug, or someone else feels the additions do not improve the work, they can edit it out, or revert the text to the previous state. But if it is good, it stays.

We write about the future, and this future will become the present faster than we think. So the book will need to be updated, or amended, or corrected to more clearly describe the new present, or the new futures.