Thank you for your quick reply, Darby! When I read it could take a
maximum of 5 business days to get a CLA verified I assumed this might
be the case for the write access to the bug tracker as well, but that
was surely not the case :)
Anyhow, I believe a good CAPTCHA plugin would help a lot to prevent
spam on the issue tracker, and might very well be sufficient. Another
solution would be to filter each comment and/or report through a spam
filter. Something like Akismet[1] might work?
Regarding Atlassion JIRA I've never used it before so I have no idea
how this works, but googling around for "Atlassion JIRA captcha"
yielded some results:
- It is possible to add a CAPTCHA to the signup page to prevent
automated signups [2]
- It is also possible to search through comments and quickly identify
and delete spam [2] and [3]
- There's an article[4] discussing the issue of JIRA spam.
Hope it helps! Looking forwards to seeing a bug tracker based on Zend
Framework as the main ZF issue tracker :P
Best regards,
Johannes H. Jensen
[EMAIL PROTECTED]
[1] http://akismet.com/
[2] http://confluence.atlassian.com/display/JIRASPAM/Deleting+JIRA
+comment+spam
[3] http://blogs.atlassian.com/developer/2006/11/
fighting_comment_spam_in_jira.html
[4] http://confluence.atlassian.com/display/JIRASPAM/JIRA+Spam
On Sep 21, 2007, at 5:30 :21, Darby Felton wrote:
Hi Johannes,
Yes, sorry for the extra step of requesting access. We were forced
to do
this because spammers would sign up for an account and then post
comments with links to irrelevant sites. Many of these comments were
posted using automation once an authorized account had been
established;
perhaps a CAPTCHA plugin for comments, edits, etc. would help if one
were available?
I am not an Atlassian guru, however, and am not aware of another
method
would do a great job of preventing spam; maybe others have experiences
or suggestions that they are willing to share?
Best regards,
Darby
Johannes H. Jensen wrote:
Darby,
Thanks for your reply. I will surely post an issue for this! I
just have
to wait for the guys at Zend to get my mail and grant my account with
write-access. *sigh* Put up a spam filter?
Best regards,
Johannes H. Jensen
[EMAIL PROTECTED]
On Sep 21, 2007, at 3:28 :49, Darby Felton wrote:
Hi Johannes,
It appears to me also that the $_namespace property is not made
available. A workaround might be to extend the class and provide
such a
getter method, but in my opinion this should be built-in. Please
file a
JIRA issue for this:
http://framework.zend.com/issues/secure/CreateIssue!default.jspa
Thanks for the report!
Best regards,
Darby
Johannes H. Jensen wrote:
Hello,
Is there any way to get the namespace string of a
Zend_Session_Namespace
instance? It would be nice to have at least a getter method for
this.
Not sure if it would make any sense to have a setter though.
Unless I've overlooked something completely in the code, I'd be
happy to
add a feature request and a tiny patch for this.
Best regards,
Johannes H. Jensen
[EMAIL PROTECTED]
