Re: [Python-Dev] No response to posts

Steve, thanks for your care-full reply. Steve Holden writes: > Particularly when the issue tracker works ... Well, sometimes it's down.But Roundup is more flexible as a database engine than a lot of people realize. Better docs would help, I'm sure, but we can also create new standard queri

Re: [Python-Dev] No response to posts

On Tue, Aug 3, 2010 at 6:56 PM, Stephen J. Turnbull wrote: > As Steven d'Aprano pointed out (admittedly with a bit of hyperbole) a > very high percentage of issues (about 97%) do get some response, and > nearly 87% of all issues ever submitted to Python have already been > closed (based on the end

Re: [Python-Dev] No response to posts

On 8/3/2010 4:56 AM, Stephen J. Turnbull wrote: > Steve Holden writes: > > > No, you don't, and the current discussion about how to ensure that bug > > reporters get at least the courtesy of a relatively quick reply is one > > of the most promising developments in building a welcoming community

Re: [Python-Dev] No response to posts

Steve Holden writes: > No, you don't, and the current discussion about how to ensure that bug > reporters get at least the courtesy of a relatively quick reply is one > of the most promising developments in building a welcoming community > that I can remember. C'mon Steve, it's not hard to se

Re: [Python-Dev] No response to posts

Steven D'Aprano writes: > I don't know. What percentage of new issues get ever get a response? My > wild guess is that it's probably about 99.9%, but the 0.1% that don't > remain languishing forever, skewing the statistics. No guess needed, we have the data. If the fraction "a" of issues ev

Re: [Python-Dev] No response to posts

Mark Lawrence writes: > I completely disagree. Mark, please stop being disagreeable. The above is *not true*. You've made no statements I can recall insisting that the only way to skin a cat is to use a GNOME theme, only that the cat needs skinning. Before you posted that, Benjamin had already

Re: [Python-Dev] No response to posts

Ron Adam writes: > Yes, but when I do it, I either get a single specific day, or 2700 > issues. If your query specifies an activity date, you will get only issues with activity that date. If it sorts or groups on activity date, you will get all issues (subject to other conditions), but you can

Re: [Python-Dev] No response to posts

On 8/2/2010 7:39 PM, Mark Lawrence wrote: > On 03/08/2010 00:24, Antoine Pitrou wrote: >> On Tue, 03 Aug 2010 00:00:46 +0100 >> Mark Lawrence wrote: >>> >>> Fly back at me if you like. I don't care about me. I don't care about >>> you. I do care about Python. >> >> Well, you should care about p

Re: [Python-Dev] No response to posts

On Aug 02, 2010, at 06:57 PM, Benjamin Peterson wrote: >You feel locked out by the current tracker? I do, but that's only because bugs.python.org is currently pinin' for the fjords. ;) -Barry signature.asc Description: PGP signature ___ Python-Dev ma

Re: [Python-Dev] No response to posts

On Tue, 3 Aug 2010 04:27:53 am Terry Reedy wrote: > On 8/2/2010 12:54 PM, Brian Curtin wrote: > > On Mon, Aug 2, 2010 at 11:39, Ralf Schmitt > > wrote: > > > > Benjamin Peterson > > > > > > writes: > > > Please, let's stop messing

Re: [Python-Dev] No response to posts

2010/8/2 Mark Lawrence : > On 02/08/2010 22:18, Benjamin Peterson wrote: >> I'm only referring to the infrastructure when I say "the current >> setup." I don't think repeatedly tweaking the tracker is likely to >> close more issues. >> > > I find this response quite pathetic.  The bulk of Terry's p

Re: [Python-Dev] No response to posts

On 03/08/2010 00:24, Antoine Pitrou wrote: On Tue, 03 Aug 2010 00:00:46 +0100 Mark Lawrence wrote: Fly back at me if you like. I don't care about me. I don't care about you. I do care about Python. Well, you should care about people. Free software is as much as about building welcoming co

Re: [Python-Dev] No response to posts

On Tue, 03 Aug 2010 00:00:46 +0100 Mark Lawrence wrote: > > Fly back at me if you like. I don't care about me. I don't care about > you. I do care about Python. Well, you should care about people. Free software is as much as about building welcoming communities than it is about writing good

Re: [Python-Dev] No response to posts

On 02/08/2010 23:43, Antoine Pitrou wrote: On Mon, 2 Aug 2010 17:13:01 -0500 Benjamin Peterson wrote: 2010/8/2 Nick Coghlan: On Tue, Aug 3, 2010 at 7:18 AM, Benjamin Peterson wrote: I'm only referring to the infrastructure when I say "the current setup." I don't think repeatedly tweaking th

Re: [Python-Dev] No response to posts

On 02/08/2010 22:18, Benjamin Peterson wrote: 2010/8/2 Terry Reedy: On 8/2/2010 12:54 PM, Brian Curtin wrote: On Mon, Aug 2, 2010 at 11:39, Ralf Schmittmailto:r...@brainbot.com>> wrote: Benjamin Petersonmailto:benja...@python.org>> writes: > Please, let's stop messing with the

Re: [Python-Dev] No response to posts

> Well, I just feel like we keep changing things to little result, > creating an organic mess of fields and statuses. Adding more queries > is fine, but let's not bow to the temptation to add more fields. AFAICT, Ezio certainly wants to solve the status/stage/resolution unclear overlap, and in gen

Re: [Python-Dev] No response to posts

On Mon, 2 Aug 2010 17:13:01 -0500 Benjamin Peterson wrote: > 2010/8/2 Nick Coghlan : > > On Tue, Aug 3, 2010 at 7:18 AM, Benjamin Peterson > > wrote: > >> I'm only referring to the infrastructure when I say "the current > >> setup." I don't think repeatedly tweaking the tracker is likely to > >

Re: [Python-Dev] No response to posts

2010/8/2 Nick Coghlan : > On Tue, Aug 3, 2010 at 7:18 AM, Benjamin Peterson wrote: >> I'm only referring to the infrastructure when I say "the current >> setup." I don't think repeatedly tweaking the tracker is likely to >> close more issues. > > But tweaking the tracker to improve the way we *int

Re: [Python-Dev] No response to posts

On Tue, Aug 3, 2010 at 7:18 AM, Benjamin Peterson wrote: > I'm only referring to the infrastructure when I say "the current > setup." I don't think repeatedly tweaking the tracker is likely to > close more issues. But tweaking the tracker to improve the way we *interact* with potential contributo

Re: [Python-Dev] No response to posts

2010/8/2 Terry Reedy : > On 8/2/2010 12:54 PM, Brian Curtin wrote: >> >> On Mon, Aug 2, 2010 at 11:39, Ralf Schmitt > > wrote: >> >>    Benjamin Peterson mailto:benja...@python.org>> >>    writes: >> >>     > Please, let's stop messing with the tracker for everything. I th

Re: [Python-Dev] No response to posts

On 02/08/2010 8:40 PM, "Martin v. Löwis" wrote: I think it's important to find out what people expect when posting to the tracker. Maybe a mandatory radio list with these options would help: - I post this to get help from you - I'm willing to work on other issues to expedite processing of this o

Re: [Python-Dev] No response to posts

> Sure it could make a difference. People who submit issues will > appreciate *some* response a great deal more than no response. That depends. Sometimes, people post to the bug tracker to get help, and they will get sad/driven away/angry when they get no response; sometimes, if they get a respons

Re: [Python-Dev] No response to posts

On 8/2/2010 1:18 PM, Michael Foord wrote: > On 02/08/2010 17:54, Brian Curtin wrote: >> On Mon, Aug 2, 2010 at 11:39, Ralf Schmitt > > wrote: >> >> Benjamin Peterson > > writes: >> >> > Please, let's stop messing with the tracker for

Re: [Python-Dev] No response to posts

On 8/2/2010 12:54 PM, Brian Curtin wrote: On Mon, Aug 2, 2010 at 11:39, Ralf Schmitt mailto:r...@brainbot.com>> wrote: Benjamin Peterson mailto:benja...@python.org>> writes: > Please, let's stop messing with the tracker for everything. I think > the current set up works reason

Re: [Python-Dev] No response to posts

If I may comment *as* a new contributor: Terry responded almost immediately to my first issue raised, and that was a huge boost. If no-one had replied at all, I suspect I would never have spent any more time contributing to any part of Python. (And I contributed 8 more hours today.) Incidentally,

Re: [Python-Dev] No response to posts

On 02/08/2010 17:54, Brian Curtin wrote: On Mon, Aug 2, 2010 at 11:39, Ralf Schmitt > wrote: Benjamin Peterson mailto:benja...@python.org>> writes: > Please, let's stop messing with the tracker for everything. I think > the current set up works reasonably w

Re: [Python-Dev] No response to posts

On Mon, Aug 2, 2010 at 11:39, Ralf Schmitt wrote: > Benjamin Peterson writes: > > > Please, let's stop messing with the tracker for everything. I think > > the current set up works reasonably well, and we should focus on the > > real problem: manpower > > Ignoring issues (probably even with some

Re: [Python-Dev] No response to posts

On 02/08/2010 17:39, Ralf Schmitt wrote: Benjamin Peterson writes: Please, let's stop messing with the tracker for everything. I think the current set up works reasonably well, and we should focus on the real problem: manpower Ignoring issues (probably even with some patches attached) will d

Re: [Python-Dev] No response to posts

Benjamin Peterson writes: > Please, let's stop messing with the tracker for everything. I think > the current set up works reasonably well, and we should focus on the > real problem: manpower Ignoring issues (probably even with some patches attached) will drive contributors away. That's not the

Re: [Python-Dev] No response to posts

On 02/08/2010 03:54, Benjamin Peterson wrote: 2010/7/31 Éric Araujo: Good call. Alternative idea: Have a new status “unread” to make searching easier for bug people. Or a predefined custom search for nosy_count == 1. Please, let's stop messing with the tracker for everything. I think the curr

Re: [Python-Dev] No response to posts

On 08/02/2010 03:57 AM, Stephen J. Turnbull wrote: Ron Adam writes: > Something that may be more useful, is a "no activity" search field > with choices of day, week, month, year, etc... and make the output > sortable on time without activity. That's exactly what a sort on date of act

Re: [Python-Dev] No response to posts

Ron Adam writes: > Something that may be more useful, is a "no activity" search field > with choices of day, week, month, year, etc... and make the output > sortable on time without activity. That's exactly what a sort on date of activity gives you, though, and it can be from longest down. Al

Re: [Python-Dev] No response to posts

2010/7/31 Éric Araujo : > Good call. > > Alternative idea: Have a new status “unread” to make searching easier > for bug people. Or a predefined custom search for nosy_count == 1. Please, let's stop messing with the tracker for everything. I think the current set up works reasonably well, and we s

Re: [Python-Dev] No response to posts

On 08/01/2010 06:14 PM, Terry Reedy wrote: On 8/1/2010 7:44 AM, Éric Araujo wrote: +1 On a prebuilt search This is not as easy as it seems. A nosy count of 1 misses posts where someone added themself as nosy without saying anything, waiting for someone else to answer (and maybe no one ever di

Re: [Python-Dev] No response to posts

On 8/1/2010 7:44 AM, Éric Araujo wrote: +1 On a prebuilt search This is not as easy as it seems. A nosy count of 1 misses posts where someone added themself as nosy without saying anything, waiting for someone else to answer (and maybe no one ever did). A message count of 1 misses posts where

Re: [Python-Dev] No response to posts

On 01/08/2010 20.43, R. David Murray wrote: On Sun, 01 Aug 2010 21:28:05 +1000, Nick Coghlan wrote: On Sun, Aug 1, 2010 at 5:41 PM, Mark Lawrence wrote: I plucked this figure out of the air thinking that if an issue was going to drop under the radar, this would be the most likely time. I was

Re: [Python-Dev] No response to posts

On Sun, 01 Aug 2010 21:28:05 +1000, Nick Coghlan wrote: > On Sun, Aug 1, 2010 at 5:41 PM, Mark Lawrence wrote: > > I plucked this figure out of the air thinking that if an issue was going to > > drop under the radar, this would be the most likely time. I was considering > > a worst case scenario

Re: [Python-Dev] No response to posts

> Perhaps just another number to track in the weekly bug summary? *puts bug person hat on* I made the same suggestion to Ezio, so +1 I’ve just created a public query named “Reports without replies”, you should be able to add it to your queries list, or a tracker admin could decide to add it to th

Re: [Python-Dev] No response to posts

On Sun, Aug 1, 2010 at 5:41 PM, Mark Lawrence wrote: > I plucked this figure out of the air thinking that if an issue was going to > drop under the radar, this would be the most likely time.  I was considering > a worst case scenario where several core triage people are at a big Python > event, ot

Re: [Python-Dev] No response to posts

On 01/08/2010 02:00, Brian Curtin wrote: On Sat, Jul 31, 2010 at 19:48, Mark Lawrencewrote: Hi all, I have been wading through outstanding issues today and have noticed that there are several where there has been no response at all to the initial post. Failing that, the only response has been

Re: [Python-Dev] No response to posts

On Sun, Aug 1, 2010 at 11:00 AM, Brian Curtin wrote: > We could just add globally visible query which shows all issues with a > message count of 1. That query currently shows 372 issues, most of which > were entered within the last few months. > 24 hours seems too soon for any kind of notification

Re: [Python-Dev] No response to posts

On Sat, Jul 31, 2010 at 19:48, Mark Lawrence wrote: > Hi all, > > I have been wading through outstanding issues today and have noticed that > there are several where there has been no response at all to the initial > post. Failing that, the only response has been Terry Reedy back in May > 2010, a

Re: [Python-Dev] No response to posts

Good call. Alternative idea: Have a new status “unread” to make searching easier for bug people. Or a predefined custom search for nosy_count == 1. Regards ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python