Live data from Hacker News

My Code made it to a Hollywood Movie

hackoftheday.securitytube.net

51–54 of 54 posts

Re: My Code made it to a Hollywood Movie

#51
post #28
post #17

Earlier quoted context omitted.

Assuming that the GPL is fully representative of Stallman's views, they would not be be required to release 3d models, scenes, or the screenplay. Those parts would not be considered software. However, I am not sure about the source code involved in the movie. He makes a distinction between art and software because software is meant to do "practical jobs" whereas art is not so he does not put the free requirement on t…

> Assuming that the GPL is fully representative of Stallman's views, What does Stallman or his views have to do with it? The GPL is a document that is interpreted by judges and juries, not by Stallman. The text of the GPL itself makes no distinction between software or other things that can be copyrighted. GPLv3 even changes its language to make it clearer that it can be applied to non-software things. For example, i…

Seeing as he wrote the first version, was involved in the updates, and spends a lot of time promoting GPL, I would assume his views have a large influence in how it is used and perceived. GPL mentions software quite a few times and the preamble states "licenses for most software and other practical works". As I mentioned above, Stallman does not consider art as a practical work.

However, I am not sure how a judge or a lawyer would interpret the word practical work.

Re: My Code made it to a Hollywood Movie

#53
post #46

Earlier quoted context omitted.

Unless the GPL license is different from what I read here ( http://www.gnu.org/licenses/gpl.html ) then it does not extend to make the entire film subject to the GPL license. The GPL license only extends to "covered works" (works based on the GPL'd work). If the entire movie was based on the GPL'd work then the GPL could extend to the entire movie and its source assets. For example, if the code of the GPL'd work form…

No, you are interpreting the license text in the wrong context. Covered works in an legal context mean derivative work, as in: "A “derivative work” is a work based upon one or more preexisting works" - United States Copyright Act in 17 U.S.C. § 101 Based upon don't mean "central pillar". If a copyrighted song plays in a movie, it would still count. The song do not need to be a "central pillar" of the movie. The film…

1) If the GPL wanted "covered work" to mean "derivative work" they would have chosen that language (the GPL is not jurisdiction specific, so they would not have included a cite to any particular statute). They chose not to, and basic rules of legal construction hold that this choice can be interpreted against that meaning.

2) You are misinterpreting the legal meaning of "based upon" which is what my post discussed.

A song in a movie does not make the movie a derivative work; it simply means the movie is distributing the song. The movie becomes a derivative work if, and only if, the movie is based upon the song, i.e., if some plot or character or some other aspect of the movie draws elements from the song. (For example, any random episode of Glee.) If the song could be replaced with another song without changing the movie, then no part of the movie is based upon the song, and the movie is not a derivative work.

Re: My Code made it to a Hollywood Movie

#54
post #46

Earlier quoted context omitted.

No, you are interpreting the license text in the wrong context. Covered works in an legal context mean derivative work, as in: "A “derivative work” is a work based upon one or more preexisting works" - United States Copyright Act in 17 U.S.C. § 101 Based upon don't mean "central pillar". If a copyrighted song plays in a movie, it would still count. The song do not need to be a "central pillar" of the movie. The film…

1) If the GPL wanted "covered work" to mean "derivative work" they would have chosen that language (the GPL is not jurisdiction specific, so they would not have included a cite to any particular statute). They chose not to, and basic rules of legal construction hold that this choice can be interpreted against that meaning. 2) You are misinterpreting the legal meaning of "based upon" which is what my post discussed. A…

On a second check into this, there is some corrections to my previous comment:

  A “covered work” means either the unmodified Program or a
  work based on the Program. - GPL
So what a covered work is, is clearly stated. Either unmodified program, or a work based on it.

You are right that a movie don't become a derivative work of any preexisting work it includes. Rather, the movie requires to have performance and "sync" rights to such works or they become legally liable for infringement.

So the real question is, do the GPL give performance and sync permission to the movie producer for using the covered work?

  This License explicitly affirms your unlimited permission to run the 
  unmodified Program. The output from running a covered work is covered by this
  License only if the output, given its content, constitutes a covered work.
The answer to that is ... only if the movie itself is based upon the code and thus become a covered work. Otherwise, the license to do not give any such permission. It could be argued that performance right is covered under the term "convey", as it states:

  "To “convey” a work means any kind of propagation that enables other parties
  to make or receive copies.".
However, it also says:

  "Conveying under any other circumstances is permitted solely under the conditions
  stated below."
Since performance and synchronization are not include below, such right can not be seen as given under the term of conveying.

So to correct my statement: The GPL can't come into effect since it is not giving any permission to the movie producer in the first place. The movie producer would have to get a separate license or be liable under copyright. You are right however that movies do not become derivative works of the preexisting works they incorporate.

For more details about sync rights: http://www.musiclawupdates.com/?p=2182

Post reply on HN