[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [mdt-ocl.dev] Unwieldy Copyright Notices
|
Hi All,
I cannot comment on copyrights on behalf of Borland because
1. Borland doesn't exist anymore. It was bought by Micro Focus.
2. I do not work for Micro Focus since 17 August 2009.
I don't know anybody in Mocro Focus who is in position to comment on Borland
copyright issues at Eclipse. I am pretty sure that no one cares about it and
no one will ever notice the absence of Borland copyright in the OCL code.
However, there is still a tiny possibility that Micro Focus might object to
this in the future.
Therefore, I would leave Borland copyrights as is. In the future I would
treat copyrights as mentioned in
http://www.eclipse.org/legal/copyrightandlicensenotice.php
Best Regards,
Alex.
-----Original Message-----
From: mdt-ocl.dev-bounces@xxxxxxxxxxx
[mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Laurent Goubet
Sent: Wednesday, September 02, 2009 12:48 PM
To: MDT OCL mailing list
Cc: Christian W. Damus
Subject: Re: [mdt-ocl.dev] Unwieldy Copyright Notices
All,
On behalf of Obeo, I'm perfectly fine with being within the "and others"
part, as long as newly created files have their copyright set to "copyright
(c) <original contributor's company> and others"... but I believe that's
never been questionned here :).
Laurent Goubet
Obeo
Ed Willink a écrit :
> Hi Christian and All
>
> OK, let's see if anyone has such a strict policy.
>
> Adolfo, on behalf of Open Canarias, is happy to see Open Canarias in
> the contributor line.
>
> Working in my own time, I do not require Thales mentioned at all. I am
> the initial author of a couple of files that show IBM copyright.
>
> ? Borland
>
> ? Obeo
>
> Christian: do/did Zeligsoft require/merit the top line credit. Can we
> revert to the initial copyright holder only recommendation of
> http://www.eclipse.org/legal/copyrightandlicensenotice.php?
>
> Regards
>
> Ed Willink
>
>
>
> Kenn Hussey wrote:
>> Ed,
>>
>> I agree that, in principle, only the companies receiving "top line
>> credit" should be those that have made the most significant
>> contribution to a given source file... but some companies have
>> restrictions governing their copyright which might require explicit
>> mention. I don't think an entry in the list of contributions is
>> sufficient to identify copyright, so in such cases both may be required.
>>
>> As a rule of thumb, I'd lead toward listing the original author
>> (company) as the only named copyright holder unless the company has a
>> strict policy (as described above), in which case it should also be
>> explicitly listed. As for entries in the list of contributions, I
>> think they should always be included, although some projects (e.g.
>> EMF) are hesitant to do so...
>>
>> Cheers,
>>
>> Kenn
>>
>> On Tue, Sep 1, 2009 at 3:57 PM, Ed Willink <ed@xxxxxxxxxxxxx
>> <mailto:ed@xxxxxxxxxxxxx>> wrote:
>>
>> Hi
>>
>> We could easily find ourselves maintaining copyright notices such
>> as
>>
>> IBM Corporation, Zeligsoft Inc., Borland Software Corp., Obeo,
>> Open Canarias, E.D.Willink and others
>>
>> I think this is untenable and gets more so with each further
>> team/employment change.
>>
>> I feel that Christain made a mistake by adding Zeligsoft.
>>
>> A plausible policy is that the Copyright is just to the initial
>> contributor with everyone else thereafter "and others".
>> Zeligsoft should not have been added.
>>
>> Another plausible policy is that a top line credit appears only
>> once 10% of the useful line count is contributed.
>>
>> Since we are now directed to make the Eclipse Modeling Project
>> the plug-in provider, I propose that when
>> a non-trivial edit occurs the copyright is changed to "Eclipse
>> Modeling Project and others". The list of
>> contributions; e.g. IBM - initial API and implementation provides
>> adequate credit.
>>
>> Regards
>>
>> Ed Willink
>>
>>
>>
>>
>>
>> _______________________________________________
>> mdt-ocl.dev mailing list
>> mdt-ocl.dev@xxxxxxxxxxx <mailto:mdt-ocl.dev@xxxxxxxxxxx>
>> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>> _______________________________________________
>> mdt-ocl.dev mailing list
>> mdt-ocl.dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
>>
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> mdt-ocl.dev mailing list
> mdt-ocl.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
>
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
