Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cran copyrights / license fix #41

Closed
sckott opened this issue Mar 21, 2016 · 7 comments
Closed

cran copyrights / license fix #41

sckott opened this issue Mar 21, 2016 · 7 comments

Comments

@sckott
Copy link
Collaborator

sckott commented Mar 21, 2016

Thanks, we see:

You have files in your package with GPLK license and copyright holders
not declared in the Authors@R fiel. Example: file src/parser.c (GPL,
copyright holder is the FSF).

Please carefully check if your license is possible and if all copyright
holders are mentioned.

We do have a COPYING.jq file and an AUTHORS.jq file.

@richfitz
Copy link
Member

From that parser file:

/* As a special exception, you may create a larger work that contains
   part or all of the Bison parser skeleton and distribute that work
   under terms of your choice, so long as that work isn't itself a
   parser generator using the skeleton or a modified version thereof
   as a parser skeleton.  Alternatively, if you modify or redistribute
   the parser skeleton itself, you may (at your option) remove this
   special exception, which will cause the skeleton and the resulting
   Bison output files to be licensed under the GNU General Public
   License without this special exception.

Not sure what the right move is here, and heading to bed...

@sckott
Copy link
Collaborator Author

sckott commented Mar 21, 2016

thanks

@sckott
Copy link
Collaborator Author

sckott commented Mar 22, 2016

thoughts @cboettig @jeroenooms never had to deal with copyright/license stuff, what's the right way to handle this, should we follow what's been done with git2r and points to copyright and authors files in inst/

Not sure what license to use either

@cboettig
Copy link
Member

@jeroenooms would know best, but here's my take: I guess they are suggesting that the authors of the included code be added as contributors [ctb] in the DESCRIPTION with a comment explaining their role (see https://github.com/rstudio/rmarkdown/blob/master/DESCRIPTION), and the DESCRIPTION should declare a compatible license. For instance, rmarkdown declares GPL-3 as the overall package license, and includes a inst/NOTICE file that lists the licenses of all the bits and pieces: https://github.com/rstudio/rmarkdown/blob/master/inst/NOTICE , (which include MIT, GPL, etc, which are all GPL compatible, but not all MIT compatible -- looks like we distribute GPL'd code here so we are thus infected and must also use GPL, if I understand correctly).

@sckott
Copy link
Collaborator Author

sckott commented Mar 22, 2016

this is what J said in slack

Also maybe use person(“Free Software Foundation", role = c("aut","cph"), comment = “Parser code"). For Brotli I did this: https://github.com/jeroenooms/brotli/blob/master/DESCRIPTION. Maybe link this file in the description? https://github.com/ropensci/jqr/blob/master/src/jq/AUTHORS

@sckott
Copy link
Collaborator Author

sckott commented Mar 22, 2016

thanks @cboettig

@sckott
Copy link
Collaborator Author

sckott commented Mar 23, 2016

@cboettig hmm, I think we can do MIT b/c jq uses MIT, and they include bison in the code base, see the special exception above listed by rich. So I think we can do MIT as well

@sckott sckott closed this as completed in 7e4b790 Mar 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants