[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

Brett C. added the comment: If Berker is comfortable with his assessment then we can ignore my "conservative" suggestion and just rename the current label "easy (Python)" and reclassify as necessary. ___ PSF Meta Tracker

[Tracker-discuss] [issue606] The sidebar "Search" is much superior to the top-right "Search"

R David Murray added the comment: Yes, there is a reason :) Someone comes to the tracker with a bug, and does a good search...and with an open-only search doesn't find an issue, because we've already fixed it but it isn't in the version of python they are running. But the default searches cl

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

R David Murray added the comment: I'm not sure what you mean by "be conservative". Leave the current tag alone and add "easy (C)" and just apply it to the identified C issues? That would actually make sense. We could also add a *new* 'easy (python)', and retire the current 'easy' tag, which

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

Guido van Rossum added the comment: But Berker's research suggests that most current easy issues are not C, so that should not be the default, IIUC. ___ PSF Meta Tracker _

[Tracker-discuss] [issue606] The sidebar "Search" is much superior to the top-right "Search"

Guido van Rossum added the comment: I'm totally open to better ideas! (I'm really more the messenger than the originator of the suggestion.) Maybe the upper-right search box can be tweaked to have a more useful search by default? (Personally I'm always surprised that it finds closed issues by def

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

Brett C. added the comment: The other option is to be conservative and mark the current easy issues as "easy (C)" and then adjust accordingly. And I'm totally happy w/ David's interpretation of the bikeshed's plans as it's shorter. ___ PSF M

[Tracker-discuss] [issue606] The sidebar "Search" is much superior to the top-right "Search"

R David Murray added the comment: Personally I rarely use 'search' (except for the canned searches I've made), and almost always use the upper right search box. I would strongly object to losing the upper right search box as it currently functions. The "usual" way this is done on other web si

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

R David Murray added the comment: So we change the current tag to 'easy (python)', and someone goes in and changes any easy C issues to 'easy (C)'? I'm not sure how useful 'easy (doc)' will be in reality, but we might as well have it for symmetry :) As you can see I've painted the bikeshed a

[Tracker-discuss] [issue593] Small improvements to issue.item.html

R David Murray added the comment: We have since had the occasion to add Developer to a couple of people specifically so they could be assigned issues (people Raymond is tutoring). So IMO that field is working as desired at the current time. There's no alternative to a thread on core-workflow

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

Guido van Rossum added the comment: Go for that! On Mon, Sep 19, 2016 at 11:12 AM, Berker Peksag < metatrac...@psf.upfronthosting.co.za> wrote: > > Berker Peksag added the comment: > > I don't see a lot of C issues in the "easy issues" list. I agree that some > of them (including a few pure Pyt

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

Berker Peksag added the comment: I don't see a lot of C issues in the "easy issues" list. I agree that some of them (including a few pure Python ones) shouldn't be classified as "easy". I'd say we should remove the following issues from the list: * http://bugs.python.org/issue1100942 (requires

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

Brett C. added the comment: "easy doc issue" wouldn't be hard to add either. Does anyone else have any feedback on this? ___ PSF Meta Tracker