A: The open sourcing of several of the Servoy products means that the (Java) source code has been made publicly available. This allows (Java) developers to take a peek at the code, come up with improvements, new features and fixes.
A: No, the source of the following Servoy products has been made available:
A: All Servoy products are licensed under the "Servoy Binary Code License" for commercial usage. Secondly, the source code of the Servoy Developer plugin for Eclipse, the Servoy Smart Client, Servoy Web Client and Servoy Headless Client is licences under the AGPL.
A: The open sourcing of several Servoy products does not influence the pricing model. Servoy has a free version of its product (Servoy Community Edition) that is free for non-commercial use (evaluating, testing, building free software) for up to 5 users. For commercial use Servoy offers several pricing schemes.
A: See servoy.com/pricing
A: No, Servoy offers its products under a dual license. When the "Servoy Binary Code License" is used, solutions created with Servoy can be released under any license.
A: The Servoy Community Edition allows you to develop at no cost if your product is released under AGPL. For deployment it will depend on the usage, if the usage is free and the product is non commercial, up to 5 users can use it for free. In other scnario's a commercial license is required.
If your product contributes to the Servoy community or is used by a non profit humanitarian organization it may qualify for an unlimited free usage, contact us to find if your product qualifies.
A: Servoy maintains the codebase. 3rd party developers can contribute by providing patches. See How to contribute for more information.
A: Nothing will change immediately for development and deployment with the Servoy.
A: The source is available in SVN. For details, see Setting up
A: The AGPL does not require that modifications are published, as long as they are used privately/internally. But if the modified version of the source code is used in other scenario's than private/internal use, the AGPL requires that the modified version of the source code is made publicly available.
The addition in AGPL over GPL is that this also goes for server-side usage: if the modified version is running on the server, but used in any way by any sort of client beyond personal/internal use, the modified version of the source code needs to be made publicly available as well.
The modified source code needs to be at least downloadable for anyone who wishes to do so, not restricted in any way.
A: Currently, it is not possible to get direct commit access, but we encourage developers to supply patches.
A: Yes, we encourage developers who implement new features, improvements and fix bugs to supply patches. For more information see How to contribute.
A: No, in order for your patches to be merged into the Servoy maintained source code, you are required to transfer the ownership to Servoy. For more information see How to contribute.
A: No, Servoy has added an exception within the AGPL to accommodate plugin and bean developers to release their products under any license, without conflicting with the AGPL license.
A: While all code is exposed, there is still the official public Java API that should be used from within plugins and beans. Besides that fact that the plugin/bean that relies on non-public classes/functions might break in future versions, it also would require the plugin/bean to be released under AGPL. See the public Java API here .
Under the plugin/bean section you mention a special exception added to the AGPL license. Can you please include this license in the FAQ or somewhere on the wiki?