Steve Lasker

Understood. This is where we can get some consensus and a vote on why we need to delcare an implementation that only supports pull is a viable starting point. They're...

Great question. To be honest, I've been focused on how we add _new_ artifacts, and how we can link artifacts together with reference types, including the reverse lookup pattern. (like...

>suggest creating an incoming or under-consideration path for artifacts in progress and an approved path for artifacts approved... This is great suggestion. Reviewing the pr again, this looks like a...

@lumjjb, we've been discussing how we can enable flexibility to the manifests to support versioning within an artifact type. @justincormack has been proposing #37 as a superset of #29 to...

Thanks @jonjohnsonjr , As I reviewed the hackmd doc, posting here, I realized we had much better structure of conversation in the [KubeCon 2019 EU Notes: OCI Catalog Listing APIs](https://hackmd.io/p6MoABuDTdCeg8V1kmqmQw)...

Suggest adding a label for vNext to avoid this being incorporated into the v1 scope.

Just bumping a few links as searching/discovering and indexing continues to come up: - [OCI Artifacts and a View of the Future](https://stevelasker.blog/2019/08/25/oci-artifacts-and-a-view-of-the-future/) - [Artifact Services, the Case for a Generalized...

helm, bicep, wasm and others that are trying to utilize registries as their package management, so they don' have to build one.

Thanks for capturing this @gokarnm [Balancing usability and security](https://github.com/notaryproject/notaryproject/discussions/159), this is one of those places where I'd suggest we need to lean a bit more to the security side, with...

Who owns the action item to update the [Directory Structure Specification](https://github.com/notaryproject/notation/blob/main/specs/directory.md)? Is this assigned to @shizhMSFT? Thinking @dtzar, @FeynmanZhou, @iamsamirzon might be able to clarify the security/usability a bit first?