Borked during merge of Products.PloneHotfix20131210 fixes.

Also fix one HTTP PyPI reference that I missed.

Because otherwise doc/INSTALL.rst lies to users when it tells them the
source tarball will have a buildout.cfg and everything.  Lying to users
is Bad.

(I don't know what to do about the .mo files that are in git.  Should
they be included in the sdist?)

PyPI will redirect to HTTPS anyway, besides, why allow the man-in-the-middle?

There is no bootstrap/ subdirectory in git.

Then again there's no bootstrap/ subdirectory nor bootstrap.py nor, in fact, buildout.cfg in https://pypi.python.org/packages/source/Z/Zope2/Zope2-2.13.22.zip, so I don't know what this document is talking about.  Broken MANIFEST.in?

The changelog is the canonical place for bug / release associations.

(was at svn.zope.org/repos/main/zope2docs/trunk/maintenance/index.rst)

Fix extends

Looks like the URL on svn.zope.org changed recently from http://svn.zope.org/repos/main/zopetoolkit… to http://svn.zope.org/zopetoolkit…. Also fix setup.py's reference to README.rst

Rename README.txt to README.rst for prettier GitHub page

Update README to warn people reading the pypi page not to just `easy_install Zope2`

This implements the idea of the patch from
https://bugs.launchpad.net/zope2/+bug/143352
but also honours the trusted-proxy setting.

This implements the idea of the patch from
https://bugs.launchpad.net/zope2/+bug/143352
but also honours the trusted-proxy setting.

The unimportant events have changed names.

The unimportant events have changed names.