Hi Justin, > The incubator-apisix-dashboard repo is using one template which is under
> MIT License, so we'd like to know which license is suitable for the > incubator-apisix-dashboard-built repo? If the release contains something under the MIT license, then you leave the > header as MIT, and you add the MIT license to the LICENSE file. [1 > ] Is [2] a dependancy or is the code actually in the release? Assuming > it’s bundled the existing LICENSE file doesn’t look correct to me, while it > mentions the MIT license, it doesn’t include the full text of the license > or a pointer to a file containing that text. A URL can change over time so > you need more than just that. > Currently it’s a little hard to give any advice as the files are missing > headers so I don’t know what their origin was and which file(s) are 3rd > party. Have the original file headers been removed? > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps > 2. https://github.com/PanJiaChen/vue-element-admin The mail above was blocked because you might use a different mail address 😅 This repository[1] is a kind of Vue.js scaffolds, under MIT License, and we can use this repository's rich components to build Dashboard :) The original files do not include any Hader content, we just added the ASF Header to original files by mistaken :) [1] https://github.com/PanJiaChen/vue-element-admin Best Regards! @ Zhiyuan Ju <https://www.shaoyaoju.org/> Zhiyuan Ju <[email protected]> 于2019年11月5日周二 上午9:35写道： > Thanks for your reply :) > > So for the incubator-apisix-dashboard-built repository which contains the > release files should be under Apache License even if it's generated by the > incubator-apisix-dashboard repository (under MIT License)? > > Best Regards! > @ Zhiyuan Ju <https://www.shaoyaoju.org/> > > > Justin Mclean <[email protected]> 于2019年11月5日周二 上午8:36写道： > >> 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, <[email protected]> >> 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, <[email protected]> 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 <[email protected]> 于 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 >> >> >> > >> >
