[Savannah-cvs] [188] more about non-savannah

[karl]

Revision: 188
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=188
Author:   karl
Date:     2016-04-28 22:07:25 +0000 (Thu, 28 Apr 2016)
Log Message:
-----------
more about non-savannah

Modified Paths:
--------------
    trunk/sviki/HomePage.mdwn
    trunk/sviki/NotSavannahAdmins.mdwn

Modified: trunk/sviki/HomePage.mdwn
===================================================================
--- trunk/sviki/HomePage.mdwn   2016-04-28 14:49:48 UTC (rev 187)
+++ trunk/sviki/HomePage.mdwn   2016-04-28 22:07:25 UTC (rev 188)
@@ -7,9 +7,9 @@
 - For gnu projects: gnu.org/software/project/ (shortcut: gnu.org/s/project/)
 - For nongnu projects: www.nongnu.org/project/ and project.nongnu.org/
 
-No symlinks (sysadmin@ says: "security reasons" and "there's also the
-fact that CVS doesn't handle symlinks") - use .symlinks instead. Add a
-file named .symlinks in each directory where you want to make symbolic
+No symlinks (address@hidden says: "security reasons" and "there's also
+the fact that CVS doesn't handle symlinks") - use .symlinks instead. Add
+a file named .symlinks in each directory where you want to make symbolic
 links. Each line of the file lists a real file name followed by the name
 of the symbolic link. The symbolic links are built every hour.
 
@@ -23,11 +23,9 @@
 Using a different VCS
 ---------------------
 Many people have requested using something other than CVS for their web
-page repositories.  This is not unreasonable, but requires substantial
-frontend work, backend work, and coordination with the FSF sysadmins.
-There is no ETA for any of this.  There are far more urgent problems in
-the Savannah infrastructure at present, and nowhere near enough
-volunteer hours to do them.
+page repositories.  This is not unreasonable in principle, but requires
+substantial frontend work, backend work, and coordination with the FSF
+sysadmins.  There is no ETA for any of this.
 
 Meanwhile, perhaps git-over-cvs could be used, but we have no experience
 with this.

Modified: trunk/sviki/NotSavannahAdmins.mdwn
===================================================================
--- trunk/sviki/NotSavannahAdmins.mdwn  2016-04-28 14:49:48 UTC (rev 187)
+++ trunk/sviki/NotSavannahAdmins.mdwn  2016-04-28 22:07:25 UTC (rev 188)
@@ -1,64 +1,76 @@
 Services Outside Savannah's Scope
----------------------------------
+=================================
+GNU Savannah is operated by volunteer admins. Many servers and services
+which are closely related to Savannah's operation are maintained by FSF
+administrators, and Savannah admins *do not have* access to them.
 
-GNU Savannah is operated by volunteer admins. Some servers and services
-which are closely related to savannah's operation are maintained by FSF
-administrators, and savannah admins *do not* have access to them.
+When a problem arises with these servers, it is best to contact FSF
+admins directly (although notifying savannah admins by CC'ing
+<address@hidden> is ok and can help us keep track of
+problems).
 
-When a problem arises with these servers, it is best to contact FSF admins
-directly (although notifying savannah admins by CC'ing
-<address@hidden> will help us keep track of problems).
+Contacting FSF sysadmin:
+------------------------
 
-Contacting FSF sys-admins:
+* FSF outage notifications: <https://pumprock.net/fsfstatus>.
 
-* FSF Services outage notifications: <https://pumprock.net/fsfstatus> .
-
-* IRC: `#fsfsys` channel on freenode (web: <https://webchat.freenode.net/>).
-  FSF sysadmins are `nully` and `quidam`.
+* IRC: `#fsfsys` channel on freenode (<https://webchat.freenode.net/>).
+  FSF sysadmins are currently `nully` and `quidam`.
   John Sullivan (FSF Executive Director) is `johnsu01`
   
(<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00037.html>).
   See also [GNU,FSF IRC Channels](http://www.gnu.org/server/irc-rules.en.html).
 
-* Email: address@hidden, address@hidden Emailing will create a new
-  support ticket. Please try not to burden them unnecessarily - prefer
-  IRC for faster communication.
+* Email: address@hidden, equivalently address@hidden Emailing will
+  create a new support ticket in their queue.  Please try not to burden
+  them unnecessarily; prefer IRC for faster communication.
 
-* FSF Administrators:
-  see [FSF Staff and Board](http://www.fsf.org/about/staff-and-board/)
+* FSF personnel:
+  see [FSF Staff and Board](http://www.fsf.org/about/staff-and-board/).
 
-* Savannah's mailing lists:
-  We (savannah admins) **do not have access** to FSF-resricted services,
-  and will not be able to help directly. However, if you are not recieving
-  responses in the above channels, we might be able to offer advice.
-  create [New Support 
Ticket](https://savannah.gnu.org/support/?func=additem&group=administration),
-  or write to address@hidden .
+Servers and services:
+---------------------
 
+* `fencepost.gnu.org` - maintained by FSF sysadmins (including login issues,
+  sending/receiving email there, installed packages, etc.). Before
+  contacting FSF sysadmins, try writing to address@hidden
+  (https://lists.gnu.org/mailman/listinfo/fencepost-users).
 
+* Mailing lists (`lists.gnu.org`) - the host, mail setup, and Mailman
+  installation are managed by FSF sysadmins.  Savannah hackers have
+  limited (non-system) access to mailing lists and archives.  (All
+  requests for deletion of archived email must go to FSF sysadmin.)
 
-Servers and services:
+* Web pages at <http://www.gnu.org>: content is maintained by
+  <address@hidden> and package maintainers, server administration by
+  FSF sysadmins.  A copy of the live configuration is in
+  `fencepost:/srv/data/www-config/` and a copy of the live server is in
+  `fencepost:/srv/data/www-mirror/`.  Individual package web pages are
+  hosted in Savannah CVS "webpages" repositories (always CVS), but are
+  sync'd to www.gnu.org for the actual serving ([[HomePage]]).
 
-* `fencepost.gnu.org` - maintained by FSF sysadmins (including login issues,
-  sending/receiving @gnu.org emails). Before contacting FSF sysadmins,
-  try writing to address@hidden
-  (https://lists.gnu.org/mailman/listinfo/fencepost-users).
-* Mailing lists (`lists.gnu.org`) - maintined by FSF sysadmins
-* web pages at <http://www.gnu.org>: content is maintained by
-  <address@hidden>, server administration by FSF sysadmins
-  (with exception of individual project's web pages, which are hosted
-   on savannah and are sync'd to www.gnu.org).
-* GNU Bug Tracker (<http://debbugs.gnu.org>) - write to address@hidden
+* `ftp.gnu.org` - the main distribution server for GNU, managed entirely
+  by FSF sysadmin.  Compare with downloads for nongnu.org, which does
+  happen on Savannah [[DownloadArea]].
+
+* GNU Bug Tracker (<http://debbugs.gnu.org>) - managed by other
+  non-Savannah volunteers; write to address@hidden
   (<https://lists.gnu.org/mailman/listinfo/help-debbugs>) for help.
 
+* The Savannah hosts themselves are virtual machines on FSF-managed
+  hardware; Savannah volunteers have root access to the virtual hosts,
+  but no access to the hardware.  So we can do nothing about the
+  recurring resource limitations of bandwidth/cpu/disk.
 
+More information:
+-----------------
 
-Further technical details:
+* Savannah/FSF servers: [[SavannahServices]], [[SavannahArchitecture]],
+  [[GnuArchitecture]]
 
-* Savannah/fsf servers: [[SavannahServices]], [[SavannahArchitecture]],
-  [[GnuArchitecture]]
-* Email: [[MailSystem]] . See also detailed description of mail system
+* Email: [[MailSystem]]. See also detailed description of mail system
   by Bob Proulx:
   
<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00029.html>,
   
<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00036.html>,
   
<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00040.html>.
-* Lists: [[ListServer]]
 
+* Lists: [[ListServer]].