Re: sparklyr codebase license scan, Jan. 2020
Javier Luraschi
Makes sense, we will do our best to address those in the next release. Tracked now with: https://github.com/sparklyr/sparklyr/issues/2239
On Mon, Jan 13, 2020 at 11:58 AM Steve Winslow <swinslow@...> wrote:
Dear sparklyr technical-discuss list,I am providing the results of a license scan of the sparklyr codebase, based on a snapshot of the repos as of January 10. Beginning this month, I am using a new format for these reports. The findings and license summary are available at:That page lists any key findings/recommendations and the corresponding files in the repo, as well as a summary of all detected licenses. The more detailed catalogue of all files for each license can be obtained at:Finally, SPDX documents are also available for the license scan results. These can be seen and obtained at https://github.com/lfscanning/spdx-lfai. The SPDX documents contain human-readable and machine-readable details about the license notices and copyright notices for each file that was scanned. Although the project does not need to do anything with these SPDX files, I am providing them in the hopes that they may be helpful for the FOSS license compliance processes for your companies and the broader community.Please feel free to reach out to me directly with any questions. Please be sure to cc me (swinslow@...) on any responses, as I might not receive messages sent to the list address.Best regards,Steve
--Steve Winslow
Director of Strategic Programs
The Linux Foundation