You are viewing a plain text version of this content. The canonical link for it is here.
Posted to license@apache.org by Dalibor Topic <ro...@kaffe.org> on 2003/11/17 03:17:23 UTC
A few comments on the proposed TCK license
Hi all,
you can find my comments below the text of the license sections I
commented on.
=====================================================================
== DO NOT PANIC! This is a draft for discussion purposes only. ==
== It has not yet been approved. It does not yet apply to any ==
== software distributed by the Apache Software Foundation. ==
== ==
== This TCK version is for use by JSR-defined projects releasing ==
== an official TCK for a JSR under JSPA 2.5. ==
==================================+==================================
Apache TCK License
Version 1.0, October 2003
http://www.apache.org/licenses/
Copyright (C) 2003 The Apache Software Foundation.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
TERMS AND CONDITIONS
FOR USE, REPRODUCTION, DISTRIBUTION, AND MODIFICATION
1. Licensing the Work.
A. These terms and conditions for use, reproduction, distribution,
and modification (the "License") apply to any original work of
authorship (the "Work") containing a notice placed by the
copyright owner (the "Licensor") indicating that the Work is
licensed under the Apache TCK License, Version 1.0.
B. The Work is distributed by the Licensor as a Technology
Compatibility Kit (TCK), the suite of tests, tools, and
documentation that allows an implementor of a Specification to
determine if their implementation is compliant with that
Specification, where the Specification is a current or proposed
industry standard defined by one or more documents listed within
I think "industry standard" is a little far fetched, unless Apache Software
Foundation starts providing TCKs for standards proposed by
standardization bodies. Sun's desire to promote their APIs as an "industry
standard", a meaningless term unless we are talking about ISO, ECMA or
ANSI, shouldn't result in marketing speak polluting the license.
the license notice; each such Specification is identified by
title, revision label (or date if no label has been assigned),
and Uniform Resource Identifier.
2. You. "You" or "Your" means an individual or legal entity
exercising permissions granted by this License. By exercising any
of the permissions granted to You in Sections 4 through 9 herein,
You indicate Your acceptance of this License and all of its terms
and conditions.
3. Contributors and Contributions.
A. The Licensor and any individual or legal entity that
voluntarily submits to the Licensor a Contribution to the Work are
collectively addressed herein as "Contributors". For legal
entities, the entity making a Contribution and all other entities
that control, are controlled by, or are under common control with
that entity are considered to be a single Contributor. For the
purposes of this definition, "control" means (i) the power, direct
or indirect, to cause the direction or management of such entity,
whether by contract or otherwise, or (ii) ownership of fifty
percent (50%) or more of the outstanding shares, or
(iii) beneficial ownership of such entity.
Beside the obvious philosophical dicussion about how much in charge a
person is about their actions ("The devil made me contribute!"), this
paragraph's vague definition of control under (1) doesn't seem to make
much sense. I can make someone read this comment by posting it to the
mailing list, therefore I'm in control of that person because I
used my indirect power to directed the person to read using
"otherwise" means aka as posting? ASF, all your code belongs to me ;)
It's not obvious why that piece of legalese is in the license.
B. A "Contribution" is the original version of the Work and any
modification or addition to the Work that has been submitted for
inclusion in the Work, where such modifications and/or additions
to the Work originate from that particular Contributor, or from
some entity acting on behalf of that Contributor.
C. A Contribution is "submitted" when any form of electronic,
verbal, or written communication is sent to the Licensor,
including but not limited to communication on electronic mailing
lists, source code control systems, and issue tracking systems
that are managed by, or on behalf of, the Licensor for the purpose
of discussing and improving the Work, but excluding communication
that is conspicuously marked or otherwise designated in writing by
the Contributor as "Not a Contribution."
How does one designate verbal communication in writing? An attempt to
be overly broad, yet so limited. Basically, anything you tell us
belongs to us, nyah nyah nyah.
There are situations imaginable where I could tell ASF about A, but
would have no right to contribute A to the ASF without being the
copyright holder. The 'ours by default' claim hidden in this license
may get in you trouble when you get lax on checking if people are
actually allowed to contribute the content of the conversation.
Example: During the discussion of a TCK test someone brings up an
excerpt from a regression test in Kaffe's regression test suite. ASF
can according to their license claim it as a contribution, and add it
to their TCK. If the TCK license turns out to be GPL incompatible, who
do I sue for copyright infringement: the ASF for violating the license
of my code, or the person that cited the code on an ASF mailing list?
D. Any Contribution submitted by You to the Licensor shall be
under the terms and conditions of this License, without any
additional terms or conditions, unless You explicitly state
otherwise in the submission.
4. Contributor Grant of License. Subject to the terms and conditions
of this License, each Contributor hereby grants to You:
(a) a perpetual, non-exclusive, worldwide, fully paid-up, royalty
free, irrevocable copyright license under its licensable
copyrights in the Work to reproduce, prepare derivative works
of, publicly display, publicly perform, sublicense, and
distribute the Work and such derivative works; and,
(b) a perpetual, non-exclusive, worldwide, fully paid-up, royalty
free, irrevocable (subject to Section 5) patent license to
make, have made, use, offer to sell, sell, import, and
otherwise transfer the Work and derivative works thereof,
where such license applies only to those patent claims
licensable by such Contributor that are necessarily infringed
by their Contribution alone or by combination of their
Contribution with the Work to which such Contribution was
submitted by the Contributor.
No assurances are provided by any Contributor that the Work does
not infringe the patent or other intellectual property rights of
any other entity. Each Contributor disclaims any liability to You
for claims brought by any other entity based on infringement of
intellectual property rights or otherwise. You assume sole
responsibility to secure any other intellectual property rights
needed, if any.
5. Reciprocity. If You institute patent litigation against a
Contributor with respect to a patent applicable to software
(including a cross-claim or counterclaim in a lawsuit), then any
patent licenses granted by that Contributor to You under this
License shall terminate as of the date such litigation is filed.
In addition, if You institute patent litigation against any entity
(including a cross-claim or counterclaim in a lawsuit) alleging
that the Work itself (excluding combinations of the Work with
other software or hardware) infringes Your patent(s), then any
patent licenses granted to You under this License for that Work
shall terminate as of the date such litigation is filed.
6. Redistribution without Modification. You may reproduce and
distribute verbatim copies of the Work as You received it, in any
medium, provided that You conspicuously publish on each copy an
appropriate copyright notice and disclaimer of warranty, keep
intact all of the notices that refer to this License and to the
absence of any warranty, and give any other recipients of the Work
a copy of this License along with the Work.
7. Redistribution with Modification. You may modify Your copy or
copies of the Work or any portion of it, thus forming another work
product based on the Work (a "Derivative Work"), and reproduce and
distribute such modifications or the Derivative Work, provided
that You also meet the following conditions:
(a) You must give any other recipients of the Derivative Work a
copy of this License along with the Derivative Work.
(b) You must retain, in the source code of any Derivative Work
that You distribute, all copyright, patent, or trademark
notices from the source code of the Work, excluding those
notices that only pertain to portions of the Work that have
been excluded from the Derivative Work. If the Work includes a
"NOTICE" file as part of its source code distribution, the
Derivative Work must include a readable copy of the notices
contained within that NOTICE file, excluding those notices
that only pertain to portions of the Work that have been
excluded from the Derivative Work, in at least one of the
following places: within a NOTICE file distributed as part of
the Derivative Work; within the source code or documentation,
if provided along with the Derivative Work; or, within a
display generated by the Derivative Work, if and wherever such
third-party notices normally appear. You may add Your own
notices alongside or as an addendum to the original NOTICE
information. The contents of the NOTICE file are for
informational purposes only and do not modify the terms and
conditions of this License.
(c) You must cause any modified files to carry prominent notices
stating that You changed the files.
(d) You must do one of the following:
(1) remove from the Derived Work all tests that are specific
to features of the Specification and all documentation
describing the Specification and those specific tests; or
(2) cause the Derived Work to be clearly and conspicuously
labeled as "not the official TCK for the Specification"
and "for research purposes only", and clearly and
conspicuously identify within the documentation and
packaging of the Derived Work that it is not the official
TCK for the Specification, and further that passing the
tests in the Derived Work does not indicate that an
implementation has passed the TCK for the Specification.
I am not sure I parse that correctly: does that mean I can do (1) such
that I take a TCK, remove everything that refers to the specification,
and redistribute it as "The real TCK" without any labelling? Cute.
The restrictions on the labeling may make the TCK license GPL
incompatible. Other restrictions, like the clause that only if you pass
the original TCK you can say that you passed it, may give the original
contributor a lot of power to close out competing implementations by
including references to code outside the specification in the TCK.
Example: If A wanted to make sure their competition wouldn't be able to
pass a TCK, all they need to do would be to put in a test case that
links to some internal, unspecified class from their implementation (say
an com.a.internal.* class). I see no protection against the licensee
using the TCK as a means to prevent competition instead of encouraging
it in the proposed license.
The license should in my opinion require that the code covered by it is
always completely runnable and buildable within the specified framework,
or referenced frameworks within the specification, or with code provided
alongside the TCK under a compatible license.
cheers,
dalibor topic
Re: A few comments on the proposed TCK license
Posted by Brian Behlendorf <br...@collab.net>.
On Mon, 17 Nov 2003, Dalibor Topic wrote:
> Brian Behlendorf wrote:
>
> >>Example: If A wanted to make sure their competition wouldn't be able to
> >>pass a TCK, all they need to do would be to put in a test case that
> >>links to some internal, unspecified class from their implementation (say
> >>an com.a.internal.* class). I see no protection against the licensee
> >>using the TCK as a means to prevent competition instead of encouraging
> >>it in the proposed license.
> >
> >
> > Your example is somewhat bogus - a TCK for a standard that tests for
> > classes outside that namespace would not be acceptable to Apache. It
> > would be a broken project. Because the source code is published, it's
> > easy to find such bogusness.
>
> I'm not saying tests, I'm saying "links to", i.e. uses classes outside
> of the namespace. It obviously has to for TCKs outside the java.lang
> namespace in order to include java.lang.Object. ;)
OK, I understand. I still think that the normal processes by which the
code is developed at Apache (or any other open source project) would be
able to identify such mistakes (intentional or otherwise) and call them
out as bugs needing to be fixed. Much more so than the current situation,
where TCKs are created by a single company and often not available in
source code form.
> It may be possible to publish a TCK that requires a third party
> component to run which is either unspecified, so that it can not be
> recreated freely (a sun.* class, for example), or encumbered by a
> non-free/non-ASL2-compatible license.
I think the same answer applies here, though there's no guarantee anyways
that non-free software would be required. E.g., there could be a JSR A
that depends on another JSR B, and JSR B might not have an open source
implementation. That doesn't mean the implementation of JSR A is useless.
Clearly, as said before, any "hidden" requirements would be clearly
brought to light.
> The situation I'm afraid of is the following: you get the TCK, but can't
> use it to create a free, competing implementation of the specification
> because a contributor sneaked in a reference to a some unacessible code
> into the spec.
If there's a defect in the spec, then the proper place to address that is
within the JSR specification process.
> I've never seen any TCK code, so I don't know how it all works, and a
> lot of this is speculation. But seeing how you've tried to address many
> ways of trying to hijack your code, I'm wondering whether you think my
> concerns are valid or not.
I think your concerns are valid, but I think there are places other than
the TCK license requirements where those concerns can and would be
addressed.
Brian
Re: A few comments on the proposed TCK license
Posted by Dalibor Topic <ro...@kaffe.org>.
Hi Brian,
thanks for your quick reply. You've cleared up my mistakes in
interpretation quite nicely ;)
Brian Behlendorf wrote:
>>Example: If A wanted to make sure their competition wouldn't be able to
>>pass a TCK, all they need to do would be to put in a test case that
>>links to some internal, unspecified class from their implementation (say
>>an com.a.internal.* class). I see no protection against the licensee
>>using the TCK as a means to prevent competition instead of encouraging
>>it in the proposed license.
>
>
> Your example is somewhat bogus - a TCK for a standard that tests for
> classes outside that namespace would not be acceptable to Apache. It
> would be a broken project. Because the source code is published, it's
> easy to find such bogusness.
I'm not saying tests, I'm saying "links to", i.e. uses classes outside
of the namespace. It obviously has to for TCKs outside the java.lang
namespace in order to include java.lang.Object. ;)
>>The license should in my opinion require that the code covered by it is
>>always completely runnable and buildable within the specified framework,
>>or referenced frameworks within the specification, or with code provided
>>alongside the TCK under a compatible license.
>
>
> What problem exists without these requirements?
It may be possible to publish a TCK that requires a third party
component to run which is either unspecified, so that it can not be
recreated freely (a sun.* class, for example), or encumbered by a
non-free/non-ASL2-compatible license.
The situation I'm afraid of is the following: you get the TCK, but can't
use it to create a free, competing implementation of the specification
because a contributor sneaked in a reference to a some unacessible code
into the spec. What matters to me is that the TCK allows creation of
competing, spec-compliant implementations without imposing restrictions
that can not be fulfilled by the free software community/independant
efforts outside the JCP, like 'here's the TCK but you need this
TCKrunner software to run the tests, which is only available under 'some
non-ASL2-compatible' license'.
I've never seen any TCK code, so I don't know how it all works, and a
lot of this is speculation. But seeing how you've tried to address many
ways of trying to hijack your code, I'm wondering whether you think my
concerns are valid or not.
thanks again for taking the time to reply,
dalibor topic
Re: A few comments on the proposed TCK license
Posted by Brian Behlendorf <br...@collab.net>.
On Mon, 17 Nov 2003, Dalibor Topic wrote:
> I think "industry standard" is a little far fetched, unless Apache Software
> Foundation starts providing TCKs for standards proposed by
> standardization bodies. Sun's desire to promote their APIs as an "industry
> standard", a meaningless term unless we are talking about ISO, ECMA or
> ANSI, shouldn't result in marketing speak polluting the license.
The scope of this license is very clear, at the top:
== This TCK version is for use by JSR-defined projects releasing ==
== an official TCK for a JSR under JSPA 2.5. ==
It's not intended to be applicable to any other standards effort. The
people from Apache have been involved in the Java Community Process on the
premise that we can drag this community, kicking and screaming if need be,
into being a real multilateral standards effort. We are not alone in that
goal, and even within Sun there are people who want to do "the right
thing" in this regard. If you don't agree with this premise, then just
ignore this license, it has no bearing on projects that are not JCP TCKs.
> 3. Contributors and Contributions.
>
> A. The Licensor and any individual or legal entity that
> voluntarily submits to the Licensor a Contribution to the Work are
> collectively addressed herein as "Contributors". For legal
> entities, the entity making a Contribution and all other entities
> that control, are controlled by, or are under common control with
> that entity are considered to be a single Contributor. For the
> purposes of this definition, "control" means (i) the power, direct
> or indirect, to cause the direction or management of such entity,
> whether by contract or otherwise, or (ii) ownership of fifty
> percent (50%) or more of the outstanding shares, or
> (iii) beneficial ownership of such entity.
>
> Beside the obvious philosophical dicussion about how much in charge a
> person is about their actions ("The devil made me contribute!"), this
> paragraph's vague definition of control under (1) doesn't seem to make
> much sense. I can make someone read this comment by posting it to the
> mailing list, therefore I'm in control of that person because I
> used my indirect power to directed the person to read using
> "otherwise" means aka as posting? ASF, all your code belongs to me ;)
>
> It's not obvious why that piece of legalese is in the license.
This is the same language as in the 2.0 license, by the way, as is the
rest of your comments.
Consider the situation where company A wishes to insert a submarine patent
into an Apache project. They form a small company, company B, and have it
write the patent-infringing code, and then donate that code to the
organization. They then disband company B, and start to pursue legal
claims against the ASF and/or its others based on the code contributed by
Company B. Our ability to pass liability for that through to the original
Contributor is really difficult when that Contributor is defunct.
Therefore, language like this helps make it clear that playing a game like
that won't work.
>
> B. A "Contribution" is the original version of the Work and any
> modification or addition to the Work that has been submitted for
> inclusion in the Work, where such modifications and/or additions
> to the Work originate from that particular Contributor, or from
> some entity acting on behalf of that Contributor.
>
> C. A Contribution is "submitted" when any form of electronic,
> verbal, or written communication is sent to the Licensor,
> including but not limited to communication on electronic mailing
> lists, source code control systems, and issue tracking systems
> that are managed by, or on behalf of, the Licensor for the purpose
> of discussing and improving the Work, but excluding communication
> that is conspicuously marked or otherwise designated in writing by
> the Contributor as "Not a Contribution."
>
> How does one designate verbal communication in writing? An attempt to
> be overly broad, yet so limited. Basically, anything you tell us
> belongs to us, nyah nyah nyah.
You're missing the "conspicuously marked", which could apply to verbal
communication.
You're also exaggerating the claim. It doesn't "belong to us", we get the
non-exclusive right to redistribute it on our terms. And yes, if someone
tells us something, whether verbal or otherwise, we want that right to
incorporate it into Apache code, unless that person clearly says we can't.
> There are situations imaginable where I could tell ASF about A, but
> would have no right to contribute A to the ASF without being the
> copyright holder. The 'ours by default' claim hidden in this license
> may get in you trouble when you get lax on checking if people are
> actually allowed to contribute the content of the conversation.
Simply telling us "about" A isn't what we're concerned about. Telling us
"this is how some other project implements A" doesn't give us all rights
to A, either. Nothing in the license suggests this. It means that, if A
is a derivative of the licensed code, any IP ownership *you* have in A,
you are granting us the right to redistribute.
> Example: During the discussion of a TCK test someone brings up an
> excerpt from a regression test in Kaffe's regression test suite. ASF
> can according to their license claim it as a contribution, and add it
> to their TCK.
That would only be true *if*
the person who posted the test case to the list was the copyright
holder, or otherwise had the necessary rights to be able to contribute
it to the ASF, and
it was a derivative work from Apache-2.0-licensed code.
In your example, it sounds like neither would be the case. The Apache 2.0
license does *not* mean that suddenly anything posted to an Apache
development list is "borg"ed into being a contribution to the ASF.
[Section 7]
> (d) You must do one of the following:
>
> (1) remove from the Derived Work all tests that are specific
> to features of the Specification and all documentation
> describing the Specification and those specific tests; or
>
> (2) cause the Derived Work to be clearly and conspicuously
> labeled as "not the official TCK for the Specification"
> and "for research purposes only", and clearly and
> conspicuously identify within the documentation and
> packaging of the Derived Work that it is not the official
> TCK for the Specification, and further that passing the
> tests in the Derived Work does not indicate that an
> implementation has passed the TCK for the Specification.
>
> I am not sure I parse that correctly: does that mean I can do (1) such
> that I take a TCK, remove everything that refers to the specification,
> and redistribute it as "The real TCK" without any labelling? Cute.
Well, you can call it "the real TCK", and without being able to claim
which standard it is a TCK for, it's pretty useless. Why would you want
to do that?
> The restrictions on the labeling may make the TCK license GPL
> incompatible.
It is not a goal for the TCK license to be GPL compatible. We know it
can't be - the concept of testing for conformance is contrary to the goals
of the GPL.
> Other restrictions, like the clause that only if you pass
> the original TCK you can say that you passed it, may give the original
> contributor a lot of power to close out competing implementations by
> including references to code outside the specification in the TCK.
This license is not intended to allow derivative works to claim to
be TCKs for a given specification.
> Example: If A wanted to make sure their competition wouldn't be able to
> pass a TCK, all they need to do would be to put in a test case that
> links to some internal, unspecified class from their implementation (say
> an com.a.internal.* class). I see no protection against the licensee
> using the TCK as a means to prevent competition instead of encouraging
> it in the proposed license.
Your example is somewhat bogus - a TCK for a standard that tests for
classes outside that namespace would not be acceptable to Apache. It
would be a broken project. Because the source code is published, it's
easy to find such bogusness.
> The license should in my opinion require that the code covered by it is
> always completely runnable and buildable within the specified framework,
> or referenced frameworks within the specification, or with code provided
> alongside the TCK under a compatible license.
What problem exists without these requirements?
Brian