You'll probably make more money and reputation by blogging about all the changes you have to do and things you discover than from a final version of a book..... ;-)
And it might be more discoverable as well. At least until I get my directory up :-) Regards, Alex. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 3 March 2017 at 17:36, Marco Reis <[email protected]> wrote: > I'm writing a book about Lucene and text processing in Portuguese (ok, maybe > I'm masochist) and I can say the evolution is really fast. I started in > version 5 and I had to update to version 6. Now I have 60% ready, but we are > in version 6.4 and going on... > > > > > Marco Reis > Software Architect > http://marcoreis.net > https://github.com/masreis > +55 61 981194620 > > 2017-03-03 15:32 GMT-03:00 Christine Poerschke (BLOOMBERG/ LONDON) > <[email protected]>: >> >> Somewhat related, any thoughts on combining the two 'How to Contribute to >> ...' wiki pages into a unified 'How to Contribute' under lucene.apache.org >> itself? >> >> https://wiki.apache.org/lucene-java/HowToContribute >> https://wiki.apache.org/solr/HowToContribute >> >> ----- Original Message ----- >> From: [email protected] >> To: [email protected] >> At: 03/03/17 17:31:10 >> >> (not directly relevant to the topic, but I do have an empty >> https://github.com/arafalov/solr-contributor-guide ....) >> >> The problem with writing the book for Lucene/Solr is that the project >> moves too fast for conventional print time. I kept having to rewrite >> first 3 chapters completely because of the rapid changes. >> >> If anybody is masochistic, I would recommend taking a smaller slice of >> the project and writing about that in an intense spike and >> self-publishing. I could offer a couple of Solr titles that I have on >> the back-burner ..... >> >> Regards, >> Alex. >> P.s. There are no developer guides. Worse, there are no "pain point >> guides either". Perhaps if somebody started the "pain-points" one, we >> could then build the "developer guide" on top of it. >> P.p.s. There is a "working with git for Lucene/Solr repo" guide >> somewhere actually. But that's different. Also, consider using a >> shallow git clone when getting the repo. Latest Git still allows to >> commit from that and you may save yourself some significant >> bandwidth/disk space. >> >> ---- >> http://www.solr-start.com/ - Resources for Solr users, new and experienced >> >> >> On 3 March 2017 at 11:26, Doug Turnbull >> <[email protected]> wrote: >> > As an aside, I'm pretty sure if anyone wanted to write a new edition of >> > Lucene in Action, and you're masochistic enough to write a book for a >> > top >> > tier tech book publisher, I'd be happy to introduce you to someone at >> > Manning :) >> > >> > And Lucene In Action is a very good read, will help you get the big >> > ideas, >> > even if the examples are outdated >> > >> > -Doug >> > >> > On Fri, Mar 3, 2017 at 11:23 AM David Smiley <[email protected]> >> > wrote: >> >> >> >> Hi, >> >> There is no developer's guide. There are Javadocs, and there's an >> >> outdated book (although the concepts are still good but it's the >> >> details >> >> that have changed). >> >> ~ David >> >> >> >> On Fri, Mar 3, 2017 at 11:16 AM Nilesh Kamani <[email protected]> >> >> wrote: >> >>> >> >>> Could anybody please help me with this ? >> >>> >> >>> On Wed, Mar 1, 2017 at 9:22 AM, Nilesh Kamani >> >>> <[email protected]> >> >>> wrote: >> >>>> >> >>>> Hello All, >> >>>> >> >>>> Are there any Developer's Guide to understand various packages and >> >>>> classes and their role ? >> >>>> I am looking to modify boolean AND search to meet some specific >> >>>> criteria. >> >>>> >> >>>> Thanks, >> >>>> Nilesh Kamani >> >>>> >> >>>> >> >>> >> >> -- >> >> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker >> >> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: >> >> http://www.solrenterprisesearchserver.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
