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


Groups > comp.lang.python > #43033

Re: im.py: a python communications tool

References (1 earlier) <roy-C84B79.21072105042013@news.panix.com> <mailman.178.1365211568.3114.python-list@python.org> <kjrcgu$dsk$2@speranza.aioe.org> <48f984a0-7702-4cba-9021-06c3985646da@googlegroups.com> <5161f508$0$29995$c3e8da3$5496439d@news.astraweb.com>
Date 2013-04-08 13:00 +1000
Subject Re: im.py: a python communications tool
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.262.1365390020.3114.python-list@python.org> (permalink)

Show all headers | View raw


On Mon, Apr 8, 2013 at 8:36 AM, Steven D'Aprano
<steve+comp.lang.python@pearwood.info> wrote:
> On Sun, 07 Apr 2013 14:47:11 -0700, jhunter.dunefsky wrote:
>
>> Actually, my current licence can be found here:
>> https://github.com/jhunter-d/im.py/blob/master/LICENCE.  Whaddaya think
>> about this, Useneters?
>
>
> I think you're looking for a world of pain, when somebody uses your
> software, it breaks something, and they sue you. Your licence currently
> means that you are responsible for the performance of your software.
>
> Why don't you use a recognised, tested, legally-correct licence, like the
> MIT licence, instead of trying to be clever and/or lazy with a one-liner?
>
> E.g. http://opensource.org/licenses/MIT

Plus there's the whole brevity thing. If I see something that says
"MIT license", I don't need to read the details. Compare the README
for one of my projects:

https://github.com/Rosuav/Gypsum/blob/master/README

(Actually, I need to update that; there are a few solved problems
listed there as still open.) You read "Licensed under the BSD Open
Source license" and then you can stop reading - you know what your
rights are. The lawyers at Roy Smith's company would have no trouble
comprehending this, and no trouble deciding whether or not it's
allowed - they either do or do not (there is no try).

License proliferation is actually a major problem. If I were to lift
code from your program and incorporate it into something GPL3, am I
violating either's terms? What if I want to put that code into
something BSD 2-clause? Am I allowed? At least if you use a well-known
license, I can do a quick web search, coming up with something like
[1], but a custom or unusual license would require careful analysis of
terms.

[1] http://www.dwheeler.com/essays/floss-license-slide.html

ChrisA

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


Thread

im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-05 17:16 -0700
  Re: im.py: a python communications tool Demian Brecht <demianbrecht@gmail.com> - 2013-04-05 17:52 -0700
    Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-06 08:35 -0700
  Re: im.py: a python communications tool Roy Smith <roy@panix.com> - 2013-04-05 21:07 -0400
    Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-05 18:13 -0700
    Re: im.py: a python communications tool Andrew Berg <bahamutzero8825@gmail.com> - 2013-04-05 20:26 -0500
      Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-06 07:54 -0700
      Re: im.py: a python communications tool garabik-news-2005-05@kassiopeia.juls.savba.sk - 2013-04-07 08:59 +0000
        Re: im.py: a python communications tool jhunter.dunefsky@gmail.com - 2013-04-07 14:47 -0700
          Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-07 22:36 +0000
            Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-08 13:00 +1000
            Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-08 03:48 -0700
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 16:16 -0700
            Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-08 22:05 -0400
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 20:37 -0700
            Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 02:04 -0400
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 23:20 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 06:47 +0000
            Re: im.py: a python communications tool Demian Brecht <demianbrecht@gmail.com> - 2013-04-08 23:42 -0700
            Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 02:42 -0400
            Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 17:14 +1000
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 00:20 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 07:38 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:02 -0700
                Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 09:08 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:29 -0700
                Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 13:05 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-12 12:57 -0700
                Re: im.py: a python communications tool Neil Cerutti <neilc@norwich.edu> - 2013-04-12 20:05 +0000
                RE: im.py: a python communications tool "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2013-04-12 21:48 +0000
                RE: im.py: a python communications tool "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2013-04-12 19:46 +0000
            Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 17:21 +1000
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 00:39 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 08:31 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:58 -0700
                Re: im.py: a python communications tool Grant Edwards <invalid@invalid.invalid> - 2013-04-09 14:41 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 09:36 -0700
                Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 19:40 +1000
                Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 13:03 +0000
                Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 23:23 +1000
                Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 19:48 +1000
                Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-09 04:09 -0700
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:46 -0700
              Re: im.py: a python communications tool Grant Edwards <invalid@invalid.invalid> - 2013-04-09 14:30 +0000
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:15 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 08:45 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:00 -0700
                Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 05:18 -0400
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:32 -0700
            Re: im.py: a python communications tool Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-04-09 17:10 +0100

csiph-web