Regarding R licensing usage guidance

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Regarding R licensing usage guidance

ANAMIKA KUMARI
Hello Team,

This mail is in reference to understanding R  license and also usage of  R
language to develop commercialised product.

I am working on one product of mine that uses R and python language.I am
trying to understand the licensing issue if any related to R, if I am going
to commercialise my product and keep my work proprietary.

I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
need to share source code of my product. if, I am moving planning  to move
it to production or I can keep my code Proprietary.

Please note that I am just using R and its packages to  develop my own
statistical tool and api and Have not done any changes to existing R code.

Please refer below for all R-packages used in my code:-

   1.
*R-3.4.4 *
   2. *'spacyr'*
   3.
*'jsonlite' *
   4.
*'lubridate' *
   5.
*'data.table' *
   6.
*'png' *
   7.
*'maps' *
   8.
*'countrycode' *
   9.
*'humaniformat' *
   10.
*'ngram' *
   11.
*'stringr' *
   12.
*'slam' *
   13.
*'tm' *
   14.
*'lsa' *
   15.
*'RTextTools' *
   16.
*'stringi' *
   17.
*'plumber' *
   18. *"Rook"*
   19. *"pdftools"*
   20. *'tokenizers'*
   21. *'zoo'*
   22. *"tidyr"*
   23. *"reqres"*
   24. *"rJava"*
   25. *"tiff"*
   26. *"splitstackshape"*
   27. *"stringdist"*
   28. *"RJSONIO"*
   29. *"ropensci/tabulizer"*
   30. *"staplr"*
   31. *"SparseM"*
   32. *"randomForest"*
   33. *"e1071"*
   34. *"ipred"*
   35. *"caTools"*
   36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
   37. *RCMD INSTALL tree_1.0-39.tar.gz*
   38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*


*Any help from you will be highly appreciated as I am literally stuck at a
dead end.*

*Regards*
*Anamika Kumari*

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Patrick (Malone Quantitative)
You're in the wrong place. This is for help with R programming.

But you shouldn't be asking us either way, as we (at least most of us)
aren't lawyers. Get your attorney to study the GNU-GPL-2.0 and tell
you what you need to and can do for your purposes.

Pat

On Mon, Jul 22, 2019 at 1:23 PM ANAMIKA KUMARI <[hidden email]> wrote:

