Understood; there are really two orthogonal issues going on here: short-term getting NHSearch working again w NH3 and long-term the future shepherding of NHSearch.
I will look into the repo perms this evening and let you know once I've got it resolved for you. Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Mon, Jan 10, 2011 at 4:28 PM, Patrick Earl <[email protected]> wrote: > I tried committing and was forbidden. I'd be happy to commit my > changes to at least get things building again. I don't use it, so I > shouldn't volunteer to maintain it, nor can I really comment on its > future viability. > > Patrick Earl > > On Mon, Jan 10, 2011 at 2:07 PM, Stephen Bohlen <[email protected]> wrote: > > If you don't have the needed perms, I believe that I can grant that for > > you. Why don't you attempt and let me know your results? > > > > However, there is a larger issue/concern about a project remaining in > > NHContrib without an (active) project lead taking responsibility for > > maintaining it (even only in re: ensuring ongoing compatibility with the > > future evolution of NH and/or other dependencies like Lucene.NET in this > > case) or else the whole of NHContrib risks withering and becoming a > 'dumping > > ground' for inactive projects with NH dependencies. > > > > Steve Bohlen > > [email protected] > > http://blog.unhandled-exceptions.com > > http://twitter.com/sbohlen > > > > > > On Mon, Jan 10, 2011 at 3:55 PM, Patrick Earl <[email protected]> wrote: > >> > >> I'm capable and willing to apply the changes I mentioned (compilation > >> fixes and migration to new logger). I do not believe I have > >> permission to commit to the repository, though I haven't actually > >> tried. > >> > >> Patrick Earl > >> > >> On Mon, Jan 10, 2011 at 1:17 PM, Stephen Bohlen <[email protected]> > wrote: > >> > Patrick: > >> > > >> > Are you personally (technically) capable of making these proposed > >> > changes to > >> > NHSearch? If so, what is your present blocker? Permissions in the > repo > >> > to > >> > actually apply the patch(es) needed? Or otherwise? > >> > > >> > Steve Bohlen > >> > [email protected] > >> > http://blog.unhandled-exceptions.com > >> > http://twitter.com/sbohlen > >> > > >> > > >> > On Mon, Jan 10, 2011 at 3:13 PM, Patrick Earl <[email protected]> > wrote: > >> >> > >> >> At this point it seems like Paul is unresponsive. How do we proceed > >> >> forward with this? While I don't use NHibernate.Search personally, > >> >> I'd at least like to get it compiling and using the new log > >> >> infrastructure in NHibernate 3.0. Right now it's causing some build > >> >> troubles for ActiveRecord. > >> >> > >> >> Patrick Earl > >> >> > >> >> On Tue, Dec 28, 2010 at 1:46 PM, Andrew Smith <[email protected] > > > >> >> wrote: > >> >> > 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 <[email protected]> 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 > >> >> >> > >> >> >> > >> >> >> [email protected]http://blog.unhandled-exceptions.comhttp:// > twitter.com/sbohlen > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> On Sun, Dec 26, 2010 at 9:07 PM, Patrick Earl <[email protected]> > >> >> >> wrote: > >> >> >> > NHibernate.Search is used by Castle.ActiveRecord, but it hasn't > >> >> >> > been > >> >> >> > upgraded to the new logging infrastructure yet, which is causing > >> >> >> > dependency problems. Is the SVN repository the official > location > >> >> >> > for > >> >> >> > this still? Is there somebody around that has authorization to > >> >> >> > make > >> >> >> > changes to it? I'm a bit lost trying to find info on this > >> >> >> > project. > >> >> >> > >> >> >> > Patrick Earl > >> >> > > >> > > >> > > > > > >
