Change license to MPL

[frenic]

Change license to MPL

[chrisdavidmills]

Yup, you've got that right. And anything you've written that sits alongside the MPL-licensed files or data does not have to be under MPL - it can be under any license you like.

I am not sure if you need to do anything here. It is OK to have two licenses governing one codebase. But you might want to keep your codebase pure (one license) and all under something more permissive like MIT.

[frenic]

Thanks for clarifying @chrisdavidmills. Both index.d.ts and index.js.flow contains data like property names, selectors, keywords, phrases (as JSDOC) etc. We also have a PR where it fetches summaries for all properties from the MDN site and cache it in a JSON-file. It sounds like these files needs to be licensed with MPL.

[frenic]

The typings (index.d.ts and index.js.flow) exists in the codebase to easily diff the results of the generator. That's quite handy for reviewing and I can't figure out a simple alternative way of doing this.

The summaries needs to be cached otherwise it will spam the MDN site and cause a major impact on build performance.

I'm not dealing with licensing very often so I need to think about how to proceed. If someone has any ideas I would be happy to hear about it.

[frenic]

I guess this isn't an issue anymore since mdn-data changed their license to MIT