So, to be clear, which of this scenarios will get Cake foundation's Counter-Uncertified-Poser-Unit knockin at my door?

1.- I write an online killer app and name it CakePack and sell it to google
2.- I write a killer app and name it CakePack and release as opensource
3.- I'm not a certified developer have a big banner on my site that reads: "I code CakePHP apps that just work"
4.- I'm a teen web-coder and I'm obviously not a certified developer but have a big banner on my site that reads "I h4v3 m4d CakePHP 5k1ll2"
5.- I've written an app that will change the world as we know it and I put a disclaimer on the site "Developed with CakePHP"
6.- I've written an app which is certainly shit and I put a disclaimer on the site "Developed with CakePHP"
7.- I open a blog entitled "The unofficial site of all things CakePHP and Tiffany Thiesen" -- and I put adsense on it--
8.- I've lost my mind and decided to --god forgives me!-- fork CakePHP into my own RailishBiscuitPHP Framework

On 6/2/06, nate <[EMAIL PROTECTED]> wrote:

> I strongly suggest that you check your local trademark law for details
> of what you can and cannot do without a licence. Don't blindly believe
> trademark owners: of course, most will try to convince you that you
> cannot use their appropriated words at all without permission.

Have we gone after anyone for simply mentioning CakePHP on their site??
No.

Rather than taking a letter-of-the-law approach (which seems a bit
confrontational), why not recognize it as an opportunity to (a) support
the comminuty and (b) score some bragging rights ;-)





--
Armando Sosa

www.nolimit-studio.com
www.dospuntocero.info
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to