On Wed, Oct 18, 2006 at 07:10:37PM +0200, Mads Toftum wrote: > On the surface everything appears fine to the point of graduating minus > the proving that you can do a release. But given past experiences with > graduating large projects too fast, I'd be much in favor of keeping > Harmony in incubation for another 6 months - it worries me slightly that > you seem to be in haste to move on almost immediately after all > requirements look ok, not giving it a bit of time to prove that this is > not just a temporary state. Also there's the whole issue of Sun and > opensourcing java - sure, it shouldn't affect Harmony directly, but on > the other hand I see a risk there (not great, but they may surprise us). > Just my EUR.02s worth on non-binding -1. > Gah, that went out a bit too fast. I missed saying that I'm biased by thinking that the project should never have happened in the first place. Not so much that there shouldn't be an a free implementation of java - but that a project like this is bound to grow to a size where it doesn't fit with the rest of the foundation. Implementing a whole language is big enough that there's plenty of foundations out there doing nothing but a language implementation (perl, python, ....) - I think that would be the best for a project like Harmony as well. The other bit is the speed at which it happened - I'd expected Harmony to be in the incubator for years and now it is aiming for graduation less than 18 months later without having even neared the first release. So, that's what my reluctance to letting Harmony graduate is about - feel free to ignore it.
vh Mads Toftum -- http://soulfood.dk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]