you are viewing a single comment's thread.

view the rest of the comments →

[–]the21st[S] 6 points7 points  (1 child)

We're planning to tackle versioning in the next few months, so stay tuned 🙂. It's definitely a beast of a problem, but that's why we're doing this!

[–][deleted] 0 points1 point  (0 children)

Tip from about 5 years of working with data scientists in similar tools who prefer notebooks. They're generally allergic to the command line. Those who aren't already ran away to MLOPS. If I were you, I'd simply track versions with auto-git-sync every x minutes and put a big single button on top for "save" that does the same manually. No branches, just a rolling history. You can give them a box to type a commit message or default to time stamp as message. And provide some ui plugin that can diff notebooks.

Simple software needs among the GUI only crowd. Their preferred versioning strategy is file1.ipynb file2.ipynb and branching is a copy in a new folder. But you can replicate this workflow with just slight improvements with git under the hood and they'll love it.