www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <bay...@apache.org>
Subject Re: Writing spec code for the OSGi Alliance within the ASF
Date Sat, 21 Jan 2017 01:10:13 GMT
Nicely said.

On Fri, Jan 20, 2017 at 11:13 AM, Ted Dunning <ted.dunning@gmail.com> wrote:

>
> Just a quick note about how things actually work.
>
> There is no code ever that is developed AT Apache (aside, perhaps from
> infra stuff).
>
> There is code developed somewhere in the world and given/licensed TO
> Apache that then lives in Apache source code control systems.
>
> If I write some code and give it to an Apache project under the correct
> procedures, I still own the code and all rights. I granted Apache a
> non-exclusive license. I can license that code to somebody else on
> different terms. I could contribute it to a GPL based project. I would sell
> it for big money as proprietary code. It is mine, not Apache's. I can't
> give anybody an exclusive license without recognizing the fact that I
> already gave Apache a non-exclusive license, but that life.
>
> If I develop code and license it to somebody else first on non-exclusive
> terms, I can contribute it to Apache as well and pretty much ignore the
> first licensing.
>
> If I develop code and license it to a standards body under the Apache
> license, then I can either take the code from the standards body and follow
> the normal license, NOTICE and header procedures or I can contribute it
> anew.
>
> Presumably, it would be nice to take it from the standards body so that
> the relationship is clear.
>
> But this is no different than including any acceptable open source code.
>
>
>
> On Fri, Jan 20, 2017 at 6:46 AM, Carsten Ziegeler <cziegeler@apache.org>
> wrote:
>
>> Guillaume Nodet wrote
>> >
>> >
>> > 2017-01-20 15:02 GMT+01:00 Carsten Ziegeler <cziegeler@apache.org
>> > <mailto:cziegeler@apache.org>>:
>> >
>> >     Guillaume Nodet wrote
>> >     > Ok, there are two more specific questions:
>> >     >
>> >     > #1 Can a committer write *new* code at the ASF with a header file
>> >     > mentioning the code is copyrighted to the OSGi Alliance  ?
>> >
>> >     Just to set the facts straight here: no one is writing code at the
>> ASF
>> >     with a header file containing the copyright of the OSGi Alliance.
>> >     So I think this question is not relevant and the title of this
>> thread is
>> >     really misleading.
>> >
>> >
>> >
>> > Well, that's precisely what I'd like to make sure.
>> > For example, see this latest commit:
>> >
>> > https://github.com/apache/felix/commit/2d6f7011a7060f4397bb5
>> 51d18d9f616ca532f38
>> > It modifies the org.osgi.util.converter package, where the files have
>> > a "Copyright (c) OSGi Alliance (2016). All Rights Reserved." in their
>> > headers.
>> > If the code is not developped within the ASF, there must be a different
>> > source somehwere else.  Where does this change come from ?
>> >
>> Yes, the source of that code is the OSGi Alliance. That's where David
>> developed the changes and once done copied them over to our repo. But
>> this code has not been developed at the ASF. The svn commit does not
>> show you that this is a copy as it always just does a diff.
>>
>> And this happens with every API development from the OSGI Alliance: it's
>> developed in the repository of the Alliance and not anywhere else.
>>
>> Regards
>>
>> Carsten
>>
>> --
>> Carsten Ziegeler
>> Adobe Research Switzerland
>> cziegeler@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>>
>>
>

Mime
View raw message