Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #72264
| References | <1fgpxn70wxrg0.1rv21r79ohz7z$.dlg@40tude.net> <CAPTjJmqTkY3g21fvn-xUf26Ua9AzTYKMCGr1i45R2chyRyVNrQ@mail.gmail.com> <CALwzidn2NL4ZpA0TO++4tMO5rDYRR2Qqax3m62bxzLYAK4P5bA@mail.gmail.com> |
|---|---|
| Date | 2014-05-30 10:26 +1000 |
| Subject | Re: Forking PyPI package |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.10465.1401409586.18130.python-list@python.org> (permalink) |
On Fri, May 30, 2014 at 7:54 AM, Ian Kelly <ian.g.kelly@gmail.com> wrote: > On Thu, May 29, 2014 at 1:40 AM, Chris Angelico <rosuav@gmail.com> wrote: >> If you absolutely can't get in touch with him, the only option is to >> go back to the original protocol and manually reimplement it, >> completely ignoring this code. It's sad but true; some code dies >> because of a trivial thing like "Oops, I forgot to actually say that >> this is MIT-licensed". > > The second part of that is that the code should actually *include* the > license text. Just writing "BSD license" somewhere on the website or > in package metadata is annoyingly common but somewhat questionable in > how a judge might interpret it. For instance, there at least four > different versions of the BSD license; which one did you mean? Agreed. I tend to have a file called README or LICENSE in the main source code directory that has license terms (in the case of a README, the license will follow whatever else there is to say); that's generally clear enough, without having to put a header on every single source file. I like to put both a short name and the full license text in there (see eg https://github.com/Rosuav/Yosemite for which I use the MIT license), so it's independent of random web sites - having nothing but a link to the license text makes it that bit more vulnerable. ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Forking PyPI package Wiktor <look@signature.invalid> - 2014-05-29 02:31 +0200
Re: Forking PyPI package Terry Reedy <tjreedy@udel.edu> - 2014-05-28 22:06 -0400
Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-05-29 17:40 +1000
Re: Forking PyPI package Duncan Booth <duncan.booth@invalid.invalid> - 2014-05-29 07:56 +0000
Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-05-29 18:06 +1000
Re: Forking PyPI package Wiktor <look@signature.invalid> - 2014-05-29 10:49 +0200
Re: Forking PyPI package Ian Kelly <ian.g.kelly@gmail.com> - 2014-05-29 15:54 -0600
Re: Forking PyPI package Wiktor <look@signature.invalid> - 2014-06-05 18:56 +0200
Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-06-06 03:37 +1000
Re: Forking PyPI package Wiktor <look@signature.invalid> - 2014-06-06 02:15 +0200
Re: Forking PyPI package Akira Li <4kir4.1i@gmail.com> - 2014-06-06 15:26 +0400
Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-05-30 10:26 +1000
csiph-web