diff options
| author | Nathaniel J. Smith <njs@pobox.com> | 2018-03-08 00:00:14 -0800 |
|---|---|---|
| committer | Nathaniel J. Smith <njs@pobox.com> | 2018-03-08 00:02:42 -0800 |
| commit | 1c2bd8a22a7a7d4e13d9330e25d20dde491d2d74 (patch) | |
| tree | ee968c7b66e47d0eb11b4ba5943d9af11e9a1b95 | |
| parent | 967cfc996657ed522c9613edd5f2b874e1bb37cc (diff) | |
| download | numpy-1c2bd8a22a7a7d4e13d9330e25d20dde491d2d74.tar.gz | |
Write down a formal procedure for declaring a NEP "accepted"
| -rw-r--r-- | doc/neps/nep-0000.rst | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/neps/nep-0000.rst b/doc/neps/nep-0000.rst index bfcfac23b..ae8603c62 100644 --- a/doc/neps/nep-0000.rst +++ b/doc/neps/nep-0000.rst @@ -91,8 +91,14 @@ The possible paths of the status of NEPs are as follows: All NEPs should be created with the ``Draft`` status. -Normally, a NEP is ``Accepted`` by consensus of all -interested Contributors. +Normally, a NEP is ``Accepted`` by consensus of all interested +Contributors. To verify that consensus has been reached, the NEP +author or another interested party should make a post on the +numpy-discussion mailing list proposing it for acceptance; if there +are no substantive objections after one week, the NEP can officially +be marked ``Accepted``, and a link to this post should be added to the +NEP for reference. + In unusual cases, the `NumPy Steering Council`_ may be asked to decide whether a controversial NEP is ``Accepted``. |