{"id":329476,"date":"2023-03-23T15:00:00","date_gmt":"2023-03-23T15:00:00","guid":{"rendered":"http:\/\/itteacheritfreelance.hk\/wordpress\/?guid=ff3957eb4f045f80fbc683312c74b93c"},"modified":"2023-03-23T15:00:00","modified_gmt":"2023-03-23T15:00:00","slug":"protecting-the-python-trademarks","status":"publish","type":"post","link":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/2023\/03\/23\/protecting-the-python-trademarks\/","title":{"rendered":"Protecting the Python Trademarks"},"content":{"rendered":"

<\/p>\n

Who is the Trademarks Working Group?<\/span><\/h2>\n
The Python Software Foundation Trademarks Working Group was created by the PSF <\/span>Board of Directors to  monitor and authorize (or prohibit) use of trademarks <\/span>held by the PSF.  The WG\u2014initially dubbed committee\u2014was created in 2008, and <\/span>has been co-chaired by me since 2010, adding Marc-Andr\u00e9 Lemburg in 2013.  We’ve <\/span>had a variety of other members over the years, with Iqbal Abdullah being a <\/span>wonderful and helpful member of the WG for the last couple years.<\/span><\/div>\n

<\/span><\/div>\n
You can write to us any time at on the <\/span>Trademarks WG mailing list<\/a><\/span>.  If you ever want to use one of our <\/span>marks, please do write to us.  Even for those uses that are completely <\/span>non-contentious, we’d rather quickly approve them and have a record in the <\/span>mailing list archives than just not know about the use (the archive is not <\/span>public, however, since legal issues, even potential litigation, are sometimes <\/span>discussed).<\/span><\/div>\n

<\/span><\/div>\n
We would welcome participation by more Python community members (being a PSF <\/span>member is not strictly required, just an interest in helping Python maintain <\/span>its branding).  Helping with the working group is a pretty small time <\/span>commitment, but as with many volunteer efforts, folks often drift away from <\/span>such efforts over the course of years.  By all means contact us if you have an <\/span>interest in trademarks and an hour or two a week to spend helping us in these <\/span>discussions.<\/span><\/div>\n


<\/span>Our Goals<\/span><\/h2>\n

<\/span><\/div>\n
The PSF holds registered trademarks in a large number of jurisdictions\u2014<\/span>incrementally increasing in number over the years\u2014and “use trademarks” <\/span>worldwide.  Obviously, legal regimes around intellectual property, and <\/span>trademarks specifically, vary somewhat around the world; for the most part <\/span>trademarks serve a similar purpose everywhere though.<\/span><\/div>\n

<\/span><\/div>\n
We don’t want the brand and reputation of Python to be used in a deceptive <\/span>manner. However, Python being <\/span>free and open source software (FOSS)<\/span>, and the PSF being devoted to such <\/span>freedom, the licensing policy adopted by the PSF is very liberal and serves the <\/span>purpose of promoting the use and knowledge of Python rather than trying to <\/span>obtain commercial advantage (as many for-profit product marks are used).<\/span><\/div>\n

<\/span><\/div>\n
Let’s go back to what marks the PSF maintains.  The name “Python” is a <\/span>wordmark<\/i> that is registered in many places.  Nominative use of the name is <\/span>always permitted when it is used to describe the Python programming language. <\/span>In contexts such as books devoted to the language or about associated <\/span>libraries, tools, etc. we ask publishers to include a small notice in the <\/span>front matter that mentions the PSF trademark.  We have an <\/span>official usage policy<\/a><\/span> and a <\/span><\/span>Frequently Asked Questions<\/a><\/span> that detail permitted usage, <\/span>with the FAQ having more examples and a less formal tone (probably best to <\/span>start with the FAQ if you have questions).<\/span><\/div>\n

<\/span><\/div>\n
Similarly, the names “PyCon” and “PyLadies” are also wordmarks of the PSF. <\/span>The policies around use of <\/span>PyCon<\/a><\/span> and of <\/span><\/span>PyLadies<\/a><\/span> are each a <\/span>little bit different from the Python wordmark, since they serve  different <\/span>purposes.  Essentially, we want to make sure that when those names are used, <\/span>they maintain an identity and advance the goals for which the marks were <\/span>created.  The PyLadies wordmark is monitored and authorized by the <\/span>PyLadies leadership<\/a><\/span> rather than the Trademarks WG, so email <\/span>to them is the best place to ask questions of them.<\/span><\/div>\n

<\/span><\/div>\n
\n
<\/a><\/div>\n<\/div>\n

Trademarks are Tricky<\/span><\/h2>\n

<\/span><\/div>\n
The trickiest part of what we do on the Working Group is approve use of the <\/span>“two-snakes” <\/span>Python logo<\/a><\/span>.  A great <\/span>many really wonderful Python-related user groups, conferences, software <\/span>projects, publications, blogs, and other efforts that do a great job of <\/span>promoting Python, understandably don’t understand the arcana of trademark law. <\/span>In particular, the rules we need to maintain about derived logos<\/i> can feel <\/span>obscure and counter-intuitive in the F<\/span>OSS<\/span> world.<\/span><\/div>\n

<\/span><\/div>\n
The key issue is that trademark is not copyright<\/b>.  For people familiar <\/span>with copyleft and software freedom, it feels like the right to create derived <\/span>products should be as little restricted as possible, perhaps not at all. <\/span>While I endorse that wholeheartedly for copyright, that’s not how trademarks <\/span>work\u2014nor, I believe, how they should work<\/i>.  Trademark is instead a kind of <\/span>consumer protection, it’s a way of saying that a particular thing is what it <\/span>purports to be.  In a way, a trademark is like a signature or a seal (whether <\/span>a physical or a digital version of such); it’s a testament to authenticity of <\/span>a thing.<\/span><\/div>\n

<\/span><\/div>\n
Apart from my particular philosophical attitudes about trademarks, the laws <\/span>around them have a specific concept of dilution<\/b> wherein merely <\/span>permitting<\/i> a use that makes a mark less distinct can remove the protection <\/span>altogether.  Specifically, it means that if the PSF allows groups to make <\/span>completely well-meaning, and often even beautiful, changes to the shape of the <\/span>two-snakes logo, we could wind up losing the ability to stop malicious actors <\/span>from misbranding their non-Python things with the logo.  To be clear, many <\/span>derived logos are absolutely permissible, and the FAQ discusses what <\/span>distinguishes permissible and impermissible derivations (and what can be <\/span>“inspired by but not derived from”).<\/span><\/div>\n

<\/span><\/div>\n
Happily, all the good actors we’ve dealt with, in my 15 years working on this, <\/span>have come to understand the concerns of the PSF, and have modified their <\/span>customized logos in ways that allow us to authorize them.  It’s slightly <\/span>unfortunate that a few others have slipped through simply because the WG never <\/span>knew they existed until they were already in use, but we’ve worked with those <\/span>groups (largely conferences and user groups, sometimes software projects) to <\/span>fix things going forward.  It’s a little bit of politics, a little bit of <\/span>professionalism, but mostly it’s just reaching out to the truly wonderful <\/span>people who make up our worldwide Python community.<\/span><\/div>\n

<\/span><\/div>\n
David Mertz (mertz@gnosis.cx)<\/span><\/div>\n\n

\\\"IT\u96fb\u8166\u88dc\u7fd2
\u7acb\u523b\u8a3b\u518a\u53ca\u5831\u540d\u96fb\u8166\u88dc\u7fd2\u8ab2\u7a0b\u5427!<\/figcaption><\/figure>\r\n<\/br>Find A Teacher Form:\r\n<\/br>https:\/\/docs.google.com\/forms\/d\/1vREBnX5n262umf4wU5U2pyTwvk9O-JrAgblA-wH9GFQ\/viewform?edit_requested=true#responses\r\n<\/br><\/br>Email:\r\n<\/br>public1989two@gmail.com






\r\nwww.itsec.hk<\/a>
\r\nwww.itsec.vip<\/a>
\r\nwww.itseceu.uk<\/a>
<\/p>","protected":false},"excerpt":{"rendered":"

Who is the Trademarks Working Group?The Python Software Foundation Trademarks Working Group was created by the PSF Board of Directors to  monitor and authorize (or prohibit) use of trademarks held by the PSF.  The WG\u2014initially dubbe…<\/p>\n<\/div>","protected":false},"author":2054,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"slim_seo":{"title":"Protecting the Python Trademarks - ITTeacherITFreelance.hk","description":"Who is the Trademarks Working Group?The Python Software Foundation Trademarks Working Group was created by the PSF Board of Directors to  monitor and"},"footnotes":""},"categories":[10700],"tags":[],"_links":{"self":[{"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/329476"}],"collection":[{"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/users\/2054"}],"replies":[{"embeddable":true,"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/comments?post=329476"}],"version-history":[{"count":1,"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/329476\/revisions"}],"predecessor-version":[{"id":329477,"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/329476\/revisions\/329477"}],"wp:attachment":[{"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/media?parent=329476"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/categories?post=329476"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itteacheritfreelance.hk\/wordpress\/index.php\/wp-json\/wp\/v2\/tags?post=329476"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}