From metatracker at psf.upfronthosting.co.za Wed May 9 13:13:33 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 09 May 2012 11:13:33 +0000 Subject: [Tracker-discuss] [issue437] Ignore a dot in urls if it's the last character In-Reply-To: <1330951468.67.0.643931051848.issue437@psf.upfronthosting.co.za> Message-ID: <1336562013.91.0.453896237316.issue437@psf.upfronthosting.co.za> Ezio Melotti added the comment: Eventually I got home and checked, and it's failing here too. The attached patch fixes the issue, ignoring a single trailing dot, comma, colon, semicolon, or exclamation mark. Maybe the question mark could be added too; closing parentheses are already ignored. I tested the patch locally and it seems to work fine, however this should be reported and fixed upstream. I'll create a new issue upstream once I prepare a proper patch with tests. ---------- nosy: +ambv _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- Index: roundup-src/roundup/cgi/templating.py =================================================================== --- roundup-src/roundup/cgi/templating.py (revision 88927) +++ roundup-src/roundup/cgi/templating.py (working copy) @@ -1379,6 +1379,10 @@ pos = s.find('>') end = s[pos:] u = s = s[:pos] + if s.endswith(tuple('.,;:!')): + # don't include trailing punctuation + end = s[-1:] + end + u = s = s[:-1] if ')' in s and s.count('(') != s.count(')'): # don't include extraneous ')' in the link pos = s.rfind(')') From metatracker at psf.upfronthosting.co.za Tue May 15 03:29:37 2012 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 15 May 2012 01:29:37 +0000 Subject: [Tracker-discuss] [issue460] Add "email" classification Message-ID: <1337045377.34.0.651169978563.issue460@psf.upfronthosting.co.za> New submission from R David Murray : I would like to add a new classification, 'email', (on which I would be auto-nosy). My motivation for this is that I don't like having all the email issues assigned to me when I obviously can't be actively working on all of them. I'd also like to mark a number of other issues as email related that aren't directly issues with the email package (imap, smtp, pop, etc, etc), because these are all issue that I, and mostly likely anyone else interested in email, would be concerned with. Any objections? ---------- messages: 2486 nosy: r.david.murray priority: feature status: unread title: Add "email" classification _______________________________________________________ PSF Meta Tracker _______________________________________________________ From barry at python.org Tue May 15 06:35:40 2012 From: barry at python.org (Barry Warsaw) Date: Tue, 15 May 2012 00:35:40 -0400 Subject: [Tracker-discuss] [issue460] Add "email" classification In-Reply-To: <1337045377.34.0.651169978563.issue460@psf.upfronthosting.co.za> References: <1337045377.34.0.651169978563.issue460@psf.upfronthosting.co.za> Message-ID: <20120515003540.0989f5f3@resist.wooz.org> On May 15, 2012, at 01:29 AM, R David Murray wrote: >I would like to add a new classification, 'email', (on which I would be >auto-nosy). +1. Though I have little time these days to hack on the email package, I'd like to be auto-nosied too (as weird as that sounds :). From metatracker at psf.upfronthosting.co.za Tue May 15 06:35:45 2012 From: metatracker at psf.upfronthosting.co.za (Barry Warsaw) Date: Tue, 15 May 2012 04:35:45 +0000 Subject: [Tracker-discuss] [issue460] Add "email" classification In-Reply-To: <1337045377.34.0.651169978563.issue460@psf.upfronthosting.co.za> Message-ID: <20120515003540.0989f5f3@resist.wooz.org> Barry Warsaw added the comment: On May 15, 2012, at 01:29 AM, R David Murray wrote: >I would like to add a new classification, 'email', (on which I would be >auto-nosy). +1. Though I have little time these days to hack on the email package, I'd like to be auto-nosied too (as weird as that sounds :). ---------- nosy: +barry status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 15 08:29:38 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 15 May 2012 06:29:38 +0000 Subject: [Tracker-discuss] [issue460] Add "email" classification In-Reply-To: <1337045377.34.0.651169978563.issue460@psf.upfronthosting.co.za> Message-ID: <1337063378.0.0.314208163716.issue460@psf.upfronthosting.co.za> Ezio Melotti added the comment: I added the "email" component and your ids on the autonosy. Let me know if there are any problems. ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri May 18 09:35:07 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 18 May 2012 07:35:07 +0000 Subject: [Tracker-discuss] [issue461] Add note about the contributor agreement on the tracker Message-ID: <1337326507.68.0.0680310875222.issue461@psf.upfronthosting.co.za> New submission from Ezio Melotti : We could add a note on the issue page that says something like "If you have contributed any patches or you are planning to, please fill in the and send it to
, specifying your user name/id in the mail." (the second half could be written in the contributor agreement page too). This can be shown to everyone that has not submitted the agreement yet, possibly only when they have submitted a patch. ---------- assignedto: ezio.melotti messages: 2489 nosy: ambv, ezio.melotti, loewis priority: feature status: unread title: Add note about the contributor agreement on the tracker _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri May 18 09:48:46 2012 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Fri, 18 May 2012 07:48:46 +0000 Subject: [Tracker-discuss] [issue461] Add note about the contributor agreement on the tracker In-Reply-To: <1337326507.68.0.0680310875222.issue461@psf.upfronthosting.co.za> Message-ID: <1337327326.13.0.945707530973.issue461@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Good idea! ---------- status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat May 19 11:35:07 2012 From: metatracker at psf.upfronthosting.co.za (Yuriy Syrovetskiy) Date: Sat, 19 May 2012 09:35:07 +0000 Subject: [Tracker-discuss] [issue462] Logging in with OpenID delegate doesn't work Message-ID: <1337420107.48.0.279533555587.issue462@psf.upfronthosting.co.za> New submission from Yuriy Syrovetskiy : Entering "cblp.su" (which is a delegate to "cblp-su.ya.ru") at bugs.python.org, I got: "Authentication failed: Discovered and asserted endpoints differ" Actually, this is a feature, but a must-have feature. I used OpenID a lot, and it's the first site that didn't accept my id. ---------- messages: 2491 nosy: cblp priority: bug status: unread title: Logging in with OpenID delegate doesn't work _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat May 19 11:58:07 2012 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sat, 19 May 2012 09:58:07 +0000 Subject: [Tracker-discuss] [issue462] Logging in with OpenID delegate doesn't work In-Reply-To: <1337420107.48.0.279533555587.issue462@psf.upfronthosting.co.za> Message-ID: <1337421487.66.0.956037873515.issue462@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Can you please report what the op_endpoint value is in the redirect back to the bugtracker? It will be part of the URL, following the string "&openid.op_endpoint=" Supposedly, this is incorrect, indicating that some cheating happened. Delegates work fine (in general) in the Python bug tracker. ---------- nosy: +loewis status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat May 19 12:00:41 2012 From: metatracker at psf.upfronthosting.co.za (Yuriy Syrovetskiy) Date: Sat, 19 May 2012 10:00:41 +0000 Subject: [Tracker-discuss] [issue462] Logging in with OpenID delegate doesn't work In-Reply-To: <1337420107.48.0.279533555587.issue462@psf.upfronthosting.co.za> Message-ID: <1337421641.74.0.0814095640322.issue462@psf.upfronthosting.co.za> Yuriy Syrovetskiy added the comment: openid.op_endpoint=http%3A%2F%2Fopenid.yandex.ru%2Fserver%2F _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat May 19 12:44:21 2012 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sat, 19 May 2012 10:44:21 +0000 Subject: [Tracker-discuss] [issue462] Logging in with OpenID delegate doesn't work In-Reply-To: <1337420107.48.0.279533555587.issue462@psf.upfronthosting.co.za> Message-ID: <1337424261.5.0.574003108235.issue462@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I see. You need to change your "openid.server" from "http://openid.yandex.ru/server.xml" to "http://openid.yandex.ru/server/", since this is what openid.yandex.ru says is the official endpoint URL. The Python bug tracker notices that the reply comes from a different location than it sent the request to, and assumes cheating. That the other web sites accept this silently is a bug. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat May 19 12:51:40 2012 From: metatracker at psf.upfronthosting.co.za (Yuriy Syrovetskiy) Date: Sat, 19 May 2012 10:51:40 +0000 Subject: [Tracker-discuss] [issue462] Logging in with OpenID delegate doesn't work In-Reply-To: <1337420107.48.0.279533555587.issue462@psf.upfronthosting.co.za> Message-ID: <1337424700.31.0.790210614257.issue462@psf.upfronthosting.co.za> Yuriy Syrovetskiy added the comment: I fixed that, now bugs.python.org accepts my id. Thanks. But does this mean that other consumers are not so strict and allow cheating? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat May 19 13:01:14 2012 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sat, 19 May 2012 11:01:14 +0000 Subject: [Tracker-discuss] [issue462] Logging in with OpenID delegate doesn't work In-Reply-To: <1337420107.48.0.279533555587.issue462@psf.upfronthosting.co.za> Message-ID: <1337425274.05.0.713863260248.issue462@psf.upfronthosting.co.za> Martin v. L?wis added the comment: > But does this mean that other consumers are not so strict and allow cheating? I'm not sure how serious this is, but the OpenID spec (http://openid.net/specs/openid-authentication-2_0.html) seems to say in section 11 that this MUST be verified by the relying party ("Discovered information matches the information in the assertion"). The table in 11.2 then says that the discovered "OP Endpoint URL" must match the openid.op_endpoint field - which in your case it didn't, meaning that a protocol-conforming relying party should reject the assertion. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 02:27:56 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 00:27:56 +0000 Subject: [Tracker-discuss] [issue447] Cannot remind password for python wiki In-Reply-To: <1333477550.44.0.112787201433.issue447@psf.upfronthosting.co.za> Message-ID: <1337646476.89.0.482549528745.issue447@psf.upfronthosting.co.za> Ezio Melotti added the comment: This is not the bug tracker for the wiki (and I don't think there is one). If you still haven't managed to recover your password you could try on http://wiki.python.org/moin/?action=recoverpass or sending an email to webmaster at python.org. ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 02:37:23 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 00:37:23 +0000 Subject: [Tracker-discuss] [issue430] Email address revealed to unauthenticated user In-Reply-To: <1322480175.95.0.81590440887.issue430@psf.upfronthosting.co.za> Message-ID: <1337647043.42.0.843533061362.issue430@psf.upfronthosting.co.za> Ezio Melotti added the comment: Since the issue has been reported upstream already, I'm going to close this. ---------- assignedto: -> ezio.melotti status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 02:52:10 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 00:52:10 +0000 Subject: [Tracker-discuss] [issue295] title is changed by email updates when only whitespace had changed In-Reply-To: <1248179761.3.0.0135867721483.issue295@psf.upfronthosting.co.za> Message-ID: <1337647930.59.0.360469281124.issue295@psf.upfronthosting.co.za> Ezio Melotti added the comment: > Apparently there's no way for a detector to know if a message > comes from an email or from the web interface See http://issues.roundup-tracker.org/issue2550731 _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 02:56:45 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 00:56:45 +0000 Subject: [Tracker-discuss] [issue365] No issue exists with that id In-Reply-To: <1293200576.2.0.44483259406.issue365@psf.upfronthosting.co.za> Message-ID: <1337648205.33.0.613296565812.issue365@psf.upfronthosting.co.za> Ezio Melotti added the comment: FWIW the review links for the patches on issue7511 are not available anymore. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 03:06:11 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 01:06:11 +0000 Subject: [Tracker-discuss] [issue422] Keyboard shortcuts In-Reply-To: <1317625041.71.0.42670053076.issue422@psf.upfronthosting.co.za> Message-ID: <1337648771.07.0.631571873887.issue422@psf.upfronthosting.co.za> Ezio Melotti added the comment: This seems to work fine and no one complained, so I'm closing it. Thanks everyone for the feedback! ---------- status: testing -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 03:12:48 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 01:12:48 +0000 Subject: [Tracker-discuss] [issue398] Roundup Refused Update with No text/plain In-Reply-To: <1304867904.05.0.182774765173.issue398@psf.upfronthosting.co.za> Message-ID: <1337649168.39.0.632362390928.issue398@psf.upfronthosting.co.za> Ezio Melotti added the comment: This now seems to work*, most likely after the Roundup update in r88888 (see #411). * http://bugs.python.org/issue2771#msg161311 ---------- assignedto: -> ezio.melotti status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 03:24:56 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 01:24:56 +0000 Subject: [Tracker-discuss] [issue418] Change background color if an issue is closed In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za> Message-ID: <1337649896.22.0.713009111654.issue418@psf.upfronthosting.co.za> Ezio Melotti added the comment: We have been using 6) for a while now, and I didn't hear anyone complaining, so unless someone has something to say, I'm going to close this. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 03:31:19 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 01:31:19 +0000 Subject: [Tracker-discuss] [issue400] when replying by email, don't send another one In-Reply-To: <1306288371.68.0.154640030812.issue400@psf.upfronthosting.co.za> Message-ID: <1337650279.97.0.412206859723.issue400@psf.upfronthosting.co.za> Ezio Melotti added the comment: > for detectors there's no way to know if a submission came > from the web browser or from a mail. See http://issues.roundup-tracker.org/issue2550731 _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 07:53:46 2012 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Tue, 22 May 2012 05:53:46 +0000 Subject: [Tracker-discuss] [issue463] HTTPS only version for login for this tracker Message-ID: <1337666026.16.0.0159243982051.issue463@psf.upfronthosting.co.za> New submission from anatoly techtonik : I often use unencrypted public WiFi networks and logging in to this tracker (which doesn't have any OAuth2 interface) imposes a high security risk. I propose to make login secure. ---------- messages: 2505 nosy: techtonik priority: critical status: unread title: HTTPS only version for login for this tracker _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 07:59:27 2012 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Tue, 22 May 2012 05:59:27 +0000 Subject: [Tracker-discuss] [issue418] Change background color if an issue is closed In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za> Message-ID: <1337666367.05.0.239574179633.issue418@psf.upfronthosting.co.za> anatoly techtonik added the comment: Sorry, but I can't see the difference between closed and open issue in Chrome 19. What does a 6) should do? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 08:14:22 2012 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Tue, 22 May 2012 06:14:22 +0000 Subject: [Tracker-discuss] [issue418] Change background color if an issue is closed In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za> Message-ID: <1337667262.27.0.526464738949.issue418@psf.upfronthosting.co.za> anatoly techtonik added the comment: Oh, I see. It is a message beneath the entry form. The problem with it is that it is not visible when a page is loaded. In all trackers status is the first thing people look at, so it should be the first to load. I'd propose to replace 'classification' literal with status, and still add a color scheme regardless of any more text placements. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 12:24:30 2012 From: metatracker at psf.upfronthosting.co.za (Victor Stinner) Date: Tue, 22 May 2012 10:24:30 +0000 Subject: [Tracker-discuss] [issue418] Change background color if an issue is closed In-Reply-To: <1337649896.22.0.713009111654.issue418@psf.upfronthosting.co.za> Message-ID: Victor Stinner added the comment: I still fail to see the difference between open and closed issue. I would prefer something like closed-issue1.png or closed-issue2.png. Or if you really don't like colors, closed-issue4.png. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 12:31:40 2012 From: metatracker at psf.upfronthosting.co.za (Ralph Corderoy) Date: Tue, 22 May 2012 10:31:40 +0000 Subject: [Tracker-discuss] [issue398] Roundup Refused Update with No text/plain In-Reply-To: <1337649168.39.0.632362390928.issue398@psf.upfronthosting.co.za> Message-ID: <20120522103138.46F202B368@orac.inputplus.co.uk> Ralph Corderoy added the comment: > This now seems to work*, most likely after the Roundup update in > r88888 (see #411). > * http://bugs.python.org/issue2771#msg161311 Thanks. Testing, this email isn't MIME. ---------- status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 13:48:47 2012 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Tue, 22 May 2012 11:48:47 +0000 Subject: [Tracker-discuss] [issue418] Change background color if an issue is closed In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za> Message-ID: <1337687327.99.0.0315823658741.issue418@psf.upfronthosting.co.za> anatoly techtonik added the comment: I'd vote for 1+4 or just 1. I've created poll to keep this alive. http://www.doodle.com/tpgky5kgixcsd7ni#table _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 14:09:08 2012 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Tue, 22 May 2012 12:09:08 +0000 Subject: [Tracker-discuss] [issue418] Change background color if an issue is closed In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za> Message-ID: <1337688548.62.0.0941210583045.issue418@psf.upfronthosting.co.za> Martin v. L?wis added the comment: It seems that the key issue is that people want to avoid commenting on a closed issue. I think this is best achieved by hiding any edit UI first, only enabling editing on explicit request. I suggest to put a text like "This issue is closed. If you have a problem that appears to be related, please still submit a /new report/. If you want to provide further information on this very issue, you may still /edit it/." where the slashed parts will be hyperlinked to appropriate URLs. Not sure how to best implement that - it may be possible to create a new template (e.g. issue.closed.html), and make that template default for closed issues. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 22 18:17:36 2012 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Tue, 22 May 2012 16:17:36 +0000 Subject: [Tracker-discuss] [issue418] Change background color if an issue is closed In-Reply-To: <1337688548.62.0.0941210583045.issue418@psf.upfronthosting.co.za> Message-ID: anatoly techtonik added the comment: On Tue, May 22, 2012 at 3:09 PM, Martin v. L?wis wrote: > > It seems that the key issue is that people want to avoid commenting on a closed issue. That's not my use case, and I doubt that's the key issue. My key issue is to know when I open a link if the issue is closed or still requires my attention. >I think this is best achieved by hiding any edit UI first, only enabling editing on explicit request. I suggest to put a text like > "This issue is closed. If you have a problem that appears to be related, please still submit a /new report/. If you want to provide further information on this very issue, you may still /edit it/." Do we really have a problem with users reopening the issues instead of reporting new ones? Anyway, this feature will only work with JavaScript enabled. Color scheme works always. I you don't have any objections, let's go for color scheme implemented first and then move to A/B testing with additional concepts and user stories to ease UX. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 00:26:28 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 22 May 2012 22:26:28 +0000 Subject: [Tracker-discuss] [issue464] Remove "test needed" and make stage editable to everyone Message-ID: <1337725588.74.0.399420856503.issue464@psf.upfronthosting.co.za> New submission from Ezio Melotti : Antoine suggested to remove the "test needed" stage. I also propose to make the stage field editable to everyone. ---------- assignedto: ezio.melotti messages: 2513 nosy: ambv, eric.araujo, ezio.melotti, loewis, pitrou priority: wish status: chatting title: Remove "test needed" and make stage editable to everyone _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 01:25:20 2012 From: metatracker at psf.upfronthosting.co.za (Ned Deily) Date: Tue, 22 May 2012 23:25:20 +0000 Subject: [Tracker-discuss] [issue464] Remove "test needed" and make stage editable to everyone In-Reply-To: <1337725588.74.0.399420856503.issue464@psf.upfronthosting.co.za> Message-ID: <1337729120.78.0.0209490892766.issue464@psf.upfronthosting.co.za> Ned Deily added the comment: > I also propose to make the stage field editable to everyone. Why make the stage field editable by everyone? Isn't the point of it to track where things are in the python-dev development process? As such, it should only be modifiable by python-dev participants who need to have tracker privileges anyway. ---------- nosy: +ned.deily _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 02:47:06 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 23 May 2012 00:47:06 +0000 Subject: [Tracker-discuss] [issue420] Display 'dependency of' and 'superseder of' In-Reply-To: <1314107935.82.0.0721577384536.issue420@psf.upfronthosting.co.za> Message-ID: <1337734026.39.0.105234523699.issue420@psf.upfronthosting.co.za> Ezio Melotti added the comment: So currently you can only see what are the dependencies or the superseder of an issue, but you can't see if an issue is a dependency or a superseder of another issue unless you like in the history, for example: http://bugs.python.org/issue6494 is superseder of http://bugs.python.org/issue7987 #7987 has #6494 in the superseder field, but #6494 only has a mention of #7987 in the history. http://bugs.python.org/issue6484 is a dependency of http://bugs.python.org/issue9923 #9923 has #6484 in the dependencies field, but #6484 only has a mention of #9923 in the history. The info that is now available only in the history could be moved in the dependencies/superseder field (with a label that says "dependency of/superseder of"), or in a new field visible only when the value is present (but that would leave an odd number of cells). ---------- nosy: +ezio.melotti status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 03:24:50 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 23 May 2012 01:24:50 +0000 Subject: [Tracker-discuss] [issue464] Remove "test needed" and make stage editable to everyone In-Reply-To: <1337725588.74.0.399420856503.issue464@psf.upfronthosting.co.za> Message-ID: <1337736290.77.0.332092711342.issue464@psf.upfronthosting.co.za> Ezio Melotti added the comment: Because IMHO they can do more good than harm. Setting the stage is even easier than setting the type, and we can also adjust it later if a regular user does a mistake. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 03:37:29 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 23 May 2012 01:37:29 +0000 Subject: [Tracker-discuss] [issue120] Allow users to report msg/file instances as misclassified In-Reply-To: <87sl79vn7r.fsf@uterus.efod.se> Message-ID: <1337737049.21.0.020060762819.issue120@psf.upfronthosting.co.za> Ezio Melotti added the comment: The attached patch should enable developers to reclassify spam. I'm not sure what's the best way to test it though (I would need either a spammy message and a non-coordinator account). ---------- assignedto: -> ezio.melotti _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- Index: schema.py =================================================================== --- schema.py (revision 88963) +++ schema.py (working copy) @@ -254,9 +254,9 @@ p = db.security.addPermission(name='View', klass=cl, description="Allowed to see content of object regardless of spam status", properties = ('content', 'summary')) - - db.security.addPermissionToRole('User', p) - + + db.security.addPermissionToRole('User', p) + spamcheck = db.security.addPermission(name='View', klass=cl, description="allowed to see content if not spam", properties=('content', 'summary'), @@ -316,7 +316,7 @@ # Coordinator permissions ########################## for cl in ('issue_type', 'severity', 'component', - 'version', 'priority', 'stage', 'status', 'resolution', 'issue', + 'version', 'priority', 'stage', 'status', 'resolution', 'issue', 'file', 'msg', 'hgrepo'): db.security.addPermissionToRole('Coordinator', 'View', cl) db.security.addPermissionToRole('Coordinator', 'Edit', cl) @@ -326,6 +326,7 @@ db.security.addPermissionToRole('Coordinator', p) db.security.addPermissionToRole('Coordinator', 'SB: May Classify') +db.security.addPermissionToRole('Developer', 'SB: May Classify') # May users view other user information? Comment these lines out # if you don't want them to From metatracker at psf.upfronthosting.co.za Wed May 23 04:06:16 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 23 May 2012 02:06:16 +0000 Subject: [Tracker-discuss] [issue461] Add note about the contributor agreement on the tracker In-Reply-To: <1337326507.68.0.0680310875222.issue461@psf.upfronthosting.co.za> Message-ID: <1337738776.86.0.7041470313.issue461@psf.upfronthosting.co.za> Ezio Melotti added the comment: Attached patch adds a box with a note about the contributor agreement on the "new issue" page when the user hasn't yet submitted the agreement. The same note could be shown to user that haven't submitted the agreement: * if they are developers (maybe only in the new issue page); * on the issue page if the user has submitted a patch there; _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- Index: html/style.css =================================================================== --- html/style.css (revision 88963) +++ html/style.css (working copy) @@ -507,6 +507,13 @@ font-size: 90%; } +p#contribform { + border: 1px solid #000000; + padding: .5em; + color: #000000; + background-color: #ffdddd; +} + .calendar_display { text-align: center; } Index: html/issue.item.html =================================================================== --- html/issue.item.html (revision 88963) +++ html/issue.item.html (working copy) @@ -42,6 +42,12 @@
+

