Thx folks. I didn't mean to cause a stir :-)
I've had colleagues receive cease & desists (and worse) before and
it's been my experience that a large # of folks have no idea these
type of cite restrictions exist.
-Bob
On Thu, Aug 4, 2016 at 6:36 AM, Uwe Ligges
ROpenSci's onboarding process has a checkbox for confirming that the
package "does not violate the Terms of Service of any service it
interacts with.":
https://github.com/ropensci/onboarding/blob/master/issue_template.md
I also have a vague memory of this discussion a few years ago on
CRAN will follow up with the package maintainer.
Best,
Uwe Ligges
On 04.08.2016 10:50, peter dalgaard wrote:
On 04 Aug 2016, at 05:21 , Dirk Eddelbuettel wrote:
On 3 August 2016 at 22:26, Bob Rudis wrote:
| I came across
On 03/08/2016 10:26 PM, Bob Rudis wrote:
I came across https://cran.rstudio.com/web/packages/boxoffice/index.html
in CRAN today and while I don't expect CRAN to be a legal authority,
should there not be some kind of policy for excluding R packages that
deliberately violate (data) site ToS? (I'm
On 04 Aug 2016, at 05:21 , Dirk Eddelbuettel wrote:
>
> On 3 August 2016 at 22:26, Bob Rudis wrote:
> | I came across https://cran.rstudio.com/web/packages/boxoffice/index.html
> | in CRAN today and while I don't expect CRAN to be a legal authority,
> | should there not be
On 3 August 2016 at 22:26, Bob Rudis wrote:
| I came across https://cran.rstudio.com/web/packages/boxoffice/index.html
| in CRAN today and while I don't expect CRAN to be a legal authority,
| should there not be some kind of policy for excluding R packages that
| deliberately violate (data) site
I came across https://cran.rstudio.com/web/packages/boxoffice/index.html
in CRAN today and while I don't expect CRAN to be a legal authority,
should there not be some kind of policy for excluding R packages that
deliberately violate (data) site ToS? (I'm asking this here vs sending
a note to CRAN