Linked by Rahul on Mon 13th Oct 2008 21:19 UTC
Permalink for comment 333944
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
More News »
Sponsored Links



Member since:
2005-07-07
You haven't answered the question. Why did Sun think that GPL dual licensing Java was the correct option there, maintaining compatibility with lots of existing software with exceptions for where they needed it, and that a completely new license in the CDDL was required elsewhere?
You didn't answer my question either. Why can't linux dual license when most projects out there do?
Ha, ha, ha, ha, ha. I love the usage of 'IP', which is meaningless. Not the point. I'm not talking about code flowing from Sun but others' willingness to commit code to Sun and Solaris. There's no evidence that Sun is even accepting that if it is happening, and things such as the PowerPC port of Solaris tell us that an awful lot is being kept in Sun's four walls. [/q]
You mean to say Linus accepts every single line of code someone wrote in to the main line tree, Really?
Based on what? There is zero code flowing into Solaris from outside Sun. That's when you know you don't have an open source community. If anything, Sun is strangling it. [/q]
That has nothing to do with the license. Do you even understand what your are saying your self. That response was the most illogical thing I have ever heard.