AnsweredAssumed Answered

Extensions licensing issue for Alfresco CE

Question asked by wvictor on Aug 21, 2008
Latest reply on Aug 26, 2008 by sbuckle

This is our situation:
We are developing a system that uses Alfresco in two ways:
1. Java client running separately, remotely communicating with an Alfresco repository using the functions in alfresco-web-service-client.jar. The client is used as a back end to automatically add content to the repository.
2. An extension to the Alfresco Web Client to view nodes created by [1] above, implemented using custom XML, JSP, and Java class files. These reside on top of Alfresco, and do not modify any of the files shipped with the standard CE distribution - files reside in the 'extension' subdirectories created using a ZIP file as described in

We are developing this software for a specific client, who will own the entire project (applications, source, IP) once completed. The client then plans on distributing the EXTENSIONS defined in [1] and [2] above as part of a proprietary content automation package. As far as the applications in question go, the source for two functions (about 15 lines of code) need to remain closed. This is due to a class included from the API of a commercial Java library (purchased by our client) being used in a very specific way.

Money will not be charged for Alfresco in itself, since that is not what he will be selling. Clients will be free to use their own installation of Alfresco, or ask our client, or an Alfresco partner, to do an installation.

My question: His clients should have the choice between using Alfresco CE or EE - bigger clients will obviously want the QA and support that comes with EE, while some small businesses will not be able to afford it. What are the legal implications of running our (closed source) solution in locations where Alfresco CE is being used? Should our entire system suddenly conform to the GPL?