Child pages
  • Open Source FAQ

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The open sourcing of several of the Servoy products means that the (Java) sourcecode source code has been made publicly available. This allows (Java) developers to take a peak at the code, come up with improvements, new features and fixes.

Is the entire codebase of Servoy made Open Source?
No, the source of the following Servoy products has been made available:

  • Servoy Developer plugin for Eclipse
  • Servoy Smart Client
  • Servoy Web Client
  • Servoy Headless Client

Under which license is Servoy is now open source. Does that mean I can licensed?

Servoy is licensed under the "Servoy Binary Code License". 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.

Does open source mean I can now use it for free?

The open sourcing of several Servoy products doesn't make it a free product, it means that the sourcecode is made publicly available. In order to use the Servoy product, licences are still required, except for the Community Edition.. For both development and deployment with Servoy, the Servoy Application Server is required, which is available under the "Servoy Binary Code License".  

Where can I find more information on the Licence Model Pricing Models for Servoy products?

See servoy.com/licensing????pricing

Servoy is open sources under AGPL. Does that mean I have to release my product developed in Servoy under AGPL as well?

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

Can I use Servoy for free if I release my product developed in Servoy under AGPL as well?

No, ...

Under which open source license has the sourcecode been released? 

AGPL

I'm a plugin/bean developer: Do I have to release my plugins and beans under AGLP now as well?

No* *currently to develop or deploy with Servoy, the Servoy Application Server is required, which is not available under AGPL

Who maintains the sourcecode?

Servoy maintains the codebase. 3rd party developers can contribute by providing patches. See How to contribute for more information.

If I make changes to the sourcecode, do I have to 

For Developers

What are my obligations if I modify the sourcecode source code and use it?

The AGPL does not require that modified versions modifications are releasedpublished, 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 AGLP required AGPL requires that the modified version of the source code is made publicly available. 

...

The modified source code needs to be at least downloadable for anyone who wishes to do so, not restricted in any way.

For Servoy Customers

About the AGPL License

What does the AGPL license mean?
Why AGPL and not something else?

Source

Are solutions created with Servoy Developer 

I'm a plugin/bean developer: Do I have to release my plugins and beans under AGLP now as well?

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 

Where can I get the source?
The source is available in SVN. For details, see see [Setting up the development environment|Setting up the development environment].

Can I get commit access
Currently, it is not possible to get direct commit access, but we encourage developers to supply patches, see Setting up the development environment.

Can I contribute patches for bugs and/or new feature implementations?
Yes, we encourage developers who implement new features and fix bugs to supply patches. For more information see see [How to contribute|How to contribute].

About the AGPL License

What does the AGPL license mean?
Why AGPL and not something else?

Source

----------------------
Open Source with commercial plugins
Credits for patches