> So - I am curious what Les and other committers think about this and also > what sorts of topics folks would like to see in a book. Is anyone else > interested in attempting to undertake this sort of project? >
I'd love to do this, but I also know writing a book is a monumental undertaking. It's hard to be a CTO and write a book at the same time ;) (Not saying that it can't be done though!) One of the things that would help me better understand how valuable this would be to identify the biggest pain points that are missing from our reference manual: http://shiro.apache.org/reference.html This doc is not as robust as I would like it to be, but it is more substantial than a lot of other open-source frameworks I've been privy to. Now, this is no excuse for not making Shiro docs better of course - I'm just curious about what the community fails is missing and where they'd get the most benefit out of a book. What should be in it? Taking an example app from scratch to fully integrated? Or should it be more like the reference guide above, but a lot more substantio? I'd love to hear community feedback on what they would find valuable/desirable! Cheers, Les
