Bugzilla – Full Text Bug Listing
| Summary: | [proposal] ee4j.jpa | ||
|---|---|---|---|
| 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: | bill.shannon, cydnie.smith, david.delabassee, dmitry.kornilov, lukas.jungmann, mike.milinkovich, odrotbohm, sharon.corbett, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-project-jpa | ||
| Whiteboard: | |||
| Bug Depends on: | 536220 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Dmitry, the proposal indicates that the project is dual licensed EPL-1.0 OR EDL-1.0. Was it intentional to make this EPL-1.0? If so, why? Shouldn't this be the same EPL-2.0 + GPL/CPE as the rest of the proposals? The JPA spec project was split off from the EclipseLink project, which uses EPL 1.0. Thus, this project will continue to use EPL 1.0 (and EDL 1.0). (In reply to Bill Shannon from comment #2) > The JPA spec project was split off from the EclipseLink project, which uses > EPL 1.0. > Thus, this project will continue to use EPL 1.0 (and EDL 1.0). EclipseLink need to update to EPL-2.0. That can be done just by asking. Changing the existing dual-licensing scheme to a EPL-2.0 with secondary licensing will be more challenging. I would very much prefer if we could create JPA as an EPL-2.0 project and would like to see if we can sort out how to make it EPL-2.0 with GPL-2.0+CPE as secondary like the rest of the projects. I'm pretty sure that the board will push back hard on a request to license a new project under EPL-1.0. This may be a new *project*, but it's not new code. And since the code was originally created under the terms of the Eclipse Contributor Agreement, we can't just change the license. I doubt that Oracle would object if you can figure out how to convert these projects to EPLv2/GPLv2+CE like the rest of EE4J. I'm not sure it's worth the effort to change them to EPLv2 without GPLv2+CE. (In reply to Bill Shannon from comment #4) > This may be a new *project*, but it's not new code. Yup. I've been briefed. > And since the code was > originally created under the terms of the Eclipse Contributor Agreement, we > can't just change the license. The ability to update to new versions is actually included in the license. https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw (In reply to Bill Shannon from comment #4) > This may be a new *project*, but it's not new code. And since the code was > originally created under the terms of the Eclipse Contributor Agreement, we > can't just change the license. That is factually incorrect. Any project can change from EPL-1.0 to EPL-2.0 by simply changing the headers. This is based on Section 7 of the EPL-1.0 and EPL-2.0 which both say: The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is the initial Agreement Steward. The EclipseFoundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. > I doubt that Oracle would object if you can figure out how to convert these > projects to EPLv2/GPLv2+CE like the rest of EE4J. I'm not sure it's worth > the effort to change them to EPLv2 without GPLv2+CE. The EPL-2.0 is just simply a better license than the EPL-1.0. The EPL-2.0 is also the default license of the Eclipse Foundation and *all* new projects must use it, and all active projects will soon be required to switch to it before doing their next release. So please just fix the headers and use the EPL-2.0. Thanks. Can we just change it to EPLv2/GPLv2+CE? Or does that require a different process/approval? We don't want to change it first to EPLv2 and then later to EPLv2/GPLv2+CE. (In reply to Bill Shannon from comment #7) > Can we just change it to EPLv2/GPLv2+CE? Or does that require a different > process/approval? > > We don't want to change it first to EPLv2 and then later to EPLv2/GPLv2+CE. I don't think that we will ever be able to add the GPLv2+CE part. That would require the permission of all past contributors. (This was answered in the FAQ that Wayne had pointed you to.) So I think this will stay dual-licensed EPL-2.0 and EDL(BSD) Btw, would It be possible to add the JPA proposal the 'EE4J projects proposals' list (https://projects.eclipse.org/projects/ee4j) ? (In reply to David Delabassée from comment #9) > Btw, would It be possible to add the JPA proposal the 'EE4J projects > proposals' list (https://projects.eclipse.org/projects/ee4j) ? It will automatically show up in the "Related Projects" box after it is created, if that's what you mean. We’ve received all of the project requirements and have scheduled the creation review to conclude on July 18/2018. Please continue to monitor communication channels. Following the creation review, we will initiate the provisioning process. As part of this process, we will bring committers on board. To gain committer status, some paperwork [1] must be completed. The exact nature of that paperwork depends on several factors, including the employment status of the individual and the Eclipse Foundation membership status of the employer. If you can be ready with the paperwork in time for the completion of the creation review, then we can move quickly through the provisioning process. When we initiate provisioning, committers will be sent an email with instructions; please don't send any paperwork in until after you receive those instructions. Please encourage all future project committers to join the incubation mailing list [2]. We use this list to connect committers from new projects to their peers in other projects in the incubation phase and to mentors who can help answer questions and discuss issues related to the project onboarding process. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://dev.eclipse.org/mailman/listinfo/incubation I declare the Creation Review successful! We will initiate the project resources provisioning process shortly. Please tell your project committers to carefully monitor their email for a message from The Eclipse Foundation with instructions for providing committer paperwork [1]. Our IT team cannot allocate project resources until after we have processed the paperwork for at least one committer, so your attention in this matter will keep the process moving forward. Be advised that the paperwork process will time out after 120 days; any committers who are unable to complete their paperwork requirements in this timeframe will have to be elected to the project (your project mentors can provide assistance with this). [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project:
Source Code Management:
As your project's main Git repository is hosted at GitHub, we will need to move it to the Eclipse organization and flatten any previous history. This work can begin as soon as you have check in permission from EMO legal.
Issue Tracker:
https://bugs.eclipse.org/bugs/describecomponents.cgi?product=jpa
Outbound Communication:
Mailing list: https://accounts.eclipse.org/mailing-list/jpa-dev
Project Website repository:
ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/ee4j/jpa.git
Commits will be published to www.eclipse.org/ee4j/jpa within 5 minutes
Downloads: http://download.eclipse.org/jpa
Archives: http://archive.eclipse.org/jpa
Builds: You can upload releases to ~committer_id/downloads/jpa 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.
This project is fully operational. Bug has been resolved. Is it intended that https://www.eclipse.org/ee4j/jpa/ points to something called Gemini JPA, a project that hasn't seen any updates since 2013? Should important milestones to the project announced to the dev list? https://accounts.eclipse.org/mailing-list/jpa-dev |