This may be a stupid question but... Does this mean that anything published at the bakery cannot be used by anyone who is using CakePHP for a commercial application?
My knowledge of licencing is far below what it should be. I understand the need for them, however in this instance I'm a little bit fuzzy. Anything published on the Bakery, by anyone, cannot be used by myself (or others) so long as the application I'm currently working on (or possibly an application I may work on in the future) will have a commercial purpose... simple example being I couldn't take a cue from the article 'Taking advantage of the pages controller' if i was working on a site for a client? Or is it more that if I were to rewrite one of the articles and publish on my own site touting it as my own work then I would be breaking the agreement. I may have shot myself in the foot in front of my peers but it is important to know. *if anyone wanted to suggest some reading material around the issue of licencing I wouldn't turn it down* thanks, freedom On 27/09/06, John Zimmerman <[EMAIL PROTECTED]> wrote: > On 9/26/06, hypercubed <[EMAIL PROTECTED]> wrote: > > > > I'd like to know what happens if you cross post something on your blog > > and the bakery. > > > > > That would be one of the specific instances that probably should be defined > in an example. > > I have thoughts on this situation as to when it would and would not be ok, > but I think PHPNut and other devs should explicitly define some of these > common scenarios so there is no doubt what is ok and what is not. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
