ORAS project community maturity

[scottrigby]

Hi everyone. As part of the goal of establishing a backwards compatibility contract for ORAS (oras-project/oras-go#47), here are a few things that may help:

• ORAS project community meeting
  • can we do weekly, at least as we work toward a 1.0 milestone for January?
  • meetings recorded, posted publicly, etc
    • anyone can join
    • are you open to using community.cncf.io to keep maintenance simple?
  • a publicly accessible notes doc
• Addtl community maintainers
  • to help with various project needs, so it can be organized in a vendor-neutral way, continue to grow, welcome new contributors, etc
    • for example, introduce an easy process for introducing new features
  • ensure regular meetings happen, are announced publicly, recorded, notes were taken etc
  • ensure policies are clearly specified and up to date (for example, that ORAS project follows Semantic Versioning. This makes clear to end users what scheme the compatibility contract follows so they know what to trust)
  • could this fit into new "subproject owners"? https://github.com/oras-project/community/blob/main/governance/GOVERNANCE.md#subproject-owners

[scottrigby]

I believe we agreed to use the old "CNCF oras-artifacts-spec" meeting as an ORAS project meeting.

• Notes doc: https://hackmd.io/P-O6n222TcSMoJgHmTTduw
• Can an existing maintainer please request CNCF update the meeting name on https://www.cncf.io/calendar/

Community maintainer PR forthcoming

[TerryHowe]

Meetings are bi-weekly now. I feel like some of the boxes/bullet items are checked. Can we make a separate issue for the remaining items like it seems like we could document semantic versioning if we need to