Aloha Editor AGPLv3 License FAQ

The following questions and answers are our personal interpretation and are not legally approved.

In short terms

You are free to

  • include Aloha Editor in AGPLv3 or GPLv3 software and ship as one package
  • include Aloha Editor in MIT, BSD or similar licensed software and ship as one package with a FOSS license exception
  • include Aloha Editor in commercial software and ship as one package
  • Use or sell services with software, where Aloha Editor is legally included

You need to publish

  • the license to users
  • changes to Aloha Editor to community as "source code" (eg. download in legal notices)
  • derived work from Aloha Editor to users as "source code" (eg. download in legal notices)

You may buy a commercial license (to support the community)

  • to support continuous development of Aloha Editor
  • if you want to sell a commercial software and don't want to publish its source code
  • if you want to provide any service using Aloha Editor and don't want to publish its source code

Our interpretation of following AGPLv3 terms regarding Javascript code

  • "source code" are all single files as in the github repository.
  • "object code" are minified, combined or any with any other method modified "source code" files
  • "derived work" are all plugins or extensions connected with Aloha Editor using the Aloha Editor API or other methods

We invite you to check http://fi.am/entry/agplv3-explained/.

Frequently asked questions and answers

1. I have server side software such as a CMS (or other software) GPLv3 licensed. Can I CHANGE OR EXTEND AND DISTRIBUTE Aloha Editor with it?

Yes, you can and we encourage you to do so. AGPLv3 and GPLv3 are compatible. See http://www.gnu.org/licenses/gpl-faq.html#v3Notwithstanding. If you modify the Aloha Editor source code or distribute derived work you need to publish the changes or the source code of the derived work AGPLv3 compatible.

2. I have server side software such as a CMS (or other software) BSD (revised), MIT, ASL or similar licensed. Can I CHANGE OR EXTEND AND DISTRIBUTE Aloha Editor with it?

Yes, you can and we encourage you to do so. You are not allowed to change the license of Aloha Editor components. If you modify the source code or distribute derived work you need to publish the changes or the source code of the derived work AGPLv3 compatible. You need a FOSS license exception to distribute Aloha Editor with BSD, MIT or similar licensed software. Eg. Locomotive CMS is MIT, Aloha Editor is AGPLv3, with the FOSS exception, Locomotive CMS can distribute Aloha Editor and remain MIT, but Aloha Editor will remain AGPLv3. Contact us to get a FOSS license exception!

3. Do I need to publish modifications to a GPLv3 server side component?

No, you do not need to publish those changes. The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization. But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL. Publishing it to the Aloha Editor project is welcomed. See http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic.

4. Do I need to publish extensions to a GPLv3 server side component?

No, you do not need to publish extensions as not needed by the GPLv3 from your server side software as long as you do not modify the software. If you modify it you may need to publish the changes depending on the GPLv3. See http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic

5. I want to use a GPLv3 licensed software, which is distributed as one package with Aloha Editor and provide a SAAS Service. Can I do that?

Yes, you can and we encourage you to do so. If you want to change the source code you need to publish changes to your users. See http://www.gnu.org/licenses/gpl-faq.html#AGPLv3CorrespondingSource or http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean. Publishing it to the Aloha Editor project is welcomed. If you don't want to publish any change think about a commercial license and support with it the continuous development of Aloha Editor.

6. I want to distribute Aloha Editor for a fee. Can I do that?

Yes, you can and we encourage you to do so. This is part of free software. See http://www.gnu.org/philosophy/selling.html.

7. I want to sell Aloha Editor along with my commercial and non open-source CMS (project) and I don't want apply to the AGPLv3. Or I just don't worry about that. Can I do that?

Yes, you can distribute Aloha Editor with your commercial project. Buy a commercial license (to support the Aloha Editor community).