Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Full and Web Profile Specification Documents... 
Good afternoon!

Please allow me a few questions.

1.) How does contributing to those spec documents work from a legal point of view?
The Eclipse Foundation Specification License (EFSL) [1] does afaiu NOT allow to modify those documents.
So how does e.g. a Pull Request work from a legal pov? Under which rights can someone modify those documents (to _potentially_ contribute back)? Where is this formally stated?

2.) The Eclipse Specification Process [2] defines that "Specification Project Committers must be Members of the Eclipse Foundation."
So a normal Eclipse Committer cannot just commit to a specification project. (s)he must first apply for Eclipse Membership. Is this correct? Is it intended? Or just a mistake?

3.) Most other specifications currently hosted under eclipse-ee4j on github are currently under either EPL (1.0 or 2.0) or ALv2. Will this remain that way? Does the EFSL only apply to the bundled final revisions of that spec? Or will those be re-licensed (and based on which right?).

4.) A similar Q like 3 applies to the TCKs. They are right now all EPL-2.0 or ALv2. Will that remain?

txs and LieGrue,
strub


[1] https://www.eclipse.org/legal/efsl.php
[2] https://www.eclipse.org/projects/efsp/


> Am 29.06.2019 um 09:52 schrieb Guillermo González de Agüero <z06.guillermo@xxxxxxxxx>:
> 
> It's not only you! Great milestone!
> 
> El vie., 28 jun. 2019 21:47, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> escribió:
> 
> Maybe it’s just me, but WOO HOOOOOOO!!
> 
> Mike Milinkovich
> mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
> (m) +1.613.220.3223
> 
> On Jun 28, 2019, at 3:45 PM, Ivar Grimstad <ivar.grimstad@xxxxxxxxx> wrote:
> 
>> Done!
>> 
>> You can find it here: https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification 
>> 
>> Ivar
>> 
>> On Fri, Jun 28, 2019 at 9:02 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>> The documents have been contributed and are approved by the IP Team for check in.
>> 
>> Any project committer can grab them off the CQ and commit them to a project repository. If the team feels that a separate repository is required, please connect with Webmaster to request one.
>> 
>> The acronym guidelines haven't propagated to the website yet. They are in the website's Git repository, however, so you can review them there. In addition to those guidelines, we'll need these documents to reference the specifications by their Jakarta names. Connect with the PMC if you need additional guidance.
>> 
>> Wayne
>> 
>> On Sun, Jun 23, 2019 at 10:32 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>> Greetings Jakarta EE Platform  Committers and Project Leads.
>> 
>> The EMO started a Restructuring Review to convert the existing Eclipse Jakarta EE Platform project into a specification project (as defined by the Eclipse Foundation Specification Process). The review has been open for a week and will conclude on Monday. Following the successful review, the EMO will update the project's name and scope, and convert the existing project into a specification project.
>> 
>> In parallel, the EMO has been working to obtain the necessary rights to contribute the existing specification documents (for both the "Full" and "Web" Profiles) to the project under the project's licensing scheme. My intent is to make these document available shortly after the successful conclusion of the Restructuring Review.
>> 
>> The specification documents have been converted from their original source formats into Asciidoc. I expect that there may have been some errors in conversion; these documents will need to be reviewed carefully.
>> 
>> I will contribute the documents to the project via IPZilla. The IP Team will give the content one final check and, with their approval, the project team can take it from IPZilla and push it into a project repository in the form that they are received (i.e. you don't need to make any changes before committing the content). 
>> 
>> The project has several repositories already: an existing repository can be used, or--if desired--a new one can be created (connect with the webmaster to request the creation of a new repository).
>> 
>> I expect that the Jakarta EE Steering Committee will publish name and acronym usage guidelines sometime this week along with some guidance regarding how to apply these guidelines to the specification documents. The EE4J PMC may also provide some guidance and/or assistance.
>> 
>> Here's what we need from you:
>> 
>> The conversion of these documents is a critical piece in the success of Jakarta EE 8. With this in mind, we need the Jakarta EE Platform committers to engage in accepting these documents, pushing them into a project repository, validating the conversion into Asciidoc, and applying the guidance provided by the Steering Committee. Please plan to spend some time scoping this work later this week.
>> 
>> Note that many of the committers on this project are also members of the Steering Committee, so questions about this process can be asked on this mailing list.
>> 
>> I will notify you (via this channel) when the documents are available.
>> 
>> Wayne
>> -- 
>> Wayne Beaton
>> Director of Open Source Projects | Eclipse Foundation, Inc.
>> 
>> 
>> -- 
>> Wayne Beaton
>> Director of Open Source Projects | Eclipse Foundation, Inc.
>> _______________________________________________
>> jakartaee-platform-dev mailing list
>> jakartaee-platform-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
>> _______________________________________________
>> jakartaee-platform-dev mailing list
>> jakartaee-platform-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top