[ckan-discuss] Extension license

Sat Jul 13 21:48:18 BST 2013

Thank you Ian,

I have to say the question of a closed license was really theory, I don't
expect to go there. The question was more to know if an extension is
affected by license constrains as would be the code of the core components.
On that point, your answer seem logical. Thanks

On Fri, Jul 12, 2013 at 5:29 PM, Ian Ward <ian at excess.org> wrote:

> On Fri, Jul 12, 2013 at 3:38 PM, Stéphane Guidoin <stephane at opennorth.ca>
> wrote:
> > Hello,
> >
> > Short question about license: So CKAN is using AGPL. But does the AGPL
> also
> > applies to extension that I would build from scratch? Or can I use any
> > license I want on my extension? Even proprietary license?
> >
> > From what I've seen, the CKAN extension build by the Gov of Canada uses
> MIT
> > (https://github.com/open-data/ckanext-canada/blob/master/COPYING) so it
> > sounds like I set any license on the extension, but I wanted to check.
>
> Hello Stéphane,
>
> IANAL but my expectation is that you can only use licenses that are
> compatible with the AGPL (such as MIT), and the combination ends up
> being covered by the AGPL requirements. For a proprietary license you
> would need permission from the CKAN authors.
>
> It would be great if someone from OKFN would chime in here, of course!
>
> Ian
> (still not a lawyer)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-discuss/attachments/20130713/667847a8/attachment.htm>