[Twisted-Python] oscar.py updates
Folk, Would you all prefer that I send the the current state of changes I've made to oscar.py (now that I've merged together what I changed for ICQ and AIM) or wait until I can write documentation and such along-side it? For that matter, can someone point me at some good "here's how we do it" type instructions for writing Twisted documentation that is consistent with ... well the rest of it. =D I don't think I'd call it stable yet, so I wouldn't be labeling it as such yet. =) What do you think? (PS, it's got quite a lot of changes in it since I first pulled it out of Twisted 1.3.0) Daniel
On Mon, 2005-09-26 at 20:50 -0400, Daniel Henninger wrote:
Assuming it's got tests, and some explanation of what you've added, then it might well go in (though that's up to the maintainer of course).
We've got a documentation standard, coding style policy etc. as part of the Twisted core documentation (the version in trunk is a bit more up to date): http://twistedmatrix.com/projects/core/documentation/howto/policy/index.html Twisted documentation is typically written with Lore: http://twistedmatrix.com/projects/lore/documentation/howto/lore.html
On Mon, 2005-09-26 at 20:50 -0400, Daniel Henninger wrote:
Assuming it's got tests, and some explanation of what you've added, then it might well go in (though that's up to the maintainer of course).
We've got a documentation standard, coding style policy etc. as part of the Twisted core documentation (the version in trunk is a bit more up to date): http://twistedmatrix.com/projects/core/documentation/howto/policy/index.html Twisted documentation is typically written with Lore: http://twistedmatrix.com/projects/lore/documentation/howto/lore.html
participants (2)
-
Daniel Henninger -
Itamar Shtull-Trauring