...
- Code modifications by users of open source licenses
- Code modifications can be submitted as feature requests to the public SourceForge Ticket System either as requests for development by SOS or as code contributions.
- Code modifications by users of commercial licenses
- Code modifications are usually effected by the SOS Development Team, not by the customer. However, we will review code contributions of customers.
- Users of commercial licenses submit their change requests to SOS. The procedure is the same for change requests that are to be developed by SOS and for code contributions of customers. The SOS Ticket System offers the issue type "Change Request". Such requests will be initially reviewed and answered by the SOS Support Team.
- Procedure for Change Requests
- If a change request is accepted during the initial review by the SOS Support Team then it will be added to the Requirements Management System.
- The process to manage requirements includes legal aspects of code submissions including compliance with our dual licensing model and technical aspects of quality of code and maintainability.
- Requirements are elaborated by the SOS Development team Team and are subject to a final review by SOS and the initiating user or customer.
- At this stage the user or customer or user will receive approval or denial for submitted change requests.
- Change requests with valid requirements are added to the public Change Management System.
- During the Release Planning period decisions are taken if change requests will be added to the next release, to a later release or will be postponed.
- Change requests based on paid development will be preferred and are assigned a fixed release date.
- Change requests that attract broader feedback from the community are equally preferred.
- If a change request is accepted during the initial review by the SOS Support Team then it will be added to the Requirements Management System.
...
- 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 Open Source License compliance will apply.
- OEM partners can bundle commercially licensed SOS products with their own products.
...