[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Retaining History for incoming EE4J Projects

David,

 

I am referring to resolving dependencies of older versions from the new EE4J repository instead of resolving those dependencies from the existing projects at the JavaEE repository (or through maven). AFAIK, the absence of the entire history in the EE4J repository is the concern here. If the existing JavaEE repositories are left as is and the old dependencies continue to get resolved from the existing JavaEE repository then, I believe, Âit is not under the scope of the EF.

 

On the other hand, it would be very cumbersome to review each and every âunmodifiedâ dependent file every time for copyright/license during every release from the EE4J repository, especially for those old versions of files that belong to existing (imported into EE4J repo) projects which are not directly part of the release. Making old code current would only be applicable if there are any changes/modifications made to the old versions (which is not likely). I am referring to the scenario where there is a future release which is published from the EE4J repository with a dependency on the old code here.

 

-Mrinal

 

From: David Lloyd
Sent: 15 January 2018 23:43
To: EE4J community discussions
Subject: Re: [ee4j-community] Retaining History for incoming EE4J Projects

 

I believe this is inaccurate. Anyone can declare a dependency on an

older version of the code already as the entire history is already

published. In order to bring old code to be current, it would have to

be reviewed in the same manner as any other change. So again, AFAICT

there is no real legal issue here.

 

On Mon, Jan 15, 2018 at 12:06 PM, Mrinal Kanti M <mrinal.kanti@xxxxxxxxx> wrote:

> I think Mike has a point here. If the due diligence is not done then it

> would be technically possible for someone (in future) to make a release

> (say, for the sake of maintenance) by declaring a dependency on an older

> version of the code. And since the older version is not completely vetted,

> the release might end up having license/copyright issues.

> 

> 

> 

> Besides, I have some bandwidth to spare. If its purely a time, effort or

> resource issue then I think it would be a good opportunity to call for

> volunteers from the community and see if the existing teams can be augmented

> to meet the resource demands during this transition process.

> 

> 

> 

> -Mrinal

> 

> 

> 

> P.S. I have already accepted the ECA and do not anticipate any issues in

> getting other relevant paperwork processed.

> 

> 

> 

> 

> 

> Sent from Mail for Windows 10

> 

> 

> 

> From: Mike Milinkovich

> Sent: 15 January 2018 23:21

> To: ee4j-community@xxxxxxxxxxx

> Subject: Re: [ee4j-community] Retaining History for incoming EE4J Projects

> 

> 

> 

> On 2018-01-15 12:40 PM, Markus KARG wrote:

> 

>> If it is not a legal issue, the file headers can stay as they are, and if

>> it

> 

>> is only a time issue,_I_Â can fetch and push the commits between the

>> repos.

> 

>> So why not letting me do that?

> 

> 

> 

> Because that's not how it works....

> 

> 

> 

> Like every large company we have ever worked with, before Oracle

> 

> contributes any code to any open source foundation they have a process

> 

> to follow. (Scanning code, reviewing copyright headers, checking license

> 

> compatibility, etc.)

> 

> 

> 

> Before the Eclipse Foundation accepts significant code contributions to

> 

> its projects, we have a process that we follow. (Scanning code,

> 

> reviewing copyright headers, checking license compatibility, etc.)

> 

> 

> 

> As I said: real time, effort, and resources are required to move the

> 

> history.

> 

> 

> 

> --

> 

> Mike Milinkovich

> 

> mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx

> 

> (m) +1.613.220.3223

> 

> 

> 

> _______________________________________________

> 

> ee4j-community mailing list

> 

> ee4j-community@xxxxxxxxxxx

> 

> To change your delivery options, retrieve your password, or unsubscribe from

> this list, visit

> 

> https://dev.eclipse.org/mailman/listinfo/ee4j-community

> 

> 

> 

> 

> _______________________________________________

> ee4j-community mailing list

> ee4j-community@xxxxxxxxxxx

> To change your delivery options, retrieve your password, or unsubscribe from

> this list, visit

> https://dev.eclipse.org/mailman/listinfo/ee4j-community

> 

 

 

 

--

- DML

_______________________________________________

ee4j-community mailing list

ee4j-community@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/ee4j-community