Re: [technology-pmc] Request assistance for Eclipse CogniCrypt

[Johannes Spaeth <johannes.spaeth@xxxxxxxxxxxxxxxxx>]

Hi Matthias, hi Wayne,


thank you very
much for the detailed responses.

Sorry, the two
missing links are:

[1] https://wiki.eclipse.org/Development_Resources/HOWTO/Parallel_IP_Process
[2] https://wiki.eclipse.org/Naming_Conventions

So we want to make the initial contribution soon. I follow the process described on here:
https://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf

I have already created CQs for each dependency that we use. This includes the soot dependency that you, Wayne, discussed earlier with Eric Bodden (https://bugs.eclipse.org/bugs/show_bug.cgi?id=526662#c20).
Thanks for the pointer to the handbook for Type A/Type B Due Diligence process. For soot I used Type B due diligence process, but I change that to Type A. Do I have to re-create the CQ, I was not able to change any field.

The CQ for the initial contribution is missing. Where should the field Contribution Record point to?
I found this discussion here:
https://dev.eclipse.org/mhonarc/lists//incubation/msg00416.html
Wayne suggests to point to the "the project creation tracking bug". Would that be the discussion found here? https://bugs.eclipse.org/bugs/show_bug.cgi?id=526662#c20

Thanks for your help!

Cheers,
Johannes

Von:
       Matthias
Sohn <matthias.sohn@xxxxxxxxx>
An:
       Technology
PMC <technology-pmc@xxxxxxxxxxx>
Datum:
       28.02.2018
08:33
Betreff:
       Re:
[technology-pmc] Request assistance for Eclipse CogniCrypt
Gesendet
von:        technology-pmc-bounces@xxxxxxxxxxx

---

On Tue, Feb 27, 2018 at 4:35 PM, Johannes
Spaeth <johannes.spaeth@xxxxxxxxxxxxxxxxx>
wrote:
Hi,

we are currently incubating the Eclipse CogniCrypt project and are going
through the required IP process to check the licenses of the used dependencies.
There are a couple of question we would like to know about.

We raised all Contribution Questionaires for the dependencies. Most of
them are resolved, but some of them are still pending. 
If I am correct, we cannot check-in any code before all IP and the CQs
are resolved in IPZilla. Unless, CogniCrypt is eligible for the parallel
IP process[1]. 

you missed to add the links


 
Therefore I wonder,

1. Is CogniCrypt eligible for the parallel IP process? If not, can we get
a preliminary approval? 

https://www.eclipse.org/projects/handbook/#ip-parallel-ip 
describes the parallel ip process 

But I wonder why the project handbook
doesn't mention the difference for Type A / Type B IP Due Diligence
process.
It seems the handbook needs an update
here.
See 
https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf,
page 6 ff
https://waynebeaton.wordpress.com/2017/01/12/license-certification-due-diligence/

2. What are the requirement for the check-in
code? 
       We would like to be prepared for the check-in.
For example I found the naming conventions[2], are they mandatory for the
first version of the checked-in? 

where is the link ?
 
3. What is the best practice to keep
the eclipse-hosted source code in sync with github repositories?
       Our code is currently hosted in github repositories.
We will make them public and would like to keep working with these repositories.
Do other projects follow a similar approach?
       Is it possible to purely stick to the github
hosted repositories, or can we keep both in sync somehow?


as soon as the CQ for the initial source
code contribution has been accepted you can check this in.
You can choose Gerrit Code Review or
Github
https://www.eclipse.org/projects/handbook/#resources-source
if you want github follow
https://www.eclipse.org/projects/handbook/#resources-github

You will get a new repository and its
history will start with the initial contribution as soon as it is approved.
This means you checkin the
initial version which was approved in
IP review and then you continue working on your project in the new repository.
You have to leave behind the history
of your project which predates the initial contribution at Eclipse which
you cannot transfer to the new
git repository you'll get for your new
Eclipse project. Reviewing the existing history would create too much work
for the legal team.

You may consider to use git replace to
concatenate old and new history in your local clone.
https://git-scm.com/docs/git-replace
https://git-scm.com/book/en/v2/Git-Tools-Replace
 
Cheers,
Johannes

__________________________________________

Fraunhofer-Institut für Entwurfstechnik Mechatronik IEM
M. Sc. Johannes Späth

Zukunftsmeile 1
33102 Paderborn

Telefon: +49 5251 5465 -355
Fax: +49 5251 5465 -102
johannes.spaeth@xxxxxxxxxxxxxxxxx
https://www.iem.fraunhofer.de
__________________________________________  

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/technology-pmc

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/technology-pmc