savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [677] minor fixes


From: ineiev
Subject: [Savannah-cvs] [677] minor fixes
Date: Thu, 30 Nov 2023 14:29:20 -0500 (EST)

Revision: 677
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=677
Author:   ineiev
Date:     2023-11-30 14:29:19 -0500 (Thu, 30 Nov 2023)
Log Message:
-----------
minor fixes

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

Modified: trunk/sviki/NotSavannahAdmins.mdwn
===================================================================
--- trunk/sviki/NotSavannahAdmins.mdwn  2023-11-28 08:19:23 UTC (rev 676)
+++ trunk/sviki/NotSavannahAdmins.mdwn  2023-11-30 19:29:19 UTC (rev 677)
@@ -1,9 +1,8 @@
-Services Outside Savannah's Scope
-=================================
+# Services Outside Savannah
 
 GNU Savannah is operated by volunteer admins. Many servers and services
 which are closely related to Savannah's operation are not handled by
-savannah admins.
+Savannah admins.
 
 When a problem arises with these servers or services, it is best to
 contact the relevant party directly: FSF sysadmins for server-related
@@ -10,12 +9,11 @@
 issues and GNU teams for GNU-related issues. See below for details.
 
 
-GNU Project and Official GNU Packages:
---------------------------------------
+## GNU Project and Official GNU Packages
 
 Savannah administrators *cannot* help with official GNU-related matters,
-such as: approving a new GNU package, changing a Savannah project's
-status from gnu to nongnu or vice versa, approving new co-maintainers,
+such as: approving a new GNU package, changing the stasus of a Savannah
+group from gnu to nongnu or vice versa, approving new co-maintainers,
 dealing with FSF copyright assignments, and plenty more.
 
 * GNU package maintenance issues (e.g., if you are a GNU package maintainer
@@ -25,16 +23,14 @@
 
 * General GNU-related issues: See <https://www.gnu.org/contact/>.
 
+## Server Issues - Contacting FSF sysadmin:
 
-Server Issues - Contacting FSF sysadmin:
-----------------------------------------
-
-Many servers and services which are closely related to Savannah's
+Many servers and services which are closely related to Savannah
 operation are maintained by FSF sysadmins, and Savannah volunteers *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
+admins directly (although notifying Savannah admins by CC'ing
 <savannah-hackers-public@gnu.org> is ok and can help us keep track of
 problems).
 
@@ -53,8 +49,7 @@
 * FSF personnel:
   see [FSF Staff and Board](http://www.fsf.org/about/staff-and-board/).
 
-Servers and services:
----------------------
+## Servers and services
 
 * `fencepost.gnu.org` - maintained by FSF sysadmins (including login issues,
   sending/receiving email there, installed packages, etc.). Before
@@ -66,8 +61,8 @@
   limited (non-root) access to mailing lists and archives.  All
   requests for deletion of archived email must go to FSF sysadmin.
 
-* Web pages at <http://www.gnu.org>: content is maintained by
-  <webmasters@gnu.org> and package maintainers, server administration by
+* Web pages at <http://www.gnu.org>: the served files are maintained by
+  <webmasters@gnu.org> and GNU package maintainers, Apache configuration 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
@@ -86,8 +81,7 @@
   hardware; Savannah volunteers have root access to the virtual hosts,
   but no access to the hardware.
 
-More information:
------------------
+## More information
 
 * Savannah/FSF servers: [[SavannahServices]], [[SavannahArchitecture]],
   [[GnuArchitecture]]




reply via email to

[Prev in Thread] Current Thread [Next in Thread]