Hi Sanjiva, The Sinhalese origin of the name has nothing to do with why I voted against it -- as I said, I would have voted down 'Apache Rules' as well (which I assume is roughly the English translation.) While I understand the space-grabbing issue, that's really something that needs to be work out at the PMC level. Apache is a non-profit organization, so I'm not willing to buy any marketing arguments. With those gone, it would seem to me that clarity of purpose should be the strongest consideration made during naming. Apache (WS) Policy or even Policy4J (or their Sinhalese/Celtic/hieroglyphic equivalents) are superior choices in my mind. (I don't like Axis(2) either, but nobody is asking for a re-vote. 8-])
-Bill On Mon, 2006-04-17 at 22:14 +0600, Sanjiva Weerawarana wrote: > Hi Glen, > > > Sorry, but -1 from me. I think Apache Commons Policy is a perfect name > > for the package, because it says what it is. Case in point - I think > > Apache Commons Logging is a great name for that project too. > > As Dims pointed out there's now an on-going movement against generic, > domain capturing names because people have started to abuse those as a > way to capture territory instead of just to name a codebase. > > > Let's leave it clear and simple without forcing people to say "Neethi, > > what's that?" (yes I understand that Sinhalese speakers might well be > > able to do that, but we've already got quite a few Sinhalese names.... :)) > > Sorry I find this to be an unacceptable reason. There are lots of > English names too .. is that a problem? Of course not. > > I'm disappointed that you (and Bill) are pointing to the non-English > nativeness of the name as the problem. Maybe English speakers don't find > an immediate association- that's PRECISELY why ASF is moving against > suggesting names. Do you know what Apache Ode is? What about Apache > Kabuki? Apache Lokahi? > > Just to assure you- Sinhalese speakers will also not associate WS-Policy > to "Neethi". > > Sanjiva. >
