[Savannah-cvs] [659] minor updates and fixes

[ineiev]

Revision: 659
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=659
Author:   ineiev
Date:     2023-10-26 14:36:45 -0400 (Thu, 26 Oct 2023)
Log Message:
-----------
minor updates and fixes

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

Modified: trunk/sviki/SavannahHackersCommunication.mdwn
===================================================================
--- trunk/sviki/SavannahHackersCommunication.mdwn       2023-10-26 18:22:58 UTC 
(rev 658)
+++ trunk/sviki/SavannahHackersCommunication.mdwn       2023-10-26 18:36:45 UTC 
(rev 659)
@@ -2,57 +2,48 @@
 -------------
 
 -   Important discussions: As a Savannah Hacker, be sure to read them
-    and be responsive (do not store them in a separate mailbox :)). The
+    and be responsive (do not store them in a separate mailbox.)  The
     lists are also open to non-subscribers, like almost all others.
-    -   savannah-hackers-public@gnu.org
-    -   savannah-hackers-private@gnu.org: immediate security issues
+    -   savannah-hackers-public@gnu.org.
+    -   savannah-hackers-private@gnu.org: immediate security issues.
 
 -   Support requests by Savannah users
     -   savannah-help-public@gnu.org: Really savannah-hackers@gnu.org by 
aliasing.
-        (savannah-hackers was not renamed so that archive urls stay valid.)
-    -   savannah-help-private@gnu.org: user confidential requests only
+        (savannah-hackers was not renamed so that archive URLs stay valid.)
+    -   savannah-help-private@gnu.org: user confidential requests only.
 
--   Project approvals
+-   Group approvals
     -   savannah-register-public@gnu.org: no private list.
 
 -   Reports
     -   savannah-reports-private@gnu.org: cron jobs, system checks and
         other programs' output.
-    -   savannah-cvs@gnu.org: commits, covers our scripts, documentation
-        (including changes on this wiki) and webpages.
-    -   mailman@gnu.org: Mailman cron jobs at lists.gnu.org
+    -   savannah-cvs@gnu.org: changes on this wiki.
+    -   mailman@gnu.org: Mailman cron jobs at lists.gnu.org.
 
--   FSF list
-    -   system-hackers-announce@gnu.org: Announcements of FSF sysadmin
-        issues which may affect Savannah.
-    -   system-hackers@gnu.org: For people interested in helping with
-        the issues announced in the announce list, etc. The point is
-        that both FSF employees and Savannah volunteers can (and do)
-        subscribe to this list. This list is open to GNU maintainers.
-
 -   Non-admin lists
     -   savannah-announce@gnu.org - announcement list. Front page news
-        items are automatically sent here. Check [[SavannahAnnounce]].
+        items are automatically sent here.  Check [[SavannahAnnounce]].
     -   savannah-users@gnu.org: User discussion of using Savannah.
 
 ### Public / private
 
 As a general guideline we use public lists as much as possible
-(searchable archives, transparency...). Private lists are provided for
+(searchable archives, transparency...)  Private lists are provided for
 users who wish to communicate about confidential matters, or when the
-Savannah Hackers need a private discussion (immediate security issue).
+Savannah Hackers need a private discussion (immediate security issue.)
 
 ### Carbon copy
 
 Try to keep the carbon-copy list intact when you reply to emails,
 unless you think this is needed (in which case, explain briefly why and
-who you added/removed from Cc: list) :)
+who you added/removed from Cc: list.)
 
 ### Spam and moderation
 
 Users do not receive notification when their message is being held, so
-as to prevent "backscatter" spam. All non-spam posts are accepted -
-there is no "moderation".
+as to prevent "backscatter" spam.  All non-spam posts are accepted -
+there is no "moderation."
 
 ### Other information
 
@@ -63,7 +54,7 @@
 [[ToDo]]: Check /com/mailer/aliases and clean-up savannah-related stuff,
 including savannah-compromise and savannah-daily-reports
 
-[[ToDo]]: deal with savannah-compromise, an alias of sv-root. We could
+[[ToDo]]: deal with savannah-compromise, an alias of sv-root.  We could
 move it to sv-ha-priv, after checking the archive at fencepost.
 
 ### Aliases
@@ -72,7 +63,7 @@
 savannah.gnu.org and savannah.nongnu.org point to
 savannah-hackers-private.
 
-Useful for, eg. [[CAcert]].org that uses those addresses to reach a
+Useful for, e.g. [[CAcert]].org that uses those addresses to reach a
 domain owner.
 
 IRC
@@ -83,7 +74,7 @@
 
 -   Remember that \#savannah is a public channel and that support
     requests should generally be submitted via our support request
-    system
+    system.
     (<https://savannah.gnu.org/support/?func=additem&group=administration>)
 -   Only a subset of volunteers hang out in the IRC channel.  Treat it
     as opportunistic communication.  The mailing list will reliably
@@ -100,3 +91,10 @@
 
 savannah-root was once used as an alias for root@sv, hosted private
 discussions, and received savannah-compromise. List is now closed.
+
+system-hackers@gnu.org: was an FSF list for people interested
+in helping with the issues that may affect Savannah.  The point is
+that both FSF employees and Savannah volunteers can (and do)
+subscribe to this list.  This list is open to GNU maintainers.
+The archives only show activity in 2010 and a single message
+in 2011.