fixed broken/bad community links

bugs.rst

-Bugs
-====
-
-General bug reporting happens in the `Launchpad bug tracker <http://bugs.launchpad.net/zodb>`_.
-
-However, the ZODB has been around much longer and thus there are some historic
-resource for bug-related information.:
-
-* Zope collector (with topic `database`) at http://collector.zope.org/Collectors/Zope
-* ZODB sourceforge bug tracker (much older) at http://sourceforge.net/tracker/?group_id=15628&atid=115628

buildout.cfg

@@ -3,7 +3,6 @@ develop =
 parts =
     stxpy
 
-eggs-directory = ${buildout:directory}/eggs
 versions = versions
 unzip = true
 eggs =

conf.py

@@ -92,7 +92,7 @@ pygments_style = 'sphinx'
 # The style sheet to use for HTML and HTML Help pages. A file of that name
 # must exist either in Sphinx' static/ path, or in one of the custom paths
 # given in html_static_path.
-html_style = 'default.css'
+#html_style = 'default.css'
 
 # The name for this set of Sphinx documents.  If None, it defaults to
 # "<project> v<release> documentation".

documentation/guide/modules.rst

@@ -275,7 +275,9 @@ that are instances of a user-defined class that doesn't supply its own
 :meth:`__cmp__` method.  Python compares such instances by memory address.  This
 is fine if such instances are used as keys in temporary BTree-based structures
 used only in a single program run.  It can be disastrous if that BTree-based
-structure is stored to a database, though. ::
+structure is stored to a database, though.
+
+::
 
    >>> class C:
    ...     pass
@@ -297,7 +299,7 @@ Another problem occurs with instances of classes that do define :meth:`__cmp__`,
 but define it incorrectly.  It's possible but rare for a custom :meth:`__cmp__`
 implementation to violate one of the three required formal properties directly.
 It's more common for it to "fall back" to address-based comparison by mistake.
-For example, ::
+For example::
 
    class Mine:
        def __cmp__(self, other):
@@ -306,7 +308,7 @@ For example, ::
            else:
                return cmp(self.data, other)
 
-It's quite possible there that the :keyword:`else` clause allows a result to be
+It's quite possible there that the ``else`` clause allows a result to be
 computed based on memory address.  The bug won't show up until a BTree-based
 structure uses objects of class :class:`Mine` as keys, and also objects of other
 types as keys, and the structure is loaded from a database, and a sequence of

features.rst

-Feature requests
-================
-
-Feature requests are currently handled a bit ad-hoc. Feel free to write a post
-to the mailing list asking for a feature and - if you don't want it to be
-forgotten - add a
-`blueprint in Launchpad <http://blueprints.launchpad.net/zodb>`_
-
-Also, formerly we used to manage proposals in our old wiki at
-http://wiki.zope.org/ZODB/ListOfProposals/contents#ListOfProposals

index.rst

@@ -42,15 +42,14 @@ Documentation
    documentation/tutorial
    documentation/guide/index
    documentation/articles/index
-   bugs
-   features
 
 * `The ZODB Book (in progress) <http://zodb.readthedocs.org/en/latest/>`_ 
 
 Downloads
 =========
 
-ZODB is distributed as Python eggs through the `Python Package Index <http://pypi.python.org/pypi/ZODB3>`_.
+ZODB is distributed through the `Python Package Index
+<http://pypi.python.org/pypi/ZODB>`_.
 
 You can install the ZODB using pip command::
 
@@ -59,9 +58,23 @@ You can install the ZODB using pip command::
 Community and contributing
 ==========================
 
-Discussion occurs on the `ZODB developers' mailing list <http://mail.zope.org/mailman/listinfo/zodb-dev>`_.
+Discussion occurs on the `ZODB mailing list
+<https://groups.google.com/forum/#!forum/zodb>`_. (And for the
+transaction system on the `transaction list
+<https://groups.google.com/forum/#!forum/python-transaction>`_
 
-:doc:`Bug reporting<bugs>`, :doc:`feature requests<features>`, and release planning are done on `Launchpad <http://launchpad.net/zodb>`_.
+Bug reporting and feature requests are submitted through github issue
+trackers for various ZODB components:
+
+- `ZODB <https://github.com/zopefoundation/zodb>`_
+
+- `persistent <https://github.com/zopefoundation/persistent>`_
+
+- `transactuon <https://github.com/zopefoundation/transaction>`_
+
+- `BTrees <https://github.com/zopefoundation/BTrees>`_
+
+- `ZEO (client-server framework) <https://github.com/zopefoundation/ZEO>`_
 
 If you'd like to contribute then we'll gladly accept work on documentation,
 helping out other developers and users at the mailing list, submitting bugs,