I've tried to contact Paul Hatcher myself on several occasions. No
Responce.
This has been a problem for me for a while. I gave up contributing to
NHibernate Search due to the lack of any sort of presence.
On Dec 27, 4:57 pm, Stephen Bohlen <
sboh...@gmail.com> wrote:
> Patrick:
>
> AFAIK the SVN repo is still authoritative for this project.
>
> re: who is 'in charge' of it, I have recently reached out the the present
> project lead (Paul Hatcher) in an attempt to gauge his continued interest in
> playing the role of project lead for the NHSR project. Thus far, I haven't
> rec'd any response from Paul either way.
>
> If we don't hear back from the present NHSR project lead by the end of the
> year that he is interested in remaining as the NHSR project lead, we will
> probably need to either:
>
> - find someone else in the community willing to act as the project lead
> for NHSR in Paul's place
> - remove NHSR from NHContrib and set it somewhere 'less official'
>
> To my mind, having a project in NHContrib does confer some responsibility on
> the project lead to ensure that its trunk remains compatible with recent NH
> releases and that binaries are provided that are compatible with each GA
> release of NH. Adopters of NHContrib projects have a (reasonable)
> expectation that the projects will remain synced with NH. Recently, this
> cannot quite seem to be said for NHSR, as you are pointing out. Though a
> patch was recently submitted to address this specific issue (NH
> compatibility) note that as yet there is still not an NH3-related release
> binary of NRSR (
http://sourceforge.net/projects/nhcontrib/files/)
>
> For NHContrib to retain its meaning and value to consumers of NH proper, I
> think we need to do everything possible to ensure that the projects that are
> within that 'umbrella' collection are active, maintained, etc. We probably
> need to be more proactive at periodically reviewing the contents of
> NHContrib to ensure that it doesn't become a collection of "abandon-ware"
> but contains vibrant projects that are actively maintained and kept in-sync
> with the main NH project. This is one of the reasons that the NHBurrow
> project was recently removed from NHContrib (no desire from anyone to
> lead/maintain it).
>
> All that said, if you want to open a JIRA issue on this (specific)
> compatibility issue and submit a patch, it would go a long way to helping
> *whomever* ultimately takes responsibility for NHSR as project lead (Paul or
> otherwise).
>
> In a related matter, we should also recall that the (ultimate) future of
> NHSR is actually even more tenuous given the possible deprecation of
>
LUCENE.NET as an Apache project (seehttp://
groups.google.com/group/nhusers/browse_thread/thread/6689418b1...
> more info).
>
> Hope this helps clarify the status of this project.
>
> Steve Bohlen
> sboh...@gmail.comhttp://blog.unhandled-exceptions.comhttp://
twitter.com/sbohlen