Re: [incubation] Initial contributions questions

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Stephane.

The Eclipse IP Policy isn't concerned with JARs, modules, or any sort of technical implementation detail. It focuses on content, or--if it helps--libraries in a general sense.

If the content has multiple modules that all come from a single open source project (or a single source code repository) with a single development team under common licensing, then that content should likely be represented as a single CQ. Apply this logic recursively with dependencies of the content.

If I'm understanding correctly, the shaded JAR itself is just a packaging detail that does not have its own source and therefore does not require a CQ. Group the contained modules into libraries and submit each library as a separate CQ.

Does this make sense?

Wayne

On Wed, Sep 13, 2017 at 8:31 AM, Stephane Epardaud <stef@xxxxxxxxxxx> wrote:

Hi,

As part of the move of Ceylon to Eclipse, I have some questions regarding the initial contributions:

We have a dependency which is a shaded jar containing renamed third-party
modules. How do I go about making a CQ for this one? Single CQ for the shaded
jar, pointing to every shaded module? Or one CQ per shaded module. If latter,
do I mark them as modified or not? They are not modified aside from the package
renaming used by shading.

Should I create one initial contribution CQ per Ceylon project (one project per git repo)? Or a single one for all of them
even though they're separate git repos?

In one of our repos, we have a single file that comes from a third-party lib,
which we did not modify except for renaming its package. That file is licensed
under a BSD licence. What sort of CQ do I need for this?

Thanks!

_______________________________________________
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