Hi Judy,

In addition to the specifics from Brendan about this code, I wanted to answer 
your question in general.

Historically, license decisions about code additions is usually made on a 
project-specific basis.

In some cases, when we add code to BSD software, we license the additions under 
BSD as well.  This has happened in ON for third-party device drivers in 
particular.  We port a driver and add Sun-specific code/support.  And we have 
licensed that additional code under the same BSD license so that the entire 
driver can be given back to the upstream community and used as a whole covered 
by one license.

In other cases, code we add to third-party software is separable and 
significant and the choice has been made to publish the additional code under 
the CDDL.

It's usually up to the project team and legal to make these decisions.

Hope that helps.

Bonnie

----- Original Message -----
From: [email protected]
To: Brendan.Doyle at Sun.COM
Cc: bonnie.corwin at oracle.com, susan.miller at oracle.com, on-ips-dev at 
opensolaris.org, Eric.Schlesinger at oracle.com
Sent: Wednesday, March 24, 2010 10:32:18 AM GMT -07:00 US/Canada Mountain
Subject: Re: New  IPS license (/ws/onnv-clone/usr/src/pkg/license_files/lic_of

thanks, that is correct.

Bonnie and Susan - do we normally license the additions we make to BSD  
code under CDDL or do we continue with the BSD for our contributions  
as well?  Or is there no real pattern/rule on this?

On Q1: Wednesday, March 24, 2010, at 08:55 AMPDT, Brendan Doyle wrote:

>
> As I mentioned on the last call we had, I need to specify
> a license for the package that contains the software we
> are delivering. Eric and yourself suggested the person
> to ask was Bonnie or Susan.
>
>
> On 24/03/2010 15:10, Judith Genovese wrote:
>> what is this for and about?
>> On Q1: Wednesday, March 24, 2010, at 04:01 AMPDT, Brendan Doyle  
>> wrote:
>>
>>> All,
>>>
>>> Unless there is an objection by COB today, we will
>>> be creating and using the following license for the
>>> driver-network-ofk pkg:
>>>
>>>
>>> usr/src/pkg/license_files/lic_of
>>>
>>> That contains:
>>>
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> = 
>>> = 
>>> ====================================================================
>>> DO NOT TRANSLATE OR LOCALIZE.
>>>
>>> This package includes software from the OpenFabrics SW Stack.
>>> Use of any of this software is governed by the terms of the  
>>> license below:
>>>
>>> OpenIB BSD License
>>>
>>> Redistribution and use in source and binary forms, with or without  
>>> modification,are permitted provided that the following conditions  
>>> are met:
>>>
>>> * Redistributions of source code must retain the above copyright  
>>> notice, this
>>> list of conditions and the following disclaimer.
>>>
>>> * Redistributions in binary form must reproduce the above  
>>> copyright notice, thislist of conditions and the following  
>>> disclaimer in the documentation and/or
>>> other materials provided with the distribution.
>>>
>>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND  
>>> CONTRIBUTORS "AS IS" AND
>>> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,  
>>> THE IMPLIED
>>> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE  
>>> ARE
>>> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS  
>>> BE LIABLE FOR
>>> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR  
>>> CONSEQUENTIAL DAMAGES
>>> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR  
>>> SERVICES;
>>> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER  
>>> CAUSED AND ON
>>> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR  
>>> TORT
>>> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE  
>>> USE OF THIS
>>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>>>
>>>
>>> The Sun components of this package are licensed under License 1,  
>>> version 1.0 of
>>> the Common Development and  Distribution License ("CDDL") as  
>>> published by Sun Microsystems, Inc. You can obtain a copy of the  
>>> license at
>>> usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing 
>>> .
>>> See the License for the specific language governing permissions
>>> and limitations under the License.
>>>
>>> When distributing Covered Code, include this CDDL HEADER in each
>>> file and include the License file at usr/src/OPENSOLARIS.LICENSE.
>>> If applicable, add the following below this CDDL HEADER, with the
>>> fields enclosed by brackets "[]" replaced with your own identifying
>>> information: Portions Copyright [yyyy] [name of copyright owner]
>>>
>>> = 
>>> = 
>>> = 
>>> = 
>>> = 
>>> = 
>>> = 
>>> = 
>>> ====================================================================
>>>
>>>
>>> The manifest will be updated to have:
>>>
>>> license cr_Sun license=cr_Sun
>>> license lic_CDDL license=lic_CDDL
>>> license lic_of license=lic_of
>>>
>>>
>>> Brendan
>>
>>
>> Judith Genovese | Legal Counsel | 1.626.408.3138
>> Oracle Legal Department/Development and Strategic Initiatives
>> 800 Royal Oaks, Monrovia, CA 91016
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> NOTICE: This E-mail message is for the sole use of the intended
>> recipient(s) and may contain confidential and privileged information.
>> Any unauthorized review, use, disclosure or distribution is  
>> prohibited.
>> If you are not the intended recipient, please contact the sender by
>> reply E-mail and destroy all copies of the original message.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>


Judith Genovese | Legal Counsel | 1.626.408.3138
Oracle Legal Department/Development and Strategic Initiatives
800 Royal Oaks, Monrovia, CA 91016

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: This E-mail message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply E-mail and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Reply via email to