On Wed, Mar 18, 2009 at 7:00 AM, Jonathan B <jonathan.b...@gmail.com> wrote:
> > On Mar 18, 2:28 pm, Baron <richar...@gmail.com> wrote: > > > If Massimo needs to publish because of academia then fair enough, but > > that doesn't prevent also making it available online. > > Most likely Massimo had to sell his copyright to the publisher, so now > it's likely that Massimo *cannot* legally give away the book for free. Please be aware you are engaging in conjecture here... and it is not accurate. > > That being said, we are creating a free & open source book right now > to help address the lack of documentation. It's going to take some > time to do, but it's on the way! There are 3 parts here: - generating content - tools to generate content & collect feedback - content area owners - guiding consistency, completeness, etc. Lots of people are asking for the end result, but there are several places to do work. Let me start with this: Who is willing and capable of taking lead for documentation wiki software? This will mean reviewing and testing, merging, making sure things work, making sure needed features (when they are big enough to warrant) are planned, and include enough people to ensure good design. Community comment and review of content is an important area to start thinking about. I think there are many who are willing to help with content. Please start writing. Text is the most basic content type. RST basics are not hard. I have seen some RST error recovery issues - we'll learn about RST, and see if we can help it. bug reporting is open on launchpad for the wiki, so please log problems that we can't identify and address quickly on-list (here). I have offered to organize general content, and identifying topic leads. We have decided to go with sphinx for some time to collect community input. This will begin after pycon, but really will depend on good content from the wiki (if you have a topic, please get writing!) There are other things behind the scene. I think we have heard the desire for open documentation that can stay up-to-date, and electronically accessible. It's just one more thing to learn about, and figure out how to best do from the publishing end. Regards, Yarko > > --Jonathan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
