9. The source contains files we are not likely to be able to distribute. e.g [3]./web/src/dss/assets/pingfangScMedium.otf A: Same as Q 9 --Typo error, should be "Same as Q8".
Shuai Di Best Regards. Chen Xia <casion...@gmail.com> 于2022年1月20日周四 13:11写道： > 1. We used gpg --print-md SHA512 to generate the hashes which caused the > format problem? > A: According to the habits of most developers, we will change to using the > sha512sum (previously gpg) tool to generate sha512 files. > > 2. In the src package, there are binary files: > > ./linkis-engineconn-plugins/engineconn-plugins/python/src/main/py4j/py4j-0.10.7-src.zip > > ./linkis-engineconn-plugins/engineconn-plugins/python/src/main/py4j/pyspark.zip？ > A: After double-checking, pyspark.zip is not necessary, so it was removed > directly from the source code. > For py4j-0.10.7-src.zip, refer to the spark project > https://github.com/apache/spark/tree/master/python/lib, we added > LICENSE-py4j-0.10.7- src.txt file, and it is also explained in the LICENSE > file of the source code. > > 3. In the Git tag [1], there's the download links[2]. I think the download > links should only exist in the download page, and it's not the time to > publish the download links for now. > A: We take the advice and delete the download link in the Git tag. For the > non-asf version, we also mark it to inform users. > > 4. In the apache-linkis-1.0.3-incubating-bin.tar.gz package, there's > apache-linkis-1.0.3-incubating-dist.tar.gz binary file? > A: apache-linkis-1.0.3-incubating-dist.tar.gz used to be the complete > package compiled by linkis. In order to avoid confusion, we changed it to a > file directory named 'linkis-package' > > 5. apache-linkis-1.0.3-incubating-bin.tar.gz is larger than 500MB, is it > possible to streamline it? > A: The size is not small indeed, We'll try to shrink it in later > releases,and we have created an issue [ > https://github.com/apache/incubator-linkis/issues/1313] to optimize this > problem > > 6. LICENSE and NOTICE are not correct and include licenses that are not > Category A licenses > B: According to official requirements:"Only licenses from software included > in the source release need to be mentioned in LICENSE and NOTICE not all > dependencies". so we make the LICENSE file different for the source > release and the binary release,as follow: > > > - |-- LICENSE //LICENSE of the project source code > - |-- LICENSE-binary //LICENSE of binary package > - |-- LICENSE-binary-ui //LICENSE of the front-end compiled package > - |-- NOTICE //NOTICE of project source code > - |-- NOTICE-binary // NOTICE of binary package > - |-- NOTICE-binary-ui // NOTICE of front-end binary package > - |-- licenses-binary //The detailed dependent license file of the > binary package > - |-- licenses-binary-ui //The license file that the front-end > compilation package depends on in detail > > > 7. There are 2 zips in the release. Theses contain source code without > headers so it is unknown how they are licensed > A: Same as Q 2 > > 8. Looks like ASF headers have been incorrectly added to some files e.g. > [2]./web/src/dss/assets/projectIconFont/iconfont.* > A: This is the font file, to avoid unnecessary controversy, the front-end > developer removed it from the web source code > > 9. The source contains files we are not likely to be able to distribute. > e.g [3]./web/src/dss/assets/pingfangScMedium.otf > A: Same as Q 9 > > 10. How are these files licensed? [4]./web/src/components/svgIcon/svg/*.svg > A: Before, we ignored the license check for svg files. After checking one > by one, we removed unused svg files, and added ASF headers to svg files of > ASF license. > > 11. Most votes in the Linkis community are not valid, should do the check > and bring the check result with each vote. need to encourage mentors to > vote too. > A: We have reorganized the release process specification( > https://linkis.apache.org/community/how-to-release) to follow the Apache > Way > > Shuai Di <shua...@apache.org> 于2022年1月20日周四 12:12写道： > > > Dear Linkis community, > > > > In the release-1.0.3-rc1 vote, the IPMC's indicated the following > > problems/non-compliances. We're here to discuss the solutions. > > > > 1. We used gpg --print-md SHA512 to generate the hashes which caused > > the format problem. > > > > 2. In the src package, there are binary files: > > > > > ./linkis-engineconn-plugins/engineconn-plugins/python/src/main/py4j/py4j-0.10.7-src.zip > > > > > ./linkis-engineconn-plugins/engineconn-plugins/python/src/main/py4j/pyspark.zip > > - In the Git tag [1], there's the download links[2]. I think the > > download links should only exist in the download page, and it's not > > the time to publish the download links for now. > > > > 3. - In the Git tag [1], there's the download links[2]. I think the > > download links should only exist in the download page, and it's not > > the time to publish the download links for now. > > > > 4. - In the apache-linkis-1.0.3-incubating-bin.tar.gz package, there's > > apache-linkis-1.0.3-incubating-dist.tar.gz binary file. > > > > 5. apache-linkis-1.0.3-incubating-bin.tar.gz is larger than 500MB, is > > it possible to streamline it? > > > > 6. LICENSE and NOTICE are not correct and include licenses that are > > not Category A licenses > > > > 7. There are 2 zips in the release. Theses contain source code without > > headers so it is unknown how they are licensed > > > > 8. Look like ASF headers have been incorrectly added to some files e.g. > [2] > > ./web/src/dss/assets/projectIconFont/iconfont.* > > > > 9. - the source contain files we are not likely to be able to > > distribute. e.g [3] > > ./web/src/dss/assets/pingfangScMedium.otf > > > > 10. - How are these files licensed? [4] > > ./web/src/components/svgIcon/svg/*.svg > > > > 11. Most votes in the Linkis community are not valid, should do the check > > and bring the check result with each vote.Need to encourage mentors to > vote > > too. > > > > Shuai Di > > Best Regards. > > >
