On 4/16/11 8:40 AM, Robert Bradshaw wrote:
Quite honestly, when have a bug to report, if I can't finish the
transaction right away then it's unlikely I'll go through the hoops
and report the bug later (unless the bug is really important). This is
especially true if I have to wait for a human to enter the loop, so we
want to have the barrier as low as possible.
+1
Ideally, anyone could file a bug on trac (or a similar system), and
only after they're moderated do they become visible. After a number
(maybe even one) ticket is accepted, the moderation would then be
lifted. Another option would be to only allow automatic account
creation for emails seen on sage-[devel|support], which could be
easily automated, perhaps with email verification (a link sent out).
Does anyone know if trac can be set up like that? +1 to a
sage-trac-admin group which could easily handle the rest. The hurdle
to jump would be someone else vouching for them or a bug to report or
an (intelligent) comment/fix to an existing bug, which is why anyone
would want an account anyways. I really don't think the bar needs to
be raise that high to filter out the spammers--I don't think we're big
enough to attract more than the semi-automated shotgun-approach
attack.
How about this plugin:
https://software.sandia.gov/trac/fast/wiki/TicketModerator
and/or this:
http://trac.edgewall.org/wiki/SpamFilter
I agree with Robert that a moderation approach is better than a huge
waiting period to get a trac account. After a person is moderated once
or twice with decent bug reports, they could be added to the
non-moderated users.
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
