On Mon, Sep 20, 2010 at 9:09 PM, Ben Bangert <b...@groovie.org> wrote: > On Sep 20, 2010, at 2:58 PM, Mike Orr wrote: > >> BFG is bigger than all the other Pylons dependencies combined. We >> can't have 30% of the Pylons manual referring to BFG features that >> aren't normally used in Pylons apps, especially if Pylons has a more >> specific way to enable it. > > Indeed, but after looking through the BFG docs, I'm having difficulty finding > something that people might not need to reference. Chris had mentioned he > planned on trimming quite a bit from the BFG docs as they are overly verbose > (650 pages printed apparently!), so I think there's room to trim and be more > concise. Pylons won't be documenting it quite the same either, the > declarative way (using ZCML) will be relegated to a single chapter for those > that want/need to use it. > >> It sounds like we need a preprocessor to import documentation sources >> and sanitize foreign cross-references. Can that be done as a Sphinx >> plugin? > > That sounds like it might be more effort than just copy/pasting the bits we > need in, and ensuring their docs flow well with the rest of the Pylons docs.
How many full-time staff do you have available for two months? Just converting the hundreds of references to plain text would take hours, plus rewording the hundred-some pages of BFG docs and hundred-some other docs and a few more for SQLAlchemy (or you want to put the entire SQLAlchemy manual in too). The Encyclopedia of Pylons! -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
