Re: [incubation] Sub-projects -- theory and practice

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Jens.

The term "subproject" has a specific meaning in the Eclipse Development Process. I'm assuming that you mean extra repositories or some de facto notion of components within a project.

Making a fork of third party content is possible, subject (of course) to the terms of the license. The IP Team would have to do full due diligence (Type B) on the contribution.

Maintaining the fork is a different matter. Using Git to synchronise changes from the original repository will be basically impossible since the IP Policy doesn't support pulling in history with an initial contribution, let alone any notion of pulling a chain of update commits for rebasing your branches. I'm not even sure how we could update the IP Policy to deal with the latter case.

Wayne

On Fri, Jun 30, 2017 at 10:53 AM, Jens von Pilgrim <developer@xxxxxxxxx> wrote:

Hi,

I have a question regarding "sub-projects". That is: The N4JS project uses two libraries: Xpect and Xsemantics. Both libraries

- are Eclipse plugins
- are developed by Eclipse committers
- are provided under EPL
- are hosted at the personal accounts of the authors at github
- are crucial to our project, that is: When we detect a problem/bug, we need that bug fixed ASAP -- and then we cannot wait for a new release and a CQ to be approved. In the past, we contributed changes to both libraries in these cases or asked the authors to fix the bugs.

We are in close contact with the authors and we are thinking to add "forks" of these libraries to the N4JS project at Eclipse. We would request additional repositories for these libraries and add the source code via a CQ. We assume that this would speed up the process and reduce the workload for the authors of these libraries (since I would create the CQ and discuss issues with the IP team, and the authors wouldn't need to create a project proposal yet).

We are not quite sure when, but in the long-run we assume that these libraries should become separate projects. We assume that this shouldn't be a problem then, would it?

What do you recommend in a situation like that in general? Or does anyone has completely different ideas of how we could solve the situation?

Best regards,
Jens

--
Dr. Jens von Pilgrim
Director Development Tools
NumberFour AG

Schönhauser Allee 8
10119 Berlin, Germany
Mobile: +49 170 2393165
Skype: jensn4
jens.von.pilgrim@xxxxxxxxxxxxx

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

--

Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation