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


Groups > comp.lang.python > #109493

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

From Random832 <random832@fastmail.com>
Newsgroups comp.lang.python
Subject Re: Don't put your software in the public domain
Date 2016-06-04 23:46 -0400
Message-ID <mailman.3.1465098396.2306.python-list@python.org> (permalink)
References (2 earlier) <5751539f$0$1586$c3e8da3$5496439d@news.astraweb.com> <CAM1e3vqNsS5x0u2QyPv-Pf15p_qRTqinwnwF10O6+kMNQN77xg@mail.gmail.com> <mailman.124.1464959672.1839.python-list@python.org> <575236a6$0$22142$c3e8da3$5496439d@news.astraweb.com> <1465098394.960291.628179457.5889267B@webmail.messagingengine.com>

Show all headers | View raw


On Fri, Jun 3, 2016, at 22:02, Steven D'Aprano wrote:
> (I am surprised that it takes so little to grant end-user usage
> rights, but IANAL and presumably the FSF's lawyers consider that
> sufficient. Perhaps there are common law usage rights involved.)

Technically, there are statutory usage rights; 17 USC 117 (a) (1):

(a)Making of Additional Copy or Adaptation by Owner of
Copy.—Notwithstanding the provisions of section 106, it is not an
infringement for the owner of a copy of a computer program to make or
authorize the making of another copy or adaptation of that computer
program provided:
(1) that such a new copy or adaptation is created as an essential step
in the utilization of the computer program in conjunction with a machine
and that it is used in no other manner, or
(2) that such new copy or adaptation is for archival purposes only and
that all archival copies are destroyed in the event that continued
possession of the computer program should cease to be rightful.

The proprietary software industry's continued ability to make demands in
an EULA rests on a rather shaky (though less than it was in the
box-full-of-disks days) theory that buying software does not in fact
make you the "owner of a copy", something that open-source types don't
tend to claim regarding their own software.

(IANAL either of course)

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