Update LICENSE and remove license header from source files

[IvanGoncharov]

No description provided.

[IvanGoncharov]

Copied from graphql-faq repository: https://github.com/graphql/faq/blob/954d07c108634ebed1414b3380c830498bb0bbb6/LICENSE#L3

[IvanGoncharov]

I looked at the source code for a couple of other projects under LF (Node.js, ESLint, esprima) and they just just have LICENSE at the root of the project and no license headers inside the source code.

Those headers add some inconvenience in the development process e.g. new contributors forget to add them, old PRs contains an old version of the license text, it's harder to diff and revert old commits, etc.

Plus they effectively double up the size of NPM package:

npm notice package size:  483.3 kB
npm notice unpacked size: 3.6 MB

VS

npm notice package size:  237.5 kB
npm notice unpacked size: 1.7 MB

[IvanGoncharov]

Plus they effectively double up the size of NPM package:

I mad mistake during measurement, in reality, it was around ~100 kB difference unpacked.

[IvanGoncharov]

@leebyron As a followup from last WG I created this PR.
I want to release 14.4.0 next week so it would be great if we can include this update copyright and relese NPM package that is > 50% smaller.
Can you please review it?

[caniszczyk]

sorry can you just switch to plain old BSD-3? no need to switch to MIT, keep everything the same license

[IvanGoncharov]

@caniszczyk Thanks for the review 👍

sorry can you just switch to plain old BSD-3? no need to switch to MIT, keep everything the same license

At the moment, almost all projects under GraphQL organization are licensed as MIT:
https://github.com/graphql/libgraphqlparser/blob/master/LICENSE
https://github.com/graphql/graphql-relay-js/blob/master/LICENSE
https://github.com/graphql/dataloader/blob/master/LICENSE
https://github.com/graphql/faq/blob/master/LICENSE
https://github.com/graphql/graphiql/blob/master/LICENSE
https://github.com/graphql/graphql-js/blob/master/LICENSE

Only two repos are under BSD+Patents:
https://github.com/graphql/codemirror-graphql/blob/master/LICENSE
https://github.com/graphql/express-graphql/blob/master/LICENSE

And another two repo is under some strange licenses:
https://github.com/graphql/swapi-graphql/blob/master/LICENSE-examples
https://github.com/graphql/graphql-language-service/blob/master/LICENSE

Also, licenses were explicitly switched by Lee, as described here:
https://medium.com/@leeb/relicensing-the-graphql-specification-e7d07a52301b

Additionally, our reference implementation GraphQL.js and client-side framework Relay will be relicensed under the MIT license,

So it would be easier to stick with MIT since it what we already used on most of the projects (6 vs 2) and also since it was long promised to the community.

Is there any reason why we can't use MIT for GraphQL Foundation projects?

[caniszczyk]

MIT is fine I was just aiming for consistency

…

On Mon, Jun 10, 2019 at 2:40 PM Ivan Goncharov ***@***.***> wrote: @caniszczyk <https://github.com/caniszczyk> Thanks for the review 👍 sorry can you just switch to plain old BSD-3? no need to switch to MIT, keep everything the same license At the moment, almost all projects under GraphQL organization are licensed as MIT: https://github.com/graphql/libgraphqlparser/blob/master/LICENSE https://github.com/graphql/graphql-relay-js/blob/master/LICENSE https://github.com/graphql/dataloader/blob/master/LICENSE https://github.com/graphql/faq/blob/master/LICENSE https://github.com/graphql/graphiql/blob/master/LICENSE https://github.com/graphql/graphql-js/blob/master/LICENSE Only two repos are under BSD+Patents: https://github.com/graphql/codemirror-graphql/blob/master/LICENSE https://github.com/graphql/express-graphql/blob/master/LICENSE And another two repo is under some strange licenses: https://github.com/graphql/swapi-graphql/blob/master/LICENSE-examples https://github.com/graphql/graphql-language-service/blob/master/LICENSE Also, licenses were explicitly switched by Lee, as described here: ***@***.***/relicensing-the-graphql-specification-e7d07a52301b Additionally, our reference implementation GraphQL.js and client-side framework Relay will be relicensed under the MIT license, So it would be easier to stick with MIT since it what we already used on most of the projects (6 vs 2) and also since it was long promised to the community. Is there any reason why we can't use MIT for GraphQL Foundation projects? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1960?email_source=notifications&email_token=AAAPSIMLFSFUUV2UL3WUINLPZ2U35A5CNFSM4HVX4JPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXLAIDI#issuecomment-500565005>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAPSILWWCMXJLRU53PHMXLPZ2U35ANCNFSM4HVX4JPA> .

-- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719

[IvanGoncharov]

@caniszczyk Thanks for the quick reply 👍

Does it mean I can merge both PRs?

[caniszczyk]

just make sure the copyright is attributed to "GraphQL Contributors"

…

On Mon, Jun 10, 2019 at 3:09 PM Ivan Goncharov ***@***.***> wrote: @caniszczyk <https://github.com/caniszczyk> Thanks for the quick reply 👍 Does it mean I can merge both PRs? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1960?email_source=notifications&email_token=AAAPSINGGIPJ3PFFAMYWXSTPZ2YG5A5CNFSM4HVX4JPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXLCXFA#issuecomment-500575124>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAPSIOG5WMI7HFU23RND3LPZ2YG5ANCNFSM4HVX4JPA> .

-- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719

[IvanGoncharov]

just make sure the copyright is attributed to "GraphQL Contributors"

@caniszczyk Done. Thanks for a fast review 👍

[IvanGoncharov]

@caniszczyk Can we apply the same LICENSE changes to all other projects under this organization?