...
- Users of the open source license do not need approval from SOS for code modifications, they are free to modify the software at their will within the limits of the GNU GPL. However, SOS will not accept to add such modifications to the source code of the products if the above-mentioned processes for Requirements Management and Change Management were not considered.
- Users of the commercial license will loose warranty and support for the products if they were to modify the source code without consideration of the above-mentioned Requirements Management and Change Management processes.
Could we get maintenance
...
and support for all modified packages if they were approved by SOS GmbH?
- Yes, definitely. It is the purpose of the Change Management process that would allow us to support and to maintain such modifications.
...
- Yes, if you created Add-Ons or Extensions yourself then you will have full ownership of the results.
- Add-Ons and Extensions are independent modules that do not include code of the Open Source products. Such Add-Ons and Extensions can make use of public APIs of SOS Open Source products.
- A good example would be an Extension that makes use of the official XML interface to integrate SOS products with other applications or usage scenarios.
- A bad example would be a reporting solution that relies on the database and respective entity relationships that are used internally by the SOS product and subject to on-going change.
- Should Add-Ons and Extensions be shipped or bundled with SOS Open Source products then the respective rules of the GNU GPL for license Open Source License compliance will apply. OEM partners can bundle commercially licensed SOS products with their own products.
For your questions on the handling of code contributions and licensing please send an e-mail to: sales@sos-berlin.com