Just a reminder for everyone that there will be a bunch of people online
on the weekend of 8-9 October working their hearts out on the Twisted
codebase. All participants welcome, people unfamiliar with the codebase
will need to be a bit self-motivated though in terms of being willing to
find their own problem to work on (check the bug tracker for ideas).
We're particularly keen for people who would be interested in adding
unti tests.
Sprinting discussion will be in #twisted and #twisted.web on
freenode.net. There should be people around at most times.
-Mary
--
I'm a regular grump on #twisted about the overall lack of docstrings in Twisted. I'd be willing to participate by offering docstrings for specific classes/methods if there's a general interest and willingness to incorporate them. What would be the preferred way to pass them on for review and commit, given that "all participants [are] welcome" but that I lack commit access and would rather not jump through the bug tracker hoops for every single docstring written? Best regards, Ed Suominen On Tue, 2005-09-27 at 10:28 +1000, Mary Gardiner wrote:
Just a reminder for everyone that there will be a bunch of people online on the weekend of 8-9 October working their hearts out on the Twisted codebase. All participants welcome, people unfamiliar with the codebase will need to be a bit self-motivated though in terms of being willing to find their own problem to work on (check the bug tracker for ideas). We're particularly keen for people who would be interested in adding unti tests.
Sprinting discussion will be in #twisted and #twisted.web on freenode.net. There should be people around at most times.
-Mary
participants (2)
-
Ed Suominen
-
Mary Gardiner