Skip to content
This repository has been archived by the owner on Jul 18, 2023. It is now read-only.

Clarify ORAS is not an OCI project #56

Closed
wants to merge 1 commit into from
Closed

Clarify ORAS is not an OCI project #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ The current state of the [OCI Artifacts][oci-artifacts] repository:
- The repository contains guidance for using [v1.0.1][oci-image-v101] of the [OCI image manifest][image-manifest] representing *individual* non-container image artifact types.
- This project recognizes that additional work is needed to find ways to improve existing OCI artifact types, such as OCI images, to formally include a software bill of materials (SBOMs), scan results, signatures, and other OCI artifact related extensions. Depending on the implementation chosen, additional APIs to manage these extensions may also be needed. We believe these requirements will either require modifications to the existing specs or some new specification depending on the output of various working groups.
This project, however, does not currently have the mission to create new specifications or commit changes to the existing specifications.
- External to OCI there exists an active community of developers working under the [oras-project/artifacts-spec repository][oras-artifacts] on proposed changes to the OCI specifications.
- An [OCI working group for reference types][oci-reftype-wg] has been proposed to work out how OCI should adopt these extensions.
- There also exists [oras-project/artifacts-spec repository][oras-artifacts] that is not part of OCI or the above working group.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about one of these instead?

Suggested change
- There also exists [oras-project/artifacts-spec repository][oras-artifacts] that is not part of OCI or the above working group.

or

Suggested change
- There also exists [oras-project/artifacts-spec repository][oras-artifacts] that is not part of OCI or the above working group.
- There also exists [oras-project/artifacts-spec repository][oras-artifacts] which has submitted [Proposal A](https://github.com/opencontainers/wg-reference-types/blob/main/docs/proposals/PROPOSAL_A.md) to the above working group.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the second edit, let's see if we need subjective comments about any of the other oci compatible / related artifact manifest/refers projects, then see if we still want this change. Cheers, Mike


## Project Governance and License

Expand Down