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