[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [140] separate vc on frontpage
|
From: |
karl |
|
Subject: |
[Savannah-cvs] [140] separate vc on frontpage |
|
Date: |
Sat, 14 Feb 2015 17:15:20 +0000 |
Revision: 140
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=140
Author: karl
Date: 2015-02-14 17:15:10 +0000 (Sat, 14 Feb 2015)
Log Message:
-----------
separate vc on frontpage
Modified Paths:
--------------
trunk/sviki/FrontPage.mdwn
trunk/sviki/SavannahInternals.mdwn
trunk/sviki/SavannahServices.mdwn
Modified: trunk/sviki/FrontPage.mdwn
===================================================================
--- trunk/sviki/FrontPage.mdwn 2015-02-14 17:06:43 UTC (rev 139)
+++ trunk/sviki/FrontPage.mdwn 2015-02-14 17:15:10 UTC (rev 140)
@@ -73,8 +73,6 @@
- [[RemovingProject]]
- [[RenamingProjectGroup]]
-- [[CurrentTasks]]
-
- [[ProjectApproval]]
- [[AboutTranslations]]
- [[ApprovingSubmission]]
@@ -106,14 +104,10 @@
- [[UpstreamCollaboration]]
- [[WhyLegalChecksBeforeRelease]]
-- [[SavannahArchitecture]
- - [[SavannahInternals]]
- - [[SavannahServices]]
- - [[AudioVideo]]
- - [[Backup]]
+- Version Control
- [[Bzr]]
- [[UsingBzr]]
- - [[Compromise2010]]
+
- [[CvS]]
- [[SynchronizedExternalRepositories]]
- [[AccessToCVSROOT]]
@@ -126,66 +120,66 @@
- [[UsingCvs]]
- [[CvsDisabling]]
- - [[DataExport]]
- - [[FrontEnd]]
-
- [[GNUArch]]
- [[Git]]
- [[UsingGit]]
- [[CvsDisabling]]
-
- - [[GnuArchitecture]]
- Mercurial
- [[Hg]]
- [[UsingHg]]
+ - Subversion
+ - [[SvN]]
+ - [[CvSToSvN]]
+ - [[CvsDisabling]]
+ - [[SavaneSvkBranch]]
+ - [[SvnImportExistingRepo]]
+ - [[AdminSvnImport]]
+
+- [[SavannahArchitecture]]
+ - [[SavannahInternals]]
+ - [[SavannahServices]]
+ - [[RunningSavaneLocally]]
+ - [[SavaneInABox]]
+
+ - [[AudioVideo]]
+ - [[Backup]]
+ - [[Compromise2010]]
+ - [[DataExport]]
+ - [[DNS]]
+ - [[FrontEnd]]
+ - [[GnuArchitecture]]
- [[HomePage]]
- [[JustSFTP]]
- [[MailSystem]]
- [[ManuallyInstalledPackages]]
+ - [[Mirmon]]
+ - [[Nagios]]
- [[RemountableHome]]
- [[SavaneConfiguration]]
- [[ShellAccess]]
- [[Stats]]
- - [[SqlQueries]]
-
- - Subversion
- - [[SvN]]
- - [[CvSToSvN]]
- - [[CvsDisabling]]
- - [[SavaneSvkBranch]]
- - [[SvnImportExistingRepo]]
- - [[AdminSvnImport]]
-
+ - [[SqlQueries]]
- [[TlS]]
-
+ - [[VPN]]
+ - [[VPNConfiguration]]
- [[ZWiki]]
- [[ZopeBackup]]
- - [[DNS]]
- - [[Mirmon]]
- - [[Nagios]]
- - [[RunningSavaneLocally]]
- - [[SavaneInABox]]
+ - [[SavannahTeam]]
+ - [[RecruitingVolunteers]]
+ - [[SavannahHacker]]
+ - [[SavannahHackersCommunication]]
-- [[SavannahTeam]]
- - [[RecruitingVolunteers]]
- - [[SavannahHacker]]
- - [[SavannahHackersCommunication]]
+ - [[TasksList]]
+ - [[CurrentTasks]]
+ - [[MonoToNe]]
+ - [[SavaneTasks]]
+ - [[SavaneRewrite]]
+ - [[SvNTasks]]
-- [[TasksList]]
- - [[MonoToNe]]
- - [[SavaneTasks]]
- - [[SavaneRewrite]]
-
- - [[SvNTasks]]
-
-- [[VPN]]
- - [[VPNConfiguration]]
-
-
# Automatically-generated list of all pages:
[[!map pages="*"]]
Modified: trunk/sviki/SavannahInternals.mdwn
===================================================================
--- trunk/sviki/SavannahInternals.mdwn 2015-02-14 17:06:43 UTC (rev 139)
+++ trunk/sviki/SavannahInternals.mdwn 2015-02-14 17:15:10 UTC (rev 140)
@@ -14,9 +14,8 @@
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.
+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
@@ -50,8 +49,8 @@
and [[SavaneInABox]].
**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/)
+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
@@ -72,11 +71,11 @@
1. Users submit a new project.
Savannah administrators approve the project (see [[ApprovingSubmission]]).
2. Project administrators of existing project can change project settings
- (e.g. add a mailing list, switch from cvs to git, etc.).
+ (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.
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 are the source for
a project's web pages. When these are updated, a special hook
@@ -98,7 +97,7 @@
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.
+ 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
@@ -121,7 +120,7 @@
* 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` form creates a new record in the database `user`
- table, with `STATUS='P'`, and sends the user a confirmation URL (e.g.
+ 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
@@ -178,7 +177,7 @@
[/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.
* The `triggercreation.php` script does the following:
- * Sets project defaults (e.g. having a homepage, having 'downloads',
+ * Sets project defaults (e.g., having a homepage, having 'downloads',
using cvs repository, using task,support,bugs 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`.
@@ -210,7 +209,7 @@
* 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-user permissions for website features (e.g., tracker management)
* 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
@@ -226,7 +225,7 @@
* 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.).
+ (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
@@ -240,7 +239,7 @@
* *features* in this context are the facilities used by the project, 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`,
+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
@@ -270,7 +269,7 @@
* 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
+ 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.
@@ -350,7 +349,8 @@
### frontend configuration files
-(files which are not in the `savane` repositories)
+(files which are not in the `administration` (or any version control)
+repositories)
### git hooks on vcs
Modified: trunk/sviki/SavannahServices.mdwn
===================================================================
--- trunk/sviki/SavannahServices.mdwn 2015-02-14 17:06:43 UTC (rev 139)
+++ trunk/sviki/SavannahServices.mdwn 2015-02-14 17:15:10 UTC (rev 140)
@@ -9,6 +9,7 @@
See also:
- [[SavannahArchitecture]]
+- [[SavannahInternals]]
- [[GnuArchitecture]]
## Conventions
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [140] separate vc on frontpage,
karl <=