So, in this case the free commercial license would be the only option. I have been working on an AGPL Clojure interface to Neo4j (but it's a bit out of date at the moment). There are other forks licensed in public domain. It seems that licensing them under something else then AGPL is strictly speaking illegal? However, AGPL prevents the ones who purchase a commercial license from using the interface. I suppose another license would be needed for that. A bit unpractical situation.
m. Craig Taverner [[email protected]] kirjoitti: > I believe that according to the spirit of the GPL/AGPL (and perhaps the > letter too), the correct implementation of option one would require writing > an alternative to Neo4j. Someone else mentioned 'glue code'. In principle > your application should be able to do its job (or at the very least start up > and run) without Neo4j, and then the user would download and install Neo4j > themselves to achieve an 'upgrade'. > > Exactly what the glue code is, or the alternative to Neo4j is, depends on > your application. If the application only uses Neo4j for some limited > features, perhaps it is good enough to just not have those features work. > But if a graph database, or graph data model, is central to your > applications purpose, then you probably need an alternative to neo4j for a > distributable open source release. > > I am not a lawyer, and I might be entirely wrong here, but I have a strong > suspicion that distributing an application that cannot work at all, until > the user downloads and installs the Neo4j component, would not pass muster. > > (P.S. all of the above is assuming the embedded Neo4j, and therefor > 'linking' to Neo4j). > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
