1. I'd agree that the current docs are great. I wonder what a book would be.
2. fwiw, friends who have written/edited tech books have said this: you basically get paid nearly nothing / a vanity fee for your book. it works out to less than minimum wage. the terms get better as you work with a publisher more. once you do a few books, it becomes worth it. 3. it's too hard to say this delicately, so i'm going to send the blunt statements to address Mike's points about Django docs to him personally. publicly... i think the bulk of django users I've met would largely be scared of pyramid and not care for it. and that is simply because they program in "Django" not "Python". it's a similar phenomena to how many people program in "Rails" and not "Ruby". The full-service frameworks have attracted a following of people who pick up the frameworks but not the language -- and the level of behind-the- scenes magic + coding style keep people from really using the actual language. coding in many of these frameworks is more like configuring an XML file than writing a program. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
