Ensure links are appropriate to Jython (index to section 3).

Check and fix hyperlinks so the reader is not carried into material
specific to CPython while navigating. Also fix up content at the
destination sections, where reasonably easy to do.

Author: jeff5

buildbots_jy.rst

@@ -34,12 +34,13 @@ and how various kinds of failures can be explained and diagnosed.
 Checking results of automatic builds
 ------------------------------------
 
-The way to view recent build results is ...
+The way to view recent build results is to go to the list of commits on GitHub
+and click on the little red cross (or whatever the symbol is when a build
+passes). In a PR-based process, the PR page itself contains a panel which shows
+what tests would pass or fail if the PR were merged.
 
-
-When several changesets are pushed in a quick succession in the same
-branch, it often happens that a single build is scheduled for all these
-changesets.
+When several changes are committed in a quick succession in the same
+branch, it often happens that only the latest is tested.
 
 
 Stability

communication.rst

@@ -6,30 +6,32 @@
 Following Python's Development
 ==============================
 
-.. warning:: At present, this is not much modified from the CPython base.
-
 Python's development is communicated through a myriad of ways, mostly through
 mailing lists, but also other forms.
+These are all relevant to Jython (even sometimes the content specific to C),
+and Jython has some dedicated channels too.
 
 .. _mailinglists:
 
-Mailing Lists
--------------
+Jython Mailing Lists
+--------------------
+
+The mailing list for discussion of Jython's development is jython-dev_.
+The list is open to the public and the Jython core developers subscribe,
+along with others interested in Jython's development.
 
-The primary mailing list for discussion of Jython's development is jython-dev_.
-The list is open to the public and all core developers subscribe,
-and others interested in Jython's development.
-Technical support questions should not be asked here but on jython-users_.
+Questions about using Jython should not be asked here but on jython-users_.
 
 Jython-checkins_ sends out an email for every commit to Jython's various
-repositories from http://hg.python.org. All core developers
-subscribe to this list and are known to reply to these emails to make comments
-about various issues they catch in the commit.
+repositories from http://hg.python.org.
+All core developers subscribe to this list.
 There is a mailing list related to issues on the `Jython issue tracker`_.
 Subscribe to jython-bugs_ if you want  an email for all changes made to any
 issue.
 
-Developers working on Jython will be interested in the developement of Python
+Python and CPython Mailing Lists
+--------------------------------
+Developers working on Jython will be interested in the development of Python
 (the language) and its reference implementation.
 
 python-dev_ is the primary mailing list for discussions about Python's

fixingissues.rst

@@ -27,6 +27,6 @@ discussion to help bring it to a close). Regardless of why the issue is open,
 you can also always provide useful comments if you do attempt a fix, successful
 or not.
 
-.. _"easy" issues: https://bugs.python.org/issue?status=1&@sort=-activity&@dispname=Easy%20issues&@startwith=0&@filter=&@group=priority&@columns=id,activity,title,creator,status&keywords=6&@action=search&@pagesize=50
+.. _"easy" issues: https://bugs.jython.org/issue?status=1&@sort=-activity&@dispname=Easy%20issues&@startwith=0&@filter=&@group=priority&@columns=id,activity,title,creator,status&keywords=6&@action=search&@pagesize=50
 
 .. TODO: add something about no active core developer for the area?

gitbootcamp.rst

@@ -83,8 +83,7 @@ Enabling ``autocrlf`` on Windows
 
 The *autocrlf* option will fix automatically any Windows-specific line endings.
 This should be enabled on Windows, since the public repository has a hook which
-will reject all changesets having the wrong line endings.
-:::::::::::::::::::::::::::::::::::::::::::::::::::::::::
+will reject all changesets having the wrong line endings::
 
     $ git config --global core.autocrlf input
 

help.rst

@@ -6,8 +6,6 @@
 Where to Get Help
 =================
 
-.. warning:: At present, this is not much modified from the CPython base.
-
 If you are working on Jython it is very possible you will come across an issue
 where you need some assistance to solve it (this happens to core developers
 all the time).
@@ -37,15 +35,17 @@ If you are interested in improving Jython and contributing to its development,
 but don’t yet feel entirely comfortable with the public channels mentioned
 above, `Python Mentors`_ are here to help you.  The Python Mentors list was
 originally created to help with CPython development, but since Jython shares
-most of the same infrastructure (Jython is hosted on python.org a Mercurial
-repository and a Roundup issue tracker) it is a good place to find help for
+most of the same infrastructure (Jython's repository is at hg.python.org
+and uses a related Roundup issue tracker) it is a good place to find help for
 Jython as well. Python is fortunate to have a community of volunteer core
 developers willing to mentor anyone wishing to contribute code, work on bug
 fixes or improve documentation.  Everyone is welcomed and encouraged to
 contribute.
 
 .. _Python Mentors: http://pythonmentors.com
 
+.. FIXME: would Python Mentors count themselves a good place to go fro Jython?
+
 Mailing Lists
 -------------
 

index.rst

@@ -1,9 +1,8 @@
-.. This file has been modified from the CPython version.
-   Modifications are extensive, and normally this would mean we should write a
-   new file index_jy.rst, but the expectation is that index.rst is the starting
-   point for the documentation.
-   We therefore keep it as modified, although merging from the CPython devguide
-   is more difficult this way.
+.. This file has been extensively modified from the CPython version.
+   Normally this would mean a new file index_jy.rst, but index.rst is the
+   starting point for the documentation.
+   We therefore keep it as modified, although merging changes from the CPython
+   devguide difficult for this file.
 
 ========================
 Jython Developer's Guide
@@ -16,14 +15,13 @@ bear in mind that:
 
 *  The CPython process is PR-based on GitHub and this guide anticipates our
    adoption of that for Jython.
