Software commands can be “Scene a Faire” in Copyright

Arista Networks successfully defended a copyright claim by Cisco based on the use of Cisco’s Command Line Interface.  The jury returned a verdict that the use was not fair use but was scènes à faire –– a copyright doctrine that has historically been applied as a defense to claims of infringement for works like books, video games, and movie scripts.  The doctrine holds that copying elements that are necessary to a genre of work is not infringement.  For instance, a western would contain a sheriff, a bad guy with a black hat, and a final showdown, and any work copying such elements would not infringe as a result.  Software lawyers have long posited that this doctrine might be applied to copying of elements of software that are standardized, so this successful invocation of the doctrine is significant.  The case may be appealed, and because the initial claims included patent claims, the Federal Circuit would hear the appeal.

Microsoft Joins Linux Foundation

In a move that would have been viewed ten years ago as hell freezing over, but seems only moderately remarkable now, Microsoft has joined the Linux Foundation.

Colorful metaphors aside, contrary to popular notions in the free software world, Microsoft has been very active in open source in recent years, including its longtime sponsorship of the Outercurve Foundation, its contributions to the Linux kernel, and its recent move to join the Eclipse Foundation.  This may give some credence to last year’s report that an open source release of Windows is possible.


WordPress Calls Out Wix for GPL Violation

On October 28, WordPress’ founder Matt Mullenweg filed a blog post admonishing Wix, a proprietary blog tools provider, for distributing some WordPress software (licensed under GPL) in Wix’ proprietary software app, and thereby violating GPL.  The tenor of the post was less a legal threat than a call to do the right thing.  He wrote,

If I were being charitable, I’d say, “The app’s editor is based on the WordPress mobile app’s editor.” If I were being honest, I’d say that Wix copied WordPress without attribution, credit, or following the license. The custom icons, the class names, even the bugs.

He went on,

I suppose we’ll take this as a compliment — I’m sure the hundreds of people who have contributed to WordPress Core and our mobile apps are flattered that you chose to build one of your company’s core features using our code. We’re also excited to see what great things you create with all the time you saved not having to write your own mobile editor.  You know what’d be even more exciting? To see you abide by the GPL and release your source code back to the community that gave you that jump start.

Wix answered with its own blog post, styled “an open letter from’s CEO Avishai Abrahami,” which sidestepped the GPL violation, saying:

[Y]ou say we have been taking from the open source community without giving back, well, of course, that isn’t true. Here is a list of 224 projects on our public GitHub page, and as you can see they are all dated before your post….

Yes, we did use the WordPress open source library for a minor part of the application (that is the concept of open source right?), and everything we improved there or modified, we submitted back as open source…If you believe that we need to give you credit, that you deserve credit, I must say, absolutely yes. You guys deserve a lot of credit, but not because of a few lines of source code, you deserve credit because you guys have been making the internet dramatically better, and for that we at Wix are big fans.

The exchange of posts set off a flurry of discussion on the Web, the gist of which was that Wix didn’t answer the allegation, along with the usual speculation, and discussion (sometimes informed, sometimes not) of whether a violation had actually occurred.

The exchange was interesting for a few reasons, beyond the legal substance of it.  GPL violations are usually open and shut cases, and this appears to be no exception.  As a threshold matter, if you include GPL code in a program, and distribute it, you have to include GPL license notices.  Laying aside what constitutes a “derivative work” subject to GPL and other such arcana, the failure to include license notices is trivial to prove.  For the most part, the only way to cure a violation of GPL in a proprietary app is to stop distributing the app, replace the GPL code, and re-release the app.  Mobile apps are generally single programs, and don’t allow for inclusion of both GPL and proprietary code — it’s all or nothing.  The other approach, of course, is to release the entire program under GPL, an approach that proprietary developers usually won’t — and sometimes can’t — take.

Then there was the social aspect of the exchange.  The initial blog post was charmingly signed, “Love, Matt and the open source community” — not your typical ending for a cease and desist letter.  And Wix’ ended “I reached out a couple of times trying to meet with you. Could I do that again here? I believe in friendly competition, and as much fun as it is to chat over the blogosphere, maybe we can also do it over a cup of coffee?”

There are many in the open source community who prefer moral suasion to legal process, to resolve compliance issues, and if there was ever an example of how to do the former, this was it.  But perhaps the soft approach led Wix down the garden path; Wix’ answer focused on perceived depredations of Wix’ morality, rather than the legal question behind the allegation, and resulted in a response which was neither legally nor substantively effective.

The next chapter in this tale is likely to be a re-release of the Wix app, but we shall see.


Not a GPL Time-Bomb

Ben Boyter’s approach to open source licensing with this “Eventually Open” license is an interesting variation on open source and proprietary licensing themes.  Boyter is initially releasing his searchcode server code under the Fair Source License for five users, but has committed to licensing his code under GPLv3, automatically, after three years from the date of publication.

For a business, committing in advance to grant a free license to all on a fixed date in the future is a bold move.  Presumably this is a self-imposed incentive for bringing out new versions, to the keep the flow of licensing revenue alive — or perhaps merely an acknowledgment that it’s impractical to charge for software that is three years old (which is about the practical lifespan of a royalty-bearing product).

This approach is reminiscent of the 2015 Transitive Grace Period Public License, which applies GPL with a grace period to comply, but works in the opposite direction.