SpringSource dm Server Licensing FAQ

Why is SpringSource using the General Public License (GPL) for the SpringSource dm Server?

The GPL is the most widely used open source software license by a huge margin. Some statistics:

  • 62.8% of projects tracked on freshmeat are GPL
  • As of November 2003 71% of projects on SourceForge were GPL

The GPL is well understood by the market and the legal community and has notable precedents such as MySQL, Java and the Linux kernel as GPL licensed projects. The GPL ensures that the software remains open and that companies do not take our products and sell against us in the marketplace. If this happened, we would not be able to sufficiently invest in the project and everyone would suffer.

Does the GPL force me to release my own code if I run it on the SpringSource dm Server?

No. GPL requirements are only triggered upon distribution of code. Under the terms of the GPL, you are only required to release software under GPL if

  • You distribute (the GPLv3 uses the word “convey”) the software. This is clarified and narrowed in GPLv3 which specifically states that “mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.” AND
  • You modify the software or create a “derivative work”. The definitions for modification and derivative works can be complicated and should be reviewed by legal counsel.

For the vast majority of organizations who do not distribute their software, the GPL has no impact. This is not legal advice from SpringSource, and you should seek competent legal counsel to best guide you in this matter.

What if we distribute software to customers?

Under the GPL, if you intend to distribute GPL-licensed code to your customers as part of other software you have created, you may, depending on the software you have created, be required to GPL that code. Companies that wish to distribute the SpringSource dm Server have the option of purchasing a commercial license from SpringSource. A commercial license would not have GPL obligations.

Which version of the GPL are you using?

GPLv3

Our company has a policy against use of GPL software. What should I do?

We would first encourage you to communicate that version 3 of the GPL may make it acceptable to your organization. Second, you always have the option of purchasing a subscription to our Enterprise versions which are licensed under a commercial license. This way you can use the SpringSource dm Server if you have concerns with the GPL.

If the GPL and the Eclipse Public License (EPL) are incompatible, how is it possible for SpringSource to license the Application Platform under GPL when EPL-licensed modules are utilized by the dm Server?

When you download the dm Server, portions of the platform are licensed to you by SpringSource under the GPL, while the Eclipse modules utilized by the platform are licensed to you under the EPL. This practice of using different open source licenses for different components is common. Anyone wishing to redistribute, rather than simply use the SpringSource dm Server and/or applications which run on the platform, should consult with legal counsel to determine the implications of such redistribution or take out a commercial license with SpringSource.

Do you intend to change the licensing for the Spring Framework?

The Spring Framework is licensed under the Apache Software License. This will not change.