[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [199] wording
From: |
karl |
Subject: |
[Savannah-cvs] [199] wording |
Date: |
Fri, 8 Jul 2016 23:03:23 +0000 (UTC) |
Revision: 199
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=199
Author: karl
Date: 2016-07-08 23:03:20 +0000 (Fri, 08 Jul 2016)
Log Message:
-----------
wording
Modified Paths:
--------------
trunk/sviki/NotSavannahAdmins.mdwn
Modified: trunk/sviki/NotSavannahAdmins.mdwn
===================================================================
--- trunk/sviki/NotSavannahAdmins.mdwn 2016-07-07 00:10:08 UTC (rev 198)
+++ trunk/sviki/NotSavannahAdmins.mdwn 2016-07-08 23:03:20 UTC (rev 199)
@@ -13,32 +13,31 @@
GNU Project and Official GNU Packages:
--------------------------------------
-Savannah administrators *can not* help with official gnu-related
-matters (e.g. approving a new GNU project, changing project's status from
-gnu to nongnu or vise-versa, approving new co-maintainers or dealing
-with FSF copyright assignments).
+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,
+dealing with FSF copyright assignments, and plenty more.
-* GNU Package maintenance issues (e.g. if you are a GNU package maintainer
+* GNU package maintenance issues (e.g., if you are a GNU package maintainer
and have a question regarding GNU issues): See the "Getting Help"
section in the GNU Maintainers Guide at
<https://www.gnu.org/prep/maintain/maintain.html#Getting-Help>.
-* General GNU related issues: See <https://www.gnu.org/contact/>.
+* General GNU-related issues: See <https://www.gnu.org/contact/>.
Server Issues - Contacting FSF sysadmin:
----------------------------------------
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.
+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
<address@hidden> is ok and can help us keep track of
problems).
-
* FSF outage notifications: <https://pumprock.net/fsfstatus>.
* IRC: `#fsfsys` channel on freenode (<https://webchat.freenode.net/>).
@@ -64,8 +63,8 @@
* 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.)
+ 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
<address@hidden> and package maintainers, server administration by
@@ -85,8 +84,7 @@
* 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.
+ but no access to the hardware.
More information:
-----------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [199] wording,
karl <=