Skip to content

Commit

Permalink
correct sentences
Browse files Browse the repository at this point in the history
Signed-off-by: Francesco Murdaca <[email protected]>
  • Loading branch information
Francesco Murdaca committed Nov 3, 2020
1 parent e3f1aab commit e17c0e1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/0000-dependencies-management-jupyter-notebooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@

How to guarantee reproducibility of Jupyter Notebooks?

In order to allow any user to re run the notebook having similar behaviour, it's important that each notebook is shipped with dependencies requirements
In order to allow any user to re run the notebook with similar behaviour, it's important that each notebook is shipped with dependencies requirements
that include direct and transitive dependencies. This would also enforce and support security, reproducibility, traecability.

Each notebook should be treated as single component/service that use its own dependencies, therefore when storing notebooks, they should be created in a specific repo.
Each notebook should be treated as single component/service that use its own dependencies, therefore when storing notebooks, they should be stored each in a specific repo.

## Decision Drivers <!-- optional -->

Expand Down

0 comments on commit e17c0e1

Please sign in to comment.