Thanks Buck.



I know all of this info was already on the web-site, but I think I just read too much into the questions and began to second-guess myself.



Another area of our concern is if a Vendor is suddenly (for some reason) unable to use the open source code any longer (pirated for example), what would be our exposure? Could we be accused of accepting stolen goods? What happens to the product if, during a dispute, the open source component is no longer available to the Vendor? Will we need to back it out of our own code? Can the functionality change? Will we be (as you mentioned) risking some portion of our own profit just because we made use of the product?



So the risks seem to range the gamut from civil to criminal.



These are the types of things that seem to keep lawyers awake at night...and the points they want handled prior to the introduction of this type of product.



We live in a murky world where people will split hairs for a nickel.



Thanks!



Steve



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Sent: Tuesday, July 06, 2010 3:52 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Open Source component list for the RDi Plugin



On 7/6/2010 4:36 PM, Stephen wrote:



In order to allow this open source stuff into the world I work in, I need a bit of info. John Zurich of Softlanding pointed me to this list.



1. Open Source Product Name

SoftLanding RSE Extensions Plug-in for IBM Rational Developer for i



2. Open Source Product Description

RSE Extensions Plug-in for IBM Rational Developer for i



3. Open Source Vendor

SoftLanding



The classic reason to ask these questions is because you are making a

'for profit' product and you don't want to inadvertently include some

snippet of open source software that will forever doom your company to

provide the entire source code base for free to the public.



I personally think that's an urban legend, but don't take legal advice

from some comment on the Internet. I think that adding an open source

extension to IBM software is a very different proposition from adding

open source software to your in-house software. That's my opinion of

course, but my boss is a stickler for 100% compliance with software

agreements and he didn't blink when I told him I'd be adding open source

extensions to WDSC.



Good luck, hope to see more of your posts in the future!

--buck

--

This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list

To post a message email: WDSCI-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit: http://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx

Before posting, please take a moment to review the archives

at http://archive.midrange.com/wdsci-l.



==============================================================================
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.