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


Groups > comp.lang.python > #109558

Re: Don't put your software in the public domain

From Paul Rudin <paul.nospam@rudin.co.uk>
Newsgroups comp.lang.python
Subject Re: Don't put your software in the public domain
Date 2016-06-06 13:36 +0100
Message-ID <87twh6335b.fsf@rudin.co.uk> (permalink)
References (2 earlier) <5751539f$0$1586$c3e8da3$5496439d@news.astraweb.com> <c32d2b5f-77f6-49fa-b285-572696397939@googlegroups.com> <pan.2016.06.03.21.00.59.976000@nowhere.invalid> <57523cd3$0$1587$c3e8da3$5496439d@news.astraweb.com> <pan.2016.06.06.05.57.20.251000@nowhere.invalid>

Show all headers | View raw


Nobody <nobody@nowhere.invalid> writes:

> On Sat, 04 Jun 2016 12:28:33 +1000, Steven D'Aprano wrote:
>
>>> OTOH, a Free software licence is unilateral; the author grants the user
>>> certain rights, with the user providing nothing in return.
>> 
>> That's not the case with the GPL.
>> 
>> The GPL requires the user (not the end-user, who merely avails themselves
>> of their common law right to run the software, but the developer user, who
>> copies, distributes and modifies the code) to do certain things in return
>> for the right to copy, distribute and modify the code:
>
> The GPL places limitations on the granted licence. That isn't the same
> thing as requiring the distributor to do something "in return".
>

The distributor grants the licence.

> This is why the (relatively few) cases where GPL infringements have
> resulted in litigation, the legal basis of the litigation is copyright
> infringement, not breach of contract.

Right, but the defence is that the licence grants permission to use; so
that's where the law if contract comes into it. You have to figure out
whether the use in question falls within the licence terms.

So if someone brings an action for copyright infringement you can argue
at least some of:

1. Copyright doesn't subsist in the copied material.
2. You didn't copy it.
3. One of the legal defences (fair use etc.) applies.
4. You had the permission of the copyright owner (i.e. a licence to copy
in these circumstances).


In the last case we're essentially into contract law.

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-02 00:59 +1000
  Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-01 18:44 +0300
  Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-01 13:45 -0700
    Re: Don't put your software in the public domain John Wong <gokoproject@gmail.com> - 2016-06-01 17:00 -0400
      Re: Don't put your software in the public domain Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-06-02 13:38 +1000
    Re: Don't put your software in the public domain Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-06-02 13:43 +1000
  Re: Don't put your software in the public domain Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-06-02 18:41 +1200
    Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-02 21:56 +1000
      Re: Don't put your software in the public domain Chris Angelico <rosuav@gmail.com> - 2016-06-02 22:04 +1000
        Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-02 15:26 +0300
          Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-02 18:11 -0700
    Re: Don't put your software in the public domain Robin Becker <robin@reportlab.com> - 2016-06-02 13:52 +0100
    Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-03 19:53 +1000
      Re: Don't put your software in the public domain Michael Torrie <torriem@gmail.com> - 2016-06-03 07:14 -0600
        Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-04 12:02 +1000
          Re: Don't put your software in the public domain Random832 <random832@fastmail.com> - 2016-06-04 23:46 -0400
      Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-03 09:15 -0700
        Re: Don't put your software in the public domain Nobody <nobody@nowhere.invalid> - 2016-06-03 21:58 +0100
          Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-03 18:10 -0700
            Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-04 09:04 +0100
          Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-04 12:28 +1000
            Re: Don't put your software in the public domain Nobody <nobody@nowhere.invalid> - 2016-06-06 06:54 +0100
              Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-06 13:36 +0100
              Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-07 01:59 +1000
          Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-04 08:24 +0100
            Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-04 11:24 +0300
              Re: Don't put your software in the public domain Terry Reedy <tjreedy@udel.edu> - 2016-06-04 15:12 -0400
                Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-05 00:26 +0300
        Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-04 12:12 +1000
        Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-04 08:20 +0100

csiph-web