Hi Justin, For the first issue, it means that our incubator-apisix repo contains one submodule called dashboard, which is linked to the incubator-apisix-dashboard-built repo and contains production files generated by another repo called incubator-apisix-dashboard.
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? Ming Wen <[email protected]> 于 2019年11月4日周一 22:46写道： > Hi, Justin, > https://www.apache.org/legal/src-headers.html#3party solved my confusion, > thanks. > > Zhiyuan, can you explain the first issue in more detail? I feel that it can > be solved in the same way. > > Thanks, > Ming Wen, Apache APISIX > Twitter: _WenMing > > > Justin Mclean <[email protected]> 于2019年11月4日周一 下午10: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 >
