Remote procedure call, license of code call to scif library

[Minh_H_]

Hi,
We have developed a low latency, remote procedure call (rpc) Framework  for Xeon <--> Xeon Phi based on SCIF, which is very successful for our applications.  We think it could be helpful for other Intel Xeon Phi  users.  We would like to share the code to communities as open-source project. However we does not know if  there are any problem with Intel's license, copyright or copyright infringement, which we believe do not. Would you please help us? Thanks, Minh

[BelindaLiviero]

Hi, we are identifying the best person to help you.   we are waiting for response from our internal groups and will get back to you

[BelindaLiviero]

Hi, here are some answers:

 SCIF is released under LGPL v. 2.1 open source license, main outbound license for MPSS honors individual component licenses.

Typically LGPL v. 2.1 allows to  freely reuse src/binaries of the component with very few restrictions, like keeping the copyrights intact and license type intact.

The question below suggests that you are aware of open source license types, hence should be aware what’s possible with LGPL.

See scif.h header:

/*

* Copyright 2010-2013 Intel Corporation.

*

* This library is free software; you can redistribute it and/or modify it

* under the terms of the GNU Lesser General Public License as published

* by the Free Software Foundation, version 2.1.

*

* This library is distributed in the hope that it will be useful,

* but WITHOUT ANY WARRANTY; without even the implied warranty of

* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU

* Lesser General Public License for more details.

*

* Disclaimer: The codes contained in these modules may be specific

* to the Intel Software Development Platform codenamed Knights Ferry,

* and the Intel product codenamed Knights Corner, and are not backward

* compatible with other Intel products. Additionally, Intel will NOT

* support the codes or instruction set in future products.

*

* Intel offers no warranty of any kind regarding the code. This code is

* licensed on an "AS IS" basis and Intel is not obligated to provide

* any support, assistance, installation, training, or other services

* of any kind. Intel is also not obligated to provide any updates,

* enhancements or extensions. Intel specifically disclaims any warranty

* of merchantability, non-infringement, fitness for any particular

* purpose, and any other warranty.

*

* Further, Intel disclaims all liability of any kind, including but

* not limited to liability for infringement of any proprietary rights,

* relating to the use of the code, even if Intel is notified of the

* possibility of such liability. Except as expressly stated in an Intel

* license agreement provided with this code and agreed upon with Intel,

* no license, express or implied, by estoppel or otherwise, to any

* intellectual property rights is granted herein.

*/

Please let us know if you have any additional questions, and thank you for taking the initiative to share what you have created!

[Minh_H_]

Hi,

Our library calls SCIF but  we do not release the scif (source code / or binary) with our code. Do we need to follow scif license?  We are planning to release the code under MIT or BSD license. Are there any legal problem for doing so regarding Intel view?

  Thanks, MH