On Thu, 9 Feb 2023 at 19:37, Antonio <anto...@vieiro.net.invalid> wrote: > How am I expected to do this? I mean, > > a) Shall I keep the original license in a commit, so it can be tracked > in the future, and then replace the license with the Apache License and > continue with modifications in future commits? That won't do, because > commits are only for Apache-2 license, right? > > b) May I keep the original MIT license and keep on using this license? > That won't do eiher, for the same reason as above.
We can't remove the existing license and copyright notice, but could add the Apache header on top. Closest thing I've found quickly is here - https://www.apache.org/foundation/license-faq.html#code-developed-elsewhere-received-under-a-category-a-license-incorporated-into-apache-projects-distributed-by-apache-and-licensed-to-downstream-users-under-its-original-license In particular "If changes are made to the code while at Apache, the standard Apache header is prepended to each changed file. Additionally, any legally-required notices related to the code are published in the distribution." So we also need to make sure the original license is covered correctly in the (sources) NOTICE file. I'm sure I read something more detailed on this scenario quite recently, but currently am failing to find it! :-\ Anyone else? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
