Hey Tom, all, This is a great idea. I think it would help to both disseminate some deep understanding of OODT as well as how to use it more thoroughly.
Addressing your points: a) In-depth architectural overview, usage scenario, and configurability guidance for each component of OODT. Customization/ configuration code examples, especially for the many extension points across the framework. Also, articulation of undocumented "gotchas" that we developers know about but new users may not. Plus a little history of OODT would be fun. b) Definitely count me in to help with the book effort. Thanks, Rishi > On May 20, 2015, at 9:51 AM, Freeborn, Dana J (398G) > <[email protected]> wrote: > > Hi Tom, > > This is great. I would be happy to contribute to the book if my level of > experience with OODT (which is high) is helpful. It's not clear to me your > focus for the book, so you'll just have to tap me if I can contribute. Paul > and Chris will know if I do. Otherwise, I will cheer on your efforts. :-) > > Thanks, > Dana > > > From: Tom Barber <[email protected]<mailto:[email protected]>> > Reply-To: "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>> > Date: Wednesday, May 20, 2015 2:02 AM > To: "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>> > Subject: OODT book proposal > > Hi guys, > > I was on the phone to Manning today about an OODT book that me, Chris and > Mike Starch mulled over in Texas. > > I've been tasked with coming up with a TOC as the proposal so I'll knock > something together and share it later in the week, but on this topic. > > a) Does anyone have anything they'd especially like to see in an OODT book? > b) Does anyone want to help donate some hours writing a bit of the book > (won't be any time soon and takes months so don't worry about it, and I > wont hold you to it, just looking for interest) > > > Tom >
