> It seems to me that a few individuals are mis-understanding > our words and have a general mis-understanding of trademark policy.
That was exactly my point, and I think such a document would help others avoid confusion. Confusion so high that some people even thought CSF lawyers were going to hunt them down if they mention CakePHP to a friend on the privacy of their homes. I mean the CSF is not a record label company :) > But the more I have to do this, the less I have time to work on the > thing that matters most, CakePHP. What about appointing people for areas, such as writing documents about trademark protection or marketing decisions (regarding website), that are not *core PHP* oriented? > This is a community built on the trust of everyone to > do their part. And some of us try to :) > The MIT license covers the copyright on the code The day I found CakePHP and discovered it was licensed under MIT was the day that I felt in love with it. MIT license simply rocks. -MI --------------------------------------------------------------------------- Remember, smart coders answer ten questions for every question they ask. So be smart, be cool, and share your knowledge. BAKE ON! blog: http://www.MarianoIglesias.com.ar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
