Jon Johnson

Just to be clear, my answers are based mostly on experience operating a registry and writing a few registry clients -- I wasn't part of the initial spec writing, so...

> And, that's not the expensive part. I think that's roughly the point of the "never delete" crowd -- it doesn't cost that much to store these, so why clean...

I am really confused about why you want to check in a requirements doc to the spec?

> we propose Who is we? > To foster consistency > enabling the community > To facilitate discussions, prioritization and phased implementations Just as general feedback, I would omit stuff...

> Is there anything you're not opposed to? 😏 In terms of breaking changes, probably not. For additive changes that introduce new concepts, the change need to be _obviously good_,...

@jdolitsky relevant to the PR @dmcgowan may have more historical context for this client authors: please let me know if you disagree with my assessment of SRMU use in the...

@rchincha I'm not sure I follow -- can you explain how on-prem use cases relate to monolithic uploads?

> How many customers actually do SRMU and why? I am only aware of one client that does this (by default). Not sure why, but I would guess because sending...

Oh and I forgot to respond to the original point re: on-prem... The multi-request upload path _allows_ for the registry to hand off ingress to a separate service, but doesn't...

What does this solve?