While the proposed organization is a positive step, I find it has one major flaw. It offers too much product control to developers.
Developer control of a product can be a positive thing when a product is immature and needs to expand its feature set rapidly. As a product matures, however, developers are notoriously bad at managing changes outside of their own development process. They tend to get pet projects that require lots of care and feeding, or they decide an otherwise worthwhile feature is not going to happen on the basis of some obscure technical nuance or personal preference, or conversely they implement features for their gee-whiz factor rather than their general applicability.
I'd prefer to see this three person committee formed from persons who are not directly involved in the work. For example, technical needs can be addressed by a competent developer, but that developer should not be an SME Server developer. Likewise, communications can be overseen by an experienced writer or webmaster, but that person should not be doing the actual work. And so forth. This would afford the community a certain level of abstraction, which would be a good thing in translating between the technical desires and community desires of the product.