-*  The existing Jython process uses Mercurial hosted at ``python.org``, and
-   patches via the bug-tracker: you will find that in this guide too.
-*  When the guide says "Python", that section is true for Jython too.
+*  The existing Jython process uses Mercurial so the guide describes that too.
+*  Statements about "Python" should apply to both CPython and Jython.
 *  The adaptation is imperfect: parts of the guide will say (or mean) CPython.
 
 This guide is :ref:`maintained <helping-with-the-developers-guide>` by the same
 community that maintains CPython and Jython.
-We welcome your contributions to both these implementations of Python!
+We welcome your contributions to either implementation of Python!
 
 
 Quick Reference
@@ -32,11 +30,11 @@ Quick Reference
 Mercurial
 ^^^^^^^^^
 
-1. :ref:`Get the source code <checkout>`::
+1. :ref:`Get the source code <checkout-jy>`::
 
       hg clone http://hg.python.org/jython
 
-2. :ref:`Build Jython <compiling>`::
+2. :ref:`Build Jython <compiling-jy>`::
 
       ant
 
@@ -178,11 +176,12 @@ Contributing
 ------------
 
 We encourage everyone to contribute to Python and that's why we have put up this
-We encourage everyone to contribute to Jython and that's why we have put up this
 developer's guide.  If you still have questions after reviewing the material in
 this guide, then the `Python Mentors`_ group is available to help guide new
 contributors through the process.
 
+.. FIXME: do Python Mentors help Jython contributors with process?
+
 A number of individuals from the Python community have contributed to a series
 of excellent guides at `Open Source Guides <https://opensource.guide/>`_.
 
@@ -193,17 +192,17 @@ Core developers and contributors alike will find the following guides useful:
 
 Guide for contributing to Jython:
 
-* :doc:`setup`
+* :doc:`setup_jy`
 * :doc:`help`
-* :doc:`pullrequest`
-* :doc:`patch_hg_jy`
+* :doc:`patch_hg_jy` (existing process)
+* :doc:`pullrequest` (partly usable future process)
 * :doc:`runtests`
 * Beginner tasks to become familiar with the development process
     * :doc:`docquality`
     * :doc:`coverage`
 * Advanced tasks for once you are comfortable
     * :doc:`silencewarnings`
-    * Fixing issues found by the :doc:`buildbots <buildbots>`
+    * Fixing issues found by the :doc:`buildbots <buildbots_jy>`
     * :doc:`fixingissues`
 * :ref:`tracker` and :ref:`helptriage`
     * :doc:`triaging`
@@ -213,8 +212,7 @@ Guide for contributing to Jython:
     * :doc:`committing`
     * :doc:`committing_hg_jy`
     * :doc:`devcycle`
-    * :doc:`buildbots`
-    * :doc:`coverity`
+    * :doc:`buildbots_jy`
 * :doc:`gitbootcamp`
 
 It is **recommended** that the above documents be read in the order listed.  You
@@ -245,8 +243,8 @@ happen and that process is also described as part of this guide:
 Other Interpreter Implementations
 ---------------------------------
 
-This guide is specifically for contributing to Python on the JVM,
-also known as Jython. (While most of the standard library is written in Python,
+This guide is specifically for contributing to Jython, that is,
+Python on the JVM. (While most of the standard library is written in Python,
 the interpreter core is written in Java and integrates most easily with the Java
 SE and EE ecosystems).
 
@@ -276,8 +274,8 @@ Key Resources
       tracker for the issue tracker)
     * :doc:`experts`
 * Source code
-    * `Browse online <http://hg.python.org/jython/file/default/>`_
-      <https://github.com/jython/jython/>`_
+    * `Browse in Mercurial online <http://hg.python.org/jython/file/default/>`_
+    * `Browse in GitHub <https://github.com/jython/jython/>`_
 
 * PEPs_ (Python Enhancement Proposals)
 * :doc:`help`
@@ -294,7 +292,6 @@ Additional Resources
     * :doc:`grammar_jy`
     * :doc:`compiler_jy`
 * Tool support
-    * Various tools with configuration files as found in the `Misc directory`_
     * Information about editors and their configurations can be found in the
       `wiki <https://wiki.python.org/moin/PythonEditors>`_
 
@@ -350,8 +347,8 @@ Specific to CPython_
 --------------------
 
 These are sections from the CPython guide, retained for reference.
-A comparison with the CPython implementation of a feature can help you
-understand the Jython one.
+A comparison with the CPython implementation of a feature will sometimes help
+you understand the Jython one.
 
 .. We're also keeping these files for the technical reason that changes from
    CPython upstream can only be merged if these CPython files continue to exist.

patch_hg_jy.rst

@@ -54,8 +54,9 @@ When creating a patch for submission, there are several things that you should
 do to help ensure that your patch is accepted.
 
 First, make sure to follow Python's style guidelines. For Python code you
-should follow :PEP:`8`, and for Java code you should follow the
-`Style Guide for Java code`_. If you have one or two discrepancies those can be
+should follow :PEP:`8`, and for Java code you should follow Jython's
+`Java coding standard <https://wiki.python.org/jython/CodingStandards>`_.
+If you have one or two discrepancies those can be
 fixed by the core developer who commits your patch. But if you have systematic
 deviations from the style guides your patch will be put on hold until you fix
 the formatting issues.

runtests.rst

@@ -12,7 +12,6 @@ Running & Writing Tests
 .. note::
 
     This document assumes you are working from an
-    :ref:`in-development <indevbranch>` checkout of Python. If you
     :ref:`in-development <indevbranch>` checkout of Jython. If you
     are not then some things presented here may not work as they may depend
     on new features not available in earlier versions of Jython.