Derek McGowan

Does this still work having `before = ["."]` in the Protobuild file? I noticed with this change it wasn't able to resolve a local file unless I converted `"."` to...

> **Manifest**: a JSON document which defines an Artifact. Manifests are defined under the OCI Image Spec The definition given for 1.0 was more about what is being done today...

@ad-m we have tried to avoid a need to including authorization in the specification. From an implementation standpoint though, it is hard to be completely opaque and attempting to do...

@JeremyLoy the original issue was stalled not on politics, but rather a full assessment done on the impact and a recommendation for how to change the spec. It is related...

> At the very least, we should update the spec to say that clients should interpret 201 as "upload succeeded" and 202 as "proceed with upload at Location" This sounds...

> Without releases I can't tell its stability. Is this an experiment that might easily change or something that's stable with staying power? I would like to better understand what...

> Why do clients need to know anything about pull-through caching if its implemented server-side? The clients should know how the registry host was resolved from a given image reference....

> Right... isn't that the point? That is one use case that will still work. In the example you mentioned, when a repository is proxied in that fashion, the puller...

> I'm concerned we're adding quite a bit of complexity to address a use case that has simpler solutions when configured on the registry side. Can you elaborate here? Configuring...

> how does the client know that? The clients have the most context and really does not need to be defined here, only that a client SHOULD make that distinction...