Sorry for bad autocorrect in my last message. It depends on who owns the IP of the file. You should never remove or replace a 3rd party header from a file without their permission even if you have made changes.
On Tue, 5 Nov 2019, 11:33 Justin Mclean, <jus...@classsoftware.com> wrote: > Hi, > It celebs who the filed necking to and who owns the IP on each file. The > release should be under the Apache license that's required. > Thanks, > Justin > > On Tue, 5 Nov 2019, 11:15 Zhiyuan Ju, <juzhiy...@apache.org> wrote: > >> Hi Justin, >> >> Just to make sure, for the incubator-apisix-dashboard repo, all unchanged >> files should remove our ALv2 header and all significant >> changes files will be added the ALv2 header, and the repo will keep the >> MIT License? >> >> Justin Mclean <jus...@classsoftware.com> 于 2019年11月4日周一 22:25写道： >> >> > Hi, >> > >> > > I have two issues about the dashboard license so far >> > >> > I replied to this before. >> > >> > > 1. The first one is the question mentioned in the email above： >> > > how to deal with the license for frontend production build files in >> > > incubator-apisix-dashboard-built [1]? >> > >> > It ALv2 in an apache repo so what’s the issue? >> > >> > > 2. The second is that the dashboard is based on vue-element-admin[3], >> > > we need to carefully sort out which files should keep the original MIT >> > > license and which our modified files can add the apache license >> header. >> > >> > That's easy, all files should keep the original MIT license. If you have >> > permission from the owner you can change it, but otherwise unless their >> are >> > significant changes it is best to keep the original header and license. >> [1] >> > >> > Thanks, >> > Justin >> > >> > 1. https://www.apache.org/legal/src-headers.html#3party >> >
