I have not found any discussion on the mailing list about this. JSON License has not been considered an open source license by Apache [1], Debian [2] and FSF [3] and is not OSI approved [4].
Douglas Crockford has relicensed org.json:json java library to be Public Domain starting with version 20220924 [5]. Jenkins requires plugins and its dependencies to be free and open source software [6][7]. I did some analysis on the latest Jenkins plugins usage of org.json:json [8]. I have found a total of 473 plugins that depend on org.json:json (directly or transitively), with 104 plugins being free versions, 67 plugins directly depend on non free versions of org.json:json. Is this an actual concern for the Jenkins project ? If so, how to proceed ? Filipe Roque [1] https://lwn.net/Articles/707510/ [2] https://wiki.debian.org/qa.debian.org/jsonevil [3] https://www.gnu.org/licenses/license-list.html#JSON [4] https://opensource.org/licenses/ [5] https://github.com/stleary/JSON-java/issues/686 [6] https://www.jenkins.io/doc/developer/publishing/preparation/#license [7] https://www.jenkins.io/project/governance/#3rd-party-library-licenses-in-the-plugins [8] https://docs.google.com/spreadsheets/d/1MWNi796iAovFa6GK7LJ0gilbQRwvb8Su3c7YgpH_fuc/edit?usp=sharing -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/DB8PR04MB6649BE556B877585022D4E7DD303A%40DB8PR04MB6649.eurprd04.prod.outlook.com.
