Correct. You still need a file header. 

Mike Milinkovich
[email protected]
(m) +1.613.220.3223
Please note new email address. 

> On Sep 6, 2017, at 4:46 PM, Alois Z. <[email protected]> wrote:
> 
> Mike,
>  
> you are right this is not directyl what I needed to know. But it is still a 
> very intersting response. We'll have to dig deeper what would be the best 
> license for our examples and the library.
>  
> But even using EDL we will to do some copyright header like thing, wouldn't 
> we?
>  
> Alois
>  
> Gesendet: Mittwoch, 06. September 2017 um 17:07 Uhr
> Von: "Mike Milinkovich" <[email protected]>
> An: [email protected]
> Betreff: Re: [incubation] Handling Copyright Headers in Model Examples and 
> Libraries
> On 2017-09-06 10:52 AM, Alois Z. wrote:
> In Eclipse 4diac we have a library of model elements and application examples 
> to help our users getting started with 4diac. The models are stored in a 
> dedicated XML format. This would allow to just add the classic Eclipse 
> copyright header as XML comment.
> The problem that I now see is that when the model is loaded in 4diac and 
> stored again this header is currently not preserved. So using that approach 
> for the copyright header is quite cumbersome. Adding code to handle this 
> would be quite challenging I think.
> The model we are using has dedicated fields for comments, which are intended 
> for describing the model and also a version entry. These could be used to add 
> copyright notices. Especially the latter seams suitable.
> Is there a best practice for such a use case? What are experiences of other 
> projects?
> Alois,
> 
> Probably not the answer that you are looking for, but are you aware that you 
> are allowed to license your build scripts and examples under the BSD (also 
> known as the Eclipse Distribution License 1.0) without requiring any further 
> approvals? I would consider that a best practice, as it makes it clear that 
> your examples could be used as the starting point for a product or 
> application without any copyleft implications from the EPL.
> 
> See https://www.eclipse.org/legal/noncodelicenses.php
> 
> --
> Mike Milinkovich
> [email protected]
> (m) +1.613.220.3223
> 
> 
> _______________________________________________ incubation mailing list 
> [email protected] To change your delivery options, retrieve your 
> password, or unsubscribe from this list, visit 
> https://dev.eclipse.org/mailman/listinfo/incubation
> _______________________________________________
> incubation mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/incubation
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

Reply via email to