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

Document dependencies #2

Open
ttoine opened this issue May 9, 2019 · 0 comments
Open

Document dependencies #2

ttoine opened this issue May 9, 2019 · 0 comments
Labels
corporations Target: Encourage corporate contributions critical Severity: Critical high Priority: High IP management Category: Intellectual property management activities

Comments

@ttoine
Copy link
Contributor

ttoine commented May 9, 2019

In order to make it easy for non developers to study the dependencies of the PrestaShop open source software, the Devdocs must include a tree of the dependencies, for the core and the native modules.

This must include:

  • Integrated dependencies in the repositories
  • Composer managed dependencies
  • NPM managed dependencies
  • The dependencies of the dependencies
  • And in general, all third party code and libraries used in the project.

A difference must be made between:

  • The dependencies that are built and redistributed in the PrestaShop installer of a release (the zip file)
  • The dependencies used only for development purpose and that are not included in the build

There are two aims:

  • Study and identify dependencies that are not compatible with the OSL license for redistribution
  • Generate comprehensive "third party licenses" files with lists and licences of all the dependencies in the project builds (core and native modules)

In general, please note that the PrestaShop open source project is distributed under the OSL license. It means that in the build/release, only third party code and libraries distributed under the compatible licenses must be used:

  • MIT
  • BSD
  • EUPL
  • AFL
  • OSL

"Development only" dependencies are not built and distributed in the software, so this license restriction does not apply.

@ttoine ttoine added high Priority: High IP management Category: Intellectual property management activities corporations Target: Encourage corporate contributions labels May 9, 2019
@ttoine ttoine added the critical Severity: Critical label Sep 11, 2019
M0rgan01 pushed a commit to M0rgan01/ps-open-source that referenced this issue Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
corporations Target: Encourage corporate contributions critical Severity: Critical high Priority: High IP management Category: Intellectual property management activities
Projects
None yet
Development

No branches or pull requests

1 participant