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

On 2018-01-16 2:17 PM, Markus KARG wrote:
Now I am confused even more. So what can commiters like me help with to make
the history being migrated?

Nothing. Just accept that the history is staying where it is.

I owe you an apology, as I read your initial email too quickly and misunderstood what you were saying. You were correct the first time: there is nothing that the committers can do to help move the history over. The initial code contribution for projects of this size and complexity are a special case.


-----Original Message-----
From: ee4j-community-bounces@xxxxxxxxxxx
[mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Dienstag, 16. Januar 2018 20:09
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] Retaining History for incoming EE4J Projects


None of that is true, and I have no idea what was said that drove you to that conclusion.

Surely you can recognize that the initial code contribution for projects of
this size and complexity are a bit of a special case.


On 2018-01-16 1:37 PM, Markus KARG wrote:
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.

-Markus


-----Original Message----- From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich Sent: Montag, 15. Januar 2018 18:51 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


-- Mike Milinkovich mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx (m) +1.613.220.3223