edit OT-JS license info so that GitHub recognizes it

eirinikos commented 6 years ago

(All CNCF projects should use the Apache License 2.0 - see opentracing/specification#61 for context.)

Please correct me if I'm wrong, but it seems like the original intent was to license OT-JavaScript as Apache 2.0, anyway (as mentioned in the README).
However, the LICENSE file itself contains the text for the MIT License, and a copyright reference to 2016 Resonance Labs, Inc.
In any case, GitHub currently detects the OT-JavaScript license as MIT, not Apache 2.0.
Could someone clarify the reason for referencing the Apache license in README and using the MIT license in the LICENSE file?

If this commit really does represent a switch from MIT to Apache, then we'd like to give previous contributors a 7-day period to air any objections.

(If you have any concerns or feedback, please post a comment here by April 11. Thanks!)

CCing @dankohn @bhs

CCing previous contributors: @bcronin @oibe @yurishkuro @bripkens @skzinc @felixfbecker @rochdev @eli-jordan @aroc @AloisReitbauer @jhorowitz @strongliang

coveralls commented 6 years ago

Coverage remained the same at 88.525% when pulling 513082737e6c89c1c05e551759b7b3a4b3adbf2f on eirinikos:update-license into 3abef18b8533ef75e6ee5d4fcca5af712b2d92b9 on opentracing:master.

felixfbecker commented 6 years ago

Note that package.json also declares MIT as license.

austinlparker commented 6 years ago

This has been sitting for a while with the appropriate approvals and no feedback to the negative, so I'll go ahead and merge it.

opentracing / opentracing-javascript

edit OT-JS license info so that GitHub recognizes it #105