A random thought.
Have a "Scheduler" at boinc.ssl.berkeley.edu.
Have the users that want to work on TRAC actually attach to the Project.
Now you have the CPID and can look up the CobbleStone contribution of those
users for all projects.
Set a minimum contribution for the creation of a TRAC ticket. (Perhaps
10,000 CS).
Or possibly base it on enrolment in BOINC Alpha test - with a minimum CS
contribution there (maybe 10).
jm7
Eric Myers
<[email protected]
et> To
Sent by: David Anderson
boinc_dev-bounces <[email protected]>
@ssl.berkeley.edu cc
BOINC Developers Mailing List
<[email protected]>
08/18/2009 02:37 Subject
PM Re: [boinc_dev] trac spam
On Tue, 18 Aug 2009, David Anderson wrote:
>
> We're looking at upgrading to the current version of trac (0.11)
> which may have better spam-prevention features.
If the newer Trac does not prevent this, another way to prevent such spam
is to require some kind of approval for creating new Trac accounts, so
that the spammers cannot do so, but legit users can. Hopefully the
permission to do so could be delegated to a few volunteers, to keep from
adding work load to the core developers. One would hope it would be less
work than what it takes now for the people who are kindly cleaning up the
spam.
The drawback to that would be that it adds an extra barrier to getting
information and contributions from people who are willing to help. But
hopefully the barrier would be small enough not to scare them away, but
large enough to keep the spammers out.
Another possible way to handle it is an intermediate reporting form, like
the one I set up for I2U2: http://www.i2u2.org/HelpDeskRequest.php It
collects all the info needed to create a ticket, but it does not create a
ticket. It sends the report to a very short mailing list, and can also
post to a BOINC forum. If and only if the issue is worthy of a ticket in
our bugzilla then someone on our team creates the ticket, not the
reporting user. But they can do so easily with the info collected, while
editing appropriately.
Anonymous requests are allowed, provided the user solves a RECAPTCHA. If
you are already logged in to the site (based on BOINC) then it
automatically fills in the user user info and posts to the forum under
your name.
I can share the code for it if someone wants to modifiy it for
BOINC alpha or however, but I'm afraid I don't have time (or awake brain
cells) to do that right now.
-Eric
--
Eric Myers <[email protected]> 503-564-4169
PGP Key #6E2D2259/RSA: BA39 1D46 5EC3 0D59 C2AC 6FCB F920 4DC8
PGP Key #E519EAC3/DSS: D15B 9A50 B1ED 2947 EC29 B0F6 EA61 FB6E E519 EAC3
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