+ If you are contributing any patches or you are planning to, + please fill in the contributor + agreement and send it to + contributors at python.org, specifying your user name/id in the mail.

+
From metatracker at psf.upfronthosting.co.za Wed May 23 04:10:28 2012 From: metatracker at psf.upfronthosting.co.za (Nick Coghlan) Date: Wed, 23 May 2012 02:10:28 +0000 Subject: [Tracker-discuss] [issue420] Display 'dependency of' and 'superseder of' In-Reply-To: <1314107935.82.0.0721577384536.issue420@psf.upfronthosting.co.za> Message-ID: <1337739028.3.0.908107751818.issue420@psf.upfronthosting.co.za> Nick Coghlan added the comment: Yeah, something simple like your first suggestion should work reasonably well. Since the "dependencies" and "superceder" nouns are ambiguous about the direction of the relationship, and aren't particularly common words anyway, it's probably better to make all four labels use simpler and more explicit verb forms: "Blocked by:" (current "dependencies" field) "Blocking:" (new field) "Replaced by:" (current "superceders" field) "Replaces:" (new field) _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 04:38:17 2012 From: metatracker at psf.upfronthosting.co.za (Ned Deily) Date: Wed, 23 May 2012 02:38:17 +0000 Subject: [Tracker-discuss] [issue464] Remove "test needed" and make stage editable to everyone In-Reply-To: <1337725588.74.0.399420856503.issue464@psf.upfronthosting.co.za> Message-ID: <1337740697.74.0.907979216371.issue464@psf.upfronthosting.co.za> Ned Deily added the comment: I'm not convinced of the benefit, so -0.5. In any case, before making a change, I think the current release managers should be consulted, if they haven't already. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 13:53:48 2012 From: metatracker at psf.upfronthosting.co.za (Giampaolo Rodola') Date: Wed, 23 May 2012 11:53:48 +0000 Subject: [Tracker-discuss] [issue465] Default search should be set to "open" instead of "all" Message-ID: <1337774028.06.0.0677609085172.issue465@psf.upfronthosting.co.za> New submission from Giampaolo Rodola' : I'm talking about the top-right radio button: http://bugs.python.org/ ---------- messages: 2521 nosy: giampaolo.rodola priority: wish status: unread title: Default search should be set to "open" instead of "all" _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 15:14:52 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 23 May 2012 13:14:52 +0000 Subject: [Tracker-discuss] [issue465] Default search should be set to "open" instead of "all" In-Reply-To: <1337774028.06.0.0677609085172.issue465@psf.upfronthosting.co.za> Message-ID: <1337778892.93.0.0530520054824.issue465@psf.upfronthosting.co.za> Ezio Melotti added the comment: It used to be "open", but we changed it to search for "all" the issues and added the checkboxes. The reason is that people reporting issues might attempt a search and miss closed issue with a solution to their problems (e.g. the issue is already fixed, the idea has been rejected). ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 15:27:04 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 23 May 2012 13:27:04 +0000 Subject: [Tracker-discuss] [issue420] Display 'dependency of' and 'superseder of' In-Reply-To: <1314107935.82.0.0721577384536.issue420@psf.upfronthosting.co.za> Message-ID: <1337779624.86.0.911011890181.issue420@psf.upfronthosting.co.za> Ezio Melotti added the comment: Changing the names might be a good idea, but I'd rather avoid adding 2 more fields. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 15:54:10 2012 From: metatracker at psf.upfronthosting.co.za (Nick Coghlan) Date: Wed, 23 May 2012 13:54:10 +0000 Subject: [Tracker-discuss] [issue420] Display 'dependency of' and 'superseder of' In-Reply-To: <1314107935.82.0.0721577384536.issue420@psf.upfronthosting.co.za> Message-ID: <1337781250.4.0.758790330249.issue420@psf.upfronthosting.co.za> Nick Coghlan added the comment: I'm not a big fan either, but it's the simplest option available that displays the relevant information. Here's a more complex option that may work: 1. Keep the existing Dependencies/Superceder fields for editing purposes (perhaps changing the names to "Needs" and "Replaced By"), but move them below the priority and keywords fields 2. Remove the current "View" mini displays for those fields 2. Add a new full width "Related Issues" field above the comment field 3. Display any related issues something like the following (truncating the titles if needed): Replaced by 6494 (xmlrpc client does not support HTTPS) Replaces 7987 (Python 3.1's http.client doesn't support HTTPS) Needs 6484 (No unit test for mailcap module) Needed by 9923 (mailcap module may not work on non-POSIX platforms if MAILCAPS env variable is set) After all, it isn't the field *editing* that needs changing, it's only the display of additional information. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 23 18:37:13 2012 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 23 May 2012 16:37:13 +0000 Subject: [Tracker-discuss] [issue393] Security policy should be visible on top page of tracker, maybe every page In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za> Message-ID: <1337791033.53.0.799840388417.issue393@psf.upfronthosting.co.za> Ezio Melotti added the comment: > In http://bugs.python.org/issue12792 I proposed > a doc patch to document security at python.org. This is now documented in the devguide, the attached patch also adds a note that appears when the "security" type is selected. _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- Index: html/issue.item.js =================================================================== --- html/issue.item.js (revision 88963) +++ html/issue.item.js (working copy) @@ -351,3 +351,17 @@ 'background-color', '#efeff9'); }); }); + + +$(document).ready(function() { + /* Show a note about security at python.org for security issues */ + $('td#issue_type select').change(function() { + if ($(this).find("option:selected").text() == 'security') { + var p = $(['

Note: If you think the issue ', + 'should
not be made public, please report
', + 'it to ', + 'security at python.org instead.

'].join('\n')); + $(this).after(p); + } + }); +}); Index: html/issue.item.html =================================================================== --- html/issue.item.html (revision 88963) +++ html/issue.item.html (working copy) @@ -64,7 +64,7 @@ Type: - type + type Stage: Index: html/style.css =================================================================== --- html/style.css (revision 88963) +++ html/style.css (working copy) @@ -502,6 +502,14 @@ text-decoration: line-through !important; } +#issue_type p { + border: 1px solid black; + color: #000000; + background-color: #ffdddd; + margin: .2em 0 0; + padding: .3em; +} + #submit_td input{ padding: .3em .7em; font-size: 90%; From metatracker at psf.upfronthosting.co.za Wed May 23 18:38:00 2012 From: metatracker at psf.upfronthosting.co.za (Giampaolo Rodola') Date: Wed, 23 May 2012 16:38:00 +0000 Subject: [Tracker-discuss] [issue339] Colors for quoted text In-Reply-To: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za> Message-ID: <1337791080.2.0.20928221727.issue339@psf.upfronthosting.co.za> Giampaolo Rodola' added the comment: Being a fan of google mail, I personally like #500050 color, which I've also seen used else where in public forums and similars. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri May 25 19:43:59 2012 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Fri, 25 May 2012 17:43:59 +0000 Subject: [Tracker-discuss] [issue463] HTTPS only version for login for this tracker In-Reply-To: <1337666026.16.0.0159243982051.issue463@psf.upfronthosting.co.za> Message-ID: <1337967839.0.0.0569785718163.issue463@psf.upfronthosting.co.za> Martin v. L?wis added the comment: The risk isn't really high. Just chose a password that you don't use anywhere else, and the threat of somebody stealing it can be safely ignored. Somebody might be posting in your name, but that doesn't scare me at all. ---------- nosy: +loewis status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From martin at v.loewis.de Fri May 25 19:57:51 2012 From: martin at v.loewis.de (martin at v.loewis.de) Date: Fri, 25 May 2012 19:57:51 +0200 Subject: [Tracker-discuss] Rietveld update Message-ID: <20120525195751.Horde.h5spV6GZi1VPv8gfJLFUMFA@webmail.df.eu> As some have probably noticed: I updated the Rietveld version that we use to the current code base. There have been a few incompatible changes (schema, GAE API) which I hope I resolved. If you find new problems, please report them to the meta tracker. Regards, Martin From metatracker at psf.upfronthosting.co.za Fri May 25 22:39:05 2012 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Fri, 25 May 2012 20:39:05 +0000 Subject: [Tracker-discuss] [issue463] HTTPS only version for login for this tracker In-Reply-To: <1337666026.16.0.0159243982051.issue463@psf.upfronthosting.co.za> Message-ID: <1337978345.51.0.17719685743.issue463@psf.upfronthosting.co.za> anatoly techtonik added the comment: I will be interested to know how many developers are using the same password for all *.python.org services. Can you run a hash compare check to see that the risk is really not that high? ---------- priority: wish -> critical _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat May 26 00:52:43 2012 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Fri, 25 May 2012 22:52:43 +0000 Subject: [Tracker-discuss] [issue463] HTTPS only version for login for this tracker In-Reply-To: <1337666026.16.0.0159243982051.issue463@psf.upfronthosting.co.za> Message-ID: <1337986363.98.0.0922545665278.issue463@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Comparing the password hashes is inconclusive; the passwords are salted. In any case, this issue is about a problem that you perceive for yourself. Whether or not other people feel likewise threatened, we cannot know. ---------- priority: critical -> wish _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 29 12:49:00 2012 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 29 May 2012 10:49:00 +0000 Subject: [Tracker-discuss] [issue463] HTTPS only version for login for this tracker In-Reply-To: <1337666026.16.0.0159243982051.issue463@psf.upfronthosting.co.za> Message-ID: <1338288540.55.0.938049746933.issue463@psf.upfronthosting.co.za> R David Murray added the comment: I use unique passwords for all services for exactly this reason so I, for one, am not worried. ---------- nosy: +r.david.murray _______________________________________________________ PSF Meta Tracker _______________________________________________________