[Twisted-Python] oscar.py updates
jadestorm at nc.rr.com
Tue Sep 27 11:01:50 EDT 2005
>> 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?
> Assuming it's got tests, and some explanation of what you've added,
> it might well go in (though that's up to the maintainer of course).
Ok then I've got a little bit more work to do with it. ;D
And that reminds me, am I considered the maintainer of it at this
point? I recall a conversation not-so-long ago about it and z3p
saying "it's yours". =)
>> 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?
> 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
> Twisted documentation is typically written with Lore:
Excellent, thanks! I'll look them over!
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
More information about the Twisted-Python