|Re: [ee4j-community] Retaining History for incoming EE4J Projects|
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.
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
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
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
ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit