Dave Berenbaum
Dave Berenbaum
After the discussions in https://github.com/iterative/dvc.org/pull/4460 about whether pipelines should be part of data management, experiments, or neither, I think we need to revisit this not only from a docs perspective,...
The first step could be adding a flag (`--no-exp`?) to make the current `dvc exp run` behave like `repro` so that we have one consolidated command we could use when...
Reminder that we also need to update the landing page if we decide to add a top-level command because it currently shows `dvc exp run`.
🤔 I prefer a top-level command to `exp run` for a few reasons: 1. It's not only about experiments. I'd say it's mostly about pipelines, and it happens to also...
> Yep, but what is the primary user scenario, high level case that we'll be explaining. E.g. can we start by writing a summary for this command that people, and...
Stepping back, here were my goals for prioritizing this: > Why it matters: > > * `repro` vs `exp run` confuses people > > * `exp run` (and its prominence...
> > bout adding a flag to exp run to make it work like repro (--no-exp/--no-save/--no-ref) and then making repro an alias of exp run > > I'm fine with...
Thanks @omesser! I don't think 2 is critical, especially since it doesn't sound like a breaking change. I was thinking of limiting 3.0 scope to 1 and making `dvc repro`...
@skshetry Thoughts on this?
> Hey, guys, my team also would find it useful to have `params.yaml` and `dvc.yaml` in the same folder. Something like > > ``` > contexts > └── > └──...