PEP status and python-dev summaries

[Jeremy Hylton]

I just scanned the responses on comp.lang.python to Andrew's
announcement that he would stopping write the python-dev summaries.
The respondents indicated that they found it hard to keep track of
what was going on with python development, particularly PEPs.

We're still learning how to use the PEP process.  It's been better for
2.1 than for 2.0, but still has some problems.  It sounds like the key
problem has been involving the community outside python-dev.

I would suggest a couple of changes, with the burden mostly falling on
Barry and me:

- Regular announcements of PEP creation and PEP status changes should
  be posted to comp.lang.python and c.l.p.a.

- The release status PEPs should be kept up to date and regularly
  posted to the same groups.

- We should have highly visible pointers from python.org to PEPs and
  other python development information.  I'm sure we do this as part
  of the Zopification plans that Guido mentioned.

- We should not approve PEPs that aren't announced on comp.lang.python
  with enough time for people to comment.

Jeremy