Scott Ganyo

We'll just want to be very careful about package structure, names, and contents as we'd be implicitly declaring that this shouldn't break - at least between major versions.

Before digging into specific technical decisions, maybe we should discuss and agree on the UX benefits we'd like to accrue on the CLI. I'll take a crack at some that...

> Atomic configurations (ie. no partial property sets). I need help to understand this one Perhaps "coherent" would a better term. By this I mean that the entirety of a...

I feel flags are generally the better option for overrides as they require being explicit on the command line - as opposed to potentially unexpected overrides from the environment.

### Config reading proposal 1. Centralize a config lib for our code in all repos to use that consolidates access to configuration elements here in `pkg/config`. The config lib will...

> Is this proposal scoped to only the registry tool? This would be for all *clients* of the registry. The server should remain [configured on env vars](https://12factor.net/config). > Can you...

Sounds good. I'll move `connection/` to `/pkg/connection` as its related client library code and add the config loading there. We can start with the existing `Client` and `Settings` types in...

All related issues (links above) have been completed. Closing.

It would seem the prior art here is either git - which uses a tilde (eg. branch~2), or programming languages - which generally use a negative array reference counting from...

Perhaps we can work to get the generator fixed as well?