Ralph Goers wrote:
What about the issues with Rhino? Was the licensing issue resolved? Do we have permission to do a release with the current Rhino?
we always had.
the issues are not about *us* releasing it but by users misinterpreting the "cocoon is *all* covered by the ASF license" while only some parts of it are (rhino is not).
So, chris licensed the code he wrote under the MPL, as Rhino is. And this makes it legal to redistribute rhino for us.
for users, if they want to redistribute with their software, they have to comply to *all* the licensing restrictions that come with the software (we place them in the /legal directory).
we *do* make sure that all these licenses are mutually compatible. We always had, but from that point on it's up to you to understand what to and if your software complies and the MPL is the most tricky of those licenses, especially for IP issues.
But, let me repeat, there is nothing *illegal* in us distributing rhino. not even immoral. Neither for users, if they comply to the licensing restrictions (and due to the nature of cocoon is totally safe to assume so).
The problem was just a huge misunderstanding between some ASF directors and their lawyer's paranoia.
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
