The information we currently have on Decision Making can be found in our Orientation section:
http://openoffice.apache.org/orientation/decision-making.html On that page, there are explanations for types of decision making used in this project specifically and within the Apache Software Foundation. In my opinion, this is very good "how to" guide, but somewhat limited as a "when to" guide. Most of the source code changes done currently are preceded by a BZ issue. This is wonderfully simple and anyone on the commits list can follow what and why something has been done. In other cases, for much larger changes, discussions have been initiated. So, we would NOT see an action such as deleting an entire module undertaken without discussion. Decision making for these types of change follow a a well-known and followed process. Aside from code changes, there are changes to other areas of the project -- web sites, wiki, forums -- whose changes are not typically noted in BZ. Sometimes there are proposals and discussions, sometimes not. These are the kinds of changes that may need additional clarification with regard to decision making. In summary, what kinds of change for non-source code need a [PROPOSAL]/discussion before change? ------------------------------------------------------------------------------------------------- MzK "Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities. Truth isn't." -- "Following the Equator", Mark Twain
