Don’t Love It to Death: Best Practices for Downstream Use of Project Trademarks
summary
Open source trademarks must identify the project as the source or risk confusion, alienating contributors and even invalidating trademark rights. Practical steps include following a project’s trademark usage guidelines, using official artwork and the correct TM/® marks, and emailing the project’s trademark contact before renaming products. Examples: don’t bake kubernetes or Docker into a brand name—use a tagline or docs instead; publish clear trademark notices, sponsor or run joint case studies, and credit projects like ebpf or projects under the Linux Foundation.
AI-written summary · about
chapters (18)
- 0:00Trademark best practices
- 1:25What is a trademark
- 3:14Legal foundations
- 4:40Trademarks as beacons
- 5:54Trademark rights and licenses
- 7:39Registration and use rules
- 9:03Why control usage
- 10:30Risks of modifying trademarks
- 11:11When and how to use trademarks
- 13:56Branding alignment
- 16:06Compliant use steps
- 17:10Usage guidelines
- 19:18Names in product branding
- 21:24Beyond legal compliance
- 22:48Clear trademark notices
- 23:33Publicizing contributions
- 24:55Mutual promotion
- 26:19Closing & Q&A
related talks
33mPractical Trademark Law For FOSS Projects
52mPractical Trademark Law For FOSS Projects
32mPractical Trademark Law For FOSS Projects
54mTrademarks and Open Source
50mRunning a Successful Open Source Project
26mThings Your Mother Didn't Teach You About....
40mHow to Open Source a Project and Possibly Not Fail While Trying
31mOperationalizing Open Source Projects: When the Rubber Meets the Road