[Savannah-cvs] [566] minor updates, cosmetics

[ineiev]

Revision: 566
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=566
Author:   ineiev
Date:     2023-02-09 04:14:00 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
minor updates, cosmetics

Modified Paths:
--------------
    trunk/sviki/SavannahServices.mdwn

Modified: trunk/sviki/SavannahServices.mdwn
===================================================================
--- trunk/sviki/SavannahServices.mdwn   2023-02-09 09:11:30 UTC (rev 565)
+++ trunk/sviki/SavannahServices.mdwn   2023-02-09 09:14:00 UTC (rev 566)
@@ -38,7 +38,7 @@
 - PHP code runs defined in `frontend0:/etc/apache2/sites-available/sv.inc`,
   stored in `frontend0:/var/www/savane/frontend/php/`.
 
-- PHP source code: <https://savannah.gnu.org/projects/administration>
+- [PHP source code](//savannah.nongnu.org/projects/administration)
 
 
 ## vcs0
@@ -53,23 +53,23 @@
 completely in due course.)
 
 
-### vcs - project member access (commits)
+### vcs - group member access (commits)
 
 - ssh: used for read/write access to the repositories by members
-    of a project.  Before using ssh, the Savannah user must upload a
+    of a group.  Before using ssh, the Savannah user must upload a
     public ssh key through the Savannah web interface. Upon attempted
     login, this user key is checked against the Savannah MySQL database,
     using the `AuthorizedKeysExec` command defined in
     `vcs0:/etc/ssh/sshd_config`.  The user must also be a member of the
-    given project.
+    given group.
 
     The repositories' access methods are:
-    - bzr: `bzr branch 
bzr+ssh://<USER>@bzr.savannah.nongnu.org/<PROJECT>/branch`
-    - cvs: `cvs -d:ext:<USER>@cvs.savannah.nongnu.org:/sources/<PROJECT> co 
<modulename>`
-    - git: `git clone <USER>@git.savannah.gnu.org:/srv/git/<PROJECT>.git`
-    - hg:  `hg clone ssh://<USER>@hg.savannah.gnu.org/<PROJECT>`
-    - svn: `svn co 
svn+ssh://<USER>@svn.savannah.gnu.org/<PROJECT>/<modulename>`
-    - webcvs: `cvs -d:ext:<USER>@cvs.savannah.nongnu.org:/web/<PROJECT> co 
<PROJECT>`
+    - bzr: `bzr branch bzr+ssh://<USER>@bzr.savannah.nongnu.org/<GROUP>/branch`
+    - cvs: `cvs -d:ext:<USER>@cvs.savannah.nongnu.org:/sources/<GROUP> co 
<modulename>`
+    - git: `git clone <USER>@git.savannah.gnu.org:/srv/git/<GROUP>.git`
+    - hg:  `hg clone ssh://<USER>@hg.savannah.gnu.org/<GROUP>`
+    - svn: `svn co svn+ssh://<USER>@svn.savannah.gnu.org/<GROUP>/<modulename>`
+    - webcvs: `cvs -d:ext:<USER>@cvs.savannah.nongnu.org:/web/<GROUP> co 
<GROUP>`
 
 ### vcs - public anonymous access (read-only)
 
@@ -76,12 +76,12 @@
 - rsync - read-only anonymous access to the raw repository files.
     configuration in `vcs0:/etc/rsync.conf`, started with `xinetd` in
     `vcs0:/etc/xinetd.d/rsync`.
-    - bzr: `rsync://bzr.savannah.gnu.org/bzr/<PROJECT>`
-    - cvs: `rsync://cvs.savannah.gnu.org/sources/<PROJECT>`
-    - git: `rsync://svn.savannah.gnu.org/git/<PROJECT>`
+    - bzr: `rsync://bzr.savannah.gnu.org/bzr/<GROUP>`
+    - cvs: `rsync://cvs.savannah.gnu.org/sources/<GROUP>`
+    - git: `rsync://svn.savannah.gnu.org/git/<GROUP>`
     - hg:  not defined.
