Epic Goal

• Allow organizations to carry user visible metadata that allows to identify origin and ownership of content contained in this organization
• allow FOSS projects like CentOS to provide a representation of their project via a Quay.io organization

Why is this important?

• For quay.io to be a viable alternative to DockerHub we have to improvement the level of customization FOSS project owners can apply to their representation on quay.io
• Currently there is no way to provide information about the project/software/group at a Quay.io organization level, compared to https://index.docker.io/_/centos/ for instances
• community users need a way to learn about the authenticity and ownerships of a project represented on quay.io otherwise there are trust issues

Scenarios

1. An org owner wants to share details about the FOSS project that delivers it's content via Quay.io
2. An org owner wants to share license details about the content provided
3. An org owner wants to set a particular icon for their project (doable today)

Acceptance Criteria

• Limited Markdown support (no external references)
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. n/a

Open questions:

1. Any other discrete metadata that we are missing here?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>