www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LEGAL-50) Day spec license with addendum
Date Fri, 04 Sep 2009 04:28:57 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751298#action_12751298

Niclas Hedhman commented on LEGAL-50:

The LICENSE.txt is a bit bizarre. I have the right to sublicense an unmodified copy of the
JAR. But if I then sublicense under Apache License the next user is allowed to modify it.

I would like to be practical in this case. Clearly the "intent" from Day and the spec lead
is to try and make sure that the specification doesn't fork, yet allow any licensing terms
on the implementation. Considering that Day is just like "family", I think we safely can go
ahead. If there is something we are doing wrong, I am sure a nudge from Day will push us in
the right direction. Especially since I guess it is mostly Day employees that will be working
on this...

> Day spec license with addendum
> ------------------------------
>                 Key: LEGAL-50
>                 URL: https://issues.apache.org/jira/browse/LEGAL-50
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Jukka Zitting
> The JCR API jar file is available under the terms of the Day spec license [1] and the
addendum [2]. The essential part of the addendum says:
>     In addition to the permissions granted under the Specification
>     License, Day Management AG hereby grants to You a perpetual,
>     worldwide, non-exclusive, no-charge, royalty-free, irrevocable
>     license to reproduce, publicly display, publicly perform,
>     sublicense, and distribute unmodified copies of the Content
>     Repository for Java Technology API (JCR 1.0) Java Archive (JAR)
>     file ("jcr-1.0.jar") and to make, have made, use, offer to sell,
>     sell, import, and otherwise transfer said file on its own or
>     as part of a larger work that makes use of the JCR API.
> This is pretty much similar to the LEGAL-36 case where broad rights are given to redistribute
*unmodified* versions of the file. The consensus seems to be that such dependencies are OK
and can be embedded in binaries, but that such unmodifiable files should not be kept in our
> [1] http://www.day.com/maven/jsr170/licenses/day-spec-license.htm
> [2] http://www.day.com/maven/jsr170/jars/LICENSE.txt

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message