- 🇳🇿New Zealand quietone
Based on #5 I am closing this as won't fix.
If there are still concerns about licensing and core, open an issue in the core issue queue instead of here. This project is deprecated.
In #2917161-6: JavaScript library evaluation: polymer license compatibility with GPL2 → , @droplet asked:
Does Drupal CORE compatible with Apache 2.0? I realise a (very popular) Polymer lib kit released under this license: https://vaadin.com/elements
So now, Drupal has no plans move to GPL v3
https://www.drupal.org/about/licensing#q12 →On Apache 2.0 page, it says not compatible if I read it correctly.
https://www.gnu.org/licenses/license-list.html#apache2Do we need to do a research on the these frameworks' popular `components` libs if we have a plan to reuse it instead make a custom one? (this question not limited to Polymer
IMO, this is correct. Drupal core, so long as it continues to be licensed as GPL2, may not include Apache2-licensed libraries.
Discuss if this is a problem. Do React, Vue, Polymer, or other frameworks have ecosystems that are too dominated by GPL2-incompatible libraries, such that not being able to use them give us concern about core using the framework at all? @droplet mentions https://vaadin.com/elements as an example, but I don't know if that example alone is enough to be concerned about.
Closed: won't fix
Idea
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Based on #5 I am closing this as won't fix.
If there are still concerns about licensing and core, open an issue in the core issue queue instead of here. This project is deprecated.