Groups > comp.lang.java.programmer > #39846

Re: Any software law experts?

Path	csiph.com!aioe.org!LeVffQP25j5GAigzc2gaQA.user.46.165.242.75.POSTED!not-for-mail
From	Arne Vajhøj <arne@vajhoej.dk>
Newsgroups	comp.lang.java.programmer
Subject	Re: Any software law experts?
Date	Wed, 9 Nov 2022 14:38:25 -0500
Organization	Aioe.org NNTP Server
Message-ID	<tkgvji$1vl8$1@gioia.aioe.org> (permalink)
References	<fee4fd9f-8b60-4703-9c7b-2551cff7ee37n@googlegroups.com> <tkesfg$1ohq$1@gioia.aioe.org> <6672570a-42f6-4a92-a427-92e342ce1235n@googlegroups.com>
Mime-Version	1.0
Content-Type	text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding	7bit
Injection-Info	gioia.aioe.org; logging-data="65192"; posting-host="LeVffQP25j5GAigzc2gaQA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Content-Language	en-US
X-Notice	Filtered by postfilter v. 0.9.2
Xref	csiph.com comp.lang.java.programmer:39846

Show key headers only | View raw

On 11/9/2022 7:21 AM, e.d.pro...@gmail.com wrote:
>> There are 3 fundamental types of open source licenses: * permissive
>> (Apache, MIT, BSD etc.) * weak copy left (LGPL, GPL with linking
>> exception, MPL etc.) * strong copy left (GPL, AGPL)
>> 
> It appears with LGPL you can make a closed source product and the
> code of your dependency must be available somewhere, no special
> requirement when you're not modifying their code.

The LGPL library must be independently upgradeable.

>                                                  With AGPL it
> appears if you use their library, you must make all your source
> available to all users of your app when you're using the dependency
> unmodified, that the AGPL states this requirement for when you're
> modifying the third party code apparently includes using it as a
> dependency as a modification. The only way around this is to write
> something using the third party code that runs independently of your
> main app code, where your app is viable without that piece.

You can use the AGPL code with your code for your self or internal
in your organization.

But if you distribute your code or make your code available
as SaaS then the users has the right to not only the original
AGPL code but also to your code under AGPL. And if you do not
comply with that, then you have no right to use the original
AGPL code.

Arne

Thread

Any software law experts? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-11-08 06:00 -0800
  Re: Any software law experts? Arne Vajhøj <arne@vajhoej.dk> - 2022-11-08 19:32 -0500
    Re: Any software law experts? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-11-09 04:21 -0800
      Re: Any software law experts? Arne Vajhøj <arne@vajhoej.dk> - 2022-11-09 14:38 -0500
        Re: Any software law experts? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-11-09 11:51 -0800
          Re: Any software law experts? Arne Vajhøj <arne@vajhoej.dk> - 2022-11-09 16:12 -0500
    Re: Any software law experts? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-11-09 04:53 -0800
      Re: Any software law experts? Arne Vajhøj <arne@vajhoej.dk> - 2022-11-09 14:34 -0500
        Re: Any software law experts? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-11-09 11:42 -0800
          Re: Any software law experts? Arne Vajhøj <arne@vajhoej.dk> - 2022-11-09 14:50 -0500
            Re: Any software law experts? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-11-09 11:55 -0800
              Re: Any software law experts? Arne Vajhøj <arne@vajhoej.dk> - 2022-11-09 20:21 -0500

csiph-web