[Compcomm] Kde composite manager...
Mike Dransfield
mike at blueroot.co.uk
Thu May 31 05:37:02 EDT 2007
Nicholas Thomas wrote:
>> Competition? Why? It are both open source projects, which means they
>> can both exchange ideas and code, and work together, instead of
>> working against each other.
>>
>>
> Well, you know, compiz core is MIT whereas kwin4 is GPL...
>
Are you a lawyer?
>From what I understand the license of the final work has nothing to
do with it whatsoever.
You can easily include GPL'd code in MPL code and vice-versa.
It is down to the author who holds the original copyright to
decide.
For example, if I wrote a function and addded it to kwin4 - I could
ALSO put that code into compiz without a problem because its my code.
If someone else wrote to me and said can I use your function in
compiz and I agreed then they can include it, the code itself does
not become 'tainted'.
It is only in the case that you cannot contact the original author that
you cannot do GPL -> MIT, as you know, you can always do MIT -> GPL
even without the original authors permission (although its always nice
to ask)
There is plenty of code in compiz that has come from metacity or
kwin, but its OK because the original authors were asked. This is
why we keep an AUTHORS file.
As for working together, I think its a great idea. We could probably
start with a libwindowmanager as mentioned here, obviously FDO
would be the place to host it.
http://lists.freedesktop.org/archives/compiz/2007-February/001397.html
>
>> so maybe compiz/beryl should be tightly intergrated with gnome since
>> kde has its own tightly intergrated system(that most users will use)
>>
>> you can get a better product when you're dealing with only one de.
>>
>
> Nonononononononononononononononononononononono
> nonononononononononononononononononononononono
> nonononononononononononononononononononononono
> nonononononononononononononononononononononono
> nonononononononononononononononononononononono
> nonononononononononononononononononononononono
> nonononononononononononononononononononononono
> nonononononononononononononononononononononono
>
> pretty much sums up my response to that idea. The reasons should be obvious.
>
> /Nick
>
>
> _______________________________________________
> CompComm mailing list
> CompComm at Rock3d.org
> http://www.ubaight.com/mailman/listinfo/compcomm
>
More information about the CompComm
mailing list