[Python-Dev] Issues with process and discussions (Re: Issues with Py3.1's new ipaddr)

Jesse Noller jnoller at gmail.com
Wed Jun 3 21:08:33 CEST 2009


On Wed, Jun 3, 2009 at 2:56 PM, Michael Foord <fuzzyman at voidspace.org.uk> wrote:
> Paul Moore wrote:
>>
>> 2009/6/3  <glyph at divmod.com>:
>>
>>>
>>> So, here are my recommendations:
>>>
>>>  1. Use the tracker for discussing tickets, so that it's easy to refer
>>> back
>>> to a previous point in the discussion, and so that people working on
>>> those
>>> tickets can easily find your commentary.
>>>  2. Use the mailing list for drawing attention to these discussions if
>>> they
>>> are of general interest, especially if the discussion is time- critical.
>>>  In
>>> this case, an announcement "You have six weeks to review ipaddr now until
>>> its inclusion is permanent, anyone interested please look at issue 3959."
>>>  3. If you have an opinion, put your +1/+0/-0/-1 on a line by itself at
>>> the
>>> top of your message, so that it's easy for newcomers to the discussion to
>>> get a general feel.
>>>
>>
>> Mostly, I agree, but I definitely disagree, I'm afraid, on the use of
>> the tracker for discussions. To keep track of discussions on a ticket,
>> I have to personally keep a list of the tickets I'm interested in,
>> check back regularly to see if there's anything new,
>
> Not true - if you are added as nosy on a tracker item (which happens when
> you make a comment or you can do yourself) then you get emailed about new
> comments. The email contains the body of the comment so you can follow
> discussions completely by email only going to the tracker to add responses.
>
> Michael
>

You can also directly reply to tracker issues via email, which is how
I do most of my responses. It's cool.


More information about the Python-Dev mailing list