Tarique is exactly right: >The term "CakePHP" is trademarked so you can be prevented from using >that for almost everything (including blog posts) *if* CSF wishes.
>It is this ambiguity from CSF which I do not like. Now, unless CSF decides to set up a public license which allows for some basic use of the Name, CakePHP is unusable in a commercial environment. Actually, right now CSF is even violating the MIT license under which Cake is published: the MIT license allows for redistribution of the Software, which I can't though, as the software contains the word CakePHP all over, but I am not allowed to use this word. Now, to make this clear: I have total understanding if the CSF wants to protect themselves against anyone who might abuse the term CakePHP by giving the impression that he is certified, or his book is an official Cake-Book or whatsoever. But a simple use of the word CakePHP, stating "My Company has used the CakePHP framework in so many projects" should be allowed. Once again: "ACME is an officially licensed CakePHP-company" should be forbidden unless licensed by CSF. "ACME has produced software using the CakePHP framework" should be allowed. CSF should provide such a statement with every copy of CakePHP. Unless they do so, no company should seriously consider investing time in this framework, because tomorrow CSF may decide it's time to cash in. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
