I'm not sure there is any benefit to having a separation of powers
here. I would argue that the overlap in purpose actually makes
sense(and due to that, there is a high probability that a FWT member may
be a release manager).
Having the RM on the FWT may not be a necessity, but having the RM
involved as a voting member (by happenstance) can only really serve to
improve the communication between FWT and RM. in the end, we count on
the release manager to be a benevolent dictator; the worst things that
could happen is a RM totally ignore the FWT and be absent from all
The FWT serves as an instrument to aid the RM, a channel to enforce
process, a buffer against organic groupthink decision making. The
process of review is the more important part, and as long as there are
people with open ears who care voting, all is well.
| david "whit" morriss
| contact :: http://public.xdi.org/=whit
"If you don't know where you are,
you don't know anything at all"
Dr. Edgar Spencer, Ph.D., 1995
"I like to write code like
other ppl like to tune their
cars or 10kW hifi equipment..."
Christian Heimes, 2004
fn:D. Whitfield Morriss
Framework-Team mailing list