[Savannah-dev] [bugs #7380] Reassigned item: Another "spam" message in one of bugs

[Mathieu Roy]

This mail is an automated notification from the bugs tracker
 of the project: Savane at Savannah.

/**************************************************************************/
[bugs #7380] Latest Modifications:

Changes by: 
                Mathieu Roy <address@hidden>
'Date: 
                ven 16.07.2004 à 13:28 (Europe/Paris)

            What     | Removed                   | Added
---------------------------------------------------------------------------
            Category | None                      | Web Frontend
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
Savannah development, now renamed Savane, continues at
https://gna.org/p/savane 

Bug reports should be submitted to the bug tracker where he
stands now at https://gna.org/bugs/?group=savane 
Check there if the bug you noticed/feature you'd like to use is
not already registered.







/**************************************************************************/
[bugs #7380] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=7380>
Project: Savane at Savannah
Submitted by: Earl Hood
On: jeu 22.01.2004 à 15:47

Category:  Web Frontend
Severity:  3 - Ordinary
Priority:  1 - Later
Resolution:  None
Assigned to:  None
Status:  Closed
Fixed Release:  
Affected release:  


Summary:  Reassigned item: Another "spam" message in one of bugs

Original Submission:  
It has happened again, someone has created a "spam"
comment in a (closed) bug for my project, MHonArc,
(http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=4719&group_id=1968)

I request that offending comment be removed.

This is the second incident with my project, and I
wonder if the Savannah team is considering ways
to prevent or minimize this problem.

Follow-up Comments
------------------


-------------------------------------------------------
Date: ven 16.07.2004 à 13:28        By: yeupou
Savannah development, now renamed Savane, continues at
https://gna.org/p/savane 

Bug reports should be submitted to the bug tracker where he
stands now at https://gna.org/bugs/?group=savane 
Check there if the bug you noticed/feature you'd like to use is
not already registered.


-------------------------------------------------------
Date: jeu 22.01.2004 à 15:47        By: yeupou
This item has been reassigned from the project Savannah support tracker to your 
tracker.

The original report is still available at support #102613

Following are the information included in the original report:

[field #0] <font class="preinput"><font class="help" title="Unique item 
identifier">Item ID: </font></font> 102613<br>[field #1] <font 
class="preinput"><font class="help" title="Unique project identifier">Group ID: 
</font></font> 11<br>[field #2] <font class="preinput"><font class="help" 
title="Current Status">Status: </font></font> Open<br>[field #3] <font 
class="preinput"><font class="help" title="Impact of the item on the system 
(Critical, Major,...)">Severity: </font></font> 3 - Ordinary<br>[field #4] 
<font class="preinput"><font class="help" title="Generally high level modules 
or functionalities of the software (e.g. User interface, Configuration Manager, 
etc)">Category: </font></font> Web Frontend<br>[field #5] <font 
class="preinput"><font class="help" title="User who originally submitted the 
item">Submitted by: </font></font> ehood<br>[field #6] <font 
class="preinput"><font class="help" title="Who is in charge of handling the 
item">Assigned to:
</font></font> None<br>[field #7] <font class="preinput"><font class="help" 
title="Date and time of the initial submission">Submitted on: </font></font> 
Wed 11/19/03 at 20:23<br>[field #8] <font class="preinput"><font class="help" 
title="One line description of the item">Summary: </font></font> Another "spam" 
message in one of bugs<br>[field #9] <font class="preinput"><font class="help" 
title="Full description of the item">Original Submission: </font></font> <br />
It has happened again, someone has created a "spam"
<br />
comment in a (closed) bug for my project, MHonArc,
<br />
(http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=4719&group_id=1968)
<br />

<br />
I request that offending comment be removed.
<br />

<br />
This is the second incident with my project, and I
<br />
wonder if the Savannah team is considering ways
<br />
to prevent or minimize this problem.<br>[field #11] <font 
class="preinput"><font class="help" title="Characterizes the nature of the item 
(e.g. Crash Error, Documentation Typo, Installation Problem, etc">Item Group: 
</font></font> None<br>[field #12] <font class="preinput"><font class="help" 
title="Current resolution of the item">Resolution: </font></font> 
None<br>[field #13] <font class="preinput"><font class="help" title="Version of 
the System Component impacted by the item">Component Version: </font></font> 
None<br>[field #14] <font class="preinput"><font class="help" title="Name and 
version of the platform impacted by the item">Platform Version: </font></font> 
None<br>[field #15] <font class="preinput"><font class="help" title="How easy 
it is to reproduce the item">Reproducibility: </font></font> None<br>[field 
#16] <font class="preinput"><font class="help" title="Estimated size of the 
code to be developed or reworked to handle the item">Size (loc):
</font></font> None<br>[field #17] <font class="preinput"><font class="help" 
title="Release in which the item was actually implemented">Fixed Release: 
</font></font> None<br>[field #18] <font class="preinput"><font class="help" 
title="Release in which it is planned to have the item implemented">Planned 
Release: </font></font> None<br>[field #19] <font class="preinput"><font 
class="help" title="Number of hours of work needed to handle the item">Effort: 
</font></font> 0.00<br>[field #23] <font class="preinput"><font class="help" 
title="How quickly the item should be implemented (Immediate, Normal, Low, 
Later,...)">Priority: </font></font> 1 - Later<br>[field #26] <font 
class="preinput"><font class="help" title="">Percent Complete: </font></font> 
0%<br>[field #28] <font class="preinput"><font class="help" title="Release 
(global version number) impacted by the item">Release: </font></font> 
None<br>[field #53] <font class="preinput"><font class="help"
title="Customizable Select Box (pull down menu with predefined values)">Custom 
Select Box #1: </font></font> None<br>[field #54] <font class="preinput"><font 
class="help" title="Customizable Select Box (pull down menu with predefined 
values)">Custom Select Box #2: </font></font> None<br>[field #55] <font 
class="preinput"><font class="help" title="Customizable Select Box (pull down 
menu with predefined values)">Custom Select Box #3: </font></font> 
None<br>[field #56] <font class="preinput"><font class="help" 
title="Customizable Select Box (pull down menu with predefined values)">Custom 
Select Box #4: </font></font> None<br>[field #57] <font class="preinput"><font 
class="help" title="Customizable Select Box (pull down menu with predefined 
values)">Custom Select Box #5: </font></font> None<br>[field #58] <font 
class="preinput"><font class="help" title="Customizable Select Box (pull down 
menu with predefined values)">Custom Select Box #6: </font></font> 
None<br>[field
#59] <font class="preinput"><font class="help" title="Customizable Select Box 
(pull down menu with predefined values)">Custom Select Box #7: </font></font> 
None<br>[field #60] <font class="preinput"><font class="help" 
title="Customizable Select Box (pull down menu with predefined values)">Custom 
Select Box #8: </font></font> None<br>[field #61] <font class="preinput"><font 
class="help" title="Customizable Select Box (pull down menu with predefined 
values)">Custom Select Box #9: </font></font> None<br>[field #62] <font 
class="preinput"><font class="help" title="Customizable Select Box (pull down 
menu with predefined values)">Custom Select Box #10: </font></font> None<br>

-------------------------------------------------------
Date: ven 21.11.2003 à 20:53        By: ehood

The button idea may be useful.

Unfortunately, and I believe other projects are similiar,
any changes to a bug is sent to a mailing list.  Therefore,
bug comments can be used to send out spam to people mailboxes.

You may want to consider some form of approval process for
comments, with varying levels of approval.  For example,
the default is current behavior.  Other choices for project
admins could be:

* Anonymous user submissions require approval.  Registered
  users of savannah can submit comments as normal.
* All submissions require approval.  Exceptions are
  project administrators and developers (which you could
  possibly define "approval" status individually).

-------------------------------------------------------
Date: ven 21.11.2003 à 20:53        By: ehood

The button idea may be useful.

Unfortunately, and I believe other projects are similiar,
any changes to a bug is sent to a mailing list.  Therefore,
bug comments can be used to send out spam to people mailboxes.

You may want to consider some form of approval process for
comments, with varying levels of approval.  For example,
the default is current behavior.  Other choices for project
admins could be:

* Anonymous user submissions require approval.  Registered
  users of savannah can submit comments as normal.
* All submissions require approval.  Exceptions are
  project administrators and developers (which you could

-------------------------------------------------------
Date: ven 21.11.2003 à 09:09        By: yeupou

It is possible to imagine a button to allow manager of a 
tracker to hide a useless comment. This one would be kept 
in the database and accessible by a click in the details 
of an item (such as a bug), but not fully printed inside 
the detail. 
 
 












For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=7380>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/