From c1947126dc0599540d58d5051e87ea838014a30a Mon Sep 17 00:00:00 2001 From: Nick Coghlan Date: Wed, 14 Mar 2018 21:06:13 +1000 Subject: [PATCH] Revise `pipenv check` caveat for pyup.io feedback Jannis Gebauer of pyup.io let us know that he's definitely fine with commercial *use* of the `pipenv check` feature, so it's only commercial redistributors of `pipenv` that may need to take a closer look at the licensing situation, and perhaps talk to `pyup.io` directly. Follow-up to #1651 --- docs/advanced.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/advanced.rst b/docs/advanced.rst index a13c12cd..62f21ac3 100644 --- a/docs/advanced.rst +++ b/docs/advanced.rst @@ -186,11 +186,12 @@ Example:: .. note:: - Commercial users and redistributors of `pipenv` should be aware that the public - `Safety-DB` project backing this feature is licensed as CC-BY-NC-SA. Non-commercial - use of this feature and use by organisations with their own pyup.io commercial license - are thus both clearly fine, but other commercial redistributors and end users may want - to perform their own legal assessment before relying on the capability. + Commercial redistributors of `pipenv` should be aware that the public `Safety-DB` + project backing this feature is licensed as CC-BY-NC-SA by `pyup.io`. While + `pyup.io` have [stated explicitly](https://github.com/pypa/pipenv/issues/1651#issuecomment-372583779) + that commercial *use* of this `pipenv` feature is fine, commercial redistributors may want + to perform their own legal assessment and perhaps chat directly to `pyup.io` about + the specific licensing terms. ☤ Community Integrations