If there is (real) interest in doing anything about the state of Lucene.NET, I would really recommend beginning a conversation about your ideas with the ASF. This discussion here about different ways to 'rejuvinate' the Lucene.NET proeject's codebase, while useful (if it eventually leads to actual action on someone's part), sadly won't help that project remain viable in the eyes of the ASF. If there's impetus to act, then I would recommend reaching out to the ASF about all of your ideas, committments, etc. to begin a conversation with them about the project's viability ASAP (unless its already too late in their eyes since that thread I listed in the initial post to this thread seems to (still) have no response since OCT 2010 as far as I can tell). There are (at least) two issues we are conflating here: 1. What is the future of Lucene.NET (which we cannot entirely answer in this forum) 2. What can NHSEARCH do to mitigate its dependency on another OSS project with an unclear future? The 'private fork' Fabio has created seems to have addressed #2 (for the time being at least) but #1 can't be addressed/resolved here and efforts to do so need to be directed to the ASF and the 'official' Lucene.NET project team before its too late to 'save' Lucene.NET from becoming abandon-ware. -Steve B.
-- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
