[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ee4j-community] Retaining History for incoming EE4J Projects
- From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
- Date: Tue, 16 Jan 2018 19:37:20 +0100
- Delivered-to: email@example.com
- Organization: Markus KARG, Staatl. gepr. Inf.
- Thread-index: AdOOKXkTuLke/zbySpybFd2VuBifnwAzWnfA
So what you actually try to tell us is that Oracle and the EF have to scan
EACH single commit of the history for legal issues and copyright headers and
neither of both parties trusts Oracle that Oracle's licence terms and file
headers did not change between the history and the LAST commit? Furthermore
you want to express that only Oracle and the EMO can do that job but not the
newly elected commiters of that projects (which all have signed an agreement
to do such checks for each new commit)?
Okay, THEN we (the committers) really cannot help.
[mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Montag, 15. Januar 2018 18:51
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
> 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,
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 https://dev.eclipse.org/mailman/listinfo/ee4j-community