I applaud your brevity! I've pulled together some additional details into a
shared document, and copy-pasted the 'short answer' section below for convenience that intends to answer the
question regarding the pending items regarding the naming for both the project and the verification checkmark. The Short answer and a much Longer answer section with far more additional information and links to references are in the shared document.
There is no new project being introduced, the naming for the project remains “Eclipse Temurin”.
This initiative is an evolution of the reproducibility feature that has been developed under the Temurin project for the past two years. The new work is called “verified reproducibility” and it includes:
Instructions for how to reproduce a Temurin build using information found in the accompanying Temurin SBOM.
A test case to verify the reproduced artifact is byte-for-byte identical to the original downloaded Temurin artifact.
An attestation mechanism with an industry-defined format that allows reproducers to be able to report that they have verified the reproducibility of Temurin.
Naming for verification can align with the SLSA terminology, “verified reproducible”. We envisage verified reproducible build indications that link to the attestation(s) files that have been provided by 3rd parties.
Currently, the list of Temurin builds on the Adoptium website displays checkmarks. Special care was applied in naming the two checkmarks that are attached to artifacts on the Adoptium website, “JCK certified” to denote that builds are compliant with the Java language specification and “AQAvit verified” to denote that builds pass the quality bar as they have passed the AQAvit suite of tests. In keeping with that same 2-word phrasing, we are planning to introduce a third checkmark for Temurin builds listed on the Adoptium website with the wording “verified Reproducible” or “Reproducible verified” or “Reproducibility verified”.