
brianm at apache
May 10, 2005, 5:14 AM
Post #3 of 5
(2828 views)
Permalink
|
|
Re: Helping PyLucene and RubyLucene incubate
[In reply to]
|
|
The ruby part of it is from scratch, but I am using Andi's work extensively, and it relies on that work for all practical purposes. I'd be quite comfy going through the incubator, or not -- whichever people are comfortable with. Andi's work can be an external dependency (the licensing is fine). I still like the idea of a "Native Ports" lucene subproject. -Brian On May 10, 2005, at 1:24 AM, Andi Vajda wrote: > > >> If the Ruby work is going to be from scratch then no incubation is >> necessary. We can give Andi and Brian M. commit privileges to a / >> ruby tree easily already to allow that to start happening. >> > > The Ruby work may be from scratch, I don't know. But the project to > incubate, > the project we've been talking about for a while now, SWIGLucene- > unless-we-come-up-with-a-better-name, would include PyLucene, not > from scratch, RubyLucene, and maybe others. > > Andi.. > > >
|