On Wednesday 27 December 2006 01:38, Erik Hatcher wrote:
> I'd be surprised if anyone uses Lucli, given the limited utility it
> has versus using Luke.
It's actually very useful if you only have ssh access to a machine that has
no X11 running. I just fixed the small bug found by this review.
Brian Chess <[EMAIL PROTECTED]>
Date: Mon, 18 Dec 2006 21:16:06 -0800
To:
Conversation: access policy for Java Open Review Project
Subject: access policy for Java Open Review Project
Hi all, I've been busy creating JOR accounts this weekend, and it
was cool to
see so many names from L
nalysis.
Happy holidays,
Brian
> From: Brian Chess <[EMAIL PROTECTED]>
> Date: Mon, 18 Dec 2006 21:16:06 -0800
> To:
> Conversation: access policy for Java Open Review Project
> Subject: access policy for Java Open Review Project
>
> Hi all, I've been busy creatin
Brian Chess wrote:
My question is, would you like to allow outsiders to go through results and
help sort the real bugs from the chaff?
That's up to you. It's your service, not governed by the Apache Lucene
project. If you cause your system to add reasonable issues to our
bug-tracking system
: application vulnerable or is really just a "ruckus" issue? Part of
: me thinks that b/c the code is freely available, people could find
: the security issues anyway, so we aren't really protecting ourselves
: anyway by denying access.
Personally I agree ... if the source is free, all exposing
On Dec 19, 2006, at 12:16 AM, Brian Chess wrote:
My question is, would you like to allow outsiders to go through
results and
help sort the real bugs from the chaff? The upside is that
volunteers may
perform useful work and that it may be another avenue to get people
involved
with the co
Hi all, I've been busy creating JOR accounts this weekend, and it was cool
to see so many names from Lucene. Lucene, Solr, and Nutch have the lowest
defect rates among the projects we've looked at, and I'm beginning to see
why.
One of the things JOR is doing is inviting people to come and help re
