Blog Post on a Worker Pool Design Pattern without VI Server

[TCPlomp]

As for the OpenG code.

This is licensend under the BSD license:

In short this means that if you use OpenG code, you need to state that somewhere with your code including the BSD license.

Appropriate locations for binaries are:

• About screen
• License agreement

For source distributions this is only needed if you remove the front panel of the VIs since the license is embedded on the FP.

Ton

[F._Schubert]

Thank you Ton

Just to get everything in my head (I really feel illitarate when reading about this issue). I was reading a bit the last hour on this issue and try to translate it to my situation (I deliver turn-key equipment).

I place in the about page a notice similar to this:

This software contains code from OpenG (include link) that is copyrighted by

Person A

Person B

Person X

under the BSD licence (link to the license)

and include the BSD license file as txt as well.

Felix

[Tomi_Maila]

I chose CC license over BSD for example code. The code I provide is more like a creative work for communication rather than a software library. For production code and libraries I will not use CC but some other license such as BSD or LGPL. The code is not really intended to be used in a production environment, it is not production quality. It is an example of a pattern that can be used in your own programs. Yes, CC allows you to use this code in your production code. It is not viral license and doesn't force you to license everything with CC or even use CC for the code that is based on my example.

All LAVA content is, or at least was, under CC license except the code repository. Most of the forums and online communities use CC license. NI Forums content is under NI own propriatary license. OpenG libraries are under different kinds of licenses but mostly under BSD license.

[TCPlomp]

---

F. Schubert wrote:

Thank you Ton

Just to get everything in my head (I really feel illitarate when reading about this issue). I was reading a bit the last hour on this issue and try to translate it to my situation (I deliver turn-key equipment).

I place in the about page a notice similar to this:

This software contains code from OpenG (include link) that is copyrighted by

Person A

Person B

Person X

under the BSD licence (link to the license)

and include the BSD license file as txt as well.

Felix

---

This software contains code from OpenG (http://www.openg.org) that is copyrighted by

OpenG.org

under the BSD license:

Copyright (c) 2009, OpenG.org

All rights reserved.

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, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the <organization> nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY OPENG.ORG ''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 <copyright holder> 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.

That is what I would use.

Ton