>
> Hello Team,
>
> This mail is in reference to understanding R  license and also usage of  R
> language to develop commercialised product.
>
> I am working on one product of mine that uses R and python language.I am
> trying to understand the licensing issue if any related to R, if I am going
> to commercialise my product and keep my work proprietary.
>
> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
> need to share source code of my product. if, I am moving planning  to move
> it to production or I can keep my code Proprietary.
>
> Please note that I am just using R and its packages to  develop my own
> statistical tool and api and Have not done any changes to existing R code.
>
> Please refer below for all R-packages used in my code:-
>
>    1.
> *R-3.4.4 *
>    2. *'spacyr'*
>    3.
> *'jsonlite' *
>    4.
> *'lubridate' *
>    5.
> *'data.table' *
>    6.
> *'png' *
>    7.
> *'maps' *
>    8.
> *'countrycode' *
>    9.
> *'humaniformat' *
>    10.
> *'ngram' *
>    11.
> *'stringr' *
>    12.
> *'slam' *
>    13.
> *'tm' *
>    14.
> *'lsa' *
>    15.
> *'RTextTools' *
>    16.
> *'stringi' *
>    17.
> *'plumber' *
>    18. *"Rook"*
>    19. *"pdftools"*
>    20. *'tokenizers'*
>    21. *'zoo'*
>    22. *"tidyr"*
>    23. *"reqres"*
>    24. *"rJava"*
>    25. *"tiff"*
>    26. *"splitstackshape"*
>    27. *"stringdist"*
>    28. *"RJSONIO"*
>    29. *"ropensci/tabulizer"*
>    30. *"staplr"*
>    31. *"SparseM"*
>    32. *"randomForest"*
>    33. *"e1071"*
>    34. *"ipred"*
>    35. *"caTools"*
>    36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>    37. *RCMD INSTALL tree_1.0-39.tar.gz*
>    38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>
>
> *Any help from you will be highly appreciated as I am literally stuck at a
> dead end.*
>
> *Regards*
> *Anamika Kumari*
>
>         [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

R help mailing list-2
Hi,

In addition to Patrick's comments, which are spot on, other versions of the GPL (e.g. 3.0) and other GPL compatible licenses that are or may be relevant to the list of packages that are listed below need to be assessed as well. There are differences, some more nuanced than others, between GPL compatible licenses and how they may affect what you can or cannot do.

If you are going to build a presumably for profit business around open source software, then you need to invest in legal counsel with expertise in the relevant areas of open source software and intellectual property rights, to get appropriate legal opinions on what it is you plan to build, how it will interact with R and the packages you list below, and what all of that means for your product.

Regards,

Marc Schwartz


> On Jul 22, 2019, at 1:28 PM, Patrick (Malone Quantitative) <[hidden email]> wrote:
>
> You're in the wrong place. This is for help with R programming.
>
> But you shouldn't be asking us either way, as we (at least most of us)
> aren't lawyers. Get your attorney to study the GNU-GPL-2.0 and tell
> you what you need to and can do for your purposes.
>
> Pat
>
> On Mon, Jul 22, 2019 at 1:23 PM ANAMIKA KUMARI <[hidden email]> wrote:
>>
>> Hello Team,
>>
>> This mail is in reference to understanding R  license and also usage of  R
>> language to develop commercialised product.
>>
>> I am working on one product of mine that uses R and python language.I am
>> trying to understand the licensing issue if any related to R, if I am going
>> to commercialise my product and keep my work proprietary.
>>
>> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
>> need to share source code of my product. if, I am moving planning  to move
>> it to production or I can keep my code Proprietary.
>>
>> Please note that I am just using R and its packages to  develop my own
>> statistical tool and api and Have not done any changes to existing R code.
>>
>> Please refer below for all R-packages used in my code:-
>>
>>   1.
>> *R-3.4.4 *
>>   2. *'spacyr'*
>>   3.
>> *'jsonlite' *
>>   4.
>> *'lubridate' *
>>   5.
>> *'data.table' *
>>   6.
>> *'png' *
>>   7.
>> *'maps' *
>>   8.
>> *'countrycode' *
>>   9.
>> *'humaniformat' *
>>   10.
>> *'ngram' *
>>   11.
>> *'stringr' *
>>   12.
>> *'slam' *
>>   13.
>> *'tm' *
>>   14.
>> *'lsa' *
>>   15.
>> *'RTextTools' *
>>   16.
>> *'stringi' *
>>   17.
>> *'plumber' *
>>   18. *"Rook"*
>>   19. *"pdftools"*
>>   20. *'tokenizers'*
>>   21. *'zoo'*
>>   22. *"tidyr"*
>>   23. *"reqres"*
>>   24. *"rJava"*
>>   25. *"tiff"*
>>   26. *"splitstackshape"*
>>   27. *"stringdist"*
>>   28. *"RJSONIO"*
>>   29. *"ropensci/tabulizer"*
>>   30. *"staplr"*
>>   31. *"SparseM"*
>>   32. *"randomForest"*
>>   33. *"e1071"*
>>   34. *"ipred"*
>>   35. *"caTools"*
>>   36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>>   37. *RCMD INSTALL tree_1.0-39.tar.gz*
>>   38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>>
>>
>> *Any help from you will be highly appreciated as I am literally stuck at a
>> dead end.*
>>
>> *Regards*
>> *Anamika Kumari*

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Jeff Newmiller
In reply to this post by ANAMIKA KUMARI
Your internet skills are pathetic. Search Google for "proprietary use gpl" and the first hit is

https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i

Note that there are (at least) three obvious alternatives if there is any question in your case: release the code under GPL but also sell it with support (a la RStudio); only use it yourself (don't distribute it at all); or only use R for setting up your models but re-engineer implementations of the run-time prediction calculations yourself (often much easier than the initial algorithm development).

I think your desperation to steal the hard work of the various R contributors seems quite odious.

On July 22, 2019 6:55:31 AM PDT, ANAMIKA KUMARI <[hidden email]> wrote:

>Hello Team,
>
>This mail is in reference to understanding R  license and also usage of
> R
>language to develop commercialised product.
>
>I am working on one product of mine that uses R and python language.I
>am
>trying to understand the licensing issue if any related to R, if I am
>going
>to commercialise my product and keep my work proprietary.
>
>I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
>need to share source code of my product. if, I am moving planning  to
>move
>it to production or I can keep my code Proprietary.
>
>Please note that I am just using R and its packages to  develop my own
>statistical tool and api and Have not done any changes to existing R
>code.
>
>Please refer below for all R-packages used in my code:-
>
>   1.
>*R-3.4.4 *
>   2. *'spacyr'*
>   3.
>*'jsonlite' *
>   4.
>*'lubridate' *
>   5.
>*'data.table' *
>   6.
>*'png' *
>   7.
>*'maps' *
>   8.
>*'countrycode' *
>   9.
>*'humaniformat' *
>   10.
>*'ngram' *
>   11.
>*'stringr' *
>   12.
>*'slam' *
>   13.
>*'tm' *
>   14.
>*'lsa' *
>   15.
>*'RTextTools' *
>   16.
>*'stringi' *
>   17.
>*'plumber' *
>   18. *"Rook"*
>   19. *"pdftools"*
>   20. *'tokenizers'*
>   21. *'zoo'*
>   22. *"tidyr"*
>   23. *"reqres"*
>   24. *"rJava"*
>   25. *"tiff"*
>   26. *"splitstackshape"*
>   27. *"stringdist"*
>   28. *"RJSONIO"*
>   29. *"ropensci/tabulizer"*
>   30. *"staplr"*
>   31. *"SparseM"*
>   32. *"randomForest"*
>   33. *"e1071"*
>   34. *"ipred"*
>   35. *"caTools"*
>   36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>   37. *RCMD INSTALL tree_1.0-39.tar.gz*
>   38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>
>
>*Any help from you will be highly appreciated as I am literally stuck
>at a
>dead end.*
>
>*Regards*
>*Anamika Kumari*
>
> [[alternative HTML version deleted]]
>
>______________________________________________
>[hidden email] mailing list -- To UNSUBSCRIBE and more, see
>https://stat.ethz.ch/mailman/listinfo/r-help
>PLEASE do read the posting guide
>http://www.R-project.org/posting-guide.html
>and provide commented, minimal, self-contained, reproducible code.

--
Sent from my phone. Please excuse my brevity.

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

ANAMIKA KUMARI
In reply to this post by ANAMIKA KUMARI
Hi Team

Thank you for your reply. I do not intend to use hard work of community and
earn profit on it. I do not intend to do  any changes or modifications in
existing R source code and build software over it. I am just using R as
language to develop my own work, the same way people use Java or python.

I just got confused with the licensing , as I thought i can't even use R as
a language to write code. But that's not the case right? The problem arises
only if I try to do modification in existing source code and then try to
convert it into proprietary.

I am sorry , it all came out in wrong way.I didn't intended to hurt anyones
sentiment.

I totally love the community and it's work so far. And hope someday , I'll
be have enough knowledge, so that I can  give back to community.

Regards
Anamika

On Mon, Jul 22, 2019, 7:25 PM ANAMIKA KUMARI <[hidden email]> wrote:

> Hello Team,
>
> This mail is in reference to understanding R  license and also usage of  R
> language to develop commercialised product.
>
> I am working on one product of mine that uses R and python language.I am
> trying to understand the licensing issue if any related to R, if I am going
> to commercialise my product and keep my work proprietary.
>
> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
> need to share source code of my product. if, I am moving planning  to move
> it to production or I can keep my code Proprietary.
>
> Please note that I am just using R and its packages to  develop my own
> statistical tool and api and Have not done any changes to existing R code.
>
> Please refer below for all R-packages used in my code:-
>
>    1.
> *R-3.4.4 *
>    2. *'spacyr'*
>    3.
> *'jsonlite' *
>    4.
> *'lubridate' *
>    5.
> *'data.table' *
>    6.
> *'png' *
>    7.
> *'maps' *
>    8.
> *'countrycode' *
>    9.
> *'humaniformat' *
>    10.
> *'ngram' *
>    11.
> *'stringr' *
>    12.
> *'slam' *
>    13.
> *'tm' *
>    14.
> *'lsa' *
>    15.
> *'RTextTools' *
>    16.
> *'stringi' *
>    17.
> *'plumber' *
>    18. *"Rook"*
>    19. *"pdftools"*
>    20. *'tokenizers'*
>    21. *'zoo'*
>    22. *"tidyr"*
>    23. *"reqres"*
>    24. *"rJava"*
>    25. *"tiff"*
>    26. *"splitstackshape"*
>    27. *"stringdist"*
>    28. *"RJSONIO"*
>    29. *"ropensci/tabulizer"*
>    30. *"staplr"*
>    31. *"SparseM"*
>    32. *"randomForest"*
>    33. *"e1071"*
>    34. *"ipred"*
>    35. *"caTools"*
>    36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>    37. *RCMD INSTALL tree_1.0-39.tar.gz*
>    38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>
>
> *Any help from you will be highly appreciated as I am literally stuck at a
> dead end.*
>
> *Regards*
> *Anamika Kumari*
>
>
>

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Duncan Murdoch-2
On 23/07/2019 2:38 p.m., ANAMIKA KUMARI wrote:

> Hi Team
>
> Thank you for your reply. I do not intend to use hard work of community and
> earn profit on it. I do not intend to do  any changes or modifications in
> existing R source code and build software over it. I am just using R as
> language to develop my own work, the same way people use Java or python.
>
> I just got confused with the licensing , as I thought i can't even use R as
> a language to write code. But that's not the case right? The problem arises
> only if I try to do modification in existing source code and then try to
> convert it into proprietary.

No, that's not right.  The problem comes if you try to distribute copies
of R or R packages.  You can write things in R and distribute your own
code any way you like, but you have to be really careful how your users
get R in order to run your code.  The only rights you have to distribute
copies of R and other packages come from their licenses.  If you don't
follow their licenses, you may be in violation of their copyright.

Duncan Murdoch

>
> I am sorry , it all came out in wrong way.I didn't intended to hurt anyones
> sentiment.
>
> I totally love the community and it's work so far. And hope someday , I'll
> be have enough knowledge, so that I can  give back to community.
>
> Regards
> Anamika
>
> On Mon, Jul 22, 2019, 7:25 PM ANAMIKA KUMARI <[hidden email]> wrote:
>
>> Hello Team,
>>
>> This mail is in reference to understanding R  license and also usage of  R
>> language to develop commercialised product.
>>
>> I am working on one product of mine that uses R and python language.I am
>> trying to understand the licensing issue if any related to R, if I am going
>> to commercialise my product and keep my work proprietary.
>>
>> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
>> need to share source code of my product. if, I am moving planning  to move
>> it to production or I can keep my code Proprietary.
>>
>> Please note that I am just using R and its packages to  develop my own
>> statistical tool and api and Have not done any changes to existing R code.
>>
>> Please refer below for all R-packages used in my code:-
>>
>>     1.
>> *R-3.4.4 *
>>     2. *'spacyr'*
>>     3.
>> *'jsonlite' *
>>     4.
>> *'lubridate' *
>>     5.
>> *'data.table' *
>>     6.
>> *'png' *
>>     7.
>> *'maps' *
>>     8.
>> *'countrycode' *
>>     9.
>> *'humaniformat' *
>>     10.
>> *'ngram' *
>>     11.
>> *'stringr' *
>>     12.
>> *'slam' *
>>     13.
>> *'tm' *
>>     14.
>> *'lsa' *
>>     15.
>> *'RTextTools' *
>>     16.
>> *'stringi' *
>>     17.
>> *'plumber' *
>>     18. *"Rook"*
>>     19. *"pdftools"*
>>     20. *'tokenizers'*
>>     21. *'zoo'*
>>     22. *"tidyr"*
>>     23. *"reqres"*
>>     24. *"rJava"*
>>     25. *"tiff"*
>>     26. *"splitstackshape"*
>>     27. *"stringdist"*
>>     28. *"RJSONIO"*
>>     29. *"ropensci/tabulizer"*
>>     30. *"staplr"*
>>     31. *"SparseM"*
>>     32. *"randomForest"*
>>     33. *"e1071"*
>>     34. *"ipred"*
>>     35. *"caTools"*
>>     36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>>     37. *RCMD INSTALL tree_1.0-39.tar.gz*
>>     38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>>
>>
>> *Any help from you will be highly appreciated as I am literally stuck at a
>> dead end.*
>>
>> *Regards*
>> *Anamika Kumari*
>>
>>
>>
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Patrick (Malone Quantitative)
Again, consult an IP lawyer whom you are paying for legal advice.

On Tue, Jul 23, 2019 at 4:15 PM Duncan Murdoch <[hidden email]> wrote:

>
> On 23/07/2019 2:38 p.m., ANAMIKA KUMARI wrote:
> > Hi Team
> >
> > Thank you for your reply. I do not intend to use hard work of community and
> > earn profit on it. I do not intend to do  any changes or modifications in
> > existing R source code and build software over it. I am just using R as
> > language to develop my own work, the same way people use Java or python.
> >
> > I just got confused with the licensing , as I thought i can't even use R as
> > a language to write code. But that's not the case right? The problem arises
> > only if I try to do modification in existing source code and then try to
> > convert it into proprietary.
>
> No, that's not right.  The problem comes if you try to distribute copies
> of R or R packages.  You can write things in R and distribute your own
> code any way you like, but you have to be really careful how your users
> get R in order to run your code.  The only rights you have to distribute
> copies of R and other packages come from their licenses.  If you don't
> follow their licenses, you may be in violation of their copyright.
>
> Duncan Murdoch
>
> >
> > I am sorry , it all came out in wrong way.I didn't intended to hurt anyones
> > sentiment.
> >
> > I totally love the community and it's work so far. And hope someday , I'll
> > be have enough knowledge, so that I can  give back to community.
> >
> > Regards
> > Anamika
> >
> > On Mon, Jul 22, 2019, 7:25 PM ANAMIKA KUMARI <[hidden email]> wrote:
> >
> >> Hello Team,
> >>
> >> This mail is in reference to understanding R  license and also usage of  R
> >> language to develop commercialised product.
> >>
> >> I am working on one product of mine that uses R and python language.I am
> >> trying to understand the licensing issue if any related to R, if I am going
> >> to commercialise my product and keep my work proprietary.
> >>
> >> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
> >> need to share source code of my product. if, I am moving planning  to move
> >> it to production or I can keep my code Proprietary.
> >>
> >> Please note that I am just using R and its packages to  develop my own
> >> statistical tool and api and Have not done any changes to existing R code.
> >>
> >> Please refer below for all R-packages used in my code:-
> >>
> >>     1.
> >> *R-3.4.4 *
> >>     2. *'spacyr'*
> >>     3.
> >> *'jsonlite' *
> >>     4.
> >> *'lubridate' *
> >>     5.
> >> *'data.table' *
> >>     6.
> >> *'png' *
> >>     7.
> >> *'maps' *
> >>     8.
> >> *'countrycode' *
> >>     9.
> >> *'humaniformat' *
> >>     10.
> >> *'ngram' *
> >>     11.
> >> *'stringr' *
> >>     12.
> >> *'slam' *
> >>     13.
> >> *'tm' *
> >>     14.
> >> *'lsa' *
> >>     15.
> >> *'RTextTools' *
> >>     16.
> >> *'stringi' *
> >>     17.
> >> *'plumber' *
> >>     18. *"Rook"*
> >>     19. *"pdftools"*
> >>     20. *'tokenizers'*
> >>     21. *'zoo'*
> >>     22. *"tidyr"*
> >>     23. *"reqres"*
> >>     24. *"rJava"*
> >>     25. *"tiff"*
> >>     26. *"splitstackshape"*
> >>     27. *"stringdist"*
> >>     28. *"RJSONIO"*
> >>     29. *"ropensci/tabulizer"*
> >>     30. *"staplr"*
> >>     31. *"SparseM"*
> >>     32. *"randomForest"*
> >>     33. *"e1071"*
> >>     34. *"ipred"*
> >>     35. *"caTools"*
> >>     36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
> >>     37. *RCMD INSTALL tree_1.0-39.tar.gz*
> >>     38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
> >>
> >>
> >> *Any help from you will be highly appreciated as I am literally stuck at a
> >> dead end.*
> >>
> >> *Regards*
> >> *Anamika Kumari*
> >>
> >>
> >>
> >
> >       [[alternative HTML version deleted]]
> >
> > ______________________________________________
> > [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> > https://stat.ethz.ch/mailman/listinfo/r-help
> > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> > and provide commented, minimal, self-contained, reproducible code.
> >
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

John Maindonald
In reply to this post by ANAMIKA KUMARI
I think this unfair, certainly the ‘odious’ comment.  Very many of us
have been able to contribute because supported to do such work
while occupying relatively comfortable academic positions.  In the
process of getting there, we have benefited enormously from the
work of those who have gone before.  I do not know what Anamika’s
position is, but he may well be trying to build a business from a
much less privileged starting point than others of us may have
enjoyed.  In any case, the comment strikes a tone that is out of
place in respectful discourse.


John Maindonald             email: [hidden email]<mailto:[hidden email]>


On 23/07/2019, at 22:00, [hidden email]<mailto:[hidden email]> wrote:

From: Jeff Newmiller <[hidden email]<mailto:[hidden email]>>
Subject: Re: [R] Regarding R licensing usage guidance
Date: 23 July 2019 at 07:00:26 NZST
To: <[hidden email]<mailto:[hidden email]>>, ANAMIKA KUMARI <[hidden email]<mailto:[hidden email]>>


Your internet skills are pathetic. Search Google for "proprietary use gpl" and the first hit is

https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i

Note that there are (at least) three obvious alternatives if there is any question in your case: release the code under GPL but also sell it with support (a la RStudio); only use it yourself (don't distribute it at all); or only use R for setting up your models but re-engineer implementations of the run-time prediction calculations yourself (often much easier than the initial algorithm development).

I think your desperation to steal the hard work of the various R contributors seems quite odious.

On July 22, 2019 6:55:31 AM PDT, ANAMIKA KUMARI <[hidden email]<mailto:[hidden email]>> wrote:
Hello Team,

This mail is in reference to understanding R  license and also usage of
R
language to develop commercialised product.

I am working on one product of mine that uses R and python language.I
am
trying to understand the licensing issue if any related to R, if I am
going
to commercialise my product and keep my work proprietary.

I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
need to share source code of my product. if, I am moving planning  to
move
it to production or I can keep my code Proprietary.

Please note that I am just using R and its packages to  develop my own
statistical tool and api and Have not done any changes to existing R
code.

Please refer below for all R-packages used in my code:-

 1.
*R-3.4.4 *
 2. *'spacyr'*
 3.
*'jsonlite' *
 4.
*'lubridate' *
 5.
*'data.table' *
 6.
*'png' *
 7.
*'maps' *
 8.
*'countrycode' *
 9.
*'humaniformat' *
 10.
*'ngram' *
 11.
*'stringr' *
 12.
*'slam' *
 13.
*'tm' *
 14.
*'lsa' *
 15.
*'RTextTools' *
 16.
*'stringi' *
 17.
*'plumber' *
 18. *"Rook"*
 19. *"pdftools"*
 20. *'tokenizers'*
 21. *'zoo'*
 22. *"tidyr"*
 23. *"reqres"*
 24. *"rJava"*
 25. *"tiff"*
 26. *"splitstackshape"*
 27. *"stringdist"*
 28. *"RJSONIO"*
 29. *"ropensci/tabulizer"*
 30. *"staplr"*
 31. *"SparseM"*
 32. *"randomForest"*
 33. *"e1071"*
 34. *"ipred"*
 35. *"caTools"*
 36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
 37. *RCMD INSTALL tree_1.0-39.tar.gz*
 38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*


*Any help from you will be highly appreciated as I am literally stuck
at a
dead end.*

*Regards*
*Anamika Kumari*

[[alternative HTML version deleted]]

______________________________________________
[hidden email]<mailto:[hidden email]> mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide
http://www.R-project.org/posting-guide.html<http://www.r-project.org/posting-guide.html>
and provide commented, minimal, self-contained, reproducible code.

--
Sent from my phone. Please excuse my brevity.


        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Weiwen Ng, MPH
The ad hominem comment about Google skills is also out of line. Knowing
what to search for is often not trivial. The problem is magnified if
English isn't your native language.

On Tue, Jul 23, 2019 at 3:59 PM John Maindonald <[hidden email]>
wrote:

> I think this unfair, certainly the ‘odious’ comment.  Very many of us
> have been able to contribute because supported to do such work
> while occupying relatively comfortable academic positions.  In the
> process of getting there, we have benefited enormously from the
> work of those who have gone before.  I do not know what Anamika’s
> position is, but he may well be trying to build a business from a
> much less privileged starting point than others of us may have
> enjoyed.  In any case, the comment strikes a tone that is out of
> place in respectful discourse.
>
>
> John Maindonald             email: [hidden email]<mailto:
> [hidden email]>
>
>
> On 23/07/2019, at 22:00, [hidden email]<mailto:
> [hidden email]> wrote:
>
> From: Jeff Newmiller <[hidden email]<mailto:
> [hidden email]>>
> Subject: Re: [R] Regarding R licensing usage guidance
> Date: 23 July 2019 at 07:00:26 NZST
> To: <[hidden email]<mailto:[hidden email]>>, ANAMIKA KUMARI <
> [hidden email]<mailto:[hidden email]>>
>
>
> Your internet skills are pathetic. Search Google for "proprietary use gpl"
> and the first hit is
>
>
> https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i
>
> Note that there are (at least) three obvious alternatives if there is any
> question in your case: release the code under GPL but also sell it with
> support (a la RStudio); only use it yourself (don't distribute it at all);
> or only use R for setting up your models but re-engineer implementations of
> the run-time prediction calculations yourself (often much easier than the
> initial algorithm development).
>
> I think your desperation to steal the hard work of the various R
> contributors seems quite odious.
>
> On July 22, 2019 6:55:31 AM PDT, ANAMIKA KUMARI <[hidden email]
> <mailto:[hidden email]>> wrote:
> Hello Team,
>
> This mail is in reference to understanding R  license and also usage of
> R
> language to develop commercialised product.
>
> I am working on one product of mine that uses R and python language.I
> am
> trying to understand the licensing issue if any related to R, if I am
> going
> to commercialise my product and keep my work proprietary.
>
> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do I
> need to share source code of my product. if, I am moving planning  to
> move
> it to production or I can keep my code Proprietary.
>
> Please note that I am just using R and its packages to  develop my own
> statistical tool and api and Have not done any changes to existing R
> code.
>
> Please refer below for all R-packages used in my code:-
>
>  1.
> *R-3.4.4 *
>  2. *'spacyr'*
>  3.
> *'jsonlite' *
>  4.
> *'lubridate' *
>  5.
> *'data.table' *
>  6.
> *'png' *
>  7.
> *'maps' *
>  8.
> *'countrycode' *
>  9.
> *'humaniformat' *
>  10.
> *'ngram' *
>  11.
> *'stringr' *
>  12.
> *'slam' *
>  13.
> *'tm' *
>  14.
> *'lsa' *
>  15.
> *'RTextTools' *
>  16.
> *'stringi' *
>  17.
> *'plumber' *
>  18. *"Rook"*
>  19. *"pdftools"*
>  20. *'tokenizers'*
>  21. *'zoo'*
>  22. *"tidyr"*
>  23. *"reqres"*
>  24. *"rJava"*
>  25. *"tiff"*
>  26. *"splitstackshape"*
>  27. *"stringdist"*
>  28. *"RJSONIO"*
>  29. *"ropensci/tabulizer"*
>  30. *"staplr"*
>  31. *"SparseM"*
>  32. *"randomForest"*
>  33. *"e1071"*
>  34. *"ipred"*
>  35. *"caTools"*
>  36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>  37. *RCMD INSTALL tree_1.0-39.tar.gz*
>  38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>
>
> *Any help from you will be highly appreciated as I am literally stuck
> at a
> dead end.*
>
> *Regards*
> *Anamika Kumari*
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email]<mailto:[hidden email]> mailing list -- To
> UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
> http://www.R-project.org/posting-guide.html<
> http://www.r-project.org/posting-guide.html>
> and provide commented, minimal, self-contained, reproducible code.
>
> --
> Sent from my phone. Please excuse my brevity.
>
>
>         [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
> http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Abby Spurdle
In reply to this post by Duncan Murdoch-2
> > I do not intend to use hard work of community and
> > earn profit on it.

> No, that's not right. The problem comes if you try to distribute copies
> of R or R packages.

You are allowed to make a profit.
: )

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Jeff Newmiller
In reply to this post by Weiwen Ng, MPH
Your feelings are noted, but my comment about skills was not directed at the person of Anamika but at their skills, so no, it was not ad hominem.

Regarding the word "odious"... I think that wrapping GPL software in a proprietary blob is ethically flawed, and that word is appropriate regardless of the possible economic disadvantage someone might have who commits that behavior. I have no problem with people generating proprietary blobs of code they wrote combined with supporting code licensed in a way that allows for such use... my employers have paid me to produce such works in the past, but such blobs should rightfully reflect the work input by the programmer and not the massive input by people not being properly compensated for building such an extensive foundation. (Even if the only thing those programmers asked for was that you release your code as well if you use their code.)

Proprietary code is expensive. For a reason. And in the long run it always loses to the commoditization of software. And cheating to delay that outcome is *odious*.

I highly recommend using a language other than R if you don't plan to distribute source code with your software. That will simplify the licensing issue significantly and make distributing the blob much more straightforward.

On July 23, 2019 2:10:30 PM PDT, "Weiwen Ng, MPH" <[hidden email]> wrote:

>The ad hominem comment about Google skills is also out of line. Knowing
>what to search for is often not trivial. The problem is magnified if
>English isn't your native language.
>
>On Tue, Jul 23, 2019 at 3:59 PM John Maindonald
><[hidden email]>
>wrote:
>
>> I think this unfair, certainly the ‘odious’ comment.  Very many of us
>> have been able to contribute because supported to do such work
>> while occupying relatively comfortable academic positions.  In the
>> process of getting there, we have benefited enormously from the
>> work of those who have gone before.  I do not know what Anamika’s
>> position is, but he may well be trying to build a business from a
>> much less privileged starting point than others of us may have
>> enjoyed.  In any case, the comment strikes a tone that is out of
>> place in respectful discourse.
>>
>>
>> John Maindonald             email: [hidden email]<mailto:
>> [hidden email]>
>>
>>
>> On 23/07/2019, at 22:00, [hidden email]<mailto:
>> [hidden email]> wrote:
>>
>> From: Jeff Newmiller <[hidden email]<mailto:
>> [hidden email]>>
>> Subject: Re: [R] Regarding R licensing usage guidance
>> Date: 23 July 2019 at 07:00:26 NZST
>> To: <[hidden email]<mailto:[hidden email]>>, ANAMIKA
>KUMARI <
>> [hidden email]<mailto:[hidden email]>>
>>
>>
>> Your internet skills are pathetic. Search Google for "proprietary use
>gpl"
>> and the first hit is
>>
>>
>>
>https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i
>>
>> Note that there are (at least) three obvious alternatives if there is
>any
>> question in your case: release the code under GPL but also sell it
>with
>> support (a la RStudio); only use it yourself (don't distribute it at
>all);
>> or only use R for setting up your models but re-engineer
>implementations of
>> the run-time prediction calculations yourself (often much easier than
>the
>> initial algorithm development).
>>
>> I think your desperation to steal the hard work of the various R
>> contributors seems quite odious.
>>
>> On July 22, 2019 6:55:31 AM PDT, ANAMIKA KUMARI
><[hidden email]
>> <mailto:[hidden email]>> wrote:
>> Hello Team,
>>
>> This mail is in reference to understanding R  license and also usage
>of
>> R
>> language to develop commercialised product.
>>
>> I am working on one product of mine that uses R and python language.I
>> am
>> trying to understand the licensing issue if any related to R, if I am
>> going
>> to commercialise my product and keep my work proprietary.
>>
>> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do
>I
>> need to share source code of my product. if, I am moving planning  to
>> move
>> it to production or I can keep my code Proprietary.
>>
>> Please note that I am just using R and its packages to  develop my
>own
>> statistical tool and api and Have not done any changes to existing R
>> code.
>>
>> Please refer below for all R-packages used in my code:-
>>
>>  1.
>> *R-3.4.4 *
>>  2. *'spacyr'*
>>  3.
>> *'jsonlite' *
>>  4.
>> *'lubridate' *
>>  5.
>> *'data.table' *
>>  6.
>> *'png' *
>>  7.
>> *'maps' *
>>  8.
>> *'countrycode' *
>>  9.
>> *'humaniformat' *
>>  10.
>> *'ngram' *
>>  11.
>> *'stringr' *
>>  12.
>> *'slam' *
>>  13.
>> *'tm' *
>>  14.
>> *'lsa' *
>>  15.
>> *'RTextTools' *
>>  16.
>> *'stringi' *
>>  17.
>> *'plumber' *
>>  18. *"Rook"*
>>  19. *"pdftools"*
>>  20. *'tokenizers'*
>>  21. *'zoo'*
>>  22. *"tidyr"*
>>  23. *"reqres"*
>>  24. *"rJava"*
>>  25. *"tiff"*
>>  26. *"splitstackshape"*
>>  27. *"stringdist"*
>>  28. *"RJSONIO"*
>>  29. *"ropensci/tabulizer"*
>>  30. *"staplr"*
>>  31. *"SparseM"*
>>  32. *"randomForest"*
>>  33. *"e1071"*
>>  34. *"ipred"*
>>  35. *"caTools"*
>>  36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>>  37. *RCMD INSTALL tree_1.0-39.tar.gz*
>>  38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>>
>>
>> *Any help from you will be highly appreciated as I am literally stuck
>> at a
>> dead end.*
>>
>> *Regards*
>> *Anamika Kumari*
>>
>> [[alternative HTML version deleted]]
>>
>> ______________________________________________
>> [hidden email]<mailto:[hidden email]> mailing list -- To
>> UNSUBSCRIBE and more, see
>> https://stat.ethz.ch/mailman/listinfo/r-help
>> PLEASE do read the posting guide
>> http://www.R-project.org/posting-guide.html<
>> http://www.r-project.org/posting-guide.html>
>> and provide commented, minimal, self-contained, reproducible code.
>>
>> --
>> Sent from my phone. Please excuse my brevity.
>>
>>
>>         [[alternative HTML version deleted]]
>>
>> ______________________________________________
>> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
>> https://stat.ethz.ch/mailman/listinfo/r-help
>> PLEASE do read the posting guide
>> http://www.R-project.org/posting-guide.html
>> and provide commented, minimal, self-contained, reproducible code.
>>
>
> [[alternative HTML version deleted]]
>
>______________________________________________
>[hidden email] mailing list -- To UNSUBSCRIBE and more, see
>https://stat.ethz.ch/mailman/listinfo/r-help
>PLEASE do read the posting guide
>http://www.R-project.org/posting-guide.html
>and provide commented, minimal, self-contained, reproducible code.

--
Sent from my phone. Please excuse my brevity.

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [FORGED] Re: Regarding R licensing usage guidance

Rolf Turner

Jeff:  Your comments are often (almost always?) a bit rough about the
edges, and on the recipient, but are always cogent.  Although John M.
has a valid point, I tend to agree with you.  I would say that if you
want to make money, trying to sell your own software is a bad way to go
about it, GPL or no GPL.

Rather like being an actor; you will almost surely starve.   The
difference with actors is that a tiny fraction of them sometimes make
big bucks.  Whereas, with selling your own software, never.  (And
*please* don't hold up Bill Gates as a counterexample.  He did not make
his big bucks by selling his own software.  He made them from wheeling
and dealing and selling *other people's* software.  E.g. "MSDOS" was
just a renaming of "QDOS" ("Quick and Dirty Operating System") which
Gates bought for 50 thousand US dollars.)

cheers,

Rolf

P.S. To Anamika:  Please do not post in HTML.

R.

On 24/07/19 11:21 AM, Jeff Newmiller wrote:

> Your feelings are noted, but my comment about skills was not directed at the person of Anamika but at their skills, so no, it was not ad hominem.
>
> Regarding the word "odious"... I think that wrapping GPL software in a proprietary blob is ethically flawed, and that word is appropriate regardless of the possible economic disadvantage someone might have who commits that behavior. I have no problem with people generating proprietary blobs of code they wrote combined with supporting code licensed in a way that allows for such use... my employers have paid me to produce such works in the past, but such blobs should rightfully reflect the work input by the programmer and not the massive input by people not being properly compensated for building such an extensive foundation. (Even if the only thing those programmers asked for was that you release your code as well if you use their code.)
>
> Proprietary code is expensive. For a reason. And in the long run it always loses to the commoditization of software. And cheating to delay that outcome is *odious*.
>
> I highly recommend using a language other than R if you don't plan to distribute source code with your software. That will simplify the licensing issue significantly and make distributing the blob much more straightforward.
>
> On July 23, 2019 2:10:30 PM PDT, "Weiwen Ng, MPH" <[hidden email]> wrote:
>> The ad hominem comment about Google skills is also out of line. Knowing
>> what to search for is often not trivial. The problem is magnified if
>> English isn't your native language.
>>
>> On Tue, Jul 23, 2019 at 3:59 PM John Maindonald
>> <[hidden email]>
>> wrote:
>>
>>> I think this unfair, certainly the ‘odious’ comment.  Very many of us
>>> have been able to contribute because supported to do such work
>>> while occupying relatively comfortable academic positions.  In the
>>> process of getting there, we have benefited enormously from the
>>> work of those who have gone before.  I do not know what Anamika’s
>>> position is, but he may well be trying to build a business from a
>>> much less privileged starting point than others of us may have
>>> enjoyed.  In any case, the comment strikes a tone that is out of
>>> place in respectful discourse.
>>>
>>>
>>> John Maindonald             email: [hidden email]<mailto:
>>> [hidden email]>
>>>
>>>
>>> On 23/07/2019, at 22:00, [hidden email]<mailto:
>>> [hidden email]> wrote:
>>>
>>> From: Jeff Newmiller <[hidden email]<mailto:
>>> [hidden email]>>
>>> Subject: Re: [R] Regarding R licensing usage guidance
>>> Date: 23 July 2019 at 07:00:26 NZST
>>> To: <[hidden email]<mailto:[hidden email]>>, ANAMIKA
>> KUMARI <
>>> [hidden email]<mailto:[hidden email]>>
>>>
>>>
>>> Your internet skills are pathetic. Search Google for "proprietary use
>> gpl"
>>> and the first hit is
>>>
>>>
>>>
>> https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i
>>>
>>> Note that there are (at least) three obvious alternatives if there is
>> any
>>> question in your case: release the code under GPL but also sell it
>> with
>>> support (a la RStudio); only use it yourself (don't distribute it at
>> all);
>>> or only use R for setting up your models but re-engineer
>> implementations of
>>> the run-time prediction calculations yourself (often much easier than
>> the
>>> initial algorithm development).
>>>
>>> I think your desperation to steal the hard work of the various R
>>> contributors seems quite odious.
>>>
>>> On July 22, 2019 6:55:31 AM PDT, ANAMIKA KUMARI
>> <[hidden email]
>>> <mailto:[hidden email]>> wrote:
>>> Hello Team,
>>>
>>> This mail is in reference to understanding R  license and also usage
>> of
>>> R
>>> language to develop commercialised product.
>>>
>>> I am working on one product of mine that uses R and python language.I
>>> am
>>> trying to understand the licensing issue if any related to R, if I am
>>> going
>>> to commercialise my product and keep my work proprietary.
>>>
>>> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do
>> I
>>> need to share source code of my product. if, I am moving planning  to
>>> move
>>> it to production or I can keep my code Proprietary.
>>>
>>> Please note that I am just using R and its packages to  develop my
>> own
>>> statistical tool and api and Have not done any changes to existing R
>>> code.
>>>
>>> Please refer below for all R-packages used in my code:-
>>>
>>>   1.
>>> *R-3.4.4 *
>>>   2. *'spacyr'*
>>>   3.
>>> *'jsonlite' *
>>>   4.
>>> *'lubridate' *
>>>   5.
>>> *'data.table' *
>>>   6.
>>> *'png' *
>>>   7.
>>> *'maps' *
>>>   8.
>>> *'countrycode' *
>>>   9.
>>> *'humaniformat' *
>>>   10.
>>> *'ngram' *
>>>   11.
>>> *'stringr' *
>>>   12.
>>> *'slam' *
>>>   13.
>>> *'tm' *
>>>   14.
>>> *'lsa' *
>>>   15.
>>> *'RTextTools' *
>>>   16.
>>> *'stringi' *
>>>   17.
>>> *'plumber' *
>>>   18. *"Rook"*
>>>   19. *"pdftools"*
>>>   20. *'tokenizers'*
>>>   21. *'zoo'*
>>>   22. *"tidyr"*
>>>   23. *"reqres"*
>>>   24. *"rJava"*
>>>   25. *"tiff"*
>>>   26. *"splitstackshape"*
>>>   27. *"stringdist"*
>>>   28. *"RJSONIO"*
>>>   29. *"ropensci/tabulizer"*
>>>   30. *"staplr"*
>>>   31. *"SparseM"*
>>>   32. *"randomForest"*
>>>   33. *"e1071"*
>>>   34. *"ipred"*
>>>   35. *"caTools"*
>>>   36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
>>>   37. *RCMD INSTALL tree_1.0-39.tar.gz*
>>>   38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
>>>
>>>
>>> *Any help from you will be highly appreciated as I am literally stuck
>>> at a
>>> dead end.*
>>>
>>> *Regards*
>>> *Anamika Kumari*
>>>
>>> [[alternative HTML version deleted]]

--
Honorary Research Fellow
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Abby Spurdle
In reply to this post by Jeff Newmiller
> I highly recommend using a language other than R if you don't plan to
distribute source code with your software.

I disagree.
I don't think the goal of this forum is to dis-incentivise the use of R.

Yes, users are subject to the GPL.
But beyond that, what they do is up to them.

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Weiwen Ng, MPH
In reply to this post by Jeff Newmiller
Here's one way to phrase your reply:

"I'd recommend you search Google. For example, the search string
"proprietary use GPL" produces one hit that's clearly relevant to you:

https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i


Moreover, many people in this community strongly discourage disseminating
proprietary code based on R. R, after all, is free software, (fill in some
other objections here). Here are three easy alternatives I can think of:
(list the three)"

This method is more neutrally worded. It doesn't insult the original
poster. It doesn't assume the poster had bad intent.

Instead, you chose to phrase it thus:

"Your internet skills are pathetic. Search Google for "proprietary use gpl"
and the first hit is ...  Note that there are (at least) three obvious
alternatives if there is any question in your case ...   I think your
desperation to steal the hard work of the various R contributors seems
quite odious."

Think about the overall tone of your post. Consider also that someone who
agrees with you substantive argument said that your comments were "often
(almost always?) a bit rough about the
edges."

On Tue, Jul 23, 2019 at 6:27 PM Jeff Newmiller <[hidden email]>
wrote:

> Your feelings are noted, but my comment about skills was not directed at
> the person of Anamika but at their skills, so no, it was not ad hominem.
>
> Regarding the word "odious"... I think that wrapping GPL software in a
> proprietary blob is ethically flawed, and that word is appropriate
> regardless of the possible economic disadvantage someone might have who
> commits that behavior. I have no problem with people generating proprietary
> blobs of code they wrote combined with supporting code licensed in a way
> that allows for such use... my employers have paid me to produce such works
> in the past, but such blobs should rightfully reflect the work input by the
> programmer and not the massive input by people not being properly
> compensated for building such an extensive foundation. (Even if the only
> thing those programmers asked for was that you release your code as well if
> you use their code.)
>
> Proprietary code is expensive. For a reason. And in the long run it always
> loses to the commoditization of software. And cheating to delay that
> outcome is *odious*.
>
> I highly recommend using a language other than R if you don't plan to
> distribute source code with your software. That will simplify the licensing
> issue significantly and make distributing the blob much more
> straightforward.
>
> On July 23, 2019 2:10:30 PM PDT, "Weiwen Ng, MPH" <[hidden email]>
> wrote:
> >The ad hominem comment about Google skills is also out of line. Knowing
> >what to search for is often not trivial. The problem is magnified if
> >English isn't your native language.
> >
> >On Tue, Jul 23, 2019 at 3:59 PM John Maindonald
> ><[hidden email]>
> >wrote:
> >
> >> I think this unfair, certainly the ‘odious’ comment.  Very many of us
> >> have been able to contribute because supported to do such work
> >> while occupying relatively comfortable academic positions.  In the
> >> process of getting there, we have benefited enormously from the
> >> work of those who have gone before.  I do not know what Anamika’s
> >> position is, but he may well be trying to build a business from a
> >> much less privileged starting point than others of us may have
> >> enjoyed.  In any case, the comment strikes a tone that is out of
> >> place in respectful discourse.
> >>
> >>
> >> John Maindonald             email: [hidden email]<mailto:
> >> [hidden email]>
> >>
> >>
> >> On 23/07/2019, at 22:00, [hidden email]<mailto:
> >> [hidden email]> wrote:
> >>
> >> From: Jeff Newmiller <[hidden email]<mailto:
> >> [hidden email]>>
> >> Subject: Re: [R] Regarding R licensing usage guidance
> >> Date: 23 July 2019 at 07:00:26 NZST
> >> To: <[hidden email]<mailto:[hidden email]>>, ANAMIKA
> >KUMARI <
> >> [hidden email]<mailto:[hidden email]>>
> >>
> >>
> >> Your internet skills are pathetic. Search Google for "proprietary use
> >gpl"
> >> and the first hit is
> >>
> >>
> >>
> >
> https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i
> >>
> >> Note that there are (at least) three obvious alternatives if there is
> >any
> >> question in your case: release the code under GPL but also sell it
> >with
> >> support (a la RStudio); only use it yourself (don't distribute it at
> >all);
> >> or only use R for setting up your models but re-engineer
> >implementations of
> >> the run-time prediction calculations yourself (often much easier than
> >the
> >> initial algorithm development).
> >>
> >> I think your desperation to steal the hard work of the various R
> >> contributors seems quite odious.
> >>
> >> On July 22, 2019 6:55:31 AM PDT, ANAMIKA KUMARI
> ><[hidden email]
> >> <mailto:[hidden email]>> wrote:
> >> Hello Team,
> >>
> >> This mail is in reference to understanding R  license and also usage
> >of
> >> R
> >> language to develop commercialised product.
> >>
> >> I am working on one product of mine that uses R and python language.I
> >> am
> >> trying to understand the licensing issue if any related to R, if I am
> >> going
> >> to commercialise my product and keep my work proprietary.
> >>
> >> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do
> >I
> >> need to share source code of my product. if, I am moving planning  to
> >> move
> >> it to production or I can keep my code Proprietary.
> >>
> >> Please note that I am just using R and its packages to  develop my
> >own
> >> statistical tool and api and Have not done any changes to existing R
> >> code.
> >>
> >> Please refer below for all R-packages used in my code:-
> >>
> >>  1.
> >> *R-3.4.4 *
> >>  2. *'spacyr'*
> >>  3.
> >> *'jsonlite' *
> >>  4.
> >> *'lubridate' *
> >>  5.
> >> *'data.table' *
> >>  6.
> >> *'png' *
> >>  7.
> >> *'maps' *
> >>  8.
> >> *'countrycode' *
> >>  9.
> >> *'humaniformat' *
> >>  10.
> >> *'ngram' *
> >>  11.
> >> *'stringr' *
> >>  12.
> >> *'slam' *
> >>  13.
> >> *'tm' *
> >>  14.
> >> *'lsa' *
> >>  15.
> >> *'RTextTools' *
> >>  16.
> >> *'stringi' *
> >>  17.
> >> *'plumber' *
> >>  18. *"Rook"*
> >>  19. *"pdftools"*
> >>  20. *'tokenizers'*
> >>  21. *'zoo'*
> >>  22. *"tidyr"*
> >>  23. *"reqres"*
> >>  24. *"rJava"*
> >>  25. *"tiff"*
> >>  26. *"splitstackshape"*
> >>  27. *"stringdist"*
> >>  28. *"RJSONIO"*
> >>  29. *"ropensci/tabulizer"*
> >>  30. *"staplr"*
> >>  31. *"SparseM"*
> >>  32. *"randomForest"*
> >>  33. *"e1071"*
> >>  34. *"ipred"*
> >>  35. *"caTools"*
> >>  36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
> >>  37. *RCMD INSTALL tree_1.0-39.tar.gz*
> >>  38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
> >>
> >>
> >> *Any help from you will be highly appreciated as I am literally stuck
> >> at a
> >> dead end.*
> >>
> >> *Regards*
> >> *Anamika Kumari*
> >>
> >> [[alternative HTML version deleted]]
> >>
> >> ______________________________________________
> >> [hidden email]<mailto:[hidden email]> mailing list -- To
> >> UNSUBSCRIBE and more, see
> >> https://stat.ethz.ch/mailman/listinfo/r-help
> >> PLEASE do read the posting guide
> >> http://www.R-project.org/posting-guide.html<
> >> http://www.r-project.org/posting-guide.html>
> >> and provide commented, minimal, self-contained, reproducible code.
> >>
> >> --
> >> Sent from my phone. Please excuse my brevity.
> >>
> >>
> >>         [[alternative HTML version deleted]]
> >>
> >> ______________________________________________
> >> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> >> https://stat.ethz.ch/mailman/listinfo/r-help
> >> PLEASE do read the posting guide
> >> http://www.R-project.org/posting-guide.html
> >> and provide commented, minimal, self-contained, reproducible code.
> >>
> >
> >       [[alternative HTML version deleted]]
> >
> >______________________________________________
> >[hidden email] mailing list -- To UNSUBSCRIBE and more, see
> >https://stat.ethz.ch/mailman/listinfo/r-help
> >PLEASE do read the posting guide
> >http://www.R-project.org/posting-guide.html
> >and provide commented, minimal, self-contained, reproducible code.
>
> --
> Sent from my phone. Please excuse my brevity.
>

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [FORGED] Re: Regarding R licensing usage guidance

Rolf Turner

On 25/07/19 4:36 AM, Weiwen Ng, MPH wrote:

> Here's one way to phrase your reply:
>
> "I'd recommend you search Google. For example, the search string
> "proprietary use GPL" produces one hit that's clearly relevant to you:

<SNIP>

> This method is more neutrally worded. It doesn't insult the original
> poster. It doesn't assume the poster had bad intent.
>
> Instead, you chose to phrase it thus:
>
> "Your internet skills are pathetic. Search Google for "proprietary use gpl"
> and the first hit is ...  Note that there are (at least) three obvious
> alternatives if there is any question in your case ...   I think your
> desperation to steal the hard work of the various R contributors seems
> quite odious."
>
> Think about the overall tone of your post. Consider also that someone who
> agrees with you substantive argument said that your comments were "often
> (almost always?) a bit rough about the edges."

Yeah, but Jeff's rough-about-the-edges phrasing is much more colourful,
and colourful is *GOOD*.  There is far too much bland "Shhhh. We
*mustn't* offend anybody" content in current discourse.  Tell it like it
is!  Ripley into people!  If the recipient can't take the heat, he or
she should get out of the kitchen!

See also fortunes::fortune(87).

cheers,

Rolf Turner

P.S.  Jeff makes a huge and extremely useful contribution to R-help.  He
gives generously of time and effort to solve beginners' problems.  They
should appreciate the time and effort and not whinge about being offended.

R. T.

--
Honorary Research Fellow
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [FORGED] Re: Regarding R licensing usage guidance

Andrew Robinson-2
I most firmly do not agree with you, Rolf.

Over the years that I've been a member of this community I've noted the actions of a small group who have seemed to feel that it is ok to be an asshole to other people, and a group of hangers-on who have applauded and egged on this shameful behaviour.  Some members of this group have moved on, some remain. For a long while, R-help was quite toxic.

Jeff's response was uncharacteristically rude and should be called out.  I ordinarily find Jeff to be terse, which is totally fine, and not colourful, which is also fine.  If you want colour, go watch WWE.

Best wishes,

Andrew
--
Andrew Robinson
Director, CEBRA, School of BioSciences
Reader & Associate Professor in Applied Statistics  Tel: (+61) 0403 138 955 <tel:0403%20138%20955>
School of Mathematics and Statistics                        Fax: (+61) 03 8344 4599 <tel:(03)%208344%204599>
University of Melbourne, VIC 3010 Australia
Email: [hidden email]    
Website: http://www.ms.unimelb.edu.au/~andrewpr
 

On 7/25/19, 7:50 AM, "R-help on behalf of Rolf Turner" <[hidden email] on behalf of [hidden email]> wrote:

   
    On 25/07/19 4:36 AM, Weiwen Ng, MPH wrote:
   
    > Here's one way to phrase your reply:
    >
    > "I'd recommend you search Google. For example, the search string
    > "proprietary use GPL" produces one hit that's clearly relevant to you:
   
    <SNIP>
   
    > This method is more neutrally worded. It doesn't insult the original
    > poster. It doesn't assume the poster had bad intent.
    >
    > Instead, you chose to phrase it thus:
    >
    > "Your internet skills are pathetic. Search Google for "proprietary use gpl"
    > and the first hit is ...  Note that there are (at least) three obvious
    > alternatives if there is any question in your case ...   I think your
    > desperation to steal the hard work of the various R contributors seems
    > quite odious."
    >
    > Think about the overall tone of your post. Consider also that someone who
    > agrees with you substantive argument said that your comments were "often
    > (almost always?) a bit rough about the edges."
   
    Yeah, but Jeff's rough-about-the-edges phrasing is much more colourful,
    and colourful is *GOOD*.  There is far too much bland "Shhhh. We
    *mustn't* offend anybody" content in current discourse.  Tell it like it
    is!  Ripley into people!  If the recipient can't take the heat, he or
    she should get out of the kitchen!
   
    See also fortunes::fortune(87).
   
    cheers,
   
    Rolf Turner
   
    P.S.  Jeff makes a huge and extremely useful contribution to R-help.  He
    gives generously of time and effort to solve beginners' problems.  They
    should appreciate the time and effort and not whinge about being offended.
   
    R. T.
   
    --
    Honorary Research Fellow
    Department of Statistics
    University of Auckland
    Phone: +64-9-373-7599 ext. 88276
   
    ______________________________________________
    [hidden email] mailing list -- To UNSUBSCRIBE and more, see
    https://stat.ethz.ch/mailman/listinfo/r-help
    PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
    and provide commented, minimal, self-contained, reproducible code.
   
   

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [FORGED] Re: Regarding R licensing usage guidance

R help mailing list-2
In reply to this post by Rolf Turner
Hi Rolf:

As they say,  do read the posting guide:

> Good manners: Remember that customs differ. Some people are very direct. Others surround everything they say with hedges and apologies. Be tolerant. Rudeness is never warranted, but sometimes `read the manual’ is the appropriate response. Don’t waste time discussing such matters on the list. Ad hominem comments are absolutely out of place.


-Roy


>
> On Jul 24, 2019, at 2:49 PM, Rolf Turner <[hidden email]> wrote:
>
>
> On 25/07/19 4:36 AM, Weiwen Ng, MPH wrote:
>
>> Here's one way to phrase your reply:
>> "I'd recommend you search Google. For example, the search string
>> "proprietary use GPL" produces one hit that's clearly relevant to you:
>
> <SNIP>
>
>> This method is more neutrally worded. It doesn't insult the original
>> poster. It doesn't assume the poster had bad intent.
>> Instead, you chose to phrase it thus:
>> "Your internet skills are pathetic. Search Google for "proprietary use gpl"
>> and the first hit is ...  Note that there are (at least) three obvious
>> alternatives if there is any question in your case ...   I think your
>> desperation to steal the hard work of the various R contributors seems
>> quite odious."
>> Think about the overall tone of your post. Consider also that someone who
>> agrees with you substantive argument said that your comments were "often
>> (almost always?) a bit rough about the edges."
>
> Yeah, but Jeff's rough-about-the-edges phrasing is much more colourful, and colourful is *GOOD*.  There is far too much bland "Shhhh. We *mustn't* offend anybody" content in current discourse.  Tell it like it is!  Ripley into people!  If the recipient can't take the heat, he or she should get out of the kitchen!
>
> See also fortunes::fortune(87).
>
> cheers,
>
> Rolf Turner
>
> P.S.  Jeff makes a huge and extremely useful contribution to R-help.  He gives generously of time and effort to solve beginners' problems.  They should appreciate the time and effort and not whinge about being offended.
>
> R. T.
>
> --
> Honorary Research Fellow
> Department of Statistics
> University of Auckland
> Phone: +64-9-373-7599 ext. 88276
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

**********************
"The contents of this message do not reflect any position of the U.S. Government or NOAA."
**********************
Roy Mendelssohn
Supervisory Operations Research Analyst
NOAA/NMFS
Environmental Research Division
Southwest Fisheries Science Center
***Note new street address***
110 McAllister Way
Santa Cruz, CA 95060
Phone: (831)-420-3666
Fax: (831) 420-3980
e-mail: [hidden email] www: http://www.pfeg.noaa.gov/

"Old age and treachery will overcome youth and skill."
"From those who have been given much, much will be expected"
"the arc of the moral universe is long, but it bends toward justice" -MLK Jr.

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [External] Re: [FORGED] Re: Regarding R licensing usage guidance

Tierney, Luke
Thanks Roy -- I was about to write along the same lines.

Best,

luke

On Wed, 24 Jul 2019, Roy Mendelssohn - NOAA Federal via R-help wrote:

> Hi Rolf:
>
> As they say,  do read the posting guide:
>
>> Good manners: Remember that customs differ. Some people are very direct. Others surround everything they say with hedges and apologies. Be tolerant. Rudeness is never warranted, but sometimes `read the manual’ is the appropriate response. Don’t waste time discussing such matters on the list. Ad hominem comments are absolutely out of place.
>
>
> -Roy
>
>
>>
>> On Jul 24, 2019, at 2:49 PM, Rolf Turner <[hidden email]> wrote:
>>
>>
>> On 25/07/19 4:36 AM, Weiwen Ng, MPH wrote:
>>
>>> Here's one way to phrase your reply:
>>> "I'd recommend you search Google. For example, the search string
>>> "proprietary use GPL" produces one hit that's clearly relevant to you:
>>
>> <SNIP>
>>
>>> This method is more neutrally worded. It doesn't insult the original
>>> poster. It doesn't assume the poster had bad intent.
>>> Instead, you chose to phrase it thus:
>>> "Your internet skills are pathetic. Search Google for "proprietary use gpl"
>>> and the first hit is ...  Note that there are (at least) three obvious
>>> alternatives if there is any question in your case ...   I think your
>>> desperation to steal the hard work of the various R contributors seems
>>> quite odious."
>>> Think about the overall tone of your post. Consider also that someone who
>>> agrees with you substantive argument said that your comments were "often
>>> (almost always?) a bit rough about the edges."
>>
>> Yeah, but Jeff's rough-about-the-edges phrasing is much more colourful, and colourful is *GOOD*.  There is far too much bland "Shhhh. We *mustn't* offend anybody" content in current discourse.  Tell it like it is!  Ripley into people!  If the recipient can't take the heat, he or she should get out of the kitchen!
>>
>> See also fortunes::fortune(87).
>>
>> cheers,
>>
>> Rolf Turner
>>
>> P.S.  Jeff makes a huge and extremely useful contribution to R-help.  He gives generously of time and effort to solve beginners' problems.  They should appreciate the time and effort and not whinge about being offended.
>>
>> R. T.
>>
>> --
>> Honorary Research Fellow
>> Department of Statistics
>> University of Auckland
>> Phone: +64-9-373-7599 ext. 88276
>>
>> ______________________________________________
>> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
>> https://stat.ethz.ch/mailman/listinfo/r-help
>> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
>> and provide commented, minimal, self-contained, reproducible code.
>
> **********************
> "The contents of this message do not reflect any position of the U.S. Government or NOAA."
> **********************
> Roy Mendelssohn
> Supervisory Operations Research Analyst
> NOAA/NMFS
> Environmental Research Division
> Southwest Fisheries Science Center
> ***Note new street address***
> 110 McAllister Way
> Santa Cruz, CA 95060
> Phone: (831)-420-3666
> Fax: (831) 420-3980
> e-mail: [hidden email] www: http://www.pfeg.noaa.gov/
>
> "Old age and treachery will overcome youth and skill."
> "From those who have been given much, much will be expected"
> "the arc of the moral universe is long, but it bends toward justice" -MLK Jr.
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>

--
Luke Tierney
Ralph E. Wareham Professor of Mathematical Sciences
University of Iowa                  Phone:             319-335-3386
Department of Statistics and        Fax:               319-335-3017
    Actuarial Science
241 Schaeffer Hall                  email:   [hidden email]
Iowa City, IA 52242                 WWW:  http://www.stat.uiowa.edu
______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: [External] Re: [FORGED] Re: Regarding R licensing usage guidance

Abby Spurdle
I don't think these threads have answered the original question.

According to the GPL FAQ:
https://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL

"If a programming language interpreter is released under the GPL, does that
mean programs written to be interpreted by it must be under GPL-compatible
licenses? ...The interpreted program, to the interpreter, is just
data... However, when the interpreter is extended to provide “bindings” to
other facilities (often, but not necessarily, libraries), the interpreted
program is effectively linked to the facilities it uses through these
bindings. So if these facilities are released under the GPL, the
interpreted program that uses them must be released in a GPL-compatible
way..."

My interpretation of that, is that the Anamika's R program would need to be
GPL-compatible.

This issue is not completely straightforward.
(e.g. You can have an interpreted program within an interpreted program).
And CRAN packages released under permissive licenses (e.g. BSD, MIT) are
questionable.

None of this is intended to mean, that you shouldn't use R.
But rather, if you use R, there are certain constraints, and I would hope
that the benefits of using R outweigh any perceived cost of such
constraints.

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Reply | Threaded
Open this post in threaded view
|

Re: Regarding R licensing usage guidance

Richard O'Keefe-2
In reply to this post by Weiwen Ng, MPH
If calling a separate chunk of GPL code forced your code to be GPL,
nobody would be able to write proprietary code on Linux.  For example,
Intel would not be able to sell their C/C++ compiler without offering
source code, which they don't.

When you are coupling two programs in this way, one question is "how
independent are they?"  For example, if I write a program in AWK,
it will run under the One True AWK, under gawk, or under mawk.  Nobody
can claim that it is a mere extension of one of them.  Unless I use a
gawk-specific feature...  Or if I write a shell script, as long as it
works just as well with ksh as with bash, nobody can claim it is a
derived work of bash.

Now R is to S-Plus as bash is to ksh.  If your program could use *either*,
and if you just provide your own program, leaving it to the purchaser to
choose between S-Plus and (unmodified!) R, wouldn't the same apply?

You might like to check
https://discourse.julialang.org/t/what-is-the-business-model-of-julia-packages/3488/3


On Thu, 25 Jul 2019 at 04:37, Weiwen Ng, MPH <[hidden email]> wrote:

> Here's one way to phrase your reply:
>
> "I'd recommend you search Google. For example, the search string
> "proprietary use GPL" produces one hit that's clearly relevant to you:
>
>
> https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i
>
>
> Moreover, many people in this community strongly discourage disseminating
> proprietary code based on R. R, after all, is free software, (fill in some
> other objections here). Here are three easy alternatives I can think of:
> (list the three)"
>
> This method is more neutrally worded. It doesn't insult the original
> poster. It doesn't assume the poster had bad intent.
>
> Instead, you chose to phrase it thus:
>
> "Your internet skills are pathetic. Search Google for "proprietary use gpl"
> and the first hit is ...  Note that there are (at least) three obvious
> alternatives if there is any question in your case ...   I think your
> desperation to steal the hard work of the various R contributors seems
> quite odious."
>
> Think about the overall tone of your post. Consider also that someone who
> agrees with you substantive argument said that your comments were "often
> (almost always?) a bit rough about the
> edges."
>
> On Tue, Jul 23, 2019 at 6:27 PM Jeff Newmiller <[hidden email]>
> wrote:
>
> > Your feelings are noted, but my comment about skills was not directed at
> > the person of Anamika but at their skills, so no, it was not ad hominem.
> >
> > Regarding the word "odious"... I think that wrapping GPL software in a
> > proprietary blob is ethically flawed, and that word is appropriate
> > regardless of the possible economic disadvantage someone might have who
> > commits that behavior. I have no problem with people generating
> proprietary
> > blobs of code they wrote combined with supporting code licensed in a way
> > that allows for such use... my employers have paid me to produce such
> works
> > in the past, but such blobs should rightfully reflect the work input by
> the
> > programmer and not the massive input by people not being properly
> > compensated for building such an extensive foundation. (Even if the only
> > thing those programmers asked for was that you release your code as well
> if
> > you use their code.)
> >
> > Proprietary code is expensive. For a reason. And in the long run it
> always
> > loses to the commoditization of software. And cheating to delay that
> > outcome is *odious*.
> >
> > I highly recommend using a language other than R if you don't plan to
> > distribute source code with your software. That will simplify the
> licensing
> > issue significantly and make distributing the blob much more
> > straightforward.
> >
> > On July 23, 2019 2:10:30 PM PDT, "Weiwen Ng, MPH" <[hidden email]>
> > wrote:
> > >The ad hominem comment about Google skills is also out of line. Knowing
> > >what to search for is often not trivial. The problem is magnified if
> > >English isn't your native language.
> > >
> > >On Tue, Jul 23, 2019 at 3:59 PM John Maindonald
> > ><[hidden email]>
> > >wrote:
> > >
> > >> I think this unfair, certainly the ‘odious’ comment.  Very many of us
> > >> have been able to contribute because supported to do such work
> > >> while occupying relatively comfortable academic positions.  In the
> > >> process of getting there, we have benefited enormously from the
> > >> work of those who have gone before.  I do not know what Anamika’s
> > >> position is, but he may well be trying to build a business from a
> > >> much less privileged starting point than others of us may have
> > >> enjoyed.  In any case, the comment strikes a tone that is out of
> > >> place in respectful discourse.
> > >>
> > >>
> > >> John Maindonald             email: [hidden email]<mailto:
> > >> [hidden email]>
> > >>
> > >>
> > >> On 23/07/2019, at 22:00, [hidden email]<mailto:
> > >> [hidden email]> wrote:
> > >>
> > >> From: Jeff Newmiller <[hidden email]<mailto:
> > >> [hidden email]>>
> > >> Subject: Re: [R] Regarding R licensing usage guidance
> > >> Date: 23 July 2019 at 07:00:26 NZST
> > >> To: <[hidden email]<mailto:[hidden email]>>, ANAMIKA
> > >KUMARI <
> > >> [hidden email]<mailto:[hidden email]>>
> > >>
> > >>
> > >> Your internet skills are pathetic. Search Google for "proprietary use
> > >gpl"
> > >> and the first hit is
> > >>
> > >>
> > >>
> > >
> >
> https://opensource.stackexchange.com/questions/7078/is-it-legal-to-use-gpl-code-in-a-proprietary-closed-source-program-by-putting-i
> > >>
> > >> Note that there are (at least) three obvious alternatives if there is
> > >any
> > >> question in your case: release the code under GPL but also sell it
> > >with
> > >> support (a la RStudio); only use it yourself (don't distribute it at
> > >all);
> > >> or only use R for setting up your models but re-engineer
> > >implementations of
> > >> the run-time prediction calculations yourself (often much easier than
> > >the
> > >> initial algorithm development).
> > >>
> > >> I think your desperation to steal the hard work of the various R
> > >> contributors seems quite odious.
> > >>
> > >> On July 22, 2019 6:55:31 AM PDT, ANAMIKA KUMARI
> > ><[hidden email]
> > >> <mailto:[hidden email]>> wrote:
> > >> Hello Team,
> > >>
> > >> This mail is in reference to understanding R  license and also usage
> > >of
> > >> R
> > >> language to develop commercialised product.
> > >>
> > >> I am working on one product of mine that uses R and python language.I
> > >> am
> > >> trying to understand the licensing issue if any related to R, if I am
> > >> going
> > >> to commercialise my product and keep my work proprietary.
> > >>
> > >> I need your help to understand it. R comes under GNU-GPL-2.0. Now, do
> > >I
> > >> need to share source code of my product. if, I am moving planning  to
> > >> move
> > >> it to production or I can keep my code Proprietary.
> > >>
> > >> Please note that I am just using R and its packages to  develop my
> > >own
> > >> statistical tool and api and Have not done any changes to existing R
> > >> code.
> > >>
> > >> Please refer below for all R-packages used in my code:-
> > >>
> > >>  1.
> > >> *R-3.4.4 *
> > >>  2. *'spacyr'*
> > >>  3.
> > >> *'jsonlite' *
> > >>  4.
> > >> *'lubridate' *
> > >>  5.
> > >> *'data.table' *
> > >>  6.
> > >> *'png' *
> > >>  7.
> > >> *'maps' *
> > >>  8.
> > >> *'countrycode' *
> > >>  9.
> > >> *'humaniformat' *
> > >>  10.
> > >> *'ngram' *
> > >>  11.
> > >> *'stringr' *
> > >>  12.
> > >> *'slam' *
> > >>  13.
> > >> *'tm' *
> > >>  14.
> > >> *'lsa' *
> > >>  15.
> > >> *'RTextTools' *
> > >>  16.
> > >> *'stringi' *
> > >>  17.
> > >> *'plumber' *
> > >>  18. *"Rook"*
> > >>  19. *"pdftools"*
> > >>  20. *'tokenizers'*
> > >>  21. *'zoo'*
> > >>  22. *"tidyr"*
> > >>  23. *"reqres"*
> > >>  24. *"rJava"*
> > >>  25. *"tiff"*
> > >>  26. *"splitstackshape"*
> > >>  27. *"stringdist"*
> > >>  28. *"RJSONIO"*
> > >>  29. *"ropensci/tabulizer"*
> > >>  30. *"staplr"*
> > >>  31. *"SparseM"*
> > >>  32. *"randomForest"*
> > >>  33. *"e1071"*
> > >>  34. *"ipred"*
> > >>  35. *"caTools"*
> > >>  36. *RCMD INSTALL maxent_1.3.3.1.tar.gz*
> > >>  37. *RCMD INSTALL tree_1.0-39.tar.gz*
> > >>  38. *RCMD INSTALL RTextTools_1.4.2.tar.gz*
> > >>
> > >>
> > >> *Any help from you will be highly appreciated as I am literally stuck
> > >> at a
> > >> dead end.*
> > >>
> > >> *Regards*
> > >> *Anamika Kumari*
> > >>
> > >> [[alternative HTML version deleted]]
> > >>
> > >> ______________________________________________
> > >> [hidden email]<mailto:[hidden email]> mailing list -- To
> > >> UNSUBSCRIBE and more, see
> > >> https://stat.ethz.ch/mailman/listinfo/r-help
> > >> PLEASE do read the posting guide
> > >> http://www.R-project.org/posting-guide.html<
> > >> http://www.r-project.org/posting-guide.html>
> > >> and provide commented, minimal, self-contained, reproducible code.
> > >>
> > >> --
> > >> Sent from my phone. Please excuse my brevity.
> > >>
> > >>
> > >>         [[alternative HTML version deleted]]
> > >>
> > >> ______________________________________________
> > >> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> > >> https://stat.ethz.ch/mailman/listinfo/r-help
> > >> PLEASE do read the posting guide
> > >> http://www.R-project.org/posting-guide.html
> > >> and provide commented, minimal, self-contained, reproducible code.
> > >>
> > >
> > >       [[alternative HTML version deleted]]
> > >
> > >______________________________________________
> > >[hidden email] mailing list -- To UNSUBSCRIBE and more, see
> > >https://stat.ethz.ch/mailman/listinfo/r-help
> > >PLEASE do read the posting guide
> > >http://www.R-project.org/posting-guide.html
> > >and provide commented, minimal, self-contained, reproducible code.
> >
> > --
> > Sent from my phone. Please excuse my brevity.
> >
>
>         [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email] mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
> http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
12