[Twisted-Python] take my tickets, please
According to the Twisted tracker, I currently have 142 tickets. Many of these are simply because I'm the default assignee of the default "core" component, so almost all new tickets end up in my list. It's getting to the point where I don't even have time to triage all the tickets assigned to me, let alone work on them. If anyone is looking for stuff to do to help out Twisted, triaging all of the 'normal', 'core' tickets assigned to me would be a big help. Not only would it circulate tickets to more appropriate people to be working on them than me, it will also generally make me feel less discouraged when I look at the apparently infinite amount of work I have to do.
On 06:44 pm, eprparadocs@gmail.com wrote:
I thought that's what I was doing :). Don't worry about trying to triage controversial or confusing stuff, or reprioritize too much; just closing the obvious duplicates and reassigning things that have their component set blatantly wrong would be a lot of help. And of course, *any* ticket that you want to steal and fix would be fine.
On Thu, 28 Jun 2007 19:58:33 -0400, "Chas." <eprparadocs@gmail.com> wrote:
How does one get started?
Here's the list of open tickets: http://twistedmatrix.com/trac/report/1 You can also create a custom ticket view. For example, open tickets assigned to glyph are shown here: http://twistedmatrix.com/trac/query?status=new&status=assigned&status=reopened&owner=glyph&order=priority If you find a ticket you think you can resolve, attach the patch to the ticket, change its priority to highest, and add "review" to its keywords. You can also look at existing tickets with the review keyword: http://twistedmatrix.com/trac/report/11 and provide feedback for them. The review process is documented on the wiki: http://twistedmatrix.com/trac/wiki/ReviewProcess You can look at the changes proposed on a ticket which has been marked for review and comment about whether the changes are correct or if there is a problem with them. And if you don't know how to fix a ticket, you still may be able to help. If the ticket is related to a domain with which you are familiar and there is an open question as to how to resolve it, you can add a comment making a suggestion. If a ticket is for a bug but does not include a unit test, you can write a unit test and attach it; this is often even more useful than just attaching a patch with a fix. When writing code to contribute to Twisted, note that it must be MIT licenced. Also, take a look at the coding standard here: http://twistedmatrix.com/trac/browser/trunk/doc/development/policy/coding-st... You can find other suggestions for ways to contribute on the wiki: http://twistedmatrix.com/trac/wiki/ContributingToTwistedLabs Jean-Paul
On 06:44 pm, eprparadocs@gmail.com wrote:
I thought that's what I was doing :). Don't worry about trying to triage controversial or confusing stuff, or reprioritize too much; just closing the obvious duplicates and reassigning things that have their component set blatantly wrong would be a lot of help. And of course, *any* ticket that you want to steal and fix would be fine.
On Thu, 28 Jun 2007 19:58:33 -0400, "Chas." <eprparadocs@gmail.com> wrote:
How does one get started?
Here's the list of open tickets: http://twistedmatrix.com/trac/report/1 You can also create a custom ticket view. For example, open tickets assigned to glyph are shown here: http://twistedmatrix.com/trac/query?status=new&status=assigned&status=reopened&owner=glyph&order=priority If you find a ticket you think you can resolve, attach the patch to the ticket, change its priority to highest, and add "review" to its keywords. You can also look at existing tickets with the review keyword: http://twistedmatrix.com/trac/report/11 and provide feedback for them. The review process is documented on the wiki: http://twistedmatrix.com/trac/wiki/ReviewProcess You can look at the changes proposed on a ticket which has been marked for review and comment about whether the changes are correct or if there is a problem with them. And if you don't know how to fix a ticket, you still may be able to help. If the ticket is related to a domain with which you are familiar and there is an open question as to how to resolve it, you can add a comment making a suggestion. If a ticket is for a bug but does not include a unit test, you can write a unit test and attach it; this is often even more useful than just attaching a patch with a fix. When writing code to contribute to Twisted, note that it must be MIT licenced. Also, take a look at the coding standard here: http://twistedmatrix.com/trac/browser/trunk/doc/development/policy/coding-st... You can find other suggestions for ways to contribute on the wiki: http://twistedmatrix.com/trac/wiki/ContributingToTwistedLabs Jean-Paul
participants (3)
-
Chas. -
glyph＠divmod.com -
Jean-Paul Calderone