summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas A Caswell <tcaswell@gmail.com>2019-07-23 09:41:28 -0400
committerThomas A Caswell <tcaswell@gmail.com>2019-07-23 09:41:28 -0400
commit74c6d9b92eac199a8daecc0d2b25ca3cb0a84afa (patch)
treeb3c981f7132985641c2d9913b240ee5724cfbfd9
parent80de4dfa0aa818074c75a2cc96e21d7b597156ec (diff)
downloadnumpy-74c6d9b92eac199a8daecc0d2b25ca3cb0a84afa.tar.gz
DOC: add note about lack of SPEEP and role of authors
-rw-r--r--doc/neps/nep-0028-deprecation_policy.rst10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/neps/nep-0028-deprecation_policy.rst b/doc/neps/nep-0028-deprecation_policy.rst
index 6bdc19f86..6f7e89774 100644
--- a/doc/neps/nep-0028-deprecation_policy.rst
+++ b/doc/neps/nep-0028-deprecation_policy.rst
@@ -18,6 +18,16 @@ that downstream projects support. By standardizing this policy
across community we will make it easier for down stream projects to
plan.
+This is an unusual NEP in that it is recommendations for community
+wide policy and not for changes to NumPy itself. However, we do not
+currently have a place for SPEEPs (Scientific Python Ecosystem
+Enhancement Proposals) and given NumPy's central roll in our community
+this seems like the proper place to document this.
+
+
+This is being put forward by maintainers of Matplotlib, scikit-learn,
+IPython, Jupyter, yt, SciPy, NumPy, and scikit-image.
+
Detailed description