John Mark Ockerbloom wrote:
> 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?
>
>   
Primarily because of familiarity outside the educational community.  As 
you noted the licenses are
the same except for the patent statement which can be interpreted as "we 
can't tell you about what
we don't know about."
>     -- Are there problems with releasing software for the Fedora community
>           under ECL?
>   
None that I am aware.  ECL is a very compatible license for this purpose.
>         (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?)
>
>   
Not all included products need to be Apache 2 if they are used properly 
within the terms of their license.
However, it simplifies things if an "open open" license like Apache2, 
ECL, BSD and others are used.
The Fedora documentation contains an itemized list of products 
incorporated in our distribution
and their licenses.  Fedora Commons (Duraspace) can only issue a license 
on software which they hold
the intellectual property rights but can incorporate or distribute 
community-developed products with
compatible licenses or where permission is granted.  Note: I am not 
qualified to provide a legal opinion
but this is my current understanding.

It makes it easier to obtain authorization from the legal offices of 
users if software in FC distributions
are provided under an "open open" license and ECL is very good even if 
it less familiar than Apache.

Please make a distinction between software which Fedora 
Commons/Duraspace registers and software which
Fedora Commons/Duraspace distributes. There are products in the registry 
which are issued under various licenses
but only a small number which FC distributes; most of the products are 
distributed by their owners.  Using
an open-open license provides the maximum flexibility for the community, 
including FC, to bundle software and
is encouraged.
>     -- Are there compatibility or transition problems between ECL and Apache
>         in the Fedora context that we should be aware of?
>
>   
None that I am aware.
> 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
>   

-- 
Daniel W. Davis
Cornell University
Fedora Commons Affiliate
http://fedora-commons.org
[email protected]



------------------------------------------------------------------------------
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

Reply via email to