Not a "strong opinion", but I think that RTC hampers the free-flow of ideas, experimentation, evolution, and creativity. It is a damper on expressivity. You maneuver bureaucracy to get a change in. CTR is about making a change and discussing it. But you get *forward progress*.
I also feel that RTC will tend towards *exclusivity* rather than the Apache ideal of *inclusivity*. That initial review is a social and mental burden for new committers. People are afraid enough of submitting patches and trying to join into a development community, without making them run through a front-loaded process. I've participated in both styles of development. RTC is *stifling*. I would never want to see that in any Apache community for its routine development (branch releases are another matter). My opinion is that it is very unfortunate that Cassandra feels that it cannot trust its developers with a CTR model, and pushes RTC as its methodology. The group-mind smashes down the creativity of the individual, excited, free-thinking contributor. Cheers, -g On Wed, Nov 11, 2009 at 11:09, Matthieu Riou <matth...@offthelip.org> wrote: > Hi guys, > > What's the take of other mentors and the IPMC on podlings practicing RTC? > I'm asking because some seem to see it as a blocker for graduation whereas I > see it much more as a development methodology with little community impact > and therefore no real influence on graduation. Strong opinions here? > > Thanks, > Matthieu > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
