One excuse gone. 99 to go.
At 06:34 5/1/2005, Mark Womack wrote:
Starting a thread specific to the licensing issue.
Echoing Curt's concerns related to the 1.2.10 release, I told Ceki privately that we (LS PMC) would need to understand the licensing issues around slf4j as part of any approval of any release that included it, and it would need to be explained/pointed out to the ASF board as part of the approval process. Most folks did not see the reply to Ceki's query to [EMAIL PROTECTED] on this issue. I am including the latest response below. This is the most direct response I have ever seen related to a license issue in almost 2 years of being an ASF member.
Also, I want to make it clear that I do not have a real problem with the slf4j being an "outside" project and under a different license. I hear what Simon and Jake are saying about the clarity of independence and a more "compatible" license. I'm not sure what other groups have these concerns or issues, but if slf4j feels it is that important and has this as a goal, then go for it.
In any case, it does not appear that the board will have any issue with the slf4j license.
-Mark
----- Original Message ----- From: "Daniel Quinlan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, April 29, 2005 3:37 PM Subject: Re: Importing X11 licensed code
Ceki Gülcü <[EMAIL PROTECTED]> writes:
Come to think of it, I think the answer to my earlier question is pretty obvious. Since we have the right to distribute X11-licensed code in one of our distributions, it's fairly obvious that we can also place the same code in our CVS. Or am I missing something?
[1] http://www.slf4j.org/license.html
That license is compatible with ours, you can include it in your source tree and even place your modifications under the Apache License so the derivative source would be covered by both licenses. However, I'm not sure if any sort of approval would be needed for a project to continue using only the original license for an ASF-derivative version.
Maybe we should begin documenting our own internal compatibility guide on licenses for PMCs to follow?
Daniel
-- Daniel Quinlan http://www.pathname.com/~quinlan/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
