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.

Sign up for GitHub

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

Jump to bottom

DVC README #2433

Closed
dberenbaum opened this issue Apr 29, 2021 · 4 comments
Closed

DVC README #2433

dberenbaum opened this issue Apr 29, 2021 · 4 comments
Labels
p1-important Active priorities to deal within next sprints status: stale You've been groomed!

Comments

@dberenbaum
Copy link
Contributor

dberenbaum commented Apr 29, 2021 •
edited by jorgeorpinel
Loading

Review the README in https://github.com/iterative/dvc since it is the first thing some users see, and it includes sections like "Comparison to related technologies" that may need to be updated and/or integrated into dvc.org.

UPDATE: See some ideas in #2443
@jorgeorpinel jorgeorpinel added 🐛 type: bug Something isn't working. p1-important Active priorities to deal within next sprints labels Apr 29, 2021
@shcheklein shcheklein removed the 🐛 type: bug Something isn't working. label Apr 30, 2021
@casperdcl casperdcl mentioned this issue May 4, 2021
Closed
8 tasks
@jorgeorpinel
Copy link
Contributor

Should we merge or clearly separate with #2443?

@dberenbaum
Copy link
Contributor Author

I vote to keep separate since #2443 is more general about the structure of a readme and applies across products. This one is specifically a need to review the dvc readme. I view #2443 as more of an epic/discussion ticket and this one as a narrower one under that, but as long as we end up reviewing the dvc readme, I'm open to however you want to structure the tickets.

@dberenbaum
Copy link
Contributor Author

I see you and @casperdcl already came to the same conclusion in #2443! Yay, more agreement!

@jorgeorpinel
Copy link
Contributor

Closing in favor of #2443

@jorgeorpinel jorgeorpinel added the status: stale You've been groomed! label Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
p1-important Active priorities to deal within next sprints status: stale You've been groomed!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jorgeorpinel @dberenbaum @shcheklein