Benjamin Poldrack

I see two things to think about: 1.) > Rather than fiddling with the internal parameterization of a single special remote type, let's switch externaltype= when a reconfig is required....

> I could not come up with a use case that would require a local reconfiguration. AFAIR all such scenarios lead to problems down the line. I think we had...

> Can you describe a concrete case, where this is desired, and that is not a plain consumption (read-only) case? RIA store, which for consumption is set up to be...

However, this business might be addressable by having yet another `sameas` remote (+ proper costs obv.) rather than reconfiguration. May be that's the better way.

Since removing this from core somewhat "breaks" existing datasets using the special remote, while core can not pull in an extension as a dependency and we can't mark a particular...

Thx, @yarikoptic. All addressed, I think.

This has been addressed in `maint` as far as I can tell.

FTR: With the current state of things, this smells like a clone patch for resolving the DOI (just like we resolve a RIA URL). Seems to me this is the...

> maybe there is something similar for travis Closest I could find is an approach like this (so, nothing built-in): https://github.com/google/EarlGrey/pull/383/files/3b38a5dea36a88aba42a42931e77a7c5429a1837 However, I've pushed the suggestion for appveyor in PR...

> It would be nice to get this vetted by @bpoldrack so that the tiny doc fix for #6800 can finally make it in. Yes, looks good to me. Thank...