...

Where can I get the source?

The source is available in SVN. For details, see [Setting up the development environment|see Setting up the development environment].

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

The AGPL does not require that modifications are published, as long as they are used privatelyused 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 for anyone who who wishes to do so, not restricted in any way.

Can I get commit access
Currently, it is not possible to get direct commit access, but we encourage developers to supply patches. 

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

If I commit patches, do I remain the owner?

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|see How to contribute].

For plugin/bean Developers

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.

Can I call every function in any class from within my plugin/bean now that the code is open source?

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. 

About the AGPL License

What does the AGPL license mean?

The AGPL licence provides provides
Why AGPL and not something else?

...