Dave Berenbaum

UX looks good! There have been discussions before about consolidating the import syntax (cc @efiop) and wondering if we should take the opportunity to do it here. For example: ```...

Notes from discussion with @skshetry: * Require a name for now * Treat datasets as frozen -- only possible to update using `dvc ds update` * Include version info only...

@skshetry What's the status of this?

Nice @skshetry! It works well for me in doing QA over various different types. I mostly have UI questions. > $ dvc ds add dvc://[email protected]:iterative/example-get-started.git@main#path=data/data.xml Do you have thoughts on...

> I am not against supporting this. But I find this url to be very complex, and I doubt if I'll remember it when I need it. Yup, it might...

I don't see a good reason to support non-versioned types like `https`, `hdfs`, and maybe even `remote` (I guess it depends if it's `version_aware`). It seems like external dependencies already...

Can you drop them from the parser help text in this PR? I was focused on that more than actually disabling them. Edit: Or is there some case where `https`...

For checkpoints, I think it will be necessary to unprotect because it's about loading state from the existing model file and writing an updated model file at the end. However,...

Yes, this was a mistake by me. I was thinking of a `dvc.yaml` option since it seems more useful to permanently specify the behavior than have to include the option...

> To be honest, it's not that clear why do we do this extra step (unprotect) in the first place. There are a lot of cases (majority of them to...