I think you completely misunderstood me. The "developers" I was referring to aren't Apache contributors. I'm referring to a hypothetical Apache tool that would have a clear license. It might not even contain any third-party code at all. This hypothetical tool would allow someone to convert d.ts files to SWCs or something like that. It's up to a person using the tool (not Apache) to determine the copyright status of the d.ts file that they're converting. Apache would not be releasing the resulting SWC. They'd only be releasing the tool to create the SWC.
- Josh On May 30, 2015 4:28 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > Hi, > > > Mike and Alex, in case you missed it, Microsoft includes a lib.d.ts file > > with the TypeScript compiler that defines the core JS types, including > DOM > > APIs. It is very clearly licensed Apache 2.0 (with a license header in > the > > file too) in their official repository on Github: > > That would certainly be preferred over the other code and I can’t see any > issues there. > > You also said: > > > Let the individual developers figure copyright status on their own when > > using the tool. > > This is not how it is done at Apache, the licensing and province of code > needs to be clearly understood so that the ASF can own the release and > provide legal protection to the contributors. [1] This is why Apache > (unlike github) gets contributors to sign a ICLA.[2] > > Anyway I dug a little further and found this: > https://github.com/borisyankov/DefinitelyTyped/issues/96 > > Which brings up a few further questions, e.g. Are the previous > contributors OK with this license change? Was an IP review done? (doesn’t > look like it was). While other people may disagree, I think there’s enough > here to be cautious of bundling any of this code in a release. If clearer > licence alternatives can be found then just use them so it’s not an issue. > Raising a legal JIRA issue [3] could get some clarity here. > > Thanks, > Justin > > 1. http://www.apache.org/legal/src-headers.html < > http://www.apache.org/legal/src-headers.html> > 2. https://www.apache.org/licenses/icla.txt > 3. https://issues.apache.org/jira/browse/legal > >
