I don't think changing the license to GPL will change any of the
problems associated with a lack of developers working with OOo. Unpaid
developers don't code because of licensing issues as trivial as this,
they code because they are passionate about a project.
I work closely with the Postgres community which uses a Berkley license
and we have more developers working on the project today because
commercial companies are willing to pay developers to make the project
better. Sun does the same thing with OOo. What other companies are
paying developers to work on OOo and how can we increase those numbers?
Matthew Bennett
PS. It was no problem to help with OOo at OSCON because I was attending
for other reasons. Adam is really the one who deserves the Kudos because
he had went out of his way to be there.
swhiser wrote:
OOo would benefit from more developers ANYWHERE.
The dearth of OOo developers is because...
-- OOo's licenses are unappealing to individual contributors
solution: GPL
-- OOo's build process is unnecessary difficult
solution: build and participate through the Novell fork
-- OOo's joint copyright ("JCA") is unacceptable to many individuals
solution: GPL + Foundation
-- OOo's JCA takes too long to process through Sun legal
solution: file and work through the Novell fork
It took me a long time to recognize this, so it'll save you a bit.
-Sam Hiser
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
