Yesterday marks three years that I have been trying to negotiate a peaceful settlement with my ex-employees, Karen Sandler and Bradley Kuhn, of various complaints SFLC and I have about the way they treat us. After all this time when they would not even meet with us to discuss our issues, the involvement of the Trademark Trial and Appeals Board in one aspect of the matter has at least created a space for structured discussion. Intermediaries both organizations work with and trust have generously taken the opportunity to communicate our settlement proposals, and we have initiated discussion through counsel. As transparency is, indeed, a valued commitment in the free software world, we think it is now time to publish our offer:
Today a coalition of major companies—led by Red Hat and including Google, IBM and Facebook—who create, modify and distribute FOSS under copyleft licenses have committed to the use of GPLv3’s approach to license termination for all their works published under the terms of GPLv2 and LGPLv2.1. Following last month’s statement to similar effect by the developers of the Linux kernel, the world’s most widely-used GPLv2 program, today’s announcement establishes a broad consensus in favor of the “notice and cure period” approach to first-time infringement issues that Richard Stallman and I adopted in GPLv3 more than a decade ago. This adoption of GPLv3’s approach for GPLv2 programs is an enormously important step in securing the long-term viability of copyleft licensing. All computer users who wish to see their rights respected by the technology they use are better off.
On Friday, while we were putting on our annual conference at Columbia Law School, a puff of near-apocalyptic rhetoric about us was published by SFLC’s former employees, Karen Sandler and Bradley Kuhn, who now manage the Conservancy, which was originally established and wholly funded by SFLC, and still bears our name. We were busy with our conference when this happened, which seems to have been the point. We are glad to have the chance now, after a little much-needed rest, to help everyone avoid unnecessary hyperventilation.
The US Internal Revenue Service has ushered in a new and much more favorable treatment for free software projects seeking to have 501c3 tax exempt non-profit organizations of their own. After years of suffering from a specially prejudicial environment at IRS, free software projects—particularly new projects starting out and seeking organizational identity and the ability to solicit and receive tax-deductible contributions for the first time—can now do so much more easily, and with confident expectation of fast, favorable review. For lawyers and others counseling free software projects, this is without question “game-changing.”
On 21-23 June 2016, Ministers and stakeholders gathered in Cancún, Mexico, for an OECD Ministerial Meeting on the Digital Economy: Innovation, Growth and Social Prosperity, to move the digital agenda forward in four key policy areas foundational to the growth of the digital economy. Our Legal Director, Mishi Choudhary represented the United States civil society at the OECD Ministerial Panel on The Economic and Social Benefits of Internet Openness, chaired by the Canadian Minister of Innovation, Science, and Economic Development Hon’ble Navdeep Singh Bains.
There has been much recent controversy concerning the relationship between the Linux Foundation and “community,” or non-commercial organizations in the world of free software. I’ve been somewhat confused by the dynamics of that conversation, which has spilled out from private mailing lists into the public eye occasionally, and I have found it useful in clarifying my own views to state my thoughts on the subject, which I’ve now decided to share.
Questions have arisen about the possible effect of Article 14.17 of the Trans-Pacific Partnership agreement. SFLC’s analysis shows that Article 14.17 has no adverse effects on free software licensing, distribution, or government acquisition.
There has been a growing interest among Free and Open Source Software (“FOSS”) projects in the use of crypto-currencies such as Bitcoin and its myriad derivatives (hereinafter “Bitcoin”). However, uncertainty over the treatment of these currencies by US law has dissuaded developers from from using Bitcoin. This post provides some general guidance on the legal consequences of using such convertible virtual currency.
We’ve been watching with great interest this week as the travails of FOSS organizations with the US Internal Revenue Service have become a hot topic. When our client, Jim Nelson of Yorba, discussed blogging about the IRS rejection of Yorba’s application for 501c3 status with us, we hoped but did not expect that the situation, to which we had discreetly called community and company attention for years, would finally receive some. We’re very glad that’s now happening. Unfortunately, it’s really too late. Because of the long delays in determination imposed by the IRS in its increasingly anti-FOSS positioning, neither the full consequences of the IRS’s present position nor the state of our legal technology in response can be seen from the materials currently under discussion.