Practical Trademark Law For FOSS Projects
summary
Trademark is brand not code: registration gives a territorial monopoly for specific goods, costs a few hundred dollars in many countries and takes three months to three years to grant; common‑law rights exist in the US. Practical steps: use names consistently and trademark symbols, run a USPTO and TMview search before naming, adopt a simple policy (copy model trademark guidelines), allow plugin naming like “Zebra plugin for Apache Camel,” organize community policing of misuse, and avoid suing — negotiation and technical/community leverage usually work.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:05Practical trademark law
- 2:45Practical questions
- 3:08Consistent marks
- 3:59Reputation
- 5:19Policing your trademark
- 6:56Registrations
- 9:08Dont go to court
- 12:05Trademark resources
- 15:22Infringement
- 22:56Choosing a name
- 25:10TMView
related talks
33mPractical Trademark Law For FOSS Projects
52mPractical Trademark Law For FOSS Projects
54mTrademarks and Open Source
33mDon’t Love It to Death: Best Practices for Downstream Use of Project Trademarks
25mPatents and Copyright and Trademarks… Oh, why!?
50mRunning a Successful Open Source Project
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
