[Numpy-discussion] NEP process PR

[Jarrod Millman]

Hi all,

I've started working on the proposal discussed in this thread:
  https://mail.python.org/pipermail/numpy-discussion/2017-December/077481.html
here:
  https://github.com/numpy/numpy/pull/10213

You can see how I modified PEP 1 here:
  https://github.com/numpy/numpy/pull/10213/commits/eaf788940dee7d0f1c7922fac70a87144de89656

I used numbers (i.e., ``nep-0000.rst``) in the file names, since it
seems more standard and numbers are easier to refer to in discussions.
I don't have a strong preference, so I am happy to change it.  If
using numbers seems reasonable, I will number the existing NEPs.
Moreover, if the preamble seems reasonable, I will go through the
existing NEPs and make sure they all have compliant headers.  For now,
I think auto-generating the index is unnecessary.  Once we are happy
with the purpose and template NEPs as well as automatically publish to
GH pages, we can always go back and write a little script to
autogenerate the index using the preamble information.

Finally, I started preparing to host the NEPs online at:
  http://numpy.github.io/neps
If that seems reasonable, I will need someone to create a neps repo.

We also need to decide whether to move ``numpy/doc/neps`` to the
master branch of the new neps repo or whether to leave it where it is.
I don't have a strong opinion either way.  However, if no one else
minds leaving it where it is, not moving it is slightly less work.
Either way, the work is trivial.  Regardless of where the source
resides, we can host the generated web page in the same location
(i.e., http://numpy.github.io/neps).

It is probably also worth having
  https://docs.scipy.org/doc/numpy/neps/
redirect to
  http://numpy.github.io/neps

Best regards,
Jarrod