On Tue, Nov 11, 2003 at 05:24:59AM -0800, Rodney Waldhoff wrote: > On Mon, 10 Nov 2003, Greg Stein wrote: >... > > Look. Geir, Rodney: if you guys don't believe in A-C, then fine. You don't > > have to. But some others do, and it appears that some J-C components will > > move. Why is that so threatening? > > On the contrary, I think apache-commons has several things going for it, > and I'd very much like to see the project, or more generally, its mission > of creating reusable library code under the ASL, succeed. Frankly, I'm a > bit insulted you'd characterize this interest as feeling "threatened" by > the possibility, and I'm disappointed that you'd respond to any difference > of opinion about how to best accomplish that mission by with comments > along the lines of "and if you disagree, then go away".
I don't want you guys to "go away". Quite the contrary. I'd prefer if you offered constructive criticism, assistance, and insight. But to be honest, a lot of what I have seen is "but why? J-C does this already. let's just promote that instead." or "why should they give up their community?" or "svn creates barriers" or ... There has been very little, "this is how J-C operates, and to make them feel at home in A-C, we should do X." To be honest, Rodney: yes, I may have lumped you in unfairly with Geir, whose positions are very much more "J-C does this right. why should anyone bother with A-C?" But my response was built from an overall impression, which is that I'm not seeing "we can fix things <this> way". To me, I read the resistance to A-C and some of the responses as feeling threatened by a loss of community, self-rule, etc. So... that's how I read it; if that doesn't represent your thinking, then I apologize, and will blame email as an imperfect medium. What may simply be "devil's advocate" discussion or similar can easily be construed as reading a position or belief, which can be quite incorrect. And, of course, the easiest way to correct it is to call out the issue as you did :-) > Not to put to fine a point on it, but if I were "threatened" by the > possibility of jakarta-commons components moving to apache-commons, then I > probably wouldn't be offering suggestions about how best to encourage j-c > components to move to a-c, as you see me doing at > <http://article.gmane.org/gmane.comp.apache.commons.general/151> and > <http://article.gmane.org/gmane.comp.apache.commons.general/158>, to name > two examples. And re-reading those two posts also leads me to say, "hunh. there *have* been nuggets of 'here is info about J-C'". Mebbe too thick-headed to see them :-). I might suggest that the answer is to simply start asking J-C components if they want to move. If they say "yes", then fine. If they say "no", then we ask "why?". That provides very concrete info rather than continual discussion and theorizing... Cheers, -g -- Greg Stein, http://www.lyra.org/
