Show More
@@ -1,41 +1,41 b'' | |||||
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 or 3-Clause BSD) |
|
6 | New or Revised or 3-Clause BSD). See the LICENSE file. | |
7 |
|
7 | |||
8 |
|
8 | |||
9 | About the IPython Development Team |
|
9 | About the IPython Development Team | |
10 | ---------------------------------- |
|
10 | ---------------------------------- | |
11 |
|
11 | |||
12 | Fernando Perez began IPython in 2001 based on code from Janko Hauser |
|
12 | Fernando Perez began IPython in 2001 based on code from Janko Hauser | |
13 | <jhauser@zscout.de> and Nathaniel Gray <n8gray@caltech.edu>. Fernando is still |
|
13 | <jhauser@zscout.de> and Nathaniel Gray <n8gray@caltech.edu>. Fernando is still | |
14 | the project lead. |
|
14 | the project lead. | |
15 |
|
15 | |||
16 | The IPython Development Team is the set of all contributors to the IPython |
|
16 | The IPython Development Team is the set of all contributors to the IPython | |
17 | project. This includes all of the IPython subprojects. |
|
17 | project. This includes all of the IPython subprojects. | |
18 |
|
18 | |||
19 | The core team that coordinates development on GitHub can be found here: |
|
19 | The core team that coordinates development on GitHub can be found here: | |
20 | https://github.com/ipython/. |
|
20 | https://github.com/ipython/. | |
21 |
|
21 | |||
22 | Our Copyright Policy |
|
22 | Our Copyright Policy | |
23 | -------------------- |
|
23 | -------------------- | |
24 |
|
24 | |||
25 | IPython uses a shared copyright model. Each contributor maintains copyright |
|
25 | IPython uses a shared copyright model. Each contributor maintains copyright | |
26 | over their contributions to IPython. But, it is important to note that these |
|
26 | over their contributions to IPython. But, it is important to note that these | |
27 | contributions are typically only changes to the repositories. Thus, the IPython |
|
27 | contributions are typically only changes to the repositories. Thus, the IPython | |
28 | source code, in its entirety is not the copyright of any single person or |
|
28 | source code, in its entirety is not the copyright of any single person or | |
29 | institution. Instead, it is the collective copyright of the entire IPython |
|
29 | institution. Instead, it is the collective copyright of the entire IPython | |
30 | Development Team. If individual contributors want to maintain a record of what |
|
30 | Development Team. If individual contributors want to maintain a record of what | |
31 | changes/contributions they have specific copyright on, they should indicate |
|
31 | changes/contributions they have specific copyright on, they should indicate | |
32 | their copyright in the commit message of the change, when they commit the |
|
32 | their copyright in the commit message of the change, when they commit the | |
33 | change to one of the IPython repositories. |
|
33 | change to one of the IPython repositories. | |
34 |
|
34 | |||
35 | With this in mind, the following banner should be used in any source code file |
|
35 | With this in mind, the following banner should be used in any source code file | |
36 | to indicate the copyright and license terms: |
|
36 | to indicate the copyright and license terms: | |
37 |
|
37 | |||
38 | :: |
|
38 | :: | |
39 |
|
39 | |||
40 | # Copyright (c) IPython Development Team. |
|
40 | # Copyright (c) IPython Development Team. | |
41 | # Distributed under the terms of the Modified BSD License. |
|
41 | # Distributed under the terms of the Modified BSD License. |
General Comments 0
You need to be logged in to leave comments.
Login now