I was re-reading the merged version of the Governance chapter, and realizing that there's really no coherent style or voice for the text, which says to me that we don't have a core target audience. For example, this paragraph:
All open source projects operate in and with governance structures. The term "governance" carries multiple meanings in an organizational context. It can refer to regulatory matters or risk management issues, for example. More generally, though, it can also refer to a system of rules, roles, and procedures that determine how power in a project gets distributed.
In tone and style, that's aimed at middle-to-upper management for a large company or government agency.
The very next paragraph:
Because open source projects are organizations, all projects feature governance structures. Some of these structures are more explicit than others. Some are more formal than others. But every project has them.
... is written for more of a general/developer audience, especially if you change "feature governance structures" to "have governance".
It might be a good idea to attack this issue sooner rather than later; the longer you put off deciding on a style and target audience, the more re-editing you'll need to do.
I was re-reading the merged version of the Governance chapter, and realizing that there's really no coherent style or voice for the text, which says to me that we don't have a core target audience. For example, this paragraph:
In tone and style, that's aimed at middle-to-upper management for a large company or government agency.
The very next paragraph:
... is written for more of a general/developer audience, especially if you change "feature governance structures" to "have governance".
It might be a good idea to attack this issue sooner rather than later; the longer you put off deciding on a style and target audience, the more re-editing you'll need to do.