[Twisted-Python] On splitting Twisted into subprojects

[Glyph Lefkowitz]

On Apr 17, 2004, at 1:02 PM, Christopher Armstrong wrote:

> The "Twisted Book" is up for debate; personally, I don't care about 
> it, and I'd be inclined to just have a per-project "Book" (collection 
> of HOWTOs in ps/pdf form). If people really think it's a good idea, 
> though, there's no reason that we can't have the same monolithic book.

The "twisted book" should not be a random conglomeration of HOWTOs 
(which are badly named anyway, they're *not* how-to documents, they're 
articles about concepts), it should be a book with some organization 
and structure.  The articles should stand on their own where possible, 
but there are a lot of interrelated concepts that you have to learn and 
they should reference each other.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: </pipermail/twisted-python/attachments/20040417/de81fffc/attachment.sig>