Re: [incubation] File headers for generated files

["Delchev, Nedelcho" <nedelcho.delchev@xxxxxxx>]

Hi All,

We had already such an issue in ECD and we agreed that - if generated code does not "include calls to APIs or other technical instructions" back to the external 3-thd party framework, it cannot be considered as derivative work.

Regards,

Nedelcho

From: <incubation-bounces@xxxxxxxxxxx> on behalf of Tyler Jewell <tyler@xxxxxxxxxxx>
Reply-To: Discussions for new Eclipse projects <incubation@xxxxxxxxxxx>
Date: Sunday, June 4, 2017 at 23:49
To: Discussions for new Eclipse projects <incubation@xxxxxxxxxxx>
Subject: Re: [incubation] File headers for generated files

I am interested in learning more about what you define as "generated code".  Could you be more explicit and provide an example?

The Eclipse Che project generates a lot of files, but we do not put any of them under version control or license enforcement.

We do put all of our generated files into a binary package that is ultimately wrapped into a Docker image, for end users and developers to download and use as a starting point.

Tyler Jewell // CEO // tyler@​codenvy.​com // 978.884.5355

On Sun, Jun 4, 2017 at 11:40 AM, Alois Z. <alois.zoitl@xxxxxx> wrote:

Hi,

 

I think I have a question also interesting for other incubation projects:

 

We normally include into our repo also the generated code. This makes it much easier for new contributors to setup a build environment and start codeing. Espcially when they are working on plugins where they use the generated code and don't want to change it.

 

My question is now how would the legal header need to be for such files?

 

Thanks,

Alois

_______________________________________________
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