[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [571] proofread
|
From: |
ineiev |
|
Subject: |
[Savannah-cvs] [571] proofread |
|
Date: |
Thu, 9 Feb 2023 05:50:56 -0500 (EST) |
Revision: 571
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=571
Author: ineiev
Date: 2023-02-09 05:50:55 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
proofread
Modified Paths:
--------------
trunk/sviki/SavannahInternals.mdwn
Modified: trunk/sviki/SavannahInternals.mdwn
===================================================================
--- trunk/sviki/SavannahInternals.mdwn 2023-02-09 09:30:26 UTC (rev 570)
+++ trunk/sviki/SavannahInternals.mdwn 2023-02-09 10:50:55 UTC (rev 571)
@@ -4,80 +4,96 @@
This page describes inner workings of the GNU Savannah platform
(web frontend + backend processes).
-**Some terminology**
+## Some terminology
-* '*GNU Savannah*' (or just '*Savannah*') is the name of the entire
+<dl>
+<dt>GNU Savannah (or just Savannah)</dt>
+<dd> The name of the entire
platform, encompassing the various hosts (see [[SavannahArchitecture]]),
services (see [[SavannahServices]]), people (see [[SavannahTeam]]) and
other odds and ends.
+</dd>
-* '*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>).
+<dt>Savane (French for 'savannah')</dt>
+<dd>The code name for the source code
+ which runs many parts of the Savannah platform (most notably: the web
+ frontend at savannah.gnu.org).
+</dd>
+</dl>
+
While usually these are distinguished, they are sometimes used
interchangeably, and should be appropriately understood by the context.
-* '*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=N` in urls
- refer to the project internal ID.
+<dl>
+<dt>groups</dt>
-* *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 hosts.
- See [[SavannahTeam]] and
- [List of current
administrators](https://savannah.gnu.org/project/memberlist.php?group=administration).
+<dd>In savane code, software development projects are an informal subset
+ of "groups" (examples of groups that are not projects in that sense are
+ <a href="//savannah.gnu.org/projects/audio-video">GNU and FSF audio
+ and video</a> and the <a href="//savannah.gnu.org/projects/www-es">
+ Spanish GNU Translation Team</a>.
+ The database table is named `groups`, and several PHP files are named
+ `groupXXX.php`. `group_id=N` in URLS refer to group internal ID.
+</dd>
-* *Project Administrators* (in the context of this document) are savannah
- 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>.
+<dt>Savannah Administrators</dd>
+<dd>Volunteers with special access permissions
+ on the Savannah frontend website (see 'becoming super-user' below)
+ and administrator ssh access to the Savannah hosts.
+ See [[SavannahTeam]] and <a
+ href="//savannah.gnu.org/project/memberlist.php?group=administration">
+ List of current administrators</a>.
+</dd>
+<dt>Group Administrators</dt>
+<dd>Savannah users who have administrative access to their group.
+ As an example, these people are <a
+ href="//savannah.gnu.org/project/memberlist.php?group=gawk">group
+ administrators for GNU AWK</a>.
+</dd>
+</dl>
+
## 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
+The source code for the PHP frontend and most of the backend
+scripts is available at [Savane Git
+repository](//git.savannah.gnu.org/cgit/administration/savane.git).
+N.B. That's the `administration` group, and the
git repository named `savane` within it.
+This repository is the only official one.
-**Warning about repositories**: There are several other
+### 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. All code running
-on the savannah hosts comes from the `administration` project, using
+[savane-cleanup](//git.savannah.gnu.org/cgit/savane-cleanup.git/)).
+All code running on Savannah hosts comes from the `administration` group, using
several version control systems there: git, cvs, subversion; each of
which holds different stuff.
## Savannah hosts
-Please see [[SavannahArchitecture]] and [[SavannahServices]] rather than
-repeating information here.
+See [[SavannahArchitecture]] and [[SavannahServices]].
-## workflow - overview
-
[savannah-internals-2015.dia](/maintenance/savannah-internals-2015.dia)
-1. Users submit a new project.
- Savannah administrators approve the project (see [[ApprovingSubmission]]).
-2. Project administrators of existing project can change project settings
+## Workflow - overview
+
+1. A user submits a new group.
+ Savannah administrators approve the group (see [[ApprovingSubmission]]).
+2. Group administrators of existing group can change group settings
(e.g., add a mailing list, switch from cvs to git, etc.).
3. The PHP code on `frontend` updates the MySQL database, and optionally
- runs one-time project creation scripts.
+ runs one-time 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 for a new project).
-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.
+ repository for a new group).
+5. The `cvsweb` repositories hold the files which are the source for
+ a group 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. A cron job on `mgt0` regularly query the database for mailing list
@@ -85,29 +101,28 @@
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).
+ [GNU Maintainer's
guide](//www.gnu.org/prep/maintain/maintain.html#Automated-FTP-Uploads).
It is not managed by Savannah administrators, and only mentioned here
for completeness.
-9. GNU Bug Tracker (<http://debbugs.gnu.org>) is based on Debian's
+9. GNU Bug Tracker (<http://debbugs.gnu.org>) is based on Debian
[Bug Tracking System](https://www.debian.org/Bugs/). It is not managed
by Savannah administrators. Packages hosted on
- Savannah, either gnu or nongnu, can request to use the bug
+ Savannah, either GNU or non-GNU, 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
+10. For non-GNU groups, group members 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
+ groups 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
+11. Group members 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)
Anyone with a valid email account can register on GNU Savannah.
@@ -127,12 +142,15 @@
Warning: the email that Savannah sends will often be considered spam by
big email providers, or outright rejected.
-### Project submission (frontend)
+For further details, see [[IdleAccounts]].
-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>).
+### Group submission (frontend)
+Any Savannah user can submit a new group request. This
+procedure is for non-GNU groups only (for GNU packages, the first
+and additional step is
+[evaluating software for GNU](//www.gnu.org/help/evaluation.html).
+
* Public URL: <https://savannah.gnu.org/register/>
* Source code:
[/frontend/php/register/index.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/register/index.php)
(and see all files in
@@ -144,24 +162,22 @@
* Creates a new task in the task tracker (FIXME: how?)
* FIXME: the source code mentions something about `cookbook` and
`recipes` database tables?
-* The project is in `pending` state until approved by Savannah administrators.
+* The group is in `pending` state until approved by Savannah administrators.
-### Project approval, creation (frontend)
+### Group approval, creation (frontend)
-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).
+Savannah admins approve and create groups after careful and manual
+review. Group creation is the same for GNU groups.
* Public URL:
<https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=N>
- (only available to savannah admins in superuser mode).
+ (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).
+ [pending group
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).
* In this page the following changes can be made:
* 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
+ Unix group name for access control, and as directory names in various
locations. Must be unique.
* status: `pending`,`active`,`deleted`,`maintenance`,`incomplete`.
* license
@@ -171,27 +187,27 @@
* Two special commands are available in this page as well:
* The green "V" icon: calls `groupedit.php` again with cgi parameters
- `updatefast=1` and `status=A`, thus marking the project as `active`
- in the `groups` table, and in savannah.
+ `updatefast=1` and `status=A`, thus marking the group as `active`
+ in the `groups` table, and in Savannah.
* The configure (screwdriver and wrench) icon: calls
[/frontend/php/siteadmin/triggercreation.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/siteadmin/triggercreation.php),
- which calls the necessary one-time project creation scripts.
+ which calls the necessary one-time group creation scripts.
* The `triggercreation.php` script does the following:
- * Sets project defaults (e.g., having a homepage, having 'downloads',
- using cvs repository, using task,support,bugs trackers, using news,
+ * Sets group defaults (e.g., having a homepage, having 'downloads',
+ using cvs repository, using task, support, bug trackers, using news,
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
+ (this is one reason why by default, all new groups on Savannah
start with a cvs repository).
- These 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).
+ These settings can later be changed by the group administrators.
+ * Sends an email to the group administrator (based on the Savannah
+ user who registered the group).
* FIXME: `triggercreation.php` mentions `"site-specific triggers executed"`
- which ones are these and where are they executed?
-### Project administration - general information (frontend)
+### Group administration - general information (frontend)
-Project admins can modify various items for their projects using the savannah
+Group admins can modify various items for their groups using the Savannah
web interface.
* Name, Short/Long descriptions
@@ -198,23 +214,22 @@
* 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):
+* Group members: additional Savannah users with write access
* 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?
+* Group squads: per-group lists of Savannah users
* 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)
+ * per-member permissions for website features (e.g., tracker management)
* Public URL:
<https://savannah.nongnu.org/project/admin/userperms.php?group=N>
* 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 postings which appear in the
- [Contributors Wanted](https://savannah.nongnu.org/people/) page.
+ [Contributors Wanted](//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
@@ -224,41 +239,43 @@
* Configure Cookbook
* FIXME: document/explain cookbooks (or remove them).
* Set notifications:
- * Select savannah users which will be notified upon tracker activity
+ * 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=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
+ * FIXME: document trackers
-### Project administration - feature selection (frontend)
+### Group administration - feature selection (frontend)
-Project admins can enable/disable features for their projects, using the
-savannah web interface.
+Group admins can enable and disable features for their groups using the
+Savannah web interface.
-* *features* in this context are the facilities used by the project, such as
+* *features* in this context are the facilities used by the group, such as
git, cvs, homepage, downloads, news, bugs/support/patches/tasks trackers,
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
-features are initialized to the savannah defaults at project creation, but
-can be later changed by the project administrators. Examples:
+* Some features are associated with a URL. The URLs for these
+features are initialized to the Savannah defaults at group creation, but
+can be later changed by the group 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
+ `http://www.gnu.org/software/GROUP` (for GNU groups) or
+ `http://www.nongnu.org/GROUP` (for non-GNU groups). Group
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
+ `git/?group=GROUP` (which resolves to
+ `https://savannah.gnu.org/git/?group=GROUP`, a page containing
+ instructions about accessing git on Savannah for this
+ group). Group 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).
+* Public URL:
+ https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=GROUP
+ (only available to group 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).
@@ -268,15 +285,15 @@
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
- propagate (e.g., when a project administrator turns on `git`, the git
+ other VMs (see below). This is the reason why some features take time to
+ propagate (e.g., when a group 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)
+### Group administration - mailing lists (frontend)
-Project admins can add/configure/delete mailing lists for their projects using
-the savannah web interface.
+Group admins can add, configure and delete mailing lists for their
+groups using the Savannah web interface.
* Mailing lists require special handling: the mailing list server
(lists.gnu.org, using GNU Mailman) is administered by the FSF, not
@@ -284,10 +301,10 @@
* Special configuration on `lists.gnu.org` allows remote execution of
shell scripts from `frontend` to automate list creation/deletion.
More info: [[ListServer]].
-* Public URL: <https://savannah.gnu.org/mail/admin/?group=PROJECT> (only
- available to project admins).
+* Public URL: <https://savannah.gnu.org/mail/admin/?group=GROUP> (only
+ available to group 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
+* 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).
@@ -310,10 +327,10 @@
# remake user list for outgoing mail.
*/10 * * * * root nice -n 11 sv_aliases --cron && sed -e '/#
Savannah include start/,/# Savannah include end/s/\([^:]\+\): .*/\1:
INVALID.NOREPLY@gnu.org/' /etc/email-addresses -e 's,This is
/etc/email-addresses,DO NOT EDIT - GENERATED FROM email-addresses.,' >
/etc/email-addresses_SENDER
- # remake list of git repositories in each project.
+ # remake list of git repositories in each group.
*/15 * * * * root nice -n 11
/usr/src/infra/git/refresh-project-list.sh && /usr/src/infra/git/sv_cgit.pl
- # remake CVSROOT/{commit,log}/info (for cvs commit email?).
+ # remake CVSROOT/{commit,log}/info (for cvs commit email).
31 * * * * root nice -n 11 /usr/src/infra/cvs/generate_log_accum.pl
# remake list of groups for the vcs.
@@ -324,8 +341,8 @@
`alias`-type file for for exim4 mail server, used when sending commit
updates to mailing lists.
* The script queries the MySQL database, extracting user names and
- emails for all savannah users. Additionally, emails for 'squads'
- (per-project mailing groups) are queried. The results are saved in
+ emails for all Savannah users. Additionally, emails for 'squads'
+ (per-group mailing groups) are queried. The results are saved in
`vcs0:/etc/email-addresses`.
* `vcs0:/etc/email-addresses` is symlinked to the standard
`vcs0:/etc/exim4/email-addresses` file. Example:
@@ -367,7 +384,7 @@
...
These names (e.g. `Jim Meyering`) will appear
- in the *owner* field when viewing the gitweb page of the project
+ in the *owner* field when viewing the gitweb page of the group
(example: <http://git.savannah.gnu.org/gitweb/?p=coreutils.git>).
* `sv_cgit.pl` - this script updates the `vcs0:/srv/git/cgitrepos` file
@@ -377,7 +394,7 @@
* cgit configuration file is `vcs0:/etc/cgitrc`.
* Implementation detail: the script reads the `/srv/git/project-list`
file (generated by `refresh-project-list.sh`, above), and for each
- mentioned project, writes an entry in `cgitrepos`. Example:
+ mentioned group, writes an entry in `cgitrepos`. Example:
$ cat /srv/git/cgitrepos
@@ -390,18 +407,18 @@
repo.owner=Jim Meyering
...
-* `sv_groups` - This script creates new repositories for projects in the
- savannah database
- * reminder: when a new project is approved/created on
- savannah, or when a project administrator selects a new repository
- feature the `frontend` php code only updates the database. this
+* `sv_groups` - This script creates new repositories for groups in the
+ Savannah database
+ * reminder: when a new group is approved on
+ Savannah, or when a group administrator selects a new repository
+ feature the `frontend` PHP code only updates the database. this
script picks up the changes and executes them.
* file is
[/backend/accounts/sv_groups.in](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/backend/accounts/sv_groups.in).
* The script queries the `groups` table, and creates the needed
repositories.
- Example: For project `XXX`, if `groups.use_git=1`, it look for
+ Example: For group `XXX`, if `groups.use_git=1`, it look for
`vcs0:/srv/git/XXX.git`. If it doesn't exist, create it with
- `git init` and additional savannah-specific configurations (e.g.
+ `git init` and additional Savannah-specific configurations (e.g.
permissions, hooks, xattrs).
* Repository initialization and configuration is delegated to the
relevant perl module. See
@@ -414,9 +431,9 @@
* Two types of CVS repositories can be created:
`cvs` (Using `CvsMakeArea` in `Cvs.pm`) - source code repository;
`webcvs` (Using `WebCvMakeAreaSavannahGNU` in `Cvs.pm`) - webcvs
- repository (content will be available on www.gnu.org/www.nongnu.org).
+ repository (files will be available on www.gnu.org/www.nongnu.org).
The same routines also update existing CVS hooks.
- * The script also contains legacy code to create unix groups on the
+ * The script also contains legacy code to create Unix groups on the
local machine (using `/usr/sbin/groupadd`). This part is not used any
more, since groups and users are delegated to `nsswitch/libnss-mysql`
(see [[UserAuthentication]]).
@@ -437,8 +454,8 @@
*/30 * * * * root sv_groups --cron --only-download --only-arch
-* `sv_groups` - This script creates new repositories for projects in the
- savannah database. See description for `sv_groups` in the above section.
+* `sv_groups` - This script creates new repositories for groups in the
+ Savannah database. See description for `sv_groups` in the above section.
### Cron jobs on frontend
@@ -455,11 +472,11 @@
3,33 * * * * root scp vcs.sv.gnu.org:/srv/git/cgitrepos
/etc/savane
[sv_export](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/backend/export/sv_export.in)
- is an old feature which exports project data into XML.
+ is an old feature which exports group data into XML.
FIXME: remove this?
* `frontend0:/etc/cron.daily/sv_list_groups` [unfinished] - an attempt to
- publish an authoritative list of active projects hosted on GNU Savannah.
+ publish an authoritative list of active groups hosted on GNU Savannah.
The script contains the following code:
mysql savane -B -e 'SELECT group_type.type_id, group_type.name,
@@ -475,7 +492,7 @@
### Cron jobs on mgt0
-stored in `mgt0:/etc/cron.d/sv`:
+Stored in `mgt0:/etc/cron.d/sv`:
# Assign uidNumber and gidNumber inthe database (and rebuild cache for
# libnss-mysql-bg). 7211 was the latest group created by the old
@@ -497,21 +514,21 @@
* `sv_assign_uid_gid` - creates unique user ids and group ids for
- users/projects in the savannah system.
- * reminder: across all savannah hosts, unix user/group ids are managed
+ users and groups in the Savannah system.
+ * reminder: across all Savannah hosts, Unix user/group ids are managed
with nsswitch/libnss-mysql (see [[UserAuthentication]] for details).
* Source code:
[/backend/accounts/sv_assign_uid_gid.in](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/backend/accounts/sv_assign_uid_gid.in).
- * When a new user (or project) is created on savannah, the php code
+ * When a new user (or group) is created on Savannah, the php code
on `frontend` does not assign uid/gid.
* This script picks up new users (SQL: `user.uidNumber is NULL`) and
- new projects (SQL: `groups.gidNumber is NULL`) and assigns them ids.
+ new groups (SQL: `groups.gidNumber is NULL`) and assigns them ids.
-* `sv_mailman` - queries the `mail_group_list` table, and creates/updates
+* `sv_mailman` - queries the `mail_group_list` table, and creates and updates
the mailing lists on `lists.gnu.org`.
* Source code:
[/backend/mail/sv_mailman.in](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/backend/mail/sv_mailman.in).
- * This script is tightly-coupled with the php code in
+ * This script is tightly-coupled with the PHP code in
[/frontend/php/mail/admin/index.php](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/mail/admin/index.php).
* The `index.php` code sets the `mail_group_list.status` field to the
requested new status, and the `sv_mailman` script executes the
@@ -533,7 +550,7 @@
EOF
-* `sv_cleaner` - cleans up left-overs from interrupted php code?
+* `sv_cleaner` - cleans up left-overs from interrupted PHP code?
* source code:
[/backend/misc/sv_cleaner.in](http://git.savannah.gnu.org/cgit/administration/savane.git/tree/backend/misc/sv_cleaner.in).
* FIXME: investigate this script.
@@ -548,9 +565,9 @@
notification list should be warned.
Case 2: an user decided to receive a batch of open item assigned to
him each x days, minimum priority being > 5
- Case 3: a project admin decided that members assigned to some item
of
+ Case 3: a group admin decided that members assigned to some item
of
should receive a batch each x days, minimum priority > 5
- (Case 4: a project admin decided that members assigned to some item
+ (Case 4: a group admin decided that members assigned to some item
whose statut/resolution havent changed for some period should
receive
a batch each x days)
@@ -564,12 +581,15 @@
### super-user and impersonate on frontend
+- [[Impersonating|ImpersonatingSomebody]]
+- [[Deleting accounts|DeletingUserAccount]]
+- [[Renaming accounts|RenamingAccounts]]
+- [[Changing email|ManuallyChangeE-mail]]
+
### frontend configuration files
-(files which are not in the `administration` (or any version control)
-repositories)
+[[SavaneConfiguration]]
### git hooks on vcs
### cvsweb hooks on vcs
-
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [571] proofread,
ineiev <=