Comments

If independent developer want to develop opensource non-profit non-commercial application with nonGPL license (and license can't be GPL for some reasons) what can be done in this situation?
I see three ways:
1. Don't use Ice at all (bad, because Ice wants to be worldwide standard, and personally I like Ice)
2. Get personal permission from from ZeroC (or buy :eek:? for non-profit project)
3. Write own subset of Ice (nonacceptable, because it is more complex task, compare to most non-profit home-made projects)

Please note that this discussion only benefits third parties that produce GPL-covered products. The Apache Software Foundation does not allow its own projects to distribute software under licenses more restrictive than the Apache License, and the Free Software Foundation does not distribute software under the Apache License.

So while we could grant permission to link certain software released under the Apache license with Ice, it would still mean that the resulting work would have to be released under GPL. You could not release your software under the
Apache license.

I got the point. I can make core part of the application, f.e. daemon, under Apache, but it shouldn't containt any Ice dependencies. Then I can make daemon extension with Ice support, and result work will be another project, f.e. daemon-ice, and this result project should be under GPL? Looks complicated. Should this work? :cool:

Yes, this works. Because of the "incompatible license" problem, we would still have to give you a "special permission" to link Ice with Apache software (like we do for OpenSSL) in the file ICE_LICENSE, but I don't see a problem with this.