[Savannah-cvs] [495] minor updates, improve wordings

[ineiev]

Revision: 495
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=495
Author:   ineiev
Date:     2023-01-19 03:32:57 -0500 (Thu, 19 Jan 2023)
Log Message:
-----------
minor updates, improve wordings

Modified Paths:
--------------
    trunk/sviki/FightingSpam.mdwn

Modified: trunk/sviki/FightingSpam.mdwn
===================================================================
--- trunk/sviki/FightingSpam.mdwn       2023-01-03 06:47:18 UTC (rev 494)
+++ trunk/sviki/FightingSpam.mdwn       2023-01-19 08:32:57 UTC (rev 495)
@@ -11,22 +11,21 @@
 unless the real volume of spam you get is high.
 
 Savane can run checks against DNS blacklists on all forms submitted
-by non-project members (NB: not activated at Savannah).
+by non-group members (NB: not activated at Savannah).
 
-Apart from that, there are a few options that can allow a project admin
+Apart from that, there are a few options that can allow a group admin
 to prevent spam.
 
-Spam is usually generated by anonymous robots.
-
 * A starting point to avoid spam is first to set
 tracker *Posting Restrictions* to a tough policy:
-  - On every tracker that you feel dedicated to manage the project workflow,
+  - On every tracker that you feel dedicated to manage the group workflow,
   without end user's interaction, like the task tracker, set
-  _project membership_ as the minimal level of authentication.
+  _group membership_ as the minimal level of authentication.
   - On every tracker that need input from non-members, like the support
   tracker and the bug tracker, set _logged-in user_ as the minimal
   authentication level (it means that external contributors will have to create
-  an account).
+  an account).  As of 2022, most spam comments come from logged-in users,
+  though.
 
 * Another idea is too use the special *Lock Discussion* field. This field,
 that can be modified only by tracker managers, is complementary to the
@@ -35,7 +34,7 @@
 end a flamewar, it will obviously reduce the number of targets available to
 spam robots if you set one (or more) automatic transition update so whenever
 an item is closed, the item get additionnally locked. Obviously, this is
-useless on trackers where only project members can post.
+useless on trackers where only group members can post.
 
 ## Automatically Checking Potential Spam
 
@@ -51,18 +50,16 @@
 
 ### Spam Scores
 
+Any logged-in user is able to *flag as spam* comments and items that the user
+believes to be spam. This will increment the spam score of the item.
 
-Any logged-in user is able, when he sees content (comment or item) that he
-believes to be spam, to *flag it as spam*. This will increment the spam score
-of the item.
+* If the reporter is _group admin_ on which the suspected spam have been
+posted, the spam score of the post will grow of 5.  If the reporter is
+a _member_ of the group on which the suspected spam have been posted, the spam
+score of the post will grow of 3.  If the reporter is _not member_
+of the group on which the suspected spam have been posted, the spam score
+of the comment will grow of 1.
 
-* If the reporter is _project admin_ on which the suspected spam have been
-posted, the spam score of the content will grow of 5.  If the reporter is a
-_project member_ on which the suspected spam have been posted, the spam score
-of the content will grow of 3.  If the reporter is _not project member_ on
-which the suspected spam have been posted, the spam score of the content will
-grow of 1.
-
 Any item with a spam score greater than 4 is considered to be spam.
 
 All users also have their own spam scores.  When users get one of their posts
@@ -76,8 +73,8 @@
 actions accordingly (like removing accounts used to post spam or to mark
 valid posts as spam).
 
-It is also possible for project admins and site admins to unflag posts, which
-means they can reset the spam score of some content if they think there is a
+It is also possible for group admins and site admins to unflag posts, which
+means they can reset the spam score of some post if they think there is a
 mistake.
 
 ### Removing Spam