-    - svn: `rsync://svn.savannah.gnu.org/svn/<PROJECT>`
-    - webcvs: `rsync://web.cvs.savannah.gnu.org/web/<PROJECT>`
+    - svn: `rsync://svn.savannah.gnu.org/svn/<GROUP>`
+    - webcvs: `rsync://web.cvs.savannah.gnu.org/web/<GROUP>`
 
 - bzr-daemon - read-only anonymous access to bzr repositories.
     configured with `xinetd` in `vcs0:/etc/xinetd.d/bzr-hpss`.
@@ -89,12 +89,12 @@
 
 - cvs-pserver - read-only anonymous access to cvs repositories.
     configured with `xinetd` in `vcs0:/etc/xinetd.d/cvs`.
-    - cvs: `cvs 
-d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/<PROJECT> co <modulename>`
-    - webcvs: `cvs -d:pserver:anonymous@cvs.savannah.nongnu.org:/web/<PROJECT> 
co <modulename>`
+    - cvs: `cvs -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/<GROUP> 
co <modulename>`
+    - webcvs: `cvs -d:pserver:anonymous@cvs.savannah.nongnu.org:/web/<GROUP> 
co <modulename>`
 
 - git-daemon - read-only anonymous access to git repositories.
     configured with `xinetd` in `vcs0:/etc/xinetd.d/git`.
-    - git: `git clone git://git.savannah.gnu.org/<PROJECT>.git`
+    - git: `git clone git://git.savannah.gnu.org/<GROUP>.git`
 
 - hg - not defined.
 
@@ -147,11 +147,11 @@
 
 The `download.savannah.gnu.org` hosts the following:
 
