Raku and/or Rakudo trademarks #193
Comments
autarch
added
the
infrastructure
|
Do you know if it has to be software? I mean, we could point the link to rakudo, but it'd be close to cheating. A link to spectests would be more appropriate. Alternatively, would it be ok if the link would point to a page with a list of implementations to download? Event though it'd be just rakudo on that page. |
So the patent is for the name "Raku" in the area of "downloadable software". So yes, I think there needs to be something where you can "download Raku". And you might suggest a different area for the patent, but I spent a long time looking through the options and A) this is the best one; B) what we did for "Perl". That said, I think that a link that points to Rakudo would be okay.
Great question, I have no idea. But I think we could try that and see what they say. |
I think the above needs s/patent/trademark/g , since the two are not at all the same. Alternatively, if "patent" is indeed what is intended/contemplated, then I'm very confused. Pm |
AlexDaniel
changed the title
Nah, it seems like the usual confusion (trademarks vs patents vs copyright vs designs vs contracts). There is a Trademark Application. I have changed the title. |
AlexDaniel
removed
the
infrastructure
|
I do not think that this is an infrastructure issue. The first question we should be asking is whether “Raku” should be trademarked at all. It is actually right that trademarks can not apply to the name of the language itself but rather the compiler. Didn't they mean to trademark “Rakudo”? And if they wanted to trademark “Raku”, then why? Also, as I'm reading this:
I'm starting to wonder what kind of protections a Raku trademark will impose. For example, if I start new a Raku compiler, then create a website that has a user-friendly button saying “Download Raku now!”, will I be in violation? If yes, then I don't think it's right. If no, then what kind of protections is Raku trademark expected to bring? |
|
I'm sorry to see that TPF did not realize the difference between Raku and Rakudo. I'm not sure that one can create a trademark for a programming language. How does Python do this n with all of its alternate implementations? How is Python protected? Is PyPy trademarked? |
The trademark imposes no particular restrictions other than what the trademark holder decides to impose. TPF would defer to the wishes of the Raku community in these matters. The main benefit of the trademark is that it prevents someone from using the name and logo in a way that conflicts with community goals. For example, if someone were to make a "Raku compiler" that was actually a proprietary word processor, that would be a case where having the trademark would be useful. Without a trademark, there's literally nothing that could be done about this. I think the Python Foundation's statement of "General Goals" at https://www.python.org/psf/trademarks/ is a good summary of how a language name trademark should be used.
With a trademark. See https://www.python.org/psf/trademarks/ From what I can see, PyPy is not trademarked, nor is Jython. That said, they could be.
I'm not sure why you would assume this it the case. Trademarking Raku makes sense in the same way as we have a trademark for "Perl", and the same way the Python Foundation trademarked "Python". We could also trademark "Rakudo", though I don't think this would have as much value. |
|
I don't think the comparison to Python is as apt as a comparison to Lisp would be. That said, I don't know the legalities surrounding Lisp, so I'm afraid I can't be of much help. |
Python is not a language definition, but an implementation. Therefore it can have a download button. Perl is not a language definition, but an implementation. Therefore it can have a download button. Rakudo is not a language definition, but an implementation. Therefore it can have a download button. Raku is a language definition. I guess we could use a button to download roast? |
|
@lizmat As it was said, a link to a list of available compilers could be fine. |
|
@autarch Thanks to you and TPF for looking in to this. I share the concerns expressed here on the language specification vs. language implementation difference, and think it's important the trademark is obtained on a solid foundation (it'd be a pity to get it, only to find this GitHub issue with all of its doubts shows up as a court exhibit later... :-)) The situation we have seems to be to be closer to, for example, the ECMAScript trademark, which is also a trademark relating to a language standard rather than an implementation. (Our standard is executable, but I doubt that makes a difference here.) Is it possible to find out the "basis" for that trademark? Perhaps they also do it as downloadable software, in which case I'd be quite reassured. |
|
@jnthn Yes, here's the ECMAScript trademark - http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4804:ik71uw.2.1 And yes, it looks like theirs is in a different are. I think it may be possible to amend our application to use the same areas as theirs, which would make sense. I'll leave this issue open for comments for a bit to see if anyone objects or has other ideas. |
|
Here's a link to the ECMAScript trademark which (I hope) will not expire - https://tsdr.uspto.gov/#caseNumber=85383290&caseType=SERIAL_NO&searchType=statusSearch |
|
So I'm wondering if we should consider trademarking both Rakudo and Raku. The Rakudo name would be for downloadable software, and Raku as a language spec (using the same categories as ECMAScript). I'll bring this up at the TPF board meeting this Friday, but I'd love some feedback from the Raku community on this too. |
autarch
changed the title
|
From my perspective, it's worth trademarking both.
Pm
…On Mon, May 11, 2020 at 12:13:29PM -0700, Dave Rolsky wrote:
So I'm wondering if we should consider trademarking _both_ Rakudo and Raku. The Rakudo name would be for downloadable software, and Raku as a language spec (using the same categories as ECMAScript).
I'll bring this up at the TPF board meeting this Friday, but I'd love some feedback from the Raku community on this too.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#193 (comment)
|
|
My vote for both too. |
|
Sorry, somehow forgot to reply, but I'd be in favor of the two also. |
|
Having my own experience with trademarks in this area (I trademarked "Muldis"), I believe its perfectly reasonable to trademark "Raku", but it may be good to broaden it a bit to cover technical documentation, software, and services, rather than being so specific as "downloadable software". I also agree that a separate trademark for "Rakudo" should be gotten. |
lizmat
added
meta
|
Hi all, I've started with working an IP lawyer to do this properly. Here's what he suggested ...
He suggests that we can use a screenshot of docs.raku.org as support for this. This makes sense to me. Do others following this issue agree?
For this he suggests we use the rakudo.org home page as our supporting screenshot. I think this also makes sense, but I had a couple additional questions for the Raku community. I assume that we want to use Camelia as the trademarked logo for Raku, but please correct me if that's not correct. Do we want to use the logo on rakudo.org in the trademark application for Rakudo? I think the alternative is to simply not trademark any logo. |
|
My opinion would be "yes" to all three. |
|
Okay, further clarification. We are not trademarking the logos right now (we could do that later). Right now we're just trademarking the names, so I think I have everything I need to go forward. |
|
My apologies, but I wasn't clear enough. I would register the logo. "Yes" meant to be "register everything". My point is that even if ever decide to modify the logo I'd protect the current one for historical reasons. |
|
@vrurg No, you were clear. I was the one who was confused. I realized my earlier questions about logos weren't relevant to the trademarks we're filing for. If we wanted to trademark the logos that'd be a separate filing. It also occurs to me that since Larry drew Camelia (IIRC) that we should really have his blessing before we trademark that anyway. |
|
Here's an update/summary of where we are with the Raku/Rakudo trademarks as of Sept. 24: Our long-term plan is to have The Perl Foundation apply for three separate marks:
Of these, we have only started working with an attorney for (1). The blocker on moving forward is figuring out the specific categories to apply for – we obviously want the broadest protection possible without risking invalidating the trademark. Prompted by @jnthn's comment upthread, we are currently planning to follow the example set by ECMAScript which – like Raku – is a software standard rather than an implementation. The ECMAScript trademark covers two classes: On (2), we need to check that no one has already trademarked Camilla. The text description of the Camilla logo states that Larry Wall holds both the copyright and trademark rights to Camilla. However, I've searched the USPTO trademark database and haven't found any indication that Camilla was registered (though I could have missed something). We've reached out to @TimToady to confirm the details. On (3), I don't believe there's any real blocker, though it's possible we may need to as TPM's board for a bit more money (~$500) to cover the expense of registering an additional trademark. |
|
After discussing the issue with the attorney we're working with, I believe we need take the following two steps to secure our trademark to "Raku". We need to act fairly promptly because our amended trademark application is due later this month. 1) Add a reference to Raku to the message displayed when Rakudo is launchedThe attorney asked that the message "set the marks apart from the text by vertical separation and font differences and to include the TM symbol after each". They suggested a longer, four-line version, but we plan to suggest the following two-line compromise:
2) Supply a translation for "Raku"Because "Raku" is a word in Japanese, the Trademark Office requires us to provide a translation of the word, along with evidence of the translation or to agree to the translation that the Trademark Office found. They found the translation "easy" from Google Translate. However, my understanding is that our use of "Raku" has more to do with its meaning related to pottery. Based on that, I think we should submit the translation "hand-moulded, lead glazed earthenware pottery fired at low temperatures". (citation 1; citation 2. We plan to reply to the attorney in a later today, so if anyone disagrees with either of these ideas, please say so as soon as possible. (The attorney won't file anything for a few days – and certainly not before we've updated the Rakudo message – so nothing will be final immediately but it would be better to limit the amount of back and forth over this as much as possible). Other (non-essential) stepsI believe that the two steps above are all we need to do to secure our trademark. However, there are a few other changes that might be helpful, including minor changes to the website (e.g., using ™ in a few more places and changing some of the wording around the download options) and revising the 6.d specification announcement to reflect the name change. I plan to get started on PRs for these changes, but they don't need to hold up the trademark application. (I've used the pronoun "I" in this comment because I'm speaking only for myself, but the rest of the TPF legal committee has also been involved and extremely helpful – especially Nigel Hamilton, who has been the main point of contact with the attorney and thus has taken on a large share of the work) |
|
I think Larry actually intended both meanings to apply: the first about the use of the Raku Programming Language, the second on that, even though the language will have imperfections, it will nonetheless be beautiful and thus perfect after all. |
|
@lizmat thanks, that's helpful to know. We'll ask the attorney if we can supply more than one translation. If we can only supply one, do you have a preference about which one we supply? |
|
I would lean toward the second. But maybe @TimToady or @thoughtstream would like to chime in at this moment. |
|
I swear I remember Raku name discussions also talking about "Rakuda", which is one possible Japanese word for camel. See https://jisho.org/search/%E9%A7%B1%E9%A7%9D and https://translate.google.com/#view=home&op=translate&sl=ja&tl=en&text=%E9%A7%B1%E9%A7%9D |
Yeah, I came across that too – for example, it was prominently mentioned in the HackerNews discussion around the rename. However, the request from the Trademark Office is specifically to provide translations of the term "Raku", so I don't think there's a good way for us to include statements about "Rakuda" in the trademark application. (As an entirely separate matter from the TM application, it might be nice to have something in our FAQ about what the name means. We've (unsurprisingly!) got a lot of puns/linguistic shenanigans going on, and I'm not sure that new users appreciate all the layers of meaning) |
[Obligatory "I am not a lawyer", "I am not TimToady", "I am not a native speaker of Japanese" disclaimers] I always think of the name "Raku" as primarily signifying "comfort and ease". Yes, it's also the name for beautifully repaired broken things, but (a) that's not a primary meaning[1] and (b) "broken but beautiful" is not the main association I want for Raku, especially not in a public forum or a legal document. Hence I would personally favour submitting "comfort and ease" as the only translation. I would also not be inclined to mention the other word-play associations with "rakuda" ("camel") or "rakudo" ("paradise") [1] My understanding is that the name for this pottery repair technique originally derives from the "comfort and ease" meaning. But, again, I am not an expert in the Japanese language. |
|
"Paradise" might be applicable to the "Rakudo" trademark. With regards to Raku in the pottery context: https://en.wikipedia.org/wiki/Raku_ware (which does not have the string "repair" in it). |
See, not a Japanese pottery expert either. ;-) I would still prefer the "comfort and ease" connotation over the "hand-made and irregular" meaning. Though, according to the Wikipedia entry, the correct translation in that context is "enjoyment". |
That makes sense to me. I will say that I like the associations of "comfort and ease" significantly more than those of "easy" (the translation the TM office suggested). It might be a subtle distinction, but to me "easy" in a language context suggests "easy to learn" – which not only isn't a great fit for Raku, but I'd argue is actually a non-goal for Raku. For some reason, "comfort and ease" doesn't have that same "learnability" connotation to me – it seems more like a description of how it feels to use the language. |
Hmm, interesting. Wikipedia doesn't provide a source for that translation, and the first 4 online dictionaries I checked all had "comfort" rather than "enjoyment" (though they might all be sourcing their translations from the same place for all I know). There is something appealing about "enjoyment", though – I'll do a bit more digging and see what I can come up with. |
|
Just an opinion: "enjoyment and ease" sounds the best to me. If it's a correct one, I'd stick to it. Otherwise comfort is good enough. |
|
In the totally "for whatever it's worth" category, "enjoyment and ease" is exactly what I'd be aiming for, if it'll pass USPTO muster. The "enjoyment and ease" notion also reminds me of -Ofun .
Pm
…On Mon, Oct 12, 2020 at 02:11:38PM -0700, Daniel Sockwell wrote:
> Though, according to the Wikipedia entry, the correct translation in that context is "enjoyment".
Hmm, interesting. Wikipedia doesn't provide a source for that translation, and the first 4 online dictionaries I checked all had "comfort" rather than "enjoyment" (though they might all be sourcing their translations from the same place for all I know). There is something appealing about "enjoyment", though – I'll do a bit more digging and see what I can come up with.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#193 (comment)
|
|
I did a bit more digging (er, ok I got help from a friend) and located this translation, which seems to support the "enjoyment and ease" translation. Based on this source and the discussion above, we'll try to use that translation for the trademark application. Thanks, all. |
|
Update as of October 27: the attorney representing us has now filled a Response that provides the translation "enjoyment and ease" for "raku". The response also amends the basis for establishing the trademark, which will allow us to rely on the image of the Raku welcome screen shown below: The attorney will provide the trademark office the image once the trademark file has been updated. |
- to be shown when starting the REPL - to be shown when doing `raku -v` As part of the effort of trademarking Rakudo and Raku. codesections++ for working with The Perl Foundation on this.
|
TPF is currently working on both trademarks in the US. I think this can be closed. |
TPF has filed for a trademark on "Raku" in the US. There were a couple objections raised by the trademark office (see https://tsdr.uspto.gov/documentviewer?caseId=sn88782119&docId=OOA20200427#docIndex=1&page=1&tdrlink= for the letter).
One of the issues is that the raku website does not show the "raku software" available for download, only "rakudo". So in order to get the application approved we will need a download link or button that says "Raku" somewhere.
The text was updated successfully, but these errors were encountered: