Bugzilla – Full Text Bug Listing
| Summary: | [proposal] adoptium.temurin-compliance | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Ed.Merks, mariateresa.delgado, mikael.barbero, paul.buck, proposals-inbox, sharon.corbett, slambert, t.p.ellison, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-temurin-compliance | ||
| Whiteboard: | |||
|
Description
Wayne Beaton
Architecture Council Member Ed Merks has volunteered to help mentor the project. I'd like to schedule a creation review to conclude on February 17/2021. We have most of what we need. At the moment, the proposal does not list any licenses or indicate where the team wants to maintain source code. It's not clear to me whether or not the project will have any source content of its own. Is it the case that the project will consume source code artifacts produced by other projects and exists more-or-less exclusively as a means of managing the relationship with the restricted access to the Oracle Java SE Compatility Kit. Is there any need for this project to have a Git repository of its own? This project will require private Git repositories to store the TCK content received from Oracle, create issues being worked for any TCK problems identified in Temurin binaries that cannot be handled in the public project, and for capturing evidence of the TCK results to be able to demonstrate compliance if required. The license of such materials will be Oracle commercial (for TCK material), or held privately by the Eclipse Foundation only to be used in the context of this project by Temurin-compliance committers. The EMO may choose how they would like that identified in the repository. Source code authored by Eclipse contributors, such as the tooling and services to support running the TCK, will reside in AQAvit. There will be no need for an open github repositories related to this project. (terminology using JCK synonymously with TCK) Private repositories needed for: - holding FAQ/doc/issues + JCK results for committers actively running JCKs (both automated and manual) - 1 repo per version of JCK materials we pull from the Oracle site JCK8-unzipped, JCK11-unzipped, JCK16-unzipped, etc As Tim already mentioned, the nature of the licenses needed are for Eclipse Foundation to determine, based on the OCTLA with Oracle (giving Eclipse Foundation access to the compliance test material under that agreement). There is both a TCK infra requirements document and the Adoptium transition plan in the Working Group shared Google drive that describes this project's requirements and action plan in greater detail. We have the necessary agreements in place to create this project. Let's set the license to EPL-2.0; we'll adjust as (or if) necessary. Let's set the repository type to GitHub. I'm pretty sure that this project will have no publicly-accessible repositories (Maria Teresa, we'll have to keep this mind when we engage in reviews). I've added Mikael from the IT team in copy; I believe that he's already started work on the infrastructure. I believe that we can reasonably assert that the community review period requirement has been met and there's no reason to delay creation further. Maria Teresa, please proceed with the creation. I've updated the project proposal to reflect the selection of License and repository type. I've added the project relationships as well in the database. The project has been successfully created! I've taken note of the privacy of the project repo for the future. Webmaster please initiate the provisioning process. I'm closing this bug since I believe this project is fully operational. |