Clarify ORAS is not an OCI project#56
Clarify ORAS is not an OCI project#56sudo-bmitch wants to merge 1 commit intoopencontainers:mainfrom
Conversation
Signed-off-by: Brandon Mitchell <git@bmitch.net>
| 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. |
There was a problem hiding this comment.
How about one of these instead?
| - There also exists [oras-project/artifacts-spec repository][oras-artifacts] that is not part of OCI or the above working group. |
or
| - 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. |
There was a problem hiding this comment.
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
|
ok.. thx for the suggestions see new readme and reopen / rebase if you think we need more changes :-) |
|
FWIW I don't think the recent change in #57 does much to address the original goal of this PR. |
|
Yeah, reading the readme, I'm left with the impression that OCI is considering both the working group output, and ORAS equally. We should either remove ORAS or add all of the other projects implementing methods to push artifacts to avoid playing favorites. |
|
a couple reminders from the oci tob charter quoted without comment:
@sudo-bmitch I like your idea about adding/listing all other projects (artifacts related) in the Related Projects Working on Extending OCI Specs section.. that's more than fair, and proper I think. |
Based on discussions in ORAS/artifacts-spec #96 and ORAS/artifacts-spec #88, I think the wording in the readme gives the false impression that ORAS/artifact-spec is being used as a staging ground for future changes to this or other OCI specs. This clarifies they are their own project developing their own spec separate from the working group.
Signed-off-by: Brandon Mitchell git@bmitch.net