Hi,
That already exists for the application itself:
OOo for Mac and NeoOffice (_only_ for Mac)
NeoOffice removes all the X11 dependancies and publishes all the
modifications under GPL, which means the OOo Mac porting team can't
use them.
The result is we have a Mac OOo community split between NO (very user
friendly and using a more recent code base) and the official OOo for
Mac (not user friendly with an old code base).
you miss one *important* fact here. The official OOo for Mac holds more
that 95% of the codebase for NO. So .. without the "old" codebase NO
wouldn't even exist.
ATM OOo mac porting core team (which isn't really large :-( ) is hard
working to make the 2.0 codeline running on Mac. But they hear no "thank
you" from NO users ( NO team will indeed hear "Thank you", after the
interface has been reworked ... by NO developers).
But this is not only a OOo problem. It's the same with debian / ubuntu
right now. "User friendly" sub projects (or forks) attract users ant
potential contributors / developers. But often forget that they need a
base .. and that they need to promote their base.
BTW: your rants about Sun are .. well .. they tell from not knowing many
about the way Sun contributes to the project. Sun releases about 99% of
the (OOo related) code they employess produce as open source. That makes
about 95% of the current OOo source. So .. Sun is even coding NeoOffice/J.
And no .. I'm not employed by Sun, I don't make any business with OOo ..
I'm just volunteering here for a great community (what it is .. with all
the problems we have).
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
