-
Notifications
You must be signed in to change notification settings - Fork 38
protect the Gratipay brand #692
Comments
https://www.linux.com/news/how-make-money-open-source-platforms-part-3-creating-product |
+1 from @ShaneCurcuru at https://opensource.com/comment/138571#comment-138571:
|
I'm more inclined to do so in this post-#118 world. Bad actors are real. |
Let me know if there are ways I can help the legal governance of your project figure this out. |
@ShaneCurcuru Thanks for joining us here! @clone1018 and myself are the legal owners of Gratipay.
Any links to share to existing documentation on this? |
The Practical Trademark Law slides, and the ones from ApacheCon Seville: The ASF's own guidance to our projects about properly displaying their brands: https://www.apache.org/foundation/marks/pmcs The first two steps:
My collected list of useful articles on the Apache site: https://www.apache.org/foundation/marks/resources#other Especially the FOSSMarks and Model Trademark Guidelines links. Read up some, then email me and we can chat more if that will help. |
@whit537 said:
Absolutely true. What isn't obvious is that there are more bad actors out there than you've ever heard about. Many trademark issues in #opensource are solved privately, to allow everyone to save face - so for every case like you point to in #118, there are at least a half-dozen similar cases that never got public attention. I don't worry about the kinda-bad actors who will correct behavior once they are contacted privately, and once you explain yes, FOSS projects can own their own trademarks. I worry about the bad actors who either 1) keep changing a little, but keep pushing the boundaries, and 2) the true infringements from companies that simply don't care about you. |
Thanks @ShaneCurcuru, will do! |
One of the naivetes of Gittipay 1.0 was a desire not to legally enforce our brand. Here's the sort of mess that can lead to:
https://letsencrypt.org//2016/06/23/defending-our-brand.html
We should probably submit to this system.
The text was updated successfully, but these errors were encountered: