Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [technology-pmc] Request assistance for Eclipse CogniCrypt

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

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?

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.

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
if you want github follow

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.


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

technology-pmc mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top