Is osDXP Open Source
Is osDXP Open Source?
Yes, the license under which the osDXP software is released is the GPLv2 (or later).
The license under which the osDXP software is released is the GPLv2 (or later) from the Free Software Foundation. A copy of the license is included with every copy of osDXP, but you can also read the text of the license here.
It was very important for the osDXP project to be an Open Source project and be created with the input of many members of the Open Source community. To get osDXP started, several companies came together to lay the initial groundwork for the project. These Open Source companies work together in Github and osDXP Slack. We are encouraging more companies and individuals focused on the Enterprise space to get involved, give feedback and participate!
Additional Licencing Questions:
If I write a module or theme, do I have to give it away to everyone?
No. The GPL requires that if you make a derivative work of osDXP and distribute it to someone else, you must provide that person with the source code under the terms of the GPL so that they may modify and redistribute it under the terms of the GPL as well. However, you are under no obligation to distribute the code to anyone else. If you do not distribute the code but use it only within your organization, then you are not required to distribute it to anyone at all.
Is osDXP going to move to GPL version 3?
Because osDXP is licensed under the GPL version 2 or later, osDXP may be distributed under GPL version 3. At this time, a working group is being assembled to looking into a possible migration to GPL version 3 in future releases.
Do I have to give my web site's code to anyone who visits it?
No. The GPL does not consider viewing a web site to count as "distributing", so you are not required to share the code running on your server.
Is an agency, or service provider 'distributing code' on behalf of a client when under contract?
No, an agency, freelancer, or other service provider is acting as the customer's agent when assembling a code base, and not distributing the code in the sense intended by the GPL. Therefore service providers can use GPL code together with GPL-incompatible code for a client, but cannot redistribute that code to the public.
If I write a module or theme, do I have to give it away to everyone?
No. The GPL requires that if you make a derivative work of WordPress or the osDXP and distribute it to someone else, you must provide that person with the source code under the terms of the GPL so that they may modify and redistribute it under the terms of the GPL as well. However, you are under no obligation to distribute the code to anyone else. If you do not distribute the code but use it only within your organization, then you are not required to distribute it to anyone at all.
If I write a module or theme, do I have to license it under the GPL?
Yes. WordPress and/or osDXP Plugins, modules, and themes are a derivative work of WordPress/osDXP. If you distribute them, you must do so under the terms of the GPL version 2 or later. You are not required to distribute them at all, however.
However, when distributing your own WordPress and/or osDXP based work, it is important to keep in mind what the GPL applies to. The GPL on code applies to code that interacts with that code, but not to data. That is, WordPress and/or osDXP PHP code is under the GPL, and so all PHP code that interacts with it must also be under the GPL or GPL compatible. Images, JavaScript, and Flash files that PHP sends to the browser are not affected by the GPL because they are data. However, WordPress and/or osDXP's JavaScript, including the copy of jQuery that is included with WordPress and/or osDXP, is itself under the GPL as well, so any Javascript that interacts with WordPress and/or osDXP's JavaScript in the browser must also be under the GPL or a GPL compatible license.
When distributing your own plugin, module, or theme, therefore, the GPL applies to any pieces that directly interact with parts of WordPress and/or osDXP that are under the GPL. Images and Flash files you create yourself are not affected. However, if you make a new image based off of an image that is provided by WordPress and/or osDXP under the GPL, then that image must also be under the GPL.
If you commit that module or theme to a WordPress and/or osDXP Git repository, however, then all parts of it must be under the GPL version 2 or later, and you must provide the source code. That means the editable form of all files, as described above
The GPL requires that any recipients of a program receive its "source code". What does that mean for a web application?
The "source code" of a file means the format that is intended for people to edit. What that means depends on the file in question.
- For PHP code, the PHP file itself, without any compression or obfuscation, is its own source code. Note that for WordPress and/or osDXP, template files are PHP code.
- For JavaScript code, the JavaScript file itself, without any compression or obfuscation, is its own source code.
- For CSS code, the CSS file itself, without any compression or obfuscation, is its own source code.
- For images, the "source code" varies. Depending on the image, that could mean the production version of the file as a PNG or GIF, or an original high-resolution JPG, or a Photoshop, Illustrator, or GIMP file. The "source code" is whichever version is intended to be edited by people.
- For Flash files, the source code is the editable FLA and AS files, and any other files needed to build the final SWF. The SWF file itself is the "object code" version, not the source version.
-
- Articles coming soon