Copy-pasting from the email: 

Summary: Owners of container images that are not presently built in a way that enables building of corresponding source images need to adjust how their container images are built.

 

 

Hello everyone,

 

I am part of a team that helps Red Hat meet its legal obligations when we redistribute our open source-based products. To ensure that we comply with Red Hat’s[ internal policy|https://source.redhat.com/groups/public/open-source-legal-issues/open_source_legal_resources_wiki/protocol_for_source_availability_and_open_source_license_compliance] regarding source code availability, each container image that is published must be accompanied by a published source image. For container repositories that have existing, non-compliant images (no accompanying source image), there must be a source image for at least the most recently published product image. Publication of license compliance failures (container images that lack a corresponding source image) will be blocked starting at the end of CY22.

 

A great deal of work has already been done to ensure that we are compliant, however, there is currently a set of containers which are still ineligible for source container publication (approximately 10%).  Therefore, we are reaching out to you as owners of the following containers to request that you include in your Q4 planning to turn those containers eligible by the end of CY22:

• x3scale-amp2/backend-rhel8

- 3scale-amp2/system-rhel7

- 3scale-amp2/toolbox-rhel8

- 3scale-amp2/zync-rhel8

 

This work can be done by following these instructions. If you have questions on the valid content type for source containers you can also read this article.

 

After you read this email and have the opportunity to go through the instructions, please let us know:

1) When you expect to be able to perform this work.

2) If there are any impediments to being able to make the containers eligible before the end of CY22.

3) If you expect to require technical support and, if so, when and what degree of support is expected. Knowing this beforehand will allow us to plan and ensure we have the required resources available.

4) If you decide to track this by Jira, please share the issue with Beatriz Couto and Bryan Sutula . We will also be creating our own Jira for tracking purposes and we will share them with you.

 

We need to hear back from you before September 21. Please reach out in case you have any questions.

 

Thank you in advance for your support in this initiative,
 
Beatriz