##// END OF EJS Templates
upstream » ipython
RSS

Clone from https://github.com/ipython/ipython.git

Update COPYING.txt...
Jonathan Frederic -
Show More
Show file before | Show file after | Hide comments
@@ -1,85 +1,74
1 =============================
1 =============================
2 The IPython licensing terms
2 The IPython licensing terms
3 =============================
3 =============================
4
4
5 IPython is licensed under the terms of the Modified BSD License (also known as
5 IPython is licensed under the terms of the Modified BSD License (also known as
6 New or Revised BSD), as follows:
6 New or Revised or 3-Clause BSD), as follows:
7
7
8 Copyright (c) 2008-2010, IPython Development Team
8 - Copyright (c) 2008-2014, IPython Development Team
9 Copyright (c) 2001-2007, Fernando Perez. <fernando.perez@colorado.edu>
9 - Copyright (c) 2001-2007, Fernando Perez <fernando.perez@colorado.edu>
10 Copyright (c) 2001, Janko Hauser <jhauser@zscout.de>
10 - Copyright (c) 2001, Janko Hauser <jhauser@zscout.de>
11 Copyright (c) 2001, Nathaniel Gray <n8gray@caltech.edu>
11 - Copyright (c) 2001, Nathaniel Gray <n8gray@caltech.edu>
12
12
13 All rights reserved.
13 All rights reserved.
14
14
15 Redistribution and use in source and binary forms, with or without
15 Redistribution and use in source and binary forms, with or without
16 modification, are permitted provided that the following conditions are met:
16 modification, are permitted provided that the following conditions are met:
17
17
18 Redistributions of source code must retain the above copyright notice, this
18 Redistributions of source code must retain the above copyright notice, this
19 list of conditions and the following disclaimer.
19 list of conditions and the following disclaimer.
20
20
21 Redistributions in binary form must reproduce the above copyright notice, this
21 Redistributions in binary form must reproduce the above copyright notice, this
22 list of conditions and the following disclaimer in the documentation and/or
22 list of conditions and the following disclaimer in the documentation and/or
23 other materials provided with the distribution.
23 other materials provided with the distribution.
24
24
25 Neither the name of the IPython Development Team nor the names of its
25 Neither the name of the IPython Development Team nor the names of its
26 contributors may be used to endorse or promote products derived from this
26 contributors may be used to endorse or promote products derived from this
27 software without specific prior written permission.
27 software without specific prior written permission.
28
28
29 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
29 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
30 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
30 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
31 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
31 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
32 DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
32 DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
33 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
33 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
34 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
34 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
35 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
35 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
36 CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
36 CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
37 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
37 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
38 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
38 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
39
39
40 About the IPython Development Team
40 About the IPython Development Team
41 ----------------------------------
41 ----------------------------------
42
42
43 Fernando Perez began IPython in 2001 based on code from Janko Hauser
43 Fernando Perez began IPython in 2001 based on code from Janko Hauser
44 <jhauser@zscout.de> and Nathaniel Gray <n8gray@caltech.edu>. Fernando is still
44 <jhauser@zscout.de> and Nathaniel Gray <n8gray@caltech.edu>. Fernando is still
45 the project lead.
45 the project lead.
46
46
47 The IPython Development Team is the set of all contributors to the IPython
47 The IPython Development Team is the set of all contributors to the IPython
48 project. This includes all of the IPython subprojects. A full list with
48 project. This includes all of the IPython subprojects. A full list with
49 details is kept in the documentation directory, in the file
49 details is kept in the documentation directory, in the file
50 ``about/credits.txt``.
50 ``about/credits.txt``.
51
51
52 The core team that coordinates development on GitHub can be found here:
52 The core team that coordinates development on GitHub can be found here:
53 http://github.com/ipython. As of late 2010, it consists of:
53 https://github.com/ipython/.
54
55 * Brian E. Granger
56 * Jonathan March
57 * Evan Patterson
58 * Fernando Perez
59 * Min Ragan-Kelley
60 * Robert Kern
61
62
54
63 Our Copyright Policy
55 Our Copyright Policy
64 --------------------
56 --------------------
65
57
66 IPython uses a shared copyright model. Each contributor maintains copyright
58 IPython uses a shared copyright model. Each contributor maintains copyright
67 over their contributions to IPython. But, it is important to note that these
59 over their contributions to IPython. But, it is important to note that these
68 contributions are typically only changes to the repositories. Thus, the IPython
60 contributions are typically only changes to the repositories. Thus, the IPython
69 source code, in its entirety is not the copyright of any single person or
61 source code, in its entirety is not the copyright of any single person or
70 institution. Instead, it is the collective copyright of the entire IPython
62 institution. Instead, it is the collective copyright of the entire IPython
71 Development Team. If individual contributors want to maintain a record of what
63 Development Team. If individual contributors want to maintain a record of what
72 changes/contributions they have specific copyright on, they should indicate
64 changes/contributions they have specific copyright on, they should indicate
73 their copyright in the commit message of the change, when they commit the
65 their copyright in the commit message of the change, when they commit the
74 change to one of the IPython repositories.
66 change to one of the IPython repositories.
75
67
76 With this in mind, the following banner should be used in any source code file
68 With this in mind, the following banner should be used in any source code file
77 to indicate the copyright and license terms:
69 to indicate the copyright and license terms:
78
70
79 #-----------------------------------------------------------------------------
71 ::
80 # Copyright (c) 2010, IPython Development Team.
72
81 #
73 # Copyright (c) IPython Development Team.
82 # Distributed under the terms of the Modified BSD License.
74 # Distributed under the terms of the Modified BSD License.
83 #
84 # The full license is in the file COPYING.txt, distributed with this software.
85 #-----------------------------------------------------------------------------
General Comments 0
You need to be logged in to leave comments. Login now