-* The 'downloads' (aka 'releases') for projects hosted on GNU Sanannah.
-* The content of <https://audio-video.gnu.org>
+* The 'downloads' (aka 'releases') for software hosted on GNU Sanannah.
+* The records from [audio-video.gnu.org](//audio-video.gnu.org)
 * The (old, obsolete) GNU Arch repositories
 
-See [[Mirmon]] for more information about the auto-redirection mentioned
+See [[Mirroring]] for more information about the auto-redirection mentioned
 below.
 
 Configuration details:
@@ -164,10 +164,10 @@
     - uses `Apache2::Geo::Mirror` to redirect based on GeoIP.
 
 - Savannah-hosted downloads/releases:
-  These are mostly intended for nongnu projects, as GNU
-  projects are expected to put releases on `ftp.gnu.org`, as detailed in
-  the GNU Maintainer Information
-  <https://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html>.
+  These are mostly intended for nongnu software, as GNU packages
+  are expected to put releases on `ftp.gnu.org`, as detailed in
+  the [GNU Maintainer
+  
Information](//www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html).
     - web access: <https://download.savannah.gnu.org/releases/>,
     - Apache conf: `download0:/etc/apache2/sites-available/download`
     - disk location: `download0:/srv/download/`
@@ -183,7 +183,7 @@
     - Apache conf: `download0:/etc/apache2/sites-available/download`
 
 - GNU audio-video host:
-    - web access: <https://audio-video.gnu.org>, <https://audio-video.gnu.org>
+    - [web access](//audio-video.gnu.org)
     - http Apache conf: `download0:/etc/apache2/sites-available/audio-video`
     - https Apache conf: 
`download0:/etc/apache2/sites-available/audio-video-ssl`
 
@@ -204,16 +204,16 @@
          - `releases` mapped to `download0:/srv/download`.
          - `audio-video` mapped to `download0:/srv/audio-video`.
     - Anonymous access using rsync protcol:
-      `rsync -avhP rsync://download.savannah.gnu.org/releases/<PROJECT>/<FILE> 
 LOCALFILE`
-    - Listing content of a directory:
-      `rsync rsync://download.savannah.gnu.org/releases/<PROJECT>/`
+      `rsync -avhP rsync://download.savannah.gnu.org/releases/<GROUP>/<FILE>  
LOCALFILE`
+    - Listing directory:
+      `rsync rsync://download.savannah.gnu.org/releases/<GROUP>/`
     - All Savannah members can access rsync services, using the ssh public
       key configured on Savannah website (see ssh section of VCS server,
       above).
     - Download a file using ssh public key + Savannah User:
-      `rsync -avhP <USER>@download.savannah.gnu.org:/releases/<PROJECT>/<FILE> 
LOCALFILE`
-    - Uploading a file (only to projects in which USER is a member):
-      `rsync -avhP LOCALFILE  
<USER>@download.savannah.gnu.org/srv/download/<PROJECT>/<FILE>`
+      `rsync -avhP <USER>@download.savannah.gnu.org:/releases/<GROUP>/<FILE> 
LOCALFILE`
+    - Uploading a file (only to groups in which USER is a member):
+      `rsync -avhP LOCALFILE  
<USER>@download.savannah.gnu.org/srv/download/<GROUP>/<FILE>`
 
 - sftp access
     - `sftp <USER>@download.savannah.gnu.org`
@@ -227,7 +227,7 @@
     * Used in two contexts:
         1. The database for the Savannah PHP code (based on old SourceForge
            code base). These are the registered users on Savannah, registered
-           projects, trackers (tasks, bugs, etc.), etc.
+           groups, trackers (tasks, bugs, etc.), etc.
            Users upload their public ssh keys to Savannah web interface,
            and those are also stored in the database.
         2. All VMs which allow ssh access based on public ssh keys connect to
@@ -251,7 +251,8 @@
   `lists.libreplanet.org` and few other FSF-related sites.
 
 * One mailman installation handles all of the above domains (see
-  
[here](https://lists.gnu.org/archive/html/savannah-users/2015-09/msg00009.html)).
+  [message in savannah-users
+  archive](//lists.gnu.org/archive/html/savannah-users/2015-09/msg00009.html)).
 
 * web access:
     - multiple configuration files in `lists:/etc/apache2/sites-enabled`
@@ -265,7 +266,7 @@
             - `https://lists.gnu.org/archive/cgi-bin/namazu.cgi` pointing to
             - `lists:/home/mharc/cgi-bin/namazu.cgi` symlink to
             - `lists:/usr/lib/cgi-bin/namazu.cgi`.
-    - [GNU Mailman](https://www.gnu.org/software/mailman/) manages mailing list
+    - [GNU Mailman](//www.gnu.org/software/mailman/) manages mailing list
       activities (subscriptions, moderation, etc.)
         - http alias <https://lists.gnu.org/mailman/> points to
           `lists:/var/lib/mailman/cgi-bin/`.
@@ -280,11 +281,11 @@
     - To download full archive of one mailing list:  
       `rsync -avhP rsync://lists.gnu.org/mbox/bug-texinfo .`
 
-Spam handling is a whole subject in itself: [[ListHelperAntiSpam]].
+[[Spam handling|ListHelperAntiSpam]] is a whole subject in itself.
 
-`lists.gnu.org` is administered by FSF admins, not by savannah hackers,
-though savannah hackers have non-root access to the machine.
-See [[ListServer]] for more about mailing-list management.
+`lists.gnu.org` is administered by FSF admins, not by Savannah hackers,
+though Savannah hackers have non-root access to the machine.
+See [[ListServer]] for more about mailing list management.
 
 ## mgt - management
 
@@ -302,7 +303,7 @@
     * The server does *not* answer DNS queries directly. Instead, it propagates
       its DNS configuration to `ns1.gnu.org`, and only answers queries from
       `ns1.gnu.org` (enforced with `iptables` rules).
-    * More about DNS: [[DNS]].
+    * [More about DNS](DNS).
 
 --moretowrite--
 The `mgt0.savannah.gnu.org` VM runs munin, and what else?  Provides access