http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109





------- Additional Comments From [EMAIL PROTECTED]  2006-04-10 14:11 -------
> ------- Additional Comments From [EMAIL PROTECTED]  2006-04-04 11:28 -------
> Dude, you didn't "request time to review" -- you "suggested" that people 
> should
> "exercise caution and review time".  It was not clear that *you* were
> the person you wanted to exercise that review time! ;)

Perhaps I should have been more forceful in the request but its almost like
you're rushing to get the code in before anyone else can review, whats the
hurry?  Why can't we all work together to get a better handle on the optimal
solution?

> Also your first comment was 2 weeks after the patch was posted, saying "I'm 
> not
> vetoing the patch but am a little concerned".  So I took that as not 
> indicating
> a whole lot of worry.

Well, my first comment was to back up Theo's objection and near as I can tell
still outstanding veto right after the patch was posted.  Apparently, a veto
doesn't mean as much these days since clearly you ignored that one and don't
seem to be respecting mine.
 
> It is nice to support proprietary work in Apache SpamAssassin, but not to the
> detriment of the open-source product's quality.

How about hackish code at the detriment?  You've used the "lets not screw folks
using the code" argument more times than I can count.  If you seriously want
other implementations (and believe me I'm working on getting as much closed code
opened up as I can) then screwing them over certainly isn't the best path there.
 You of all people should realize that.

However, since feeding my family has taken precedence and I just don't have time
to offer alternative implementations, I'll remove my veto (since it was being
ignored anyway) but still register a -1 for the code as implemented.

I'll also note that folks who provide results for scoring should not be running
this code, it will seriously hamper our efforts to provide realtime hits in the
reuse code.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to