PEP 480: Fix status, author, discuss, reference

[brainwane]

Move from Deferred to Draft status, update discussion venue and author list, and fix an obsolete reference to Distutils.

Signed-off-by: Sumana Harihareswara sh@changeset.nyc

[brainwane]

Followup to #1681 to be reviewed by @mnm678 @trishankatdatadog @pfmoore and ideally @ncoghlan.

Also, the bit about PyPI users registering projects prior to uploading

peps/pep-0480.txt

Lines 380 to 395 in e2b198b

	The following outlines an automated signing solution that a new developer MAY
	follow to upload a distribution to PyPI:
	1. Register a PyPI project.
	2. Enter a secondary password (independent of the PyPI user account password).
	3. Optional: Add a new identity to the developer's PyPI user account from a
	second machine (after a password prompt).
	4. Upload project.
	Step 1 is the normal procedure followed by developers to `register a PyPI
	project`__.
	__ https://pypi.python.org/pypi?:action=register_form
	Step 2 generates an encrypted key file (private), uploads an Ed25519 public key
	to PyPI, and signs the TUF metadata that is generated for the distribution.

is now obsolete and needs to be updated before we can re-start deliberations on this PEP.

[brainwane]

Also, the bit about PyPI users registering projects prior to uploading

peps/pep-0480.txt

Lines 380 to 395 in e2b198b

	The following outlines an automated signing solution that a new developer MAY
	follow to upload a distribution to PyPI:
	1. Register a PyPI project.
	2. Enter a secondary password (independent of the PyPI user account password).
	3. Optional: Add a new identity to the developer's PyPI user account from a
	second machine (after a password prompt).
	4. Upload project.
	Step 1 is the normal procedure followed by developers to `register a PyPI
	project`__.
	__ https://pypi.python.org/pypi?:action=register_form
	Step 2 generates an encrypted key file (private), uploads an Ed25519 public key
	to PyPI, and signs the TUF metadata that is generated for the distribution.

is now obsolete and needs to be updated before we can re-start deliberations on this PEP.

@mnm678 if you want you could do that as a separate PR, or you could make a fresh review with a suggested replacement and I'll commit it into this PR.

[brainwane]

(Further discussion on The Update Framework's mailing list, in case anyone is curious.)

[brainwane]

@pfmoore @dstufft could this get a fresh review so we can update the authors? Thanks!

[brainwane]

@dstufft I would appreciate if you could review this and #1711, please.