Create bazel-contrib/rules_oci

[alexeagle]

The distroless team at Google is among several sponsors of a project to make a new, slimmer container-building ruleset, replacing a subset of rules_docker. Other players include http://github.com/DataDog/rules_oci_bootstrap and https://github.com/aspect-build/rules_container, https://github.com/bazeltools/rules_minidock

The distroless team has asked that the repository for this ruleset be governed by bazel-contrib rather than under the GH org of a corporate entity like aspect-build.

https://bazel-contrib.github.io/SIG-rules-authors/hosting-policy.html#adding-criteria:

Must use an open-source license, preferably Apache-2.0.

Will be Apache-2.0

Must have wide applicability in the community.

Docker/containers are clearly one of the most critical needs for Bazel users

Must have a clear point of contact who answers questions from the SIG.

I can be the POC, along with @gregmagolan and @thesayyn

Must be “production quality”: clear README or other documentation outlining the goal of these rules, how to use them etc. generated API documentation include examples of use tests that are running continuously

We'll do these, based on the rules-template

Must reply to issues/PRs in 2-3 weeks (exact service level agreement TBD)

To start with, Aspect will provide this support - other contributors welcome.

Must have more than one person who is committed to review/approve PRs We recommend encoding this as a CODEOWNERS file.

Will make a CODEOWNERS with @thesayyn and at least one other person (likely from aspect-build)

Must publish semver releases. Optional: follow the same release pattern as the rules-template does.

Will follow that release pattern.

Must work with LTS Bazel version

Yup, will do.

[griffin]

👋 Happy to talk about some of the choices we made with https://github.com/DataDog/rules_oci , which we were focussing on creating all types of OCI-based artifacts. We're currently using them internally to create multi-arch images, improve build and pull times and remove Python from our toolchains as much as possible.

Currently the rules are split into two:

• https://github.com/DataDog/rules_oci - The meat and potatoes for building and pushing artifacts
• https://github.com/DataDog/rules_oci_bootstrap - For bootstrapping the rules toolchain from an OCI store, intended to be vendored or pulled via a git_repository

[alexeagle]

Approved based on no objections in two SIG meetings and no replies to https://groups.google.com/g/bazel-contrib/c/V4hxjwE0e6Y