[ckan-dev] Meaning of AGPL for CKAN extensions

[Ross Jones]

Hi Stefan,

> On 8 Feb 2016, at 17:22, Stefan Oderbolz <stefan.oderbolz at liip.ch> wrote:
> 
> Can someone confirm, that CKAN uses the AGPL and therefore all plugins/extensions for CKAN must be under the AGPL as well? Or is there a way to create a "closed source" CKAN extension?

Yes, CKAN is licensed under the AGPL. 

> I'm asking because I want the source code of an extension which is currently labeled "closed source". Is this possible? Does someone already have experience with this kind of situation?

I've been asking the EuropeanDataPortal about their extensions, but I just get ignored. It's frustrating, but nothing that I can do about it. You may run into the same problem.

> The way I understand the AGPL is that the source code must be made available to any user that can access the server, where the code runs (i.e. if it runs on the internet, any internet user can request the source code).

This is my understanding too.

Cheers

Ross