Bugzilla – Full Text Bug Listing
| Summary: | [proposal] adoptium.temurin | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | andreas, emijiang6, georgeadams1995, hendrik.ebbers, john.oliver+eclipse, mariateresa.delgado, martijnverburg, paul.buck, proposals-inbox, sgehwolf, sharon.corbett, slambert, t.p.ellison, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-temurin | ||
| Whiteboard: | |||
|
Description
Wayne Beaton
Architecture Council Member Emily Jiang has volunteered to mentor the project. Project team: I need contact information (email addresses) for the committers listed on the proposal. Can somebody provide that, please? Note that we need to list the project leads as committers as well (along with email addresses). > Note that we need to list the project leads as committers as well (along
> with email addresses).
I added the project leads to the committers list.
I need email addresses for all committers to complete the project creation process. We're totally blocked without them. I've removed the following individuals from the committers list: * Morgan Davies * Will Parker I'll just add them to the project team when I get the required information (that is, we can bypass the election process for these two committers). Any project lead can send an email to emo@eclipse.org with this information. I hadn't actually formally scheduled a creation review for this project because we were blocked on this, but I believe that we have satisfied the Eclipse Development Process' requirement for a creation review by virtue of the project proposal being available for community/membership review and comment for almost two full months, and all other requirements being met. I have, therefore, scheduled the creation review to conclude today. FYI (for project leads and committers). We have a documentation generator that provides templates for copyright headers, CONTRIBUTING and NOTICE files, etc. (e.g., [1]). We reference the generator in our documentation, and will likely bring it up during things like intellectual property reviews. The generator assumes some things that are not true for Eclipse Temurin. Specifically, the Eclipse Temurin project lists a collection of project licenses of which, by my understanding, separate aspects/components of the project will use some subset. The generator assumes that all of the project licenses should be mashed together into a multiply-licensed header. That is, it will generate a statement indicating that content can be consumed under one of three licenses and the SPDX expression that it generators will indicate that consumers can select any of five licenses (SPDX considers our secondary licensing scheme to be an "OR" selection of licenses). That is, the documentation generator will completely botch license statements and they'll have to be crafted (or at least adjusted) by hand. The IP Team can help. [1] https://www.eclipse.org/projects/tools/documentation.php?id=technology.aqavit Why are project leads also listed as committers on AQAvit[1], but not on Temurin[2]? [1] https://projects.eclipse.org/projects/adoptium.aqavit/who [2] https://projects.eclipse.org/projects/adoptium.temurin/who The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management:(Existing at Github) As your project's main Git repository is hosted at GitHub, we will need to move it to the Eclipse organization. This work can begin as soon as you have check in permission from EMO legal. Issue Tracker: Github issues will remain enabled for your project. Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/temurin-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/temurin.git Commits will be published to www.eclipse.org/temurin within 5 minutes Downloads: http://download.eclipse.org/temurin Archives: http://archive.eclipse.org/temurin Builds: You can upload releases to ~committer_id/downloads/temurin via SFTP or SCP (to build.eclipse.org) or from a CI instance at Eclipse.org Older builds should be moved to the archives area when they are no longer required. -M. (In reply to Tim Ellison from comment #6) > Why are project leads also listed as committers on AQAvit[1], but not on > Temurin[2]? The short version is that we need committer agreements for committers, but not project leads. Project leads get listed immediately, committers get listed only after our system has confirmed that their agreements are signed and in place. I'm pretty sure that we're all caught up now. Your next step is to submit an initial contribution [1] for review by the IP Team. Please do not commit any code to an Eclipse Foundation Git repository until after you receive the IP Team's approval. You may only push content into project repositories after your initial contribution IP Request (referred to as Contribution Questionnaires or "CQs") receives “check in” and/or “full approval”. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution > I've removed the following individuals from the committers list:
>
> * Morgan Davies
> * Will Parker
>
> I'll just add them to the project team when I get the required information
> (that is, we can bypass the election process for these two committers). Any
> project lead can send an email to emo@eclipse.org with this information.
I've received contact information for Morgan and Will, have put them back into the project proposal and have inserted them into the committer agreement/provisioning system.
I'm closing this bug since the project graduated to the mature phase and it has been fully operational for a while now. |