[Savannah-cvs] [551] update

[ineiev]

Revision: 551
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=551
Author:   ineiev
Date:     2023-02-07 04:27:48 -0500 (Tue, 07 Feb 2023)
Log Message:
-----------
update

Modified Paths:
--------------
    trunk/sviki/ApprovingSubmission.mdwn
    trunk/sviki/ProjectApproval.mdwn

Modified: trunk/sviki/ApprovingSubmission.mdwn
===================================================================
--- trunk/sviki/ApprovingSubmission.mdwn        2023-02-07 09:21:17 UTC (rev 
550)
+++ trunk/sviki/ApprovingSubmission.mdwn        2023-02-07 09:27:48 UTC (rev 
551)
@@ -1,32 +1,26 @@
-Approving project submissions
-=============================
+# Approving group submissions
 
-Of course, do not approve the project unless it actually meets our
-[requirements](http://savannah.gnu.org/register/requirements.php); more
+Of course, do not approve the package unless it actually meets our
+[requirements](//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:
 
--   click on the 'Group Administration' link in the original submission
+-   Follow the 'Group Administration' link in the original submission
     of this tracker item.
--   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; often
+-   Check the group name, group type, license. To be an official GNU
+    package it *must* be listed in
+    fencepost.gnu.org:/gd/gnuorg/maintainers; otherwise, the package
+    must be [evaluated](//www.gnu.org/help/evaluation.html) first.
+    Or it can be evaluated and approved as a non-GNU package; 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.
--   click the green 'V' icon.
--   click the 'configure' (screwdriver & wrench) icon.
--   close the tracker item: change status to done, open/closed to
-    closed, assign it to yourself, and write a comment (which will be
-    seen by the OP).
+-   Visit the "Approve" link (the green 'V' icon).
+-   Visit the "Send new group instruction email and trigger group
+    creation" link.
+-   close the tracker item: change status to 'Done', 'Open/Closed' to
+    'Closed', write a comment (which will be seen by the OP).
 
 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.
+jobs to run and the group to be fully populated: create repositories
+on VCS, etc.

Modified: trunk/sviki/ProjectApproval.mdwn
===================================================================
--- trunk/sviki/ProjectApproval.mdwn    2023-02-07 09:21:17 UTC (rev 550)
+++ trunk/sviki/ProjectApproval.mdwn    2023-02-07 09:27:48 UTC (rev 551)
@@ -1,50 +1,21 @@
-Project Approval at Savannah
-============================
+# For Savannah admins: Submission approval
 
-About project reviews
----------------------
+## About submission review
 
 Savannah is a place to emphasize free software values, especially the
-non-obvious/non-technical ones. We want you to understand them and
-follow a few good practices for your project.
+non-obvious and non-technical ones.  We want people to understand them
+and follow a few good practices for their packages.
 
-The official requirements list is at
-<https://savannah.gnu.org/register/requirements.php>.
-This page explains the points in more details.
+This page explains the points of [our official
+requirements](//savannah.gnu.org/register/requirements.php) in more
+details.
 
-Check-list
-----------
+## Checklist
 
-Here is a compliance check-list, and links to further explanations.
+See [[HowToGetYourProjectApprovedQuickly]].
 
-Read them and follow them to get your project approved quickly :).
+## General principles
 
--   Make sure your project runs primarily on a completely free OS.
--   Use a license compatible with the GNU GPL.
--   Write a half-page technical description of your project: its goal,
-    its programming language and its depencies (with
-    [[URIsToTheDependencies]]).
--   Don't forget to give a pointer to the source code.
--   Apply valid copyright and license notices ([[ValidNotices]]), and
-    include a copy of the license you chose.
--   Refer to the GNU/Linux operating system and reserve the name "Linux"
-    for referring specifically to the kernel that Linus wrote. More
-    info:
-    <http://www.gnu.org/gnu/gnu-linux-faq.html>.
--   Talk about the free software movement, which we support, and not
-    open source, which we don't. Do not use "Open" in your project name.
-    More info:
-    <http://www.gnu.org/philosophy/open-source-misses-the-point.html>.
-
-The review we do can be long and tedious for both the submitter and the
-reviewer. Be sure to follow these steps; if your project doesn't comply
-with our requirements, we will ask you to make changes to your project
-or register again. This ensure a consistent level of quality and policy
-for projects hosted at Savannah.
-
-General principles
-------------------
-
 -   [[WhyLegalChecksBeforeRelease]]: solid legal basis are one of free
     software's strengths.
 -   [[RequirementThreshold]]: will we nitpick? Yes! But here are some
@@ -52,13 +23,8 @@
 -   [[FileFormats]]
 -   [[ReverseEngineering]]
 
-Related FAQ
------------
+### Links
 
--   [[WhatIsTheStatusOfMyProjectRegistration]]
-
-#### subtopics:
-
 -   [[AboutTranslations]]
 -   [[ApprovingSubmission]]
 -   [[FileFormats]]
@@ -86,30 +52,15 @@
 -   [[UpstreamCollaboration]]
 -   [[WhyLegalChecksBeforeRelease]]
 
-For Administrators
-==================
+### Pinged message
 
-Pinged message
---------------
+If the submitter of a new project for approval didn't answer after a
+week or two, the admin will to send a pinged message.
 
-If after one week, the submitter of a new project for approval didn't
-answer, the admin need to send a pinged message. The pinged message can
-be founded in [savannah.el|vim] as sv-pinged() under emacs and
-SV\_pinged() under vim.
+### Zombie groups
 
-Zombie projects
----------------
-
-When projects are removed from the tracker but not from the database,
-they stay there and increase the "pending projects" frontpage
-statistics. To find such projects, a good heuristic is:
-
-    SELECT groups.group_id, unix_group_name, groups.status, task.bug_id, 
task.status_id, groups.group_name FROM groups, task WHERE groups.status='P' AND 
task.group_id=5802 AND task.status_id=3 AND task.category_id=1 AND task.details 
LIKE CONCAT("%* System Name:  *", groups.unix_group_name, "*%") AND (SELECT 
count(*) FROM task WHERE task.group_id=5802 AND task.status_id=1 AND 
task.category_id=1 AND task.details LIKE CONCAT("%* System Name:  *", 
groups.unix_group_name, "*%")) = 0 GROUP BY groups.group_id ORDER BY bug_id;
-
-    DELETE groups FROM groups, task WHERE groups.status='P' AND 
task.group_id=5802 AND task.status_id=3 AND task.category_id=1 AND task.details 
LIKE CONCAT("%* System Name:  *", groups.unix_group_name, "*%") AND (SELECT 
count(*) FROM task WHERE task.group_id=5802 AND task.status_id=1 AND 
task.category_id=1 AND task.details LIKE CONCAT("%* System Name:  *", 
groups.unix_group_name, "*%")) = 0;
-
-It only fails if the group name was changed after the submission, or if
-a user maliciously fakes a submission item.
-
-A better solution would be to add a 'task\_id' field in the 'groups'
-table, filled in at registration time.
+When submissions are cancelled in the tracker, but the groups not
+removed from the database, they stay there and increase the "pending
+registrations" frontpage statistics. To find such projects
+visit /siteadmin/grouplist.php?status=P and compare with pending
+groups in the task tracker.