Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: Add ORAS new year blog #75

Merged
merged 11 commits into from
Jan 13, 2023
Merged

doc: Add ORAS new year blog #75

merged 11 commits into from
Jan 13, 2023

Conversation

FeynmanZhou
Copy link
Member

@FeynmanZhou FeynmanZhou commented Jan 3, 2023

This PR adds a blog to summarize the key progress and highlights in 2022 and look forward to 2023

@SteveLasker
Copy link
Contributor

Thanks @FeynmanZhou and @TerryHowe for the review.
The blog post looks great, capturing the progress on the tech and the community. Kudos to you and your team for really building the community this past year.
I agree with Terry's changes and looking forward to an LGTM with those minor tweaks.

@yizha1
Copy link

yizha1 commented Jan 4, 2023

Thanks @FeynmanZhou , incredibly good content.

Copy link
Contributor

@SteveLasker SteveLasker left a comment

Choose a reason for hiding this comment

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

LGTM
Move to publish ASAP as the "new year" is quickly fading :)

@FeynmanZhou
Copy link
Member Author

FeynmanZhou commented Jan 10, 2023

@SteveLasker Thanks!
BTW, @shizhMSFT as an ORAS owner now has the management permission of ORAS-www Netlify. We will fix the Netlify CI problem today.

image

- [Notary v2](https://github.com/notaryproject/notation)
- [KubeApps](https://github.com/vmware-tanzu/kubeapps) by VMware Tanzu
- [VMware Application Catalog](https://tanzu.vmware.com/application-catalog)
- [UOR Framework](https://universalreference.io/) by Red Hat
Copy link

Choose a reason for hiding this comment

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

Thank you for the shout-out! We've renamed UOR Framework to Emporous recently. Might you please change this entry for UOR Framework to "Emporous (Formerly UOR Framework)"?

Copy link
Member Author

Choose a reason for hiding this comment

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

Renamed to "Emporous (Formerly UOR Framework)"

- [Deploy OCI artifacts and Helm charts the GitOps way with Config Sync](https://cloud.google.com/blog/products/containers-kubernetes/gitops-with-oci-artifacts-and-config-sync) from Google Cloud blogs
- [Storing ABAP build artifacts in OCI registry](https://blogs.sap.com/2022/07/26/storing-abap-build-artifacts-in-oci-registry/) by [Lars Hvam](https://people.sap.com/lars.hvam) from the SAP community blog

### Presentations at conferences
Copy link

Choose a reason for hiding this comment

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

Might you please add the below entry to the "Presentations at conferences" section:

[Unleashing the Power of the Container Registry](https://www.youtube.com/watch?v=6fohG10y3z0&t=2002s) at DevConf.us by Andrew Block & Alex Flom

cc @sabre1041

Copy link
Member Author

Choose a reason for hiding this comment

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

@afflom Good point. Added to the list above.

Copy link

Choose a reason for hiding this comment

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

Thanks so much! @FeynmanZhou

@FeynmanZhou
Copy link
Member Author

The Netlify problem has been fixed. Now it's available to preview it https://deploy-preview-75--oras-project.netlify.app/blog/oras-looking-back-at-2022-and-forward-to-2023/


Just a few years ago, there were no standards nor tooling for registries to natively store, discover, and pull a graph of OCI artifacts. To extend the registry’s role and form the industry standard, ORAS maintainers proposed a new artifact manifest type to describe and query relationships between objects stored in a registry, without mutating the existing content.

Initially, the reference types work was incubated under the CNCF [ORAS Artifact manifest](https://github.com/oras-project/artifacts-spec) project. It has been contributed to the OCI Image and Distribution v1.1 specifications in Sep 2022. Now it forms the industry standard and has been adopted by some cloud providers and open-source projects, such as [Azure Container Registry](https://azure.microsoft.com/en-us/products/container-registry) and [Zot registry](https://zotregistry.io/v1.4.3/).
Copy link

Choose a reason for hiding this comment

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

I believe the expectation is to have more and more registries support this after OCI 1.1 gets released. We should mention that support will grow after the release of OCI 1.1.

Copy link
Contributor

Choose a reason for hiding this comment

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

Agreed with Toddy. Adding some language to encourage folks to join would shift it from "here's the ones that have", to hear some of the early adopters which we're excited to see more join as all registries can support promoting artifacts across them.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch. I have incorporated @toddysm 's suggestion.

Copy link
Contributor

@SteveLasker SteveLasker left a comment

Choose a reason for hiding this comment

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

Thanks @FeynmanZhou
LGTM

Copy link
Contributor

@shizhMSFT shizhMSFT left a comment

Choose a reason for hiding this comment

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

LGTM

@shizhMSFT shizhMSFT merged commit d86be86 into oras-project:main Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants