Pimcore licensing FAQ
The following translation of the CMS licensing reference material is dedicated to the pimcore project , originally from Austria. This system has already managed to be noted several years ago as the most promising Open Source-project according to the Open Source Awards 2010, and also to receive such an award as Frost & Sullivan Content Management Systems Technology Innovation Award 2016 this year.
In many ways, this document is based on similar material about licensing Drupal, but also has its own characteristics. If you would be interested to know them, read about it below.
What is pimcore license?
Pimcore and all files available on pimcore.org or on the official Git repository are available under two different licenses:
• GNU General Public License version 3 (GPLv3) license
• pimcore Corporate License (PEL) If you do not have a separate written license agreement between yourself and pimcore GmbH, then the GPLv3 license is always applicable to you.
')
This FAQ is about GPLv3 only.
<br/>
GPLv3 FAQ
What does GPLv3 mean licensed?
This means that you can freely download, use, modify and distribute any files hosted in the Git repositories on pimcore.org under a license like GPL version 3, and run pimcore to combine with any code distributed under any license that is compatible with a GPL version 3 license, such as an Affero General Public License (AGPL) version 3 license.
Does the license apply only to PHP or all?
We require that all files (PHP, Javascript, CSS, images, etc.) that are not part of a linked third-party library (see 3rd-party-licenses.md ) are available under GPLv3.
Copyright and Contributions
All pimcore contributors retain the copyright in their code, but agree to publish it under the same license as pimcore. If you are unable or unwilling to submit a patch under the terms of the GPL version 3 license and the pimcore corporate license, do not submit a patch.
I want to publish my work under a different license, not GPLv3 - is it possible?
Not. You may publish your work only under the terms of the GPL license version 3 or a later compatible license.
The GPL license requires me to distribute the “source code” of my files. What does this mean for a web application?
The “source code” of a file means a format that can be edited by a human. What this means depends on the specific file.
For PHP code, the PHP file itself without any compression or obfuscation is the source code. Note that in pimcore, controller / viewer files are PHP code. For JavaScript code, the JavaScript file itself without any compression or obfuscation is the source code. For CSS code, the CSS file itself without any compression or obfuscation is the source code. For images, the concept of "source code" is different. Depending on the image, this may mean a production version of the file, such as a PNG or GIF, or the original high-resolution JPG, or a Photoshop, Illustrator, or GIMP program file. “Source Code” means any possible version intended for human editing.
If I create a module, plugin, or custom code for my application, should I apply the GPL license to them?
Yes. Modules and plugins for Pimcore, as well as their own code for your application, are derivative works with respect to pimcore. If you distribute them, you must do so under the terms of the GPL license version 3 or later. In any case, you are not required to distribute them.
However, when you distribute your pimcore-based work, it is important to keep in mind that the GPLv3 license applies to it. The GPLv3 license for code is applied to code that interacts with code, but not data. So, the PHP code pimcore is licensed under the GPLv3 license, and therefore all PHP code that interacts with it must also be licensed under the GPLv3 license or the GPLv3-compatible license.
The images, javascript and flash files that PHP sends to the browser are not covered by the GPL, because it is data. However, pimcore JavaScript, which includes a copy of jQuery that is included with pimcore, is distributed under GPLv3, so JavaScript that interacts with pimcore JavaScript in a browser must also be distributed under GPLv3 or with a GPLv3 compatible license.
When you distribute your plugin, module, or theme, GPLv3 applies to any fragment that directly interacts with parts of pimcore, which is licensed under GPLv3. This does not apply to images you create and flash files. However, if you make a new image based on an image from pimcore, which is distributed under the terms of the GPL, then that image must also be licensed under GPLv3.
If you uploaded a module or plugin to the pimcore Git repository, then all of your work must be licensed under the terms of a GPL license version 3 or later, and you must provide their source code. This means all files in an editable format, as described above.
If I create a plugin, module or custom code for my application, should I provide it to anyone?
Not. The GPL license requires that if you create a derivative work from pimcore and distribute it to someone, you must provide the person with its source code under GPLv3 terms so that it can be modified and distributed also under GPLv3 terms. However, you are not required to distribute the code to anyone else. If you do not distribute the code, but only use it in your organization, you are not obliged to provide it to anyone.
However, if your plugin is a general purpose, it’s often a good idea to give the code to the community. You can receive feedback, error messages and patches of new functionality from other people for whom your module will be useful.
Can I sell pimcore or a plugin for pimcore or a theme for pimcore?
Yes. However, you must distribute it under the terms of the GPL license version 3 or later, so what you sell must also be available for modification and distribution. See the questions above.
Can I write a “glue module” for interaction between pimcore and another system or library?
It depends on the other system.
It is acceptable to distribute a module that communicates with a third-party system via HTTP, XML-RPC, SOAP, or another wired protocol that leaves the third-party system unaffected. Examples of such systems include Flickr, Mollom or certain dependency systems. Examples of such systems include Flickr, Mollom or certain dependency systems.
It is permissible to distribute a module that integrates with a third-party PHP or JavaScript library, for as long as the library is available under both a GPL license and a GPL-compatible license. Examples of compatible licenses include “permitting” licenses such as BSD / MIT or Lesser General Public License (LGPL). The Free Software Foundation maintains a list of popular GPL-compatible licenses.
It is not allowed to distribute a module that combines with pimcore a library distributed under a license that is not compatible with the GPL, because such a derivative work will be a derivative work from both pimcore and another library, and thus there will be a violation of both the GPL and another license libraries. Please keep in mind that this applies to some open source software licenses that for some reason are incompatible with the GPL, such as the PHP license used in most PEAR packages.
If you wish to load the linker module into the pimcore Git repository, please do not include it in the third-party library. Such an action will create a fork of such a third-party library, which will make support more difficult and only take up disk space. Instead, provide detailed instructions for users to download and install such a third-party library for use with your module. If you believe that your module is a special case that requires mandatory inclusion in the Git repository, usually only because you need to make significant modifications to its work, please post a question in the Licensing Working Group’s questions queue for an initial discussion of your question. .
Should I provide my site code to any of its visitors?
Not. The GPL license does not consider viewing the site as a “distribution” case, so you are not required to provide code that runs on your server.
I have a question to which there is no answer here. What should I do?
If you have a question about a specific case, please consult a lawyer specializing in copyright issues in your area. We cannot provide legal advice.
If you have a general question about pimcore licensing or other legal issues, please post your question in the pimcore discussion group.
Notifications / License of this manual page
This FAQ is based on www.drupal.org/licensing/faq (changed) - many thanks to the Drupal Association!
License: Creative Commons Attribution-ShareAlike license 2.0 (http://creativecommons.org/licenses/by-sa/2.0/)
_____________
approx. per. - My other CMS licensing translations:
In many ways, this document is based on similar material about licensing Drupal, but also has its own characteristics. If you would be interested to know them, read about it below.
What is pimcore license?
Pimcore and all files available on pimcore.org or on the official Git repository are available under two different licenses:
• GNU General Public License version 3 (GPLv3) license
• pimcore Corporate License (PEL) If you do not have a separate written license agreement between yourself and pimcore GmbH, then the GPLv3 license is always applicable to you.
')
This FAQ is about GPLv3 only.
<br/>
GPLv3 FAQ
What does GPLv3 mean licensed?
This means that you can freely download, use, modify and distribute any files hosted in the Git repositories on pimcore.org under a license like GPL version 3, and run pimcore to combine with any code distributed under any license that is compatible with a GPL version 3 license, such as an Affero General Public License (AGPL) version 3 license.
Does the license apply only to PHP or all?
We require that all files (PHP, Javascript, CSS, images, etc.) that are not part of a linked third-party library (see 3rd-party-licenses.md ) are available under GPLv3.
Copyright and Contributions
All pimcore contributors retain the copyright in their code, but agree to publish it under the same license as pimcore. If you are unable or unwilling to submit a patch under the terms of the GPL version 3 license and the pimcore corporate license, do not submit a patch.
I want to publish my work under a different license, not GPLv3 - is it possible?
Not. You may publish your work only under the terms of the GPL license version 3 or a later compatible license.
The GPL license requires me to distribute the “source code” of my files. What does this mean for a web application?
The “source code” of a file means a format that can be edited by a human. What this means depends on the specific file.
For PHP code, the PHP file itself without any compression or obfuscation is the source code. Note that in pimcore, controller / viewer files are PHP code. For JavaScript code, the JavaScript file itself without any compression or obfuscation is the source code. For CSS code, the CSS file itself without any compression or obfuscation is the source code. For images, the concept of "source code" is different. Depending on the image, this may mean a production version of the file, such as a PNG or GIF, or the original high-resolution JPG, or a Photoshop, Illustrator, or GIMP program file. “Source Code” means any possible version intended for human editing.
If I create a module, plugin, or custom code for my application, should I apply the GPL license to them?
Yes. Modules and plugins for Pimcore, as well as their own code for your application, are derivative works with respect to pimcore. If you distribute them, you must do so under the terms of the GPL license version 3 or later. In any case, you are not required to distribute them.
However, when you distribute your pimcore-based work, it is important to keep in mind that the GPLv3 license applies to it. The GPLv3 license for code is applied to code that interacts with code, but not data. So, the PHP code pimcore is licensed under the GPLv3 license, and therefore all PHP code that interacts with it must also be licensed under the GPLv3 license or the GPLv3-compatible license.
The images, javascript and flash files that PHP sends to the browser are not covered by the GPL, because it is data. However, pimcore JavaScript, which includes a copy of jQuery that is included with pimcore, is distributed under GPLv3, so JavaScript that interacts with pimcore JavaScript in a browser must also be distributed under GPLv3 or with a GPLv3 compatible license.
When you distribute your plugin, module, or theme, GPLv3 applies to any fragment that directly interacts with parts of pimcore, which is licensed under GPLv3. This does not apply to images you create and flash files. However, if you make a new image based on an image from pimcore, which is distributed under the terms of the GPL, then that image must also be licensed under GPLv3.
If you uploaded a module or plugin to the pimcore Git repository, then all of your work must be licensed under the terms of a GPL license version 3 or later, and you must provide their source code. This means all files in an editable format, as described above.
If I create a plugin, module or custom code for my application, should I provide it to anyone?
Not. The GPL license requires that if you create a derivative work from pimcore and distribute it to someone, you must provide the person with its source code under GPLv3 terms so that it can be modified and distributed also under GPLv3 terms. However, you are not required to distribute the code to anyone else. If you do not distribute the code, but only use it in your organization, you are not obliged to provide it to anyone.
However, if your plugin is a general purpose, it’s often a good idea to give the code to the community. You can receive feedback, error messages and patches of new functionality from other people for whom your module will be useful.
Can I sell pimcore or a plugin for pimcore or a theme for pimcore?
Yes. However, you must distribute it under the terms of the GPL license version 3 or later, so what you sell must also be available for modification and distribution. See the questions above.
Can I write a “glue module” for interaction between pimcore and another system or library?
It depends on the other system.
It is acceptable to distribute a module that communicates with a third-party system via HTTP, XML-RPC, SOAP, or another wired protocol that leaves the third-party system unaffected. Examples of such systems include Flickr, Mollom or certain dependency systems. Examples of such systems include Flickr, Mollom or certain dependency systems.
It is permissible to distribute a module that integrates with a third-party PHP or JavaScript library, for as long as the library is available under both a GPL license and a GPL-compatible license. Examples of compatible licenses include “permitting” licenses such as BSD / MIT or Lesser General Public License (LGPL). The Free Software Foundation maintains a list of popular GPL-compatible licenses.
It is not allowed to distribute a module that combines with pimcore a library distributed under a license that is not compatible with the GPL, because such a derivative work will be a derivative work from both pimcore and another library, and thus there will be a violation of both the GPL and another license libraries. Please keep in mind that this applies to some open source software licenses that for some reason are incompatible with the GPL, such as the PHP license used in most PEAR packages.
If you wish to load the linker module into the pimcore Git repository, please do not include it in the third-party library. Such an action will create a fork of such a third-party library, which will make support more difficult and only take up disk space. Instead, provide detailed instructions for users to download and install such a third-party library for use with your module. If you believe that your module is a special case that requires mandatory inclusion in the Git repository, usually only because you need to make significant modifications to its work, please post a question in the Licensing Working Group’s questions queue for an initial discussion of your question. .
Should I provide my site code to any of its visitors?
Not. The GPL license does not consider viewing the site as a “distribution” case, so you are not required to provide code that runs on your server.
I have a question to which there is no answer here. What should I do?
If you have a question about a specific case, please consult a lawyer specializing in copyright issues in your area. We cannot provide legal advice.
If you have a general question about pimcore licensing or other legal issues, please post your question in the pimcore discussion group.
Notifications / License of this manual page
This FAQ is based on www.drupal.org/licensing/faq (changed) - many thanks to the Drupal Association!
License: Creative Commons Attribution-ShareAlike license 2.0 (http://creativecommons.org/licenses/by-sa/2.0/)
_____________
approx. per. - My other CMS licensing translations:
Source: https://habr.com/ru/post/318772/
All Articles