CakePHP itself is released under the MIT license, and you can do anything with it the license allows.
The CSFL is a license similar to the QT license which basically says you can use the code as long as you release any modifications back so others can benefit from them. You still retain copyright to the code you create, but you have to give the same freedom you received by using the original code back so others can use it too. I see no problem with this. The 2 licenses are completely separate from each other. There are times when an application that was written by the Cake Software Foundation, Inc. may be released under the CSFL but this is because we feel that since we are writing the code and giving away this code, anyone who uses it should do the same. You are always free to contact the foundation to discuss licensing, so you could include code that is licensed under the CSFL, and release under a different license. This is "OUR" way of protecting the code we spend countless hours working on, CakePHP will always remain under the MIT license though. Welcome to the world of Open Source... -- /** * @author Larry E. Masters * @var string $userName * @param string $realName * @returns string aka PhpNut * @access public */ On 7/6/07, keymaster <[EMAIL PROTECTED]> wrote: > > > I read posts related to this subject, but never saw these two licenses > compared, to really bring out the differences. > > I'm trying to understand the practical differences between the MIT > license and Cake Software Foundation (CSFL) license, and the > implications for software developers who want to create software for > sale, or use this code in apps they build and sell to clients. > > It sounds to me like the bottom line is: > > CSFL: > > Anything containing any code which is CSFL becomes CSFL itself, and > can be freely redistributed by anyone who finds himself in posession > of the code. That seems to mean a developer who uses any CSFL code in > his app or product, has to know that anything he develops on top of > that, can never be copyrighted as his own, and anyone can take and > redistribute it. > > That does not sound so great for developers who want to protect their > work. > > MIT: > > On the other hand, with the MIT license, there seem to be no > restrictions whatsoever (other than showing the copyright in the > code), and if you use MIT code in your software product or app you > build for your client, you can still maintain copyright over the > modifications you made (ie. add your own copyright to the code you > write yourself), and thus protect your work. > > Is this accurate? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
