On 6/13/07, Sander Temme <[EMAIL PROTECTED]> wrote:
Rich Bowen wrote:
> I wonder, also, whether it would be possible to run solr, since it's
> actually an Apache project. However, having never had any success
> getting it working on my own servers, that might be a can of worms.
Firmly +1 on dogfooding. If *we* can't get Solr to work, who can? I
mean it's our project, right? Even if it's from the Java Weenie side?
I have no problem at all with that, providing someone is willing to
take charge, drive it through to completion, and assure it is
maintained for some period of time. My primary concern is with giving
our users the best possible search. Our experience with running our
own search engines on *.apache.org has been mixed at best.
Regarding Google, who's making the money from the searches? I came
across a $100M figure that Firefox is making from the search box in the
browser. While we'd obviously not be flying that high, would the ASF be
entitled to any such revenue from our own search box, or the individual
who happens to own the account?
With our current search box, all the revenue is going to google. With
CSE, since we qualify as a non-profit, we can eliminate adds entirely.
(Or we can probably participate in their revenue sharing thing if we
want; but again, that adds complication that I'm not looking for at
the moment.)
With regards to who could access the account, it would actually be all
apache comitters I believe. We could choose different access control
if we wanted, but I don't think it is a big deal. (We just don't want
anyone switching it to point to playboy.com... Or maybe we do...)
With regards to 1.3 having too much weight, I would setup a separate
search engine for each version. (I would probably also include the
wiki in all the versions.)
Regarding google or some other public search engine, we already use
google and they have a relatively easy system that doesn't show adds
(and therefore earns them no direct revenue), so I don't really see
any conflict.
(Boy, I didn't think this was going to be that complicated an issue ;-)
Joshua.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
