What license should Sun use for the open-sourcing of Java?
Posted: Wed May 17, 2006 7:18 am
Once again, Sun's schizophrenia on the move. "It's not a matter if wheater, but how" said Rich Green during JavaOne yesterday.
One of Sun's issues with open sourcing Java is that they want to keep it together, keep it consistant and prevent forking, so what license do you guys think would serve them the best?
Personally I think the LGPL would do OK, because the GPL would disallow proprietary Java apps, and there are already plenty of those, so that would be stupid. A BSD style license would just make the thing fork like crazy.
I personally think that the LGPL, which they used when they open sourced StarOffice, is the right choice, it allows for proprietary linking and discourages people from creating their own forks.
One of Sun's issues with open sourcing Java is that they want to keep it together, keep it consistant and prevent forking, so what license do you guys think would serve them the best?
Personally I think the LGPL would do OK, because the GPL would disallow proprietary Java apps, and there are already plenty of those, so that would be stupid. A BSD style license would just make the thing fork like crazy.
I personally think that the LGPL, which they used when they open sourced StarOffice, is the right choice, it allows for proprietary linking and discourages people from creating their own forks.