{"id":2574,"date":"2016-01-24T13:16:57","date_gmt":"2016-01-24T19:16:57","guid":{"rendered":"http:\/\/dev.iachieved.it\/iachievedit\/?p=2574"},"modified":"2016-05-06T10:27:57","modified_gmt":"2016-05-06T16:27:57","slug":"dont-use-the-phrase-all-rights-reserved","status":"publish","type":"post","link":"https:\/\/dev.iachieved.it\/iachievedit\/dont-use-the-phrase-all-rights-reserved\/","title":{"rendered":"Don’t Use the Phrase All Rights Reserved"},"content":{"rendered":"

Gists<\/a> are a popular method of providing code snippets to the community. These snippets frequently express complete implementations of an algorithm (for example, QuickSort in C) or smaller chunks of examples.<\/p>\n

I recently came across this implementation<\/a> of a circular buffer<\/a> in Swift to help with an upcoming chat client blog post. Unfortunately I cannot use this code as I pay close attention to the copyright statements of all source code and adhere to their caveats, restrictions, and limitations. This is one reason I’m not comfortable with including code that uses the Affero GPL<\/a>.<\/p>\n

The circular buffer gist in question above uses the phrase All rights reserved<\/a> in its copyright statement:<\/p>\n

\nCopyright (c) 2014 Pelfunc, Inc. All rights reserved.\n<\/pre>\n
Strictly speaking copyright law does not require this statement, as all copyright rights are reserved by default<\/i>, regardless of whether or not there is a copyright statement.  In other words, you are granted no rights to a copyrighted work without explicit permission.  The conclusion is I may not copy or use the code in this gist without permission from the author, even if it is for my own personal use.<\/p>\n
Now, let’s be honest.  I seriously doubt that was the intent of the author; after all, the code was posted to a gist.  If the intent wasn’t for others to make use of the code, why was it posted?  One might argue gists can be used as one’s own frequently used snippet bucket, but I find that relatively implausible considering that in this case it is a corporation (Pelfunc, Inc.) holding copyright.  The more likely explanation is that people don’t put much consideration into the copyright statement and reflexively type something they’ve seen elsewhere, namely the phrase Copyright (c) 2016 Megaco, Inc. All rights reserved.<\/code>.<\/p>\n
Make it Easy for Others to Use Your Code<\/h3>\n
Gists are for sharing, and there are ways to make it easy for others to use the code which you’ve kindly shared with the community.  The easiest method is to add a simple statement referring to the Unlicense license<\/a> or using the phrase “This is free and unencumbered software released into the public domain.”  If you do want to retain some rights, choose from the MIT<\/a>, BSD<\/a>, or ISC<\/a> licenses and include a URL to the license text.  And of course, you can always choose from one of the copyleft licenses<\/a>.<\/p>\n
Under almost no circumstances, though, should you use the phrase All rights reserved<\/i> in your gists if you actually want<\/i> to share and have others make use of your code!  I can only think of one exception and that would be if you wanted to get e-mails asking if you’d please give permission to use.  If that’s the case go ahead and add that to your gist as the uninitiated might just copy it anyway.<\/p>\n
PostScript<\/h3>\n
After writing this post I went on the hunt for another circular buffer implementation in Swift, and found this one<\/a> that has purports to use the MIT license.  Of course I went to lift out the implementation file CircularBuffer.swift<\/a> and it has the onerous All rights reserved<\/i> phrase, ostensibly as a result of the defaults set in Xcode.  I genuinely believe the author’s intent was to provide this as an open source framework, and have issued a pull request<\/a> to update the license in each of the .swift<\/code> file copyright statements.<\/p>\n","protected":false},"excerpt":{"rendered":"
Gists are a popular method of providing code snippets to the community. These snippets frequently express complete implementations of an algorithm (for example, QuickSort in C) or smaller chunks of examples. I recently came across this implementation of a circular buffer in Swift to help with an upcoming chat client blog post. Unfortunately I cannot […]<\/p>\n","protected":false},"author":1,"featured_media":2945,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[],"class_list":["post-2574","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-copyright"],"_links":{"self":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/2574"}],"collection":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/comments?post=2574"}],"version-history":[{"count":10,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/2574\/revisions"}],"predecessor-version":[{"id":2607,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/2574\/revisions\/2607"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/media\/2945"}],"wp:attachment":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/media?parent=2574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/categories?post=2574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/tags?post=2574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}