Skip to content

Commit 6067ff6

Browse files
author
Csaba Drahos
committed
move "About the Jupyter Development Team" to README.md
1 parent 239f37b commit 6067ff6

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

README.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,3 +47,31 @@ $ python -m pep517.build .
4747
- [Documentation for Project Jupyter](https://jupyter.readthedocs.io/en/latest/index.html) [[PDF](https://media.readthedocs.org/pdf/jupyter/latest/jupyter.pdf)]
4848
- [Issues](https://github.com/jupyter/jupyter_console/issues)
4949
- [Technical support - Jupyter Google Group](https://groups.google.com/forum/#!forum/jupyter)
50+
51+
## About the Jupyter Development Team
52+
53+
The Jupyter Development Team is the set of all contributors to the Jupyter project.
54+
This includes all of the Jupyter subprojects.
55+
56+
The core team that coordinates development on GitHub can be found here:
57+
https://github.com/jupyter/.
58+
59+
## Our Copyright Policy
60+
61+
Jupyter uses a shared copyright model. Each contributor maintains copyright
62+
over their contributions to Jupyter. But, it is important to note that these
63+
contributions are typically only changes to the repositories. Thus, the Jupyter
64+
source code, in its entirety is not the copyright of any single person or
65+
institution. Instead, it is the collective copyright of the entire Jupyter
66+
Development Team. If individual contributors want to maintain a record of what
67+
changes/contributions they have specific copyright on, they should indicate
68+
their copyright in the commit message of the change, when they commit the
69+
change to one of the Jupyter repositories.
70+
71+
With this in mind, the following banner should be used in any source code file
72+
to indicate the copyright and license terms:
73+
74+
```
75+
# Copyright (c) Jupyter Development Team.
76+
# Distributed under the terms of the Modified BSD License.
77+
```

0 commit comments

Comments
 (0)