Skip to content

Latest commit

 

History

History
66 lines (55 loc) · 4.87 KB

APPROVED_LIBRARIES.md

File metadata and controls

66 lines (55 loc) · 4.87 KB

TODO_START When starting a project, the other company needs to approve the libraries/tools that we use. There are two options that the company can choose:

  • Send a generic approval (via email) that all the libraries that we decide to use are pre-approved.
  • Keep a list of the libraries, and when a new library is added, add it to the list and ask the company to approve.

If the former is selected, you can delete this file. If the latter, this file represents the list.

The way it works is the following:

  • First, make sure that all the licenses listed below are still valid (i.e., they did not change). You can use the link to speedup this process.
  • Note that the last time the list was checked was on 2023-April-04.
  • Then, ask the company to approve the list by writing "approved" (or similar), with their git account (this will prove that the company approval is authentic).
  • When new libraries are added, create a new section below (Dependencies as of ...), where you copy the old list and you modify it according to your needs.
  • Ask the company to approve with the method above (git commit).

Those instructions between TODO_START and TODO_END can be deleted.

TODO_END

Here is the list of dependencies required by Mila for the project development. Note that the following dependencies will trigger some other dependencies and for sake of simplicity, we are not listing them all. Modifications since last approved version are in bold.

Dependencies as of {PROJECT_START_DATE}

General dependencies

Library dependencies

(see setup.py)

Pre-trained models

Add any pre-trained models and associated licenses here if relevant.