[Tracker-discuss] bugs.python.org schema redesign

[Brett Cannon]

On Tue, Mar 24, 2009 at 13:37, R. David Murray <rdmurray at bitdance.com>wrote:

> On Tue, 24 Mar 2009 at 20:45, "Martin v. Löwis" wrote:
>
>> "Feedback pending" reminds me of the "customer pending" status in our
>>> trouble ticket issue tracker.  But 'feedback pending' is too ambiguous.
>>> Whose feedback is pending?  I think you want it to be the submitter, in
>>> which case it should say that, I think.
>>>
>>
>> Any kind of followup should close the issue.
>>
>
> Except for followup that says don't close this issue, I presume?
>
>  It's actually not that feedback is pending (in my understanding of
>> the word "pending", i.e. "present, but not considered yet").
>> Instead, what is pending is that the issue will be closed (is
>> it then that "closure" is pending?)
>>
>
> But I think Brett is proposing something different from the current
> "close pending".  I could be wrong, though.


Nope, I'm not. I want "close pending w/o feedback", but that's too long for
the drop-down. "Close Pending" works for me.


>
>
>  I'm not sure why you suggest removing so many of the components,
>>> especially '2to3'.  'Macintosh' and 'Windows' should go, I think
>>>
>>
>> Why do you think so? The question really is "who should look at this",
>> and, in case of these two components, the answer is "a Mac expert"
>> or "a Windows expert" (just like for any other component).
>>
>
> Because a problem could be a problem with, say, a particular
> library module, but only shows up on the Mac (or the submitter has
> only seen it on a Mac).
>
> But I'm actually of two minds about that, since when I've dealt with
> these two things being separate on other trackers, I've often thought
> that filling in the platform was irrelevant since I was sure the bug
> had nothing to do with the platform.
>
> So I'm actually happy leaving Windows and Mac in there (Brett's
> proposal was to delete them entirely).  (And should it be changed to
> 'OS/X' now?)
>

Everyone knows OS X is Mac so I don't see a need other than perhaps
shortening "Macintosh" to "Mac".


>
>
>  But the others seem useful, and in fact I'd like to generalize the list
>>> into a way to identify any particular library module.  Perhaps that's
>>> a separate dropdown?
>>>
>>
>> I would think that this is only useful for modules that have actually
>> many bugs reported against them.
>>
>
> Well, the motivation for it would be so that someone who was maintainer
> of a specific module or set of modules could easily find bugs against
> just those, instead of having to fish through all bugs marked "Library".
> But I suppose we could have triage assign them, instead, if we continue
> to have enough active triage people.
>

That's what I was assuming and thus why I was suggesting trimming down the
rather long components section.


>
> Speaking of which, is there somewhere where the list Daniel gathered
> of people who wanted certain classes of bugs assigned to them is
> posted?  I should probably have that in hand while doing triage.


Nope, although it probably wouldn't hurt to have one somewhere in the wiki.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090324/02475007/attachment-0001.htm>