Closed tshepang closed 11 years ago
anyone?
Sorry about that. I changed this to "has raised". At the moment @pauleveritt has been tasked with spending down the money contributed. I'll let him weigh in on the schedule.
By the way, Rachel Roumeliotis from O'Reilly was asking around at Pycon to see if anyone was up for writing a book about Pyramid. @stevepiercy seemed a bit interested in doing that. I wonder if @tshepang would be interested too. If either or both of you are interested you might contact her at rroumeliotis at oreilly.com .
I have a lot of interest in writing a book about Pyramid. I'd like to work with @pauleveritt and @tshepang on this effort. I assume Paul has a pretty good idea of what kind of books would be easily sold to various target markets.
I actually thought Pyramid documentation was licensed non-commercial so it can easily be sold as a book (by the copyright owner). Does the narrative documentation look unsellable? I guess it's Rachel who can answer this.
I did not mean in regards to intellectual property, but toward a book's marketability. At PyCon there were discussions about targeting specific audiences with smaller books, such as "Pyramid for Dummies", "Learn Web Application Programming with Pyramid", "Learn Python Programming with Pyramid", or one massive "Pyramid for Humans".
@mcdonc can elaborate on the discussion with Rachel. Did she express anything in particular?
The definitive guide to Pylons did pretty well to get started and understand Pylons back in time. I would be interested in participating in such effort, while I'm not the right guy to write, I can help in reviewing or other tasks.
I guess I wasn't thinking of the existing docs as something we'd like to give O'Reilly control over, and I'd be surprised if they didn't ask for at least some control. I also think it'd be useful to have a second book out in some different style.
Rachel did not say anything in particular about market.
It sounds like the first step is to have a conversation with Rachel. I will schedule a conference with her for next week. Let us start a list of questions and discussion points with her:
Nice taking the initiative. Let us do this on the mailing list (all this is out of scope for this issue report)?
So we have two things going on here:
I think the former can proceed independently of the latter, but the latter needs to be mindful of any IP issues of the former.
I propose that I take the latter item to the mailing list to get more discussion points and questions for Rachel. Then schedule a Google meetup (or whatever) with Rachel from O'Reilly so that anyone from the Pyramid community can participate while respecting her time. That should give us all more clarity about what books about Pyramid published by O'Reilly would look like. What do y'all think?
is good
Sorry for the delay in replying. Yikes, where does the time go. I was focused last Friday on writing a Substance D application.
I plan this week to get started on the ideas about overhauling the docs. My interest, and I believe the mandate for the funding drive, is to carve out some beginner-oriented, higher level "user guide" docs from the reference docs. Which fits into the tutorial I just gave.
I would like to chart out all the various possible artifacts that might be involved (a user guide, the cookbook stuff, the tutorials, links to external articles and documents, screencasts, etc.) and get with Blaise to find a more accessible entry point.
--Paul
On Mar 22, 2013, at 9:28 AM, Blaise Laflamme notifications@github.com wrote:
The definitive guide to Pylons did pretty well to get started and understand Pylons back in time. I would be interested in participating in such effort, while I'm not the right guy to write, I can help in reviewing or other tasks.
— Reply to this email directly or view it on GitHub.
On Documentation Roadmap, I see that the section In-progress and planned changes needs updating... or is the money still being raised?