Just a clarification. I did not write the book to make money. Not that I do not care but there are better ways to make money. Writing a book is not worth the trouble.
The book is necessary to give weight to the project. If web2py did not have a book would not have been taken seriously. The book is also important because I need to justify the time I spend in web2py. In fact, I am employed by an academic institution and they only recognize books and papers as academic work. The book does not pay me but buys me the time to continue work on web2py. Massimo On Dec 11, 11:55 am, "Yarko Tymciurak" <[email protected]> wrote: > On Thu, Dec 11, 2008 at 11:36 AM, Christophe Gragnic < > > [email protected]> wrote: > > --- En date de : *Jeu 11.12.08, mdipierro <[email protected]>* a > > écrit : > > > Not sure I understand the comment. > > > That's because I didn't say clearly what I meant, well I didn't say it at > > all. > > I understand the fact that you sell a paper book and a pdf book as > > documentation for web2py instead of publishing it freely. It's so high > > quality that it deserves some money. > > That's what I meant by "control". If the community produces docs, you can't > > sell them anymore. > > That's not necessarily true. You can control what content goes in. Even > open source docs can be sold (printed book is worth something). See (for > example) this > project:http://groups.google.com/group/python3patternsandhttp://www.bitbucket.org/BruceEckel/python-3-patterns-idioms/ > > > > > The more people want to jump on board and help the better. I do not > > particularly want to control the docs. I tend to postpone the docs until I > > consider something stable and tested. I am open to suggestions. > > > Postponing: good strategy if it's a moving target of course. The suggestion > > from Pedro is a simple wiki, what do you think? > > This is the "bottom-up" approach; Try things until something starts to feel > right, useful - then document. The other end is to document first (what > you want), and then try to implement (top-down, the document as the spec). > When you know clearly what you want to do, you start w/ top-down, and > adapt as practical implementation details cause you to make modifications. > If you have a fuzzy idea of what you want, discovery through bottom-up is > the place to start. Doing both, and meeting in the middle is useful. > > So - a wiki for documenting current state of affairs might be marginally > useful (until the code changes); A wiki of desired projects might be a > useful top-down piece. How to combine the two in an open, community way - > that's a challenge... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
