Sign In

    Enjoy FOSSwire's content? Have it delivered! Subscribe

    MPAA hit with DMCA takedown after GPL violation

    Ars Technica is reporting that the Motion Picture Association of America have been hit with a DMCA takedown notice after offering a download of an Ubuntu-based networking monitoring tool without source code, a direct violation of the GPL.

    The MPAA software was supposedly designed to assist universities in detecting people using software to download and share copyrighted material and was apparently based on the Ubuntu Linux distribution.

    The obvious irony here is that in trying to distribute a piece of software designed to prevent copyright infringement, the MPAA have - infringed copyright by breaking the GPL licence. Leaving that irony aside for a moment though, and it's clear that Matthew Garret, who filed the DMCA takedown on behalf of the Ubuntu team, is sending out a clear message - that GPL violation is exactly the same as violating any other copyright.

    Those who aren't fans of the free software/open source movement often cite their doubt as to whether the GPL is enforceable, especially when you are dealing with individuals rights, who don't necessarily have the legal resources to chase up all possible violators. In this case, the MPAA obviously realised that not complying was definitely not an option, as the commercial arms involved in Ubuntu (and possibly others) would have piped up and put pressure on them.

    Would this have happened with a small GPL'd project with limited resources, however, if a similar violation happened? It's not really an easy question to answer, although there are efforts such as GPL Violations to raise awareness of smaller violations of this nature.

    Enforcing the licences is definitely important. It's important to send the message out to potential exploiters that there are consequences for not following those terms.


    The AGPL Announced

    Today, the Free Software Foundation issued a press release announcing a new type of open source license: the Affero GPL (AGPL).

    Basically, the AGPL is GPLv3 with one key addition: source must be shared to network users. This means if your favorite web application were to be released under the AGPL, any changes you make to it, even if just for your website, must be published.

    Think of this hypothetical situation: You run a WordPress blog. WordPress 3.0 is released under the AGPL, and you decide to run it on your site. But, you make a modification to it. You must now publish your source code to WordPress.

    For web applications that use this, it means that any changes can easily be shared back to the main project and possibly speed up development. The only restriction is that you must publish your changes: it can be tedious to publish every revision, taking out passwords and private files, etc. In this way, it might be discouraging to webmasters to download an AGPL program, as they would have to take care of all this. Nothing is released under this license yet, so we can not see any effects for sure.