Language Selection

English French German Italian Portuguese Spanish

BusyBox and Monsoon Settle Litigation with GPL Compliance Achieved

Filed under
Legal

I've just heard from the Software Freedom Law Center that the BusyBox-Monsoon Multimedia GPL-enforcement litigation has been settled on the following terms:

As a result of the plaintiffs agreeing to dismiss the lawsuit and reinstate Monsoon Multimedia's rights to distribute BusyBox under the GPL, Monsoon Multimedia has agreed to appoint an Open Source Compliance Officer within its organization to monitor and ensure GPL compliance, to publish the source code for the version of BusyBox it previously distributed on its Web site, and to undertake substantial efforts to notify previous recipients of BusyBox from Monsoon Multimedia of their rights to the software under the GPL. The settlement also includes an undisclosed amount of financial consideration paid by Monsoon Multimedia to the plaintiffs.

It was filed on September 19th, so that's a happy ending and now everyone can move on amicably. You'll notice that Monsoon had to have its GPL rights restored. It's not automatic under GPLv2.

Here's the meat of the press release:

More Here




More in Tux Machines

Android Leftovers

today's howtos

Mozilla News

  • WebExtensions in Firefox 48
  • Mozilla's WebExtensions API Is In Good Shape For Firefox 48
    Mozilla has announced that for Firefox 48 their WebExtensions API is considered to be in a stable state. They encourage developers looking to develop browser add-ons to begin using this new API. WebExtensions is an API for implementing new browser add-ons/extensions that makes it easier to port to/from other browsers, is compatible with Firefox's Electroloysis, and should be easier to work with than the current APIs. In particular, Google designed portions of the WebExtensions API around Google's Blink extension API.
  • Mozilla a Step Closer to Thunderbird Decision
    The good news is that the folks at Mozilla seem to be determined to find Thunderbird a good home where it will be able to grow and find newfound success. This isn’t surprising. As Surman pointed out in his post, the project is quite popular among those associated with the foundation — but that popularity is also contributing to the problem Mozilla has with keeping the project in-house.