[Savannah-cvs] [523] minor updates and rewording

[ineiev]

Revision: 523
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=523
Author:   ineiev
Date:     2023-02-02 06:01:50 -0500 (Thu, 02 Feb 2023)
Log Message:
-----------
minor updates and rewording

Modified Paths:
--------------
    trunk/sviki/HomePage.mdwn
    trunk/sviki/HomepageUpload.mdwn

Modified: trunk/sviki/HomePage.mdwn
===================================================================
--- trunk/sviki/HomePage.mdwn   2023-02-02 10:52:28 UTC (rev 522)
+++ trunk/sviki/HomePage.mdwn   2023-02-02 11:01:50 UTC (rev 523)
@@ -1,11 +1,15 @@
-Web pages for Savannah projects
+Web pages for Savannah groups
 ===============================
-Each project at Savannah has a "web pages" CVS repository, completely
-separate from any "sources" repositories.  These are the standard urls
+Each group at Savannah may have a "web pages" CVS repository, completely
+separate from any "sources" repositories.  These are the standard URLs
 provided:
 
-- For gnu projects: gnu.org/software/project/ (shortcut: gnu.org/s/project/)
-- For nongnu projects: www.nongnu.org/project/ and project.nongnu.org/
+- For non-GNU groups: www.nongnu.org/*group*/ and *group*.nongnu.org/
+- For GNU packages: www.gnu.org/software/*group*/
+  (shortcut: www.gnu.org/s/*group*/)
+- For [[GNU translation teams|GnuOrgTranslationTeams]]:
+  www.gnu.org/server/standards/translations/language-code
+- For portions of www.gnu.org: specific for each group.
 
 Initial upload of web pages: [[HomepageUpload]].
 

Modified: trunk/sviki/HomepageUpload.mdwn
===================================================================
--- trunk/sviki/HomepageUpload.mdwn     2023-02-02 10:52:28 UTC (rev 522)
+++ trunk/sviki/HomepageUpload.mdwn     2023-02-02 11:01:50 UTC (rev 523)
@@ -1,15 +1,15 @@
-Upload project web pages
+Upload group web pages
 ========================
 
-See [[Homepage]] for general info on the per-project web pages.
+See [[Homepage]] for general info on the per-group web pages.
 
-To import an initial setup web pages for your project, use the `web`
+To import an initial setup web pages for your group, use the `web`
 repository (this is completely separate from any source trees).  The web
 tree always uses CVS.  For basic CVS usage, see [[CvsGettingStarted]].
 
 1.  First, you need to configure your [[SshAccess]].
 
-2.  You should have read instructions in your CVS project page on
+2.  You should have read instructions in your CVS group page on
     savannah (e.g., the emacs CVS page is
     <http://savannah.gnu.org/cvs/?group=emacs>).
 
@@ -16,30 +16,30 @@
 3.  Go to the local directory where you want to put your
     local copy the CVS HTML tree. For example:
 
-        mkdir ~/project/www
-        cd ~/project/www
+        mkdir ~/group/www
+        cd ~/group/www
 
 4.  Download the CVS HTML tree structure (substitute developername with
-    your login and projectname with your project system name):
+    your login and group_name with your group system name):
 
-        cvs -z3 -d:ext:developername@cvs.sv.gnu.org:/web/projectname co 
projectname
+        cvs -z3 -d:ext:developername@cvs.sv.gnu.org:/web/group_name co 
group_name
 
-5.  Then, in the directory \~/project/www/projectname, copy all the
+5.  Then, in the directory \~/group/www/group_name, copy all the
     files you want to insert in the CVS HTML tree. For example:
 
-        cp ~/tmp/index.html ~/project/www/projectname
+        cp ~/tmp/index.html ~/group/www/group_name
 
 6.  Once you have locally set your HTML tree, you can import it. To
     import a file and a directory:
 
-        cd ~/project/www/projectname
+        cd ~/group/www/group_name
         cvs add index.html
         cvs add mydir
         # (or: cvs add index.html mydir)
         cvs commit
 
-Done! The webpages will be updated within an hour. The location of your
-homepage is the default URL in your project's Select[ed] Features.
+Done! The webpages will be updated within a few minutes. The location of your
+homepage is the default URL in your group Select Features.
 
 Similarly, updating your web pages after the initial import is a matter
 of updating and committing in your CVS tree.
@@ -49,17 +49,17 @@
 warning when this happens (Savannah does not receive any information
 from the backend FSF machines), it's just that some files may not be
 present.  If you notice this, the thing to do is submit a new ticket at
-<https://savannah.gnu.org/support/?group=administration>.
+[[Savannah support
+tracker|https://savannah.nongnu.org/support/?group=administration]].
 
 For Savannah administrators
 ---------------------------
-When a project's web pages, we can retrigger the update at the FSF side
-with the same command that is run by the CVS loginfo hook
-([[SavannahInternals]]).  Do this on the vcs machine (though probably it
-does not technically matter).
+We can retrigger the update at the FSF side with the same command that
+is run by the CVS loginfo hook ([[SavannahInternals]]).  Do this
+on the vcs machine (though probably it does not technically matter).
 
     # T=gnu or T=non-gnu
-    # PROJ=project identifier
+    # PROJ=group identifier
     vcs$ curl http://www.gnu.org/new-savannah-project/new.py \
               -s -F type=$T -F project=$PROJ
 
@@ -86,7 +86,7 @@
    The 404 errors are sent back to apache, which in turns renders
    an entire www.gnu.org "page not found" template.
 2. The script `new.py` will return HTTP-404 (page not found)
-   if the project name is invalid, or if the type is invalid
+   if the group name is invalid, or if the type is invalid
    (e.g. not "gnu" or "non-gnu").
 3. A copy of the script can be found in
    `fencepost:/srv/data/www-mirror/new-savannah-project/new.py`.