Contents
Dealing with spammers
Spam can be defined as unsolicited usually commercial messages (such as emails, text messages, or Internet postings) sent to a large number of recipients or posted in a large number of places and is prohibited (implicitly) by almost every clause in the Mageia Code of Conduct. While it's possible a new Internet user might not quite understand the finer points of online collaboration and could make an honest mistake (requiring a gentle correction), most spam that affects Mageia consists of overt commercial advertising that should be dealt with quickly and severely. Doing so appropriately depends on the system being spammed.
Bugzilla
A Bugzilla administrator can visit the admin page and search for the e-mail address (login name) of the spammer. Click on the user that shows up and add the word "spammer" to the Disable text and Real name boxes that appear, then hit Save Changes. This will block the user from logging in and being able to add further comments. Then go back and hide any spam comments that user added.
Mailing Lists
Mailing list administrators have access to remove users from mailing lists. One of the mailing list moderators can remove the spammer from all mailing lists.
TBD
Forums
TBD
Source Code Control (Git/SVN)
By the time a Mageia user gains the right to submit to our git or svn system, he/she should have shown the appropriate level of understanding of our policies and won't be committing undesired artifacts deliberately. If someone is committing garbage to our source code control systems, it is likely the user has had his/her account hacked. Have a sysadmin take the appropriate action to block the user immediately (e.g. by removing the SSH key and password hash from LDAP), then follow up to found out what happened and how to prevent it from happening again. This level of access by a hacker will require a thorough forensic examination to determine what Mageia resources were manipulated.
