Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tauthon license() needs updating to include tauthon for releases 2.2 and above #67

Open
proteasome opened this issue Feb 24, 2017 · 3 comments

Comments

@proteasome
Copy link

└─╼ ./tauthon.exe
Tauthon 2.8.0a0 (default, Feb 24 2017, 00:03:02)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

license()
A. HISTORY OF THE SOFTWARE
...
Release Derived Year Owner GPL-
...
2.2 and above 2.1.1 2001-now PSF yes
...

owner of tauthon is likely not ?PSF

@naftaliharris
Copy link
Owner

Will update the license to also include Tauthon in the history.

owner of tauthon is likely not ?PSF

I'm not an expert, but I think the software license does require the code to be licensed under the Python Software License, and copyrighted to PSF. Though I don't know what "owner" means in this context:

  1. Subject to the terms and conditions of this License Agreement, PSF hereby
    grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
    analyze, test, perform and/or display publicly, prepare derivative works,
    distribute, and otherwise use Python alone or in any derivative version,
    provided, however, that PSF's License Agreement and PSF's notice of copyright,
    i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
    2011, 2012, 2013, 2014, 2015, 2016 Python Software Foundation; All Rights
    Reserved" are retained in Python alone or in any derivative version prepared by
    Licensee.

By the way, you probably want to use ``` to wrap the copied code. The ">>>" is causing Github's markdown to think you're quoting something three times. (https://guides.github.com/features/mastering-markdown/)

@proteasome
Copy link
Author

https://docs.scipy.org/doc/numpy-dev/dev/governance/governance.html#license

might be kinda a guide. it's not under PSF control. it's probably overkill. the future will determine licensing and governance. in the meantime, a one liner is probable sufficient. (time to dig into real code). ps thx for the """>>>""" tip.

@proteasome
Copy link
Author

another example @naftaliharris

In [1]: import platform

In [2]: platform.copyright
Out[2]: '\n Copyright (c) 1999-2000, Marc-Andre Lemburg; mailto:mal@lemburg.com\n Copyright (c) 2000-2010, eGenix.com Software GmbH; mailto:info@egenix.com\n\n Permission to use, copy, modify, and distribute this software and its\n documentation for any purpose and without fee or royalty is hereby granted,\n provided that the above copyright notice appear in all copies and that\n both that copyright notice and this permission notice appear in\n supporting documentation or portions thereof, including modifications,\n that you make.\n\n EGENIX.COM SOFTWARE GMBH DISCLAIMS ALL WARRANTIES WITH REGARD TO\n THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND\n FITNESS, IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL,\n INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING\n FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,\n NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION\n WITH THE USE OR PERFORMANCE OF THIS SOFTWARE !\n\n'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants