On Sun, Mar 24, 2013 at 9:18 AM, Chris McDonough <[email protected]> wrote: > On Sun, 2013-03-24 at 16:39 +0100, Tamer Higazi wrote: >> Steve, >> Nobody really wants to write a book about pyramid.... If you would say >> "Zope", then I understand.
Steve wants to write a book about Pyramid. :) I would too if I had time, and probably others also. >> But honestly, the pyramid documentation is really written very good, the >> same as the django docs, that I don't see any reason to write one. >> >> Or do you have any idea to add anything in the book that is not >> mentioned in the docs (guide) ?! > > The existing docs are mostly written for an audience of people who > already know Python and web stuff. There's plenty of room for books > that don't make these assumptions. There's also plenty of room for > books that go into more depth about particular integrations of Pyramid > and other systems (e.g. SQLA, whatever). That's exactly it. Beware of the blind spot, "The docs are good enough for me, so they're good enough for everybody." *You* may have come to Pyramid with a background in Python web development, or even just Python, or just web development. Or you may be unusually talented in understanding complex reference material. The issues is not that more details need to be explained, but that the first half of the manual needs to be explained in a different way (maybe several different ways). The Pyramid docs may be the same as the Django reference docs, but still Django is touted as a framework that's "easy to learn" and Pyramid isn't. Why is that? It seems to come down to Django having so many tutorial-level docs, and books, and consultants, and the like. > > - C > > >> >> >> >> Am 23.03.2013 11:14, schrieb Steve Piercy: >> > Howdy, >> > >> > While at PyCon, an editor, Rachel Roumeliotis, from O'Reilly Media >> > informed @mcdonc that they would like to publish books about Pyramid. >> > At this point we don't have a lot of information about the potential >> > arrangement or what the books would cover. Discussion amongst Pyramid >> > folks about the matter is on GitHub. >> > >> > https://github.com/Pylons/pyramid/issues/807 >> > >> > I am collecting discussion points and questions for Rachel. Here's what >> > I have so far. >> > >> > * What kind of book about Pyramid do you think would be successful? >> > * We want the IP of Pyramid to remain the property of Agendless/"The >> > Foundation" (for lack of a better term). >> > * What level of control over the content would O'Reilly want? >> > * What level of ownership of the content would O'Reilly want? >> > * What kind of guidance would O'Reilly provide to the author(s)? >> > Editorial? Publishing? >> > >> > Please reply with any comments. >> > >> > In the next week I'll ask Rachel to schedule a Google meetup (or >> > whatever) so that anyone who has an interest in books about Pyramid can >> > participate while respecting her time. >> > >> > Thank you! >> > >> > --steve >> > >> > --steve >> > >> > > > -- > 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. > > -- Mike Orr <[email protected]> -- 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.
