We can update the book as frequently as we like. I think this is the place for announcements (there's also the Twitter feed). Aside from that, I suppose we could maintain some kind of framework roadmap document, but we don't really have a formal roadmap process, and I'm not sure there is a desire to adopt one.
Anthony On Thursday, May 23, 2013 12:47:35 PM UTC-4, Arnon Marcus wrote: > > On the contrary. I think information about testing using web2py, in > conjuction with various testing-frameworks/tools, is highly relevant in the > book, along with common testing-practices, and the way they apply when > testing with web2py. > > The book, in that case, would act as an information-centralization tool. > So it's not about the book. Its about > information-centralization/consolidation, for the sake of > research-efficiency, and prevention of duplication-of-efforts. There may be > other tools/platforms that can searve this role. > > The book might be a less-efficient way than others, in terms of how > frequent it is updated. > > I am deliberatelty refraining from specific suggestions, because the > actual solution-implementation is less important than understanding the > problem. The need is more important than the strategy for meeting it. > > Where I think a book is a terrible option, is when concearning exposure of > frequently-updating information. Say, announcement of a feature-project > that is underway, This should belong to a "news-feed", a newsletter, or > both. > > The 2 worlds might meet, say, as an announcement for additions to the > book, with links to the chapters. > > The FAQ is really old and dated, so I think it should be updated as well. > And it uses some usefull categories, that should be retargeted to a > newsfeed. > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
