[Twisted-Python] Reminder: Virtual Twisted Sprint, 8-9 October
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 -- <e@ircnet> on the internet the concepts of time and space lose meaning
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:
[Moving discussion onto twisted-python only] On Mon, Sep 26, 2005, Ed Suominen wrote:
Well, asking at the time will give you the ultimate answer, but whichever of the following is acceptable to you: 1. Make your patches available on a website and give the person who has agreed to review them the URL. 2. Mail them to the person who has agreed to review them. 3. Make a single bug and attach all the patches to it. (Depends on exactly what bug tracker hoops you object to.) 1 and 3 are preferrable because it means that if someone drops the ball on the day, you can nag about it on the list. -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:
[Moving discussion onto twisted-python only] On Mon, Sep 26, 2005, Ed Suominen wrote:
Well, asking at the time will give you the ultimate answer, but whichever of the following is acceptable to you: 1. Make your patches available on a website and give the person who has agreed to review them the URL. 2. Mail them to the person who has agreed to review them. 3. Make a single bug and attach all the patches to it. (Depends on exactly what bug tracker hoops you object to.) 1 and 3 are preferrable because it means that if someone drops the ball on the day, you can nag about it on the list. -Mary
participants (2)
-
Ed Suominen -
Mary Gardiner