We're developing software to work with various packages we're using or
considering in our library, including Fedora, Sakai, and other Kuali
projects. Sakai and Kuali software uses the Educational Community
License (ECL), as did Fedora 2. I see that Fedora 3 has moved to the
Apache license. The ECL appears to be the same as the Apache license,
but with slightly more limited patent grants; and it doesn't appear
to be used as often.
As we consider releasing some of our software as open source (and looking
to get university approval for this), we have some questions on the two
licenses.
-- What were the reasons for Fedora moving from ECL to Apache? Was
it simply that the Apache license is better-known, or were there
specific compatibility or patent issues, or something else?
-- Are there problems with releasing software for the Fedora community
under ECL?
(I'm presuming anything meant to be included in the Fedora repository
software release itself would need to use Apache, since that's the
agreed-on license for that software. But are there any problems
or issues with using ECL for other community-developed software meant
to be used in conjunction with Fedora, such as something that might
go in the Community Software Registry?)
-- Are there compatibility or transition problems between ECL and Apache
in the Fedora context that we should be aware of?
Thanks for any answer or pointers you might give.
John Mark Ockerbloom
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
