[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [138] Internals wording, etc.
|
From: |
karl |
|
Subject: |
[Savannah-cvs] [138] Internals wording, etc. |
|
Date: |
Sat, 14 Feb 2015 17:03:16 +0000 |
Revision: 138
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=138
Author: karl
Date: 2015-02-14 17:03:06 +0000 (Sat, 14 Feb 2015)
Log Message:
-----------
Internals wording, etc.
Modified Paths:
--------------
trunk/sviki/ApprovingSubmission.mdwn
trunk/sviki/DownloadArea.mdwn
trunk/sviki/FrontPage.mdwn
trunk/sviki/SavannahInternals.mdwn
trunk/sviki/SavannahTeam.mdwn
Modified: trunk/sviki/ApprovingSubmission.mdwn
===================================================================
--- trunk/sviki/ApprovingSubmission.mdwn 2015-02-14 04:17:55 UTC (rev
137)
+++ trunk/sviki/ApprovingSubmission.mdwn 2015-02-14 17:03:06 UTC (rev
138)
@@ -1,3 +1,10 @@
+Approving project submissions
+=============================
+
+Of course, do not approve the project unless it actually meets our
+[requirements] (http://savannah.gnu.org/register/requirements.php); more
+details at [[HowToGetYourProjectApprovedQuickly]].
+
As Savannah superuser, that is, do "become superuser" (in the main left
hand menu bar) in the web interface:
@@ -6,9 +13,9 @@
- check the project name, group type, license. To be an official GNU
project it *must* be listed in
fencepost.gnu.org:/gd/gnuorg/maintainers; otherwise, the project
- must be evaluated first per http://www.gnu.org/help/evaluation.html.
- Or it can be evaluated and approved as a non-GNU project; usually
- submitters choose "official GNU" by mistake, please discuss with them.
+ must be evaluated first per <http://www.gnu.org/help/evaluation.html>.
+ Or it can be evaluated and approved as a non-GNU project; often
+ submitters choose "official GNU" by mistake, so please discuss with them.
- if all is ok, set the status to 'Active' and save (click the
'Update' button) if necessary. Do this before any of the following
steps.
@@ -18,12 +25,8 @@
closed, assign it to yourself, and write a comment (which will be
seen by the OP).
-Following that it will take approximately one hour for the cron jobs to
-run and the project to be fully populated (for the sake of, e.g.,
-[[ImportingCVSRepository]]): make groups in the database-based accounts
-system, replicate the groups to Savannah hosts, create
+Following that it will unfortunately take up to one hour for the cron
+jobs to run and the project to be fully populated (for the sake of,
+e.g., [[ImportingCVSRepository]]): make groups in the database-based
+accounts system, replicate the groups to Savannah hosts, create
repositories on vcs, etc.
-
-Of course, do not approve the project unless it actually meets our
-requirements. These are spelled out at
-[[HowToGetYourProjectApprovedQuickly]].
Modified: trunk/sviki/DownloadArea.mdwn
===================================================================
--- trunk/sviki/DownloadArea.mdwn 2015-02-14 04:17:55 UTC (rev 137)
+++ trunk/sviki/DownloadArea.mdwn 2015-02-14 17:03:06 UTC (rev 138)
@@ -124,4 +124,4 @@
2) on dl.sv.gnu.org, add the mirror url(s) to 2a)
`/srv/download/00_MIRRORS.html` (alphabetical, check
<http://download.savannah.gnu.org/releases-noredirect/00_MIRRORS.html>)
-and 2b) `/srv/download/00_MIRRORS.txt` (no order).
+and 2b) `
Modified: trunk/sviki/FrontPage.mdwn
===================================================================
--- trunk/sviki/FrontPage.mdwn 2015-02-14 04:17:55 UTC (rev 137)
+++ trunk/sviki/FrontPage.mdwn 2015-02-14 17:03:06 UTC (rev 138)
@@ -48,8 +48,8 @@
- [[SavannahURLShortcuts]]
- [[WhyLogin]]
-- [[HowToAdminThisWiki]]
- [[CommonTasks]]
+ - [[HowToAdminThisWiki]]
- [[Accounts]]
- [[DeletingUserAccount]]
- [[ImpersonatingSomebody]]
@@ -61,7 +61,6 @@
- [[ListHelperAntiSpam]]
- [[ResetListPassword]]
- [[SavannahAnnounce]]
- - [[MySQL]]
- [[Projects]]
- [[ChangingLicense]]
@@ -107,7 +106,9 @@
- [[UpstreamCollaboration]]
- [[WhyLegalChecksBeforeRelease]]
-- [[SavannahArchitecture]]
+- [[SavannahArchitecture]
+ - [[SavannahInternals]]
+ - [[SavannahServices]]
- [[AudioVideo]]
- [[Backup]]
- [[Bzr]]
@@ -115,12 +116,6 @@
- [[Compromise2010]]
- [[CvS]]
- [[SynchronizedExternalRepositories]]
- - [[LockDir]]
- - [[ViewVC]]
- - [[ViewCVS]]
- - [[CVSup]]
- - [[ArX]]
- - CVSFAQs
- [[AccessToCVSROOT]]
- [[CvsAnonymous]]
- [[CvsFromBehindFirewall]]
@@ -133,12 +128,14 @@
- [[DataExport]]
- [[FrontEnd]]
+
- [[GNUArch]]
- [[Git]]
- [[UsingGit]]
- [[CvsDisabling]]
+
- [[GnuArchitecture]]
- Mercurial
- [[Hg]]
@@ -169,8 +166,6 @@
- [[DNS]]
- [[Mirmon]]
- - [[GeoIP]]
-
- [[Nagios]]
- [[RunningSavaneLocally]]
- [[SavaneInABox]]
Modified: trunk/sviki/SavannahInternals.mdwn
===================================================================
--- trunk/sviki/SavannahInternals.mdwn 2015-02-14 04:17:55 UTC (rev 137)
+++ trunk/sviki/SavannahInternals.mdwn 2015-02-14 17:03:06 UTC (rev 138)
@@ -1,71 +1,68 @@
Savannah Internals
==================
-This page describes the inner-working of the GNU Savannah platform
+This page describes inner workings of the GNU Savannah platform
(web frontend + backend processes).
-**NOTE on terminology**
+**Some terminology**
* '*GNU Savannah*' (or just '*Savannah*') is the name of the entire platform,
- encompasing the various VMs (see [[SavannahArchitecture]]), services (see
+ encompassing the various hosts (see [[SavannahArchitecture]]), services (see
[[SavannahServices]]), people (see [[SavannahTeam]]) and other odds and ends.
-* '*Savane*' (French for 'savannah') is the code-name for the source code
+
+* '*Savane*' (French for 'savannah') is the code name for the source code
which runs many parts of the savannah platform (most notably: the web
frontend at <http://savannah.gnu.org>).
+
* While every attempt has been made to use the correct term, they are
sometimes used interchangeably in this document, and should be appropriately
understood by the context.
-* '*groups*' - In the savane code-base, projects are refered to as groups (and
- in few cases, these are conceptually groups rather than code projects, e.g.
- the [Free Software Free Society
Purtuguese](https://savannah.gnu.org/projects/fsfs)
- or the [GNU Spanish Translation
Team](https://savannah.gnu.org/projects/www-es)).
+
+* '*groups*' - in the savane code, projects are referred to as "groups" (and
+ in a few cases, these are conceptually groups rather than programming
+ projects, e.g., the [Free Software Free Society
+ Portuguese](https://savannah.gnu.org/projects/fsfs) and the [GNU
+ Spanish Translation Team](https://savannah.gnu.org/projects/www-es)).
The database table is named `groups`, and several php files are named
- `groupXXX.php` while referring to projects. `group_id=NNN` in URLs refer
- to the project internal ID.
+ `groupXXX.php` while referring to projects. `group_id=N` in urls
+ refer to the project internal ID.
+
* *Savannah Administrators* are volunteers with special access permissions on
the savannah frontend website (see 'becoming super-user' below), and
- administrator SSH access to the savannah VMs.
+ administrator ssh access to the savannah hosts.
See [[SavannahTeam]] and
[List of current
administrators](https://savannah.gnu.org/project/memberlist.php?group=administration).
+
* *Project Administrators* (in the context of this document) are savannah
- users which have administrative access to their own project.
- example: The following people are project administrator for GNU AWK:
+ users who have administrative access to their own project.
+ As an example, these people are project administrators for GNU AWK:
<https://savannah.gnu.org/project/memberlist.php?group=gawk>.
-## source code
+## Savannah source code
The source code for the php frontend and most of the perl/shell backend
scripts is available at:
<http://git.savannah.gnu.org/cgit/administration/savane.git>.
+N.B. That's the `administration` project/group, and the
+git repository named `savane' within it.
To experiment with running a local copy of Savane see [[RunningSavaneLocally]]
and [[SavaneInABox]].
-**NOTE on repositories**: There are several other repositories/clones/forks
which look like
-the savane repositories (e.g.
+**Warning about repositories**: There are several other
+repositories/clones/forks which look like the savane repositories (e.g.
[savane-cleanup](http://git.savannah.gnu.org/cgit/savane-cleanup.git/)
[another savane.git](http://git.savannah.gnu.org/cgit/savane.git/) ).
-The repository listed above is the only official one, and code running on the
-savannah machines comes from that repository alone.
+The repository listed above is the only official one. All code running
+on the savannah hosts comes from the `administration` project, using
+several version control systems there: git, cvs, subversion; each of
+which holds different stuff.
+## Savannah hosts
-## server setup
+Please see [[SavannahArchitecture]] and [[SavannahServices]] rather than
+repeating information here.
-savannah uses the following servers:
-
-* `frontend.savannah.gnu.org` - hosts the php frontend code which serves
- <https://savannah.gnu.org/>
-* `internal.savannah.gnu.org` - hosts the MySQL database containing
- project and user information.
-* `vcs.savannah.gnu.org` - serves the source code repositories
- (git/hg/bzr/svn/cvs) and the web-frontends (e.g. gitweb,cgit/viewVC).
-* `download.savannah.gnu.org` - hosts the download/releases for non-gnu
- projects, and hosts the arch source code repositories (note: GNU arch
- is decomissioned in favor of BZR).
-* `lists.gnu.org` - hosts the mailing lists for savannah projects.
-
-For detailed information about servers setup see [[SavannahServices]].
-
## workflow - overview
@@ -79,18 +76,17 @@
3. The PHP code on `frontend` updates the MySQL database, and optionally
runs one-time project creation scripts.
4. On `vcs` and `download`, cron jobs regularly query the database for
- updates, and make the necessary changes (e.g. create a new GIT repository
+ updates, and make the necessary changes (e.g. create a new git repository
for a new project).
-5. The `cvsweb` repositories hold the HTML files which should be displayed
- on each project's web page. When these are updated, a special hook
- calls a CGI script on `www.gnu.org`, and requests a website update.
+5. The `cvsweb` repositories hold the html files which are the source for
+ a project's web pages. When these are updated, a special hook
+ calls a cgi script on `www.gnu.org` to request a website update.
6. A cron job on `www.gnu.org` regularly checks for update requests,
and `cvs updates` the requested repositories.
7. Unlike code repositories (which use cron+database access), mailing list
creation is performed by `frontend` running a remote command on
- `lists.gnu.org` using SSH.
- This is done becuase `lists.gnu.org` is not managed by Savannah
- administrators.
+ `lists.gnu.org` using ssh.
+ This is done because `lists.gnu.org` is managed by the FSF, not Savannah.
8. Publishing a new tarball release for GNU packages is performed by an
automated process, explained in the
[GNU Maintainer's
guide](https://www.gnu.org/prep/maintain/maintain.html#Automated-FTP-Uploads).
@@ -98,40 +94,47 @@
completeness.
9. GNU Bug Tracker (<http://debbugs.gnu.org>) is based on Debian's
[Bug Tracking System](https://www.debian.org/Bugs/). It is not managed
- by savannah administrators. GNU packages (and other packages hosted on
- savannah?) can request to join the bug tracker. More information here:
- <http://debbugs.gnu.org/Using.html>.
-10. For non-gnu projects, project members with write access can upload new
- files to be availble for download as 'releases' (e.g.
- <http://download.savannah.gnu.org/releases/freetype/>). While GNU projects
- can also store files on this server, it is highly recommended for
- official GNU packages to use GNU's automated ftp uploads (see item 8,
- above). For details, see 'download' section in [[SavannahServices]].
- See also [[UserAuthentication]].
-11. Project members with write access can push code to the repositories on
- `vcs` using SSH. See 'vcs' section in [[SavannahServices]] for
- configuration details. See [[CvsGettingStarted]],[[Svn]],[[UsingHg]],
- [[UsingBzr]],[[UsingGit]] for usage information.
- See [[UserAuthentcation]] for SSH authentication details.
+ by Savannah administrators. Packages hosted on
+ Savannah, either gnu or nongnu, can request to use the bug
+ tracker. More information: <http://debbugs.gnu.org/Using.html>.
+10. For nongnu projects, project members with write access can upload
+ new files to be available for download as 'releases' (e.g.
+ <http://download.savannah.gnu.org/releases/freetype/>). While GNU
+ projects can also store files this way, it is very strongly
+ recommended that official GNU packages use ftp.gnu.org via the
+ automated ftp uploads (see item 8, above). For details, see
+ download section in [[SavannahServices]]. See also
+ [[UserAuthentication]].
+11. Project members with write access can push code to the repositories
+ on `vcs` using ssh. See 'vcs' section in [[SavannahServices]] for
+ configuration details. See [[CvsGettingStarted]], [[Svn]],
+ [[UsingHg]], [[UsingBzr]], [[UsingGit]] for usage information, and
+ [[UserAuthentication]] for ssh authentication details.
-### User Registration (frontend)
+### User registration (frontend)
Anyone with a valid email account can register on GNU Savannah.
* Public URL: <https://savannah.gnu.org/account/register.php>
+
* Source code:
[/frontend/php/account/register.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/account/register.php)
-* The `register.php` creates a new record in the database `user` table, with
- `STATUS='P'`, and sends the user a confirmation URL (e.g.
-
`https://savannah.nongnu.org/account/verify.php?confirm_hash=1f12158d4be45a41`).
+
+* The `register.php` form creates a new record in the database `user`
+ table, with `STATUS='P'`, and sends the user a confirmation URL (e.g.
+ `https://savannah.nongnu.org/account/verify.php?confirm_hash=a1b2...`).
+
* The confirmation URL leads to
-
[/frontend/php/account/verify.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/account/verify.php),
which updates the user's record in
- `user` table to `STATUS='A'`.
+
[/frontend/php/account/verify.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/account/verify.php),
+ which updates the user's record in `user` table to `STATUS='A'`.
+Warning: the email that Savannah sends will often be considered spam by
+big email providers, or outright rejected.
+
### Project submission (frontend)
-Any savannah user can submit a submit a new project request. This procedure is
-for non-gnu projects only (for gnu projects see here:
+Any savannah user can submit a submit a new project request. This
+procedure is for nongnu projects only (for gnu projects see here:
<http://www.gnu.org/help/evaluation.html>).
* Public URL: <https://savannah.gnu.org/register/>
@@ -147,13 +150,13 @@
### Project approval, creation (frontend)
-Savannah admins approve and create projects after manual review
-(the manul review process is outside the scope of savannah). Project creation
-is the same for GNU projects as well (except manual review is done by other GNU
-members, not savannah admins).
+Savannah admins approve and create projects after careful and manual
+review. Project creation is the same for GNU projects (the manual
+review for GNU projects is done by the GNU evaluation volunteers, not
+savannah admins).
-* Public URL:
<https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=NNNNNN>
- (only available to savanah admins in 'super-user' mode).
+* Public URL: <https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=N>
+ (only available to savannah admins in superuser mode).
* The URL is display as 'group administration' link when viewing a
[pending project
ticket](https://savannah.gnu.org/task/?group=administration&category_id=1&status_id=1&set=custom#results).
* Source code:
[/frontend/php/siteadmin/groupedit.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/siteadmin/groupedit.php).
@@ -161,7 +164,7 @@
* system name (i.e. 'short name') - the name will be used in URLs, as a
unix group name for access control, and as directory names in various
locations. Must be unique.
- * status: `pending`,`active`,`deleted`,`maintaenance`,`incomplete`.
+ * status: `pending`,`active`,`deleted`,`maintenance`,`incomplete`.
* license
* visibility (public/private)
@@ -180,11 +183,11 @@
etc.). This are fields such as `use_homepage=1` in the `groups` table.
The items set by default are hard-coded in `triggercreation.php`.
(this is one reason that by default, all new projects on savannah start
- with a cvs repository.)
+ with a cvs repository).
This settings can later be changed by the project administrators.
* Sends an email to the project administrator (based on the savannah user
who submitted/registered the project).
-* FIXME: `triggerscreation.php` mentions `"site-specific triggers executed"` -
+* FIXME: `triggercreation.php` mentions `"site-specific triggers executed"` -
which ones are these and where are they executed?
### Project administration - general information (frontend)
@@ -193,38 +196,38 @@
web interface.
* Name, Short/Long descriptions
- * public URL:
<https://savannah.nongnu.org/project/admin/editgroupinfo.php?group=XXXXX>
+ * public URL:
<https://savannah.nongnu.org/project/admin/editgroupinfo.php?group=N>
* source code:
[/frontend/php/project/admin/editgroupinfo.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/project/admin/editgroupinfo.php).
* The script modifies the `group` table.
* Project members (additional savannah users with write-access):
- * public URL:
<https://savannah.nongnu.org/project/admin/useradmin.php?group=XXXXXX>
+ * public URL:
<https://savannah.nongnu.org/project/admin/useradmin.php?group=N>
* source code:
[/frontend/php/project/admin/useradmin.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/project/admin/useradmin.php)
* modifications are stored in the `user_group` table (a many-to-many
relation table between `user` and `groups` tables).
* uses code from
[/frontend/php/include/member.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/include/member.php).
* Project squads
* FIXME: a per-project list of multiple savannah users?
- * public URL:
<https://savannah.nongnu.org/project/admin/squadadmin.php?group=XXXXX>
+ * public URL:
<https://savannah.nongnu.org/project/admin/squadadmin.php?group=N>
* Source code:
[/frontend/php/project/admin/squadadmin.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/project/admin/squadadmin.php).
* Permissions
* per-user permissions for website features (e.g. tracker management)
- * Public URL:
<https://savannah.nongnu.org/project/admin/userperms.php?group=XXXXX>
+ * Public URL:
<https://savannah.nongnu.org/project/admin/userperms.php?group=XXN>
* Source code:
[/frontend/php/project/admin/userperms.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/project/admin/userperms.php).
* Jobs
- * '*jobs*' are posting which will appear in the
- [Contributers Wanted](https://savannah.nongnu.org/people/) page.
- * Public URL:
<https://savannah.nongnu.org/people/createjob.php?group=XXXXX>
+ * "jobs" are postings which appear in the
+ [Contributors Wanted](https://savannah.nongnu.org/people/) page.
+ * Public URL: <https://savannah.nongnu.org/people/createjob.php?group=N>
* Source code:
[/frontend/php/people/createjob.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/people/createjob.php).
* Select Features
* See "feature selection" section below.
* Configure Mailing lists
* See "mailing lists" section below.
* Configure Cookbook
- * FIXME: document/explain cookbooks
+ * FIXME: document/explain cookbooks (or remove them).
* Set notifications:
* Select savannah users which will be notified upon tracker activity
(e.g. new task, new support ticket, new bug report, etc.).
- * Public URL:
<https://savannah.nongnu.org/project/admin/editgroupnotifications.php?group=XXXXX>
+ * Public URL:
<https://savannah.nongnu.org/project/admin/editgroupnotifications.php?group=N>
* Source code:
[/frontend/php/project/admin/editgroupnotification.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/project/admin/editgroupnotifications.php).
* FIXME: document/explain trackers
@@ -239,50 +242,58 @@
mailing lists, etc.
Each feature has a corresponding field in the `groups` table (e.g. `use_git`,
`use_homepage`, `use_downloads`) which is set to `1` or `0`.
-* some features are associated with a URL. The URLs for these
+
+* Some features are associated with a url. The urls for these
features are initialized to the savannah defaults at project creation, but
can be later changed by the project administrators. Examples:
1. If `use_homepage=1`, the `url_homepage` field defaults to
`http://www.gnu.org/software/PROJECT` (for gnu projects) or
- `http://www.nongnu.org/PROJECT` (for nongnu projects). project
- administrators can change this to any other URL.
- example: The [lilypond](https://savannah.gnu.org/p/lilypond/) homepage
- is set to <http://lilypond.org/>.
- 2. If `use_git=1`, the `url_git` field defaults to `git/?group=PROJECT`
- (which resolves to `https://savannah.gnu.org/git/?group=PROJECT`, a
- page containing instructions about accessing git on savannah for this
- project). Project administrators can change this to any other URL.
- example: The [GNU Social](https://savannah.gnu.org/p/social) git url
points
- to <https://gitorious.org/+socialites>.
+ `http://www.nongnu.org/PROJECT` (for nongnu projects). Project
+ administrators can change this, although GNU packages should not
+ do so.
+ 2. If `use_git=1`, the `url_git` field defaults to
+ `git/?group=PROJECT` (which resolves to
+ `https://savannah.gnu.org/git/?group=PROJECT`, a page containing
+ instructions about accessing git on savannah for this
+ project). Project administrators can change this to any other
+ URL, although they should not do so, especially not GNU packages.
+ (The purpose of Savannah is to host source code.)
+
* Public URL:
<https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=PROJECT>
(only available to project admins).
+
* Source code:
[/frontend/php/project/admin/editgroupfeatures.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/project/admin/editgroupfeatures.php).
+
* When updating features (selecting or deselecting features), the changes are
- saved to the database, in the `groups` table. No other changes are perfomed.
-* These database changed will be later picked-up by the cron-jobs running on
+ saved to the database, in the `groups` table. No other changes are
+ performed.
+
+* These database changes will be picked up by the cron jobs running on
other VMs (see below). This is the reasons some features take time to
- propegate (e.g. when a project administrator turns on `git`, the git
- repository is not created immediately).
+ propagate (e.g. when a project administrator turns on `git`, the git
+ repository is not created immediately). It would be better to do
+ things synchronously, or at least very quickly.
### Project administration - mailing lists (frontend)
Project admins can add/configure/delete mailing lists for their projects using
the savannah web interface.
-* Mailing list require special handling: the mailing list server (running
- GNU Mailman) is a GNU server and is not administrated by Savannah admins.
-* sepcial configuration on `lists.gnu.org` allows remote execution of
+* Mailing lists require special handling: the mailing list server
+ (lists.gnu.org, using GNU Mailman) is administered by the FSF, not
+ Savannah.
+* Special configuration on `lists.gnu.org` allows remote execution of
shell scripts from `frontend` to automate list creation/deletion.
- (for more details see [[ListServer]]).
+ More info: [[ListServer]].
* Public URL: <https://savannah.gnu.org/mail/admin/?group=PROJECT> (only
available to project admins).
* Source code:
[/frontend/php/mail/admin/index.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/mail/admin/index.php).
-* The PHP code updates the `mail_group_list` table (no other direct changes
- are done by the script). new mailing lists are added as new records in the
- tables. change requests to mailing lists are done by changing the
+* The php code updates the `mail_group_list` table (no other direct changes
+ are done by the script). New mailing lists are added as new records in the
+ tables. Change requests to mailing lists are done by changing the
`status` field (see source code for possible values).
-* A cronjob on `frontend` reads the changes in the `mail_group_list` and
- executes the necessary changes on `lists.gnu.org` using SSH, then updates
+* A cron job on `frontend` reads the changes in the `mail_group_list` and
+ executes the necessary changes on `lists.gnu.org` using ssh, then updates
the database with the result of the change.
See
[/backend/mail/sv_mailman.in](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/backend/mail/sv_mailman.in).
@@ -320,7 +331,7 @@
*/30 * * * * root sv_groups --cron --only-download --only-arch
```
-### Cron jobs on Fronend
+### Cron jobs on frontend
FIXME: work-in-progress
@@ -335,7 +346,7 @@
## Additional functionality
-### super-user and imporsonate on frontend
+### super-user and impersonate on frontend
### frontend configuration files
@@ -343,7 +354,7 @@
### git hooks on vcs
-### cvseweb hooks on vcs
+### cvsweb hooks on vcs
### other scripts on vcs
Modified: trunk/sviki/SavannahTeam.mdwn
===================================================================
--- trunk/sviki/SavannahTeam.mdwn 2015-02-14 04:17:55 UTC (rev 137)
+++ trunk/sviki/SavannahTeam.mdwn 2015-02-14 17:03:06 UTC (rev 138)
@@ -11,35 +11,29 @@
- [karl] - Karl Berry (general, not git)
- [meyering] - Jim Meyering (emergencies)
- [mjflick] - Michael J. Flickinger (emergencies)
-- [rgm] - Glenn Morris (bzr)
+- [rgm] - Glenn Morris (bzr, debbugs)
- [rwp] - Bob Proulx (general, including git)
Many are also GNU contributors, see <http://www.gnu.org/people>.
-FSF system administrators
--------------------------
+The FSF system administrators (not listed individually here since FSF
+staffing is not our purview) also significantly contribute to Savannah;
+for example, all Savannah hosts are virtualized on FSF-maintained
+hardware.
-- [lisam] - FSF sysadmin
+Inactive savannah hackers - contributed in the past but are now inactive
+------------------------------------------------------------------------
-
-Inactive savannah hackers - contributed a lot in the past but are now inactive
-------------------------------------------------------------------------------
-
- [alexshulgin] - Alexander Shulgin
-- [baughj] - FSF sysadmin
-- [bernie] - FSF sysadmin
- [beuc] - Sylvain Beucler
-- [jag] - Joshua Ginsberg, FSF sysadmin
- [jbailey] - Jeff Bailey
- [kickino]
- [loic] - Loic Dachary, gna et al.
-- [nico] - FSF sysadmin
- [rudy]
- [snoogie] - Jean-Michel Frouin
- [sp]
- [stevenr]
- [tizzef]
-- [ward] - FSF part-time sysadmin
- [zerodeux] - Vincent Caron
- [zeus] - Jonathan Gonzalez V.
(et al.)
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [138] Internals wording, etc.,
karl <=