Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


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

Re: Any software law experts?

From Arne Vajhøj <arne@vajhoej.dk>
Newsgroups comp.lang.java.programmer
Subject Re: Any software law experts?
Date 2022-11-09 16:12 -0500
Organization Aioe.org NNTP Server
Message-ID <tkh54n$f1i$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> <tkgvji$1vl8$1@gioia.aioe.org> <b0296d5b-dbef-4f6b-9986-14c464a5f291n@googlegroups.com>

Show all headers | View raw


On 11/9/2022 2:51 PM, e.d.pro...@gmail.com wrote:
> On Wednesday, November 9, 2022 at 2:38:40 PM UTC-5, Arne Vajhøj wrote:
>>> 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.

> Obviously if you add someone else's library as a dependency, it's not
> upgradeable as your dependency without possibly modifying your code,
> but you could share just that code as is and they can modify it in
> the repo you got it from.
If you have yourapp.jar that depend on somelgpllib.jar, then
the somelgpllib.jar can be updated independently of yourapp.jar.

If somelgpllib has made incompatible changes then it may
no longer work, but that is not your problem. You have
complied with the LGPL requirement - the end user can
upgarde somelgpllib.jar - it is their responsibility to
only upgrade to a version that works.

>> 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.

> I take that to mean if you write code for an organization, a web app
> accessible only to members of that organization, any member of that
> organization could request your source. Technically that sounds like
> any member of that organization could then publish that source with
> an AGPL license, but that would sound problematic if they all signed
> NDAs.
Traditionally an org is considered a single legal entity. The org
use it internally. No problem. All the rules apply when the code
is used by someone outside the org.

Arne

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


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