On Tue, 9 Nov 2010, Magnus Enger wrote:

1. RFCs agreement workflow (discussion about the workflow for RFCs to be accepted/validated)

an RFC is a curtasy, having a RFC 'accepted' doesn't mean that the code that results will be accepted, conversely, having an RFC 'rejected' doesn't mean that the code created will never make it in. in closed source development, RFCs have a lot of weight, and approving or rejecting one is committing to future acceptance or rejection of a bunch of code to implement that feature. in open source development, an RFC is an outline of your intent and design, which may or may not get a lot of review by people. It's a good thing to do so that you can explain to others what you are working on, and the general approach that you are taking. It's useful for others who are interested in that feature (or the things that you will affect in implementing that feature), but even if people object, you may still be able to convince others that the benefits you are providing are worth the cost that people are objecting to. On the other hand, even if people like you design, they may not like the resulting code. an e-mail to this list is either 1. a response to another message 2. a request for help or 3. a proposed change (either in code or otherwise), all messages that fall in category #3 are RFCs, even if they don't have that tag in the subject. David Lang