On Tue, Jan 27, 2009 at 5:02 PM, Jukka Zitting <[email protected]> wrote: > Hi, > > On Mon, Jan 26, 2009 at 8:26 AM, Mark Brouwer <[email protected]> wrote: >> It has been mentioned before but RIVER-160 contains a patch for 3 >> issues in the list of outstanding issues, mainly enhancements to the >> Service Browser with ServiceUI support. The fact that nobody reviews >> them or notified me that at least he/she applied it locally to see >> whether it works makes me hesitate to apply it. I can commit these >> with a press of a button when I'm at home but it doesn't give me good >> feeling to continue to work like this.
Mark, perhaps the best way to instill more activity is that things start breaking. Wise people in ASF has said that "great vision, bad code creates vibrant communities", meaning code that is too good will fail to create strong communities. No itches to scratch, too much fear to break a perfect setting and so on... > I hear you. Unfortunately it seems that waiting for proper reviews is > not going to get us anywhere. Can we come up with alternative > failsafes, like improved test cases, etc.? The test suite is quite extensive, but far from easy to run (by ASF standards), and sits in different source root. I say go for it, very little 3rd party will be affected even if the patch is horrible. In a regular ASF project, these things would have been committed straight to trunk and little considerations... Cheers Niclas -- http://www.qi4j.org - New Energy for Java
