| Re: [ee4j-pmc] [jakartaee-spec-project-leads] Specification Documents |
Wayne,
If this really is an issue, then I think the EF needs to obtain this 1.3 version of the Transactions Specification since that's the one that we tagged for Jakarta EE. If you remember, the JTA spec did this 1.3 maintenance update right about when Jakarta EE 8 was getting kicked off. This was done to separate the Java EE JTA artifacts from the Java SE JTA artifacts. So, since this was specifically done in support of Jakarta EE, then Oracle should have contributed the 1.3 Spec and not the 1.2 Spec... imho, of course... :-)
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Cc: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>, Jakarta EE Specification Community Discussions <jakarta.ee-spec@xxxxxxxxxxx>
Date: 03/10/2020 08:48
Subject: [EXTERNAL] Re: [jakartaee-spec-project-leads] [ee4j-pmc] Specification Documents
Sent by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
No. It's not fine. AFAICT, the content in that repository is not licensed in a manner that permits the sort of reuse that you're describing. Selecting parts of those documents to incorporate into the Jakarta Transactions document would be a copyright violation (FWIW, the license does appear to allow copying small sections for the purposes of discussion, but that is very different from what you want to do).
If you want to use that content, we'll need the current owners to contribute it under the terms of the Jakarta Transactions' project license.
HTH,
Wayne
On Tue, Mar 10, 2020 at 7:26 AM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
Hi Wayne,
The Jakarta Transactions project had the version 1.2 of the Oracle specification contributed via IPzilla, although a 1.3 version exists. It was discussed a bit in this thread:
https://www.eclipse.org/lists/jakartaee-platform-dev/msg01595.html
A legal question; it is fine to use the version 1.2 of the specification as the basis of the conversion but selecting parts of the 1.3 version from https://github.com/javaee/jta-specor would that pose any legal issues?
Thanks for your input,
Tom
On Fri, 17 Jan 2020 at 21:55, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Greetings folks.
We finally managed to clear all of the specification documents provided to us by our good friends at Oracle.
I have contributed all of them to their projects via IPzilla. I've copied project leads on the CQs; project leads should have all received notification of the creation of the CQs via email. I've updated our tracking board. Committers can see the list of CQs we're using to track the intellectual property due diligence process on these documents here. Committers who want to stay informed of progress can add themselves in CC to a record.
Project teams, please wait until the IP Team grants you "checkin" before you grab the contents and add it to your Git repository (the IP Team will add the "checkin" keyword to the record; those who are in CC will be copied on the message). Note that "checkin" is only the first part of the IP review process; the CQs will need to be "approved" before the release, so please respond promptly to any questions or concerns expressed by the IP Team.
Side note: I noticed that Jakarta XML Binding has no project lead. We need somebody from that project team to step up. Project leads are the main liaison between the project team and the EMO and first link in the leadership chain, responsible for ensuring that the project team is doing the right sorts of things to be successful and just generally following the rules; it's a role primarily of responsibility, not power.
Thank you to everyone who contributed to the process of sorting out the intellectual property issues around these documents.
I'll take this opportunity to remind specification project teams that if you are planning to do more for the Jakarta EE 9 release than is included in the current plan, you need to craft a plan for your project and get ballot approval from the Jakarta EE Specification Committee. Use the jakarta.ee-spec@xxxxxxxxxxxto communicate with the specification committee and community as you develop your plan (please do not develop your plan in a vacuum and expect the specification committee to approve it).
Wayne
--Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc._______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.