Generalize copyright headers in files

[mudpy.git] / doc / source / coder.rst

diff --git a/doc/source/coder.rst b/doc/source/coder.rst
index 80edcf8..0487cb8 100644 (file)
--- a/doc/source/coder.rst
+++ b/doc/source/coder.rst
@@ -2,10 +2,9 @@
  coder guide
 =============
 
-.. Copyright (c) 2004-2018 Jeremy Stanley <fungi@yuggoth.org>.
-   Permission to use, copy, modify, and distribute this software is
-   granted under terms provided in the LICENSE file distributed with
-   this software.
+.. Copyright (c) 2004-2018 mudpy authors. Permission to use, copy,
+   modify, and distribute this software is granted under terms
+   provided in the LICENSE file distributed with this software.
 
 This guide attempts to embody a rudimentary set of rules for developer
 submissions of source code and documentation targeted for inclusion
@@ -21,24 +20,19 @@ documented, and contributions to that end are heartily welcomed.
 version control system
 ~~~~~~~~~~~~~~~~~~~~~~
 
-Git_ is used for version control on the project, and the archive can be
-cloned anonymously from http://mudpy.org/git/mudpy if desired. For now,
-detailed commits can be E-mailed to fungi@yuggoth.org, but there will
-most likely be a developer mailing list for more open presentation and
-discussion of patches soon.
+Git_ is used for version control on the project, and the archive can
+be browsed or cloned anonymously from https://mudpy.org/code/mudpy .
+For now, detailed commits can be E-mailed to fungi@yuggoth.org, but
+there will most likely be a developer mailing list for more open
+presentation and discussion of patches soon.
 
-A Gitweb_ interface is available, to make the change history easier to
-browse. This is found at http://mudpy.org/gitweb/mudpy/ and should be
-fairly self-explanatory.
+A :file:`ChangeLog` is generated automatically from repository
+commit logs, and is included automatically in all sdist_ tarballs. It
+can be regenerated easily by running :command:`tox -e dist` from the
+top level directory of the Git repository in a working `developer
+environment`_.
 
-A ChangeLog file is generated automatically from repository commit
-logs, and is included automatically in all sdist_ tarballs. It can
-be regenerated easily by running `tox -e venv python setup.py sdist`
-from the top level directory of the Git repository in a working
-`developer environment`_.
-
-.. _Git: http://git-scm.com/
-.. _Gitweb: http://git.wiki.kernel.org/index.php/Gitweb
+.. _Git: https://git-scm.com/
 .. _sdist: https://packaging.python.org/glossary
            /#term-source-distribution-or-sdist
 
@@ -47,12 +41,11 @@ developer environment
 
 Basic developer requirements are a POSIX Unix derivative (such as
 Linux), a modern Python 3 interpreter (any of the minor revisions
-mentioned in the ``metadata.classifier`` section of setup.cfg_) and
-a recent release of the tox_ utility (at least the
-``tox.minversion`` mentioned in tox.ini_).
+mentioned in the ``metadata.classifier`` section of
+:file:`setup.cfg`) and a recent release of the tox_ utility (at least
+the ``tox.minversion`` mentioned in :file:`tox.ini`).
 
-.. _setup.cfg: http://mudpy.org/gitweb?p=mudpy.git;a=blob;f=setup.cfg
-.. _tox.ini: http://mudpy.org/gitweb?p=mudpy.git;a=blob;f=tox.ini
+.. _tox: https://tox.readthedocs.io/
 
 application program interface
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -82,5 +75,5 @@ as part of mudpy should serve as a suitable reference. Testing of all
 new patches with the flake8_ utility should be performed with ``tox
 -e flake8`` to ensure adherence to preferred style conventions.
 
-.. _Style Guide: http://www.python.org/dev/peps/pep-0008/
-.. _flake8: https://pypi.python.org/pypi/flake8
+.. _Style Guide: :pep:`0008`
+.. _flake8: https://pypi.org/project/flake8