Re: [incubation] Initial contributions questions

[Stephane Epardaud <stef@xxxxxxxxxxx>]

OK, clear, thanks a lot!

On 14/09/17 18:42, Wayne Beaton wrote:

Sorry, I got fixated on the one.

One initial contribution CQ, would be ideal. How the project code is structured across project-owned Git repositories is not a factor in the IP due diligence process. If it makes it somehow easier for you or there is some other factor to consider, you can submit multiple "projectcode" CQs.

Consider that single separate file as being from a separate source of content ("library"). A separate CQ is required, please.

I think I got 'em all this time :-/

HTH,

Wayne

On Thu, Sep 14, 2017 at 11:39 AM, Stephane Epardaud <stef@xxxxxxxxxxx> wrote:

OK thanks. So for a shaded jar I have to make a CQ per shaded projects.

What about my two other questions?

Thanks!

On 13/09/17 21:08, Wayne Beaton wrote:

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

_______________________________________________
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

_______________________________________________ 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

_______________________________________________
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