Good afternoon. The ISC (Internet Software Consortium) license[1] is a permissive, open-source license that is considered "functionally equivalent"[2] to the Simplified (2-clause) BSD[3] and MIT[4] licenses, but with extraneous language removed. There is at least one package on CRAN which incorporates some code using it[5]. Are there plans to include this license in the list at <https://svn.r-project.org/R/trunk/share/licenses/license.db>? Will packages developed for R using this run into problems during submission? Thank you, Avraham Adler [1] <http://opensource.org/licenses/ISC> [2] <http://www.openbsd.org/policy.html>, <http://choosealicense.com/licenses/#isc> [3] <http://opensource.org/licenses/BSD-2-Clause> [4] <http://opensource.org/licenses/MIT> [5] <http://cran.r-project.org/web/packages/ff/LICENSE> This message is intended only for the use of the address...{{dropped:9}}
On 23/07/2014, 6:13 PM, Adler, Avraham wrote:> Good afternoon. > > The ISC (Internet Software Consortium) license[1] is a permissive, open-source license that is considered "functionally equivalent"[2] to the Simplified (2-clause) BSD[3] and MIT[4] licenses, but with extraneous language removed. There is at least one package on CRAN which incorporates some code using it[5]. Are there plans to include this license in the list at <https://svn.r-project.org/R/trunk/share/licenses/license.db>? Will packages developed for R using this run into problems during submission?You are writing to the wrong place. You need to read the CRAN policies on CRAN, and if they don't answer your question, write to CRAN to ask it. Duncan Murdoch
Reasonably Related Threads
- Optimization algorithm to be applied to S4 classes - specifically sparse matrices
- Notes on building a gcc toolchain for Rtools (but not multilib)
- Matrix inversion-different answers from LAPACK and LINPACK
- Notes on building a gcc toolchain for Rtools (but not multilib)
- Has the changelog for R-devel and R-patched moved?