Re: Value of OpenChain for different sectors - creating one sentence explanation of value

Jan Thielscher

Hi Gary,

I can confirm this to be a common case. Both situations appear quiet often.
I would want to add one more case: changing circumstances. there are only few projects I came across, that did not change scope over time. Parts of the solution suddenly should be shared with others, solution should be transferred to another legal entity, a solution should be shipped inside a VM,... 
without a structured approach, it is an enormous effort to clarify options and consequnces.

Mit freundlichem Gruß / kind regards
Jan Thielscher

EACG GmbH - s.a.
T: +49 69 153 22 77 50

On 25. May 2018, at 17:56, Gary O'Neall <gary@...> wrote:

For SaaS - the client-side software is the most common and compelling reason to use OpenChain.  My only suggestion is to elaborate a bit more on "client-side software".  I would propose adding "(e.g. browser-based software or agents downloaded by the user)".

There are two other less common situations requiring open source policy updates which my clients have run into:
- Deciding to offer an "on premise" solution for security sensitive customers where the server software is deployed to their customer premises
- A sale/acquisition involving the transfer of assets which would include the server-side software

I don't know if either of these are common enough to include, but I though I would put them out there for consideration.  


-----Original Message-----
From: openchain-bounces@... <openchain-
bounces@...> On Behalf Of Matija Šuklje
Sent: Friday, May 25, 2018 8:11 AM
To: openchain@...
Subject: Re: [OpenChain] Value of OpenChain for different sectors - creating
one sentence explanation of value

On sreda, 23. maj 2018 09:57:28 CEST Shane Coughlan wrote:
- Help wanted!

How about something in the line:
“OpenChain helps SaaS providers to provide the needed information on
their client-side software in order to comply with the key international
Open Source license compliance processes.”

…I’m not 100% happy with it, but offer it for butchering.

For the reasoning behind it, I’m copying from my reply from the openchain-
specs list re FOSS compliance risks in SaaS:

• least risky, as code is in generally not distributed (NB: AGPL, EUPL) •
caveat: client-side (e.g. JavaScript) code is still traditionally distributed, and
as such fits in that category • (ultra-LTS is not very likely)

Matija Šuklje
gsm:    +386 41 849 552
xmpp:   matija.suklje@...
sip:    matija_suklje@...

OpenChain mailing list

OpenChain mailing list

Join to automatically receive all group messages.