もっと詳しく

“GitHub has announced a partnership with the Stanford Law School to support developers facing takedown requests related to the Digital Millennium Copyright Act (DMCA),” reports VentureBeat:

While the DMCA may be better known as a law for protecting copyrighted works such as movies and music, it also has provisions (17 U.S.C. 1201) that criminalize attempts to circumvent copyright-protection controls — this includes any software that might help anyone infringe DMCA regulations. However, as with the countless spurious takedown notices delivered to online content creators, open source coders too have often found themselves in the DMCA firing line with little option but to comply with the request even if they have done nothing wrong. The problem, ultimately, is that freelance coders or small developer teams often don’t have the resources to fight DMCA requests, which puts the balance of power in the hands of deep-pocketed corporations that may wish to use DMCA to stifle innovation or competition. Thus, GitHub’s new Developer Rights Fellowship — in conjunction with Stanford Law School’s Juelsgaard Intellectual Property and Innovation Clinic — seeks to help developers put in such a position by offering them free legal support.
The initiative follows some eight months after GitHub announced it was overhauling its Section 1201 claim review process in the wake of a takedown request made by the Recording Industry Association of America (RIAA), which had been widely criticized as an abuse of DMCA… [M]oving forward, whenever GitHub notifies a developer of a “valid takedown claim,” it will present them with an option to request free independent legal counsel.

The fellowship will also be charged with “researching, educating, and advocating on DMCA and other legal issues important for software innovation,” GitHub’s head of developer policy Mike Linksvayer said in a blog post, along with other related programs.

Explaining their rationale, GitHub’s blog post argues that currently “When developers looking to learn, tinker, or make beneficial tools face a takedown claim under Section 1201, it is often simpler and safer to just fold, removing code from public view and out of the common good.

“At GitHub, we want to fix this.”

Read more of this story at Slashdot.