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

Absorbing Understanding DVC #1320

Closed
wants to merge 2 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 0 additions & 53 deletions content/docs/understanding-dvc/collaboration-issues.md

This file was deleted.

20 changes: 0 additions & 20 deletions content/docs/understanding-dvc/core-features.md

This file was deleted.

34 changes: 0 additions & 34 deletions content/docs/understanding-dvc/existing-tools.md

This file was deleted.

141 changes: 0 additions & 141 deletions content/docs/understanding-dvc/related-technologies.md

This file was deleted.

57 changes: 0 additions & 57 deletions content/docs/understanding-dvc/what-is-dvc.md

This file was deleted.

9 changes: 9 additions & 0 deletions content/docs/use-cases/index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# Use Cases

## Collaboration Issues in Data Science

Even with all the success we've seen today in machine learning (ML),
specifically deep learning and its applications in business, the data science
community still lacks good practices for organizing their projects and
effectively collaborating across their varied ML projects. This is a critical
challenge: we need to evolve towards ML algorithms and methods no longer being
tribal knowledge and making them easy to implement, reuse, and manage.

We provide short articles on common ML workflow or data management scenarios
that DVC can help with or improve. These include the motivating context (usually
extracted from real-life cases); And the approaches to solving them can combine
Expand Down
16 changes: 16 additions & 0 deletions content/docs/user-guide/index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,21 @@
# User Guide

Data Version Control, or DVC, is **a new type of experiment management
software** that has been built **on top of the existing engineering toolset that
you're already used to**, and particularly on a source code version control
system (currently Git). DVC reduces the gap between existing tools and data
science needs, allowing users to take advantage of experiment management
software while reusing existing skills and intuition.

The underlying source code control system eliminates the need to use external
services. Data science experiment sharing and collaboration can be done through
regular Git tools (commit messages, merges, pull requests, etc) the same way it
works for software engineers.

DVC implements a **Git experimentation methodology** where each experiment
exists with its code as well as data, and can be represented as a separate Git
branch or commit.

Comment on lines +3 to +18
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here (copy-pasted from content/docs/understanding-dvc/what-is-dvc.md)

Our guides describe the main DVC concepts and features comprehensively,
explaining when and how to use them, as well as connections between them. These
guides don't focus on specific scenarios, but have a general scope – like a user
Expand Down