Add notes on options for handling model dependencies #366
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Ed Chalstrey <[email protected]>
|
My potentially controversial opinion is that if we get to the stage where the frontend successfully implements the model cards idea (described in 2.) we should go with option 3 "SaaS first" and even consider removing install functionality completely - see #346 |
Keep focus on problem in first section, rather than what we should do about it
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This note attempts to describe some of the options we've been considering for handling model packages and their dependencies (particularly system dependencies that can't be completely installed with pip), and some ideas about requirements we want from whatever we settle on.
The final version of this document is intended to describe the solution we have chosen, with some rationale, and the other options that weren't chosen. For now it is a collection of notes on a few of these options.
Comments and additional commits to this PR most welcome, particularly with additional ideas, extra detail on the existing ideas, thoughts, opinions, preferences etc.
Note that #325 and #347 would result in something like the second option ("pip with a 'model card'").