doc: more updates to remove darcs references

Author: ralphlange

documentation/Installation.txt

@@ -22,9 +22,9 @@ should do. Starting with seq-`2.2.6`_, EPICS 7 can be used.
 re2c
 ^^^^
 
-Building the sequencer also requires the lexer generator tool `re2c`_. The
-minimum version required is 0.9.9, but I recommend using the latest version
-that is avaliable for your system. If you are building on a Linux system,
+Building the sequencer also requires the lexer generator tool re2c. The
+minimum version required is 0.9.9, but it is recommend to use the latest
+version avaliable for your system. If you are building on a Linux system,
 you can use the re2c package your distribution provides.
 
 On Windows things are not quite as smooth. The `old re2c download`_ page on
@@ -55,9 +55,8 @@ a new release.
 
 .. note::
 
-  The documentation and download links you will find on this page are for
-  version 2.2.
-
+  The documentation and download links you will find on this page
+  mostly are for version 2.2, which is on GitHub.
 
 Here are all releases for version 2.2:
 
@@ -75,22 +74,10 @@ Here are all releases for version 2.2:
    `2.2.1`_   `Release_Notes_2.2.1`   `Known_Problems_2.2.1`
    ========== ======================= ============================
 
-If you want to help testing, please check out
-the `darcs`_ repository for `branch-2-2`_::
-
-   darcs get https://hub.darcs.net/bf/seq-branch-2-2
-
-Using this git mirror, you can as well ::
+If you want to help testing, please clone ::
 
    git clone https://github.com/epics-modules/sequencer.git
 
-but please note that this is just a mirror: I cannot accept git
-patches or work with GitHub Pull Requests; it may also happen that I have
-to re-create the whole git repo from scratch (because incremental conversion
-sometimes fails).
-
-Development of new features now happens on `branch-2-3`_.
-
 See `Contribute`_ for a short description how to record and send patches.
 
 .. _2.2.9: https://github.com/epics-modules/sequencer/releases/tag/R2-2-9
@@ -184,7 +171,7 @@ The html pages are generated by issuing::
    make html
 
 This will generate the home page and install it into the directory
-``$SEQ/html``. This step requires that you have `Python`_ and `Sphinx`_
+``$SEQ/html``. This step requires that you have Python and Sphinx
 installed on your system.
 
 If, in addition, you want a printable version (pdf), do::
@@ -291,7 +278,7 @@ into your Makefile. Here, ``xyz.st`` is the name of your SNL program, and
 ``abc`` is the name of the library or binary to produce. Note that ``.st``
 files are run through the C preprocessor (`cpp`) before giving them to
 the SNL compiler. Use the extension ``.stt`` to avoid this. For details,
-see the `relevant part in the EPICS Application Developer's Guide
+see the `SNL part of the EPICS Application Developer's Guide
 <https://docs.epics-controls.org/en/latest/build-system/specifications.html#state-notation-programs>`_.
 
 A complete example application that also uses the sequencer can be
@@ -305,64 +292,20 @@ Take a look at ``exApp/src``, especially the ``Makefile``.
 Report Bugs
 -----------
 
-Please send bug reports to to tech-talk@aps.anl.gov or the maintainer
-(currently this is `me <benjamin.franksen@helmholtz-berlin.de>`_). It helps
-if you include which release of the sequencer and EPICS base release
+Please file bug reports in the GitHub `issue tracker`_.
+It helps if you include which release of the sequencer and EPICS base release
 you are using.
 
+.. _issue tracker: https://github.com/epics-modules/sequencer/issues
 
 Contribute
 ----------
 
-I am always happy to receive patches (bug fixes, improvements, whatever).
-For minor changes you don't need to bother with `darcs`_, just send me a
-`patch file`_.
-
-.. _patch file: http://en.wikipedia.org/wiki/Patch_%28Unix%29
-
-For more involved changes you might want to send a `darcs`_ patch. You can
-create a local copy of the `darcs`_ repository (the stable branch in this
-example) by saying::
-
-   darcs get https://hub.darcs.net/bf/seq-branch-2-2
-
-Assuming you have made some changes, first update your repository to
-include the latest changes from upstream (with darcs this is not
-strictly necessary, but good practice as it helps to avoid unnecessary
-conflicts)::
-
-   darcs pull
-
-(darcs will ask you for each patch that is not yet in your repo). Then
-record your changes (if you haven't already)::
-
-   darcs record
-
-(darcs will prompt you for every single change you made and then prompt
-you for giving the patch a name). Finally say::
-
-   darcs send
-
-A word of caution: it may happen that I `darcs obliterate`_ patches in
-the experimental branch. If `darcs send`_ asks whether to include patches
-that you don't have authored, this is probably what happened. In that case
-can (but you need not necessarily) quit and obliterate them in your source
-tree, too, before trying to `darcs send`_ again.
+Please prepare improvements and fixes as Pull Requests.
 
-Please respect the coding style when making changes. This includes
+Respect the coding style when making changes. This includes
 indentation (tabs or spaces, how many) and all the other little things
 on which programmers like to differ ;-) like placement of braces etc.
-Note that for historical reasons the style differs somewhat between
-files and subdirectories. It is much easier for me to review patches if
-they do not contain gratuitous changes or combine several unrelated
-changes in a single patch.
-
-Also, please take care that your patch does not accidentally contain
-site-specific changes (typically done in configure). For my own work, I
-usually record such changes with a description that contains 'DONT SEND
-THIS' or something similar, so I don't accidentally record them together
-with other changes.
-
-.. _darcs: http://darcs.net/
-.. _darcs obliterate: http://darcs.net/manual/bigpage.html#SECTION00694000000000000000
-.. _darcs send: http://darcs.net/manual/bigpage.html#SECTION00664000000000000000
+To make review easier, please avoid whitespace changes
+(or keep them in a separate commit)
+and do not combine several unrelated changes in a single commit.

documentation/templates/home.html

@@ -6,17 +6,12 @@ <h3>{{ 'Main Topics' }}</h3>
 <li>Manual (<a href="{{ pathto('Manual.html', 1) }}">html</a>,
     <a href="{{ pathto('Manual.pdf', 1) }}">pdf</a>)</li>
 </ul>
-<h3>{{ 'Other Versions' }}</h3>
-<ul class="topless">
-<li><a href="{{ pathto('../sequencer-2-1/index.html', 1) }}">Version 2.1</a></li>
-</ul>
 <h3>{{ 'Sources' }}</h3>
 <ul class="topless">
-<li><a href="https://github.com/epics-modules/sequencer/">{{ 'This Git mirror (GitHub)' }}</a></li>
-<li><a href="https://hub.darcs.net/bf/seq-branch-2-2/">{{ 'Upstream darcs mirror (darcs hub)' }}</a></li>
+<li><a href="https://github.com/epics-modules/sequencer/">{{ 'This Git repository (GitHub)' }}</a></li>
 </ul>
 <h3>{{ 'Related' }}</h3>
 <ul class="topless">
 <li><a href="https://epics-controls.org/">{{ 'EPICS' }}</a></li>
-<li><a href="https://epics.anl.gov/base/R3-14/12-docs/CAref.html">{{ 'Channel Access' }}</a></li>
+<li><a href="https://docs.epics-controls.org/en/latest/ca-ref/introduction.html">{{ 'Channel Access' }}</a></li>
 </ul>