From metatracker at psf.upfronthosting.co.za Wed Jun 2 13:58:50 2010 From: metatracker at psf.upfronthosting.co.za (Yaniv Aknin) Date: Wed, 02 Jun 2010 11:58:50 +0000 Subject: [Tracker-discuss] [issue340] Add 'website' component to report www.python.org issues In-Reply-To: <1275479930.06.0.353171360103.issue340@psf.upfronthosting.co.za> Message-ID: <1275479930.06.0.353171360103.issue340@psf.upfronthosting.co.za> New submission from Yaniv Aknin : The topic says it all; I believe just like we have a 'documentation' component we should have a 'website' component to allow bugs/patches to be reported against python.org itself (especially the development documents, but maybe not just). ---------- messages: 1667 nosy: yaniv.aknin priority: feature status: unread title: Add 'website' component to report www.python.org issues _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jun 2 17:44:17 2010 From: metatracker at psf.upfronthosting.co.za (techtonik) Date: Wed, 02 Jun 2010 15:44:17 +0000 Subject: [Tracker-discuss] [issue340] Add 'website' component to report www.python.org issues In-Reply-To: <1275479930.06.0.353171360103.issue340@psf.upfronthosting.co.za> Message-ID: <1275493457.72.0.975832947154.issue340@psf.upfronthosting.co.za> techtonik added the comment: http://wiki.python.org/moin/SiteImprovements - for now the last entry in Miscellaneous. I've put it on hold, because Rich Leland proposed to make a research of http://richleland.bitbucket.org/pydotorg-pm/ pydotorg infrastructure and present a proposal for improvement. The full research is planned to be presented in two weeks. http://richleland.bitbucket.org/pydotorg-pm/timeline.html ---------- nosy: +techtonik status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jun 2 19:02:02 2010 From: metatracker at psf.upfronthosting.co.za (techtonik) Date: Wed, 02 Jun 2010 17:02:02 +0000 Subject: [Tracker-discuss] [issue340] Add 'website' component to report www.python.org issues In-Reply-To: <1275479930.06.0.353171360103.issue340@psf.upfronthosting.co.za> Message-ID: <1275498122.76.0.180699392084.issue340@psf.upfronthosting.co.za> techtonik added the comment: Given that supporting yet another Roundup tracker takes too much energy (due to badly defined and outdated process), I wonder if we could/should use Google Code (or any other tracker) for this purpose. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Jun 3 00:58:27 2010 From: metatracker at psf.upfronthosting.co.za (Giampaolo Rodola') Date: Wed, 02 Jun 2010 22:58:27 +0000 Subject: [Tracker-discuss] [issue339] Colored sintax for quoted text In-Reply-To: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za> Message-ID: <1275519507.23.0.22902560035.issue339@psf.upfronthosting.co.za> Giampaolo Rodola' added the comment: My intention was not to introduce a quote button but have the server parse the messages, check for "line.startswith('>')" and assign a different color via CSS. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From techtonik at gmail.com Thu Jun 3 10:16:39 2010 From: techtonik at gmail.com (anatoly techtonik) Date: Thu, 3 Jun 2010 11:16:39 +0300 Subject: [Tracker-discuss] confusing committed/rejected status Message-ID: How about splitting committed/rejected into two? This will remove unneeded uncertainty that requires to skip to the end of an issue for actual status check. -- anatoly t. From brett at python.org Thu Jun 3 19:52:56 2010 From: brett at python.org (Brett Cannon) Date: Thu, 3 Jun 2010 10:52:56 -0700 Subject: [Tracker-discuss] confusing committed/rejected status In-Reply-To: References: Message-ID: The stage field is going to disappear at some point; it was an experiment that showed it would be good to mark what is needed to be done, but that it shouldn't be a dropbox. I suspect Ezio's GSoC project will make sure this field gets cleaned up. On Thu, Jun 3, 2010 at 01:16, anatoly techtonik wrote: > How about splitting committed/rejected into two? > This will remove unneeded uncertainty that requires to skip to the end > of an issue for actual status check. > -- > anatoly t. > _______________________________________________ > Tracker-discuss mailing list > Tracker-discuss at python.org > http://mail.python.org/mailman/listinfo/tracker-discuss > From techtonik at gmail.com Sat Jun 5 17:41:27 2010 From: techtonik at gmail.com (anatoly techtonik) Date: Sat, 5 Jun 2010 18:41:27 +0300 Subject: [Tracker-discuss] confusing committed/rejected status In-Reply-To: References:

Message-ID: It may never happen. Is it that hard to change label to just "committed" for now? If I understand correctly there are already two resolutions - "won't fix" and "rejected" that are used instead. -- anatoly t. On Thu, Jun 3, 2010 at 8:52 PM, Brett Cannon wrote: > The stage field is going to disappear at some point; it was an > experiment that showed it would be good to mark what is needed to be > done, but that it shouldn't be a dropbox. I suspect Ezio's GSoC > project will make sure this field gets cleaned up. > > On Thu, Jun 3, 2010 at 01:16, anatoly techtonik wrote: >> How about splitting committed/rejected into two? >> This will remove unneeded uncertainty that requires to skip to the end >> of an issue for actual status check. >> -- >> anatoly t. >> _______________________________________________ >> Tracker-discuss mailing list >> Tracker-discuss at python.org >> http://mail.python.org/mailman/listinfo/tracker-discuss >> > From georg at python.org Sat Jun 5 17:47:26 2010 From: georg at python.org (Georg Brandl) Date: Sat, 05 Jun 2010 17:47:26 +0200 Subject: [Tracker-discuss] confusing committed/rejected status In-Reply-To: References:

Message-ID: <4C0A718E.1000708@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 05.06.2010 17:41, schrieb anatoly techtonik: > It may never happen. Is it that hard to change label to just > "committed" for now? If I understand correctly there are already two > resolutions - "won't fix" and "rejected" that are used instead. Well, the resolution field is different from the stage field. The committed/rejected stage applies for "fixed" as well as for "rejected". How about renaming it to "done"? Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEARECAAYFAkwKcY4ACgkQN9GcIYhpnLAVPwCgsQ8hDL/gmRt3fS9+Kz3kT0jm B6cAoI/hzctdrOgLCRatFQWZT0LumYrm =LgYV -----END PGP SIGNATURE----- From techtonik at gmail.com Sat Jun 5 17:54:51 2010 From: techtonik at gmail.com (anatoly techtonik) Date: Sat, 5 Jun 2010 18:54:51 +0300 Subject: [Tracker-discuss] confusing committed/rejected status In-Reply-To: <4C0A718E.1000708@python.org> References:

<4C0A718E.1000708@python.org> Message-ID: On Sat, Jun 5, 2010 at 6:47 PM, Georg Brandl wrote: > > Am 05.06.2010 17:41, schrieb anatoly techtonik: >> It may never happen. Is it that hard to change label to just >> "committed" for now? If I understand correctly there are already two >> resolutions - "won't fix" and "rejected" that are used instead. > > Well, the resolution field is different from the stage field. ?The > committed/rejected stage applies for "fixed" as well as for "rejected". > > How about renaming it to "done"? Ok to me. I just thought it should be possible to leave it blank in some cases. -- anatoly t. From metatracker at psf.upfronthosting.co.za Fri Jun 11 19:31:15 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=) Date: Fri, 11 Jun 2010 17:31:15 +0000 Subject: [Tracker-discuss] [issue17] Chronological sort order of comments Message-ID: <1276277475.31.0.348354681185.issue17@psf.upfronthosting.co.za> ?ric Araujo added the comment: As a user of the Python and Mercurial roundup instances, I can testify that reverse chronological order is highly annoying. I have to scroll down to read the first message, and for each long message, I have to do the up-down-up dance. I agree that it?s a tiny bit unpractical to get to the newest message, but that?s another issue (add a jump link near the top of the page). Cheers :) ---------- nosy: +merwok status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Jun 11 19:34:43 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=) Date: Fri, 11 Jun 2010 17:34:43 +0000 Subject: [Tracker-discuss] [issue17] Chronological sort order of comments Message-ID: <1276277683.59.0.640252429882.issue17@psf.upfronthosting.co.za> ?ric Araujo added the comment: Sorry for the noise, I didn?t notice I reopened the bug. It?s hard to tell if bugs concern the bugs.python.org installation or Roundup itself. Is there another bug where I can advocate setting chronological order by default? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Jun 11 20:22:19 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Fri, 11 Jun 2010 18:22:19 +0000 Subject: [Tracker-discuss] [issue17] Chronological sort order of comments Message-ID: <1276280539.72.0.452412567865.issue17@psf.upfronthosting.co.za> Martin v. L?wis added the comment: You should use the bug tracker of roundup, not this meta tracker. ---------- nosy: +loewis status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Jun 14 16:39:11 2010 From: metatracker at psf.upfronthosting.co.za (techtonik) Date: Mon, 14 Jun 2010 14:39:11 +0000 Subject: [Tracker-discuss] [issue17] Chronological sort order of comments Message-ID: <1276526351.63.0.143167031205.issue17@psf.upfronthosting.co.za> techtonik added the comment: I would reopen this bug to add an user setting for sorting order. ---------- nosy: +techtonik status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Jun 14 16:47:22 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=) Date: Mon, 14 Jun 2010 14:47:22 +0000 Subject: [Tracker-discuss] [issue17] Chronological sort order of comments Message-ID: <1276526842.14.0.474989213951.issue17@psf.upfronthosting.co.za> ?ric Araujo added the comment: Please don?t. You?re making the same mistake that I?ve been corrected for: This bug is about the bugs.python.org instance, not Roundup in general. ---------- status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jun 15 09:30:53 2010 From: metatracker at psf.upfronthosting.co.za (techtonik) Date: Tue, 15 Jun 2010 07:30:53 +0000 Subject: [Tracker-discuss] [issue17] Chronological sort order of comments Message-ID: <1276587053.84.0.177323121466.issue17@psf.upfronthosting.co.za> techtonik added the comment: I do not know if Roundup has a user setting for message order, but I want it for b.p.o - it may have some plugin or something. ---------- status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Jun 18 17:41:29 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 18 Jun 2010 15:41:29 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1276875689.09.0.310314977833.issue266@psf.upfronthosting.co.za> Ezio Melotti added the comment: Here is a new patch to add the 'add me to nosy' button. While doing the patch I took the following decisions: 1) Add self to nosy is a common operation and it's not easy to do (either click on the field and write the username, or click on "list", fill in the form, search, select the name, apply), so it definitely deserves a button; 2) On the other hand, removing self from nosy is not that common and it's easier to do (select the name and hit delete on the keyboard), so IMHO it doesn't deserve a button; 3) Assign an issue to self is not a common operation and it can be already done quite easily (click, scroll, click), so it doesn't deserve a 'claim' button; In this way an 'Add me' button will be visible only on the issues where the user is not nosy. If the user decides to add himself to the nosy the button will disappear and the user won't see any other button while visiting the issue again the following times. If the user doesn't care about that issue it will just leave it there. Therefore the impact on the tracker should be minimal. In the patch I used TAL to create the button only if the user is registered and the name is not in the nosy list. The button has display:none and it's made visible by javascript. This makes sure that if the user doesn't have JS enabled the button won't be available. I put the JS code to make the button visible and the callback function to add the user to the nosy list in a separate file to keep the JS separate from the HTML. The following thing should be checked before committing: 1) does the script deserves a whole new js file? if so a more appropriate name should be selected (I used help_controls2.js because there is already an help_controls.js file -- also note that I could use the same file for other patches, I just didn't use help_controls.js because I wasn't sure it was related in any way); 2) is the position and size of the button OK?; 3) when the button is pressed the name is added and then it disappears, causing a minor change in the layout. This should usually be avoided, but IMHO in this case is not a big problem, since I don't see how it can practically affect the usability. ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti, merwok status: chatting -> in-progress _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: issue266.diff Type: text/x-diff Size: 2590 bytes Desc: not available URL: From metatracker at psf.upfronthosting.co.za Sat Jun 19 17:11:18 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 19 Jun 2010 15:11:18 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1276960278.7.0.232759225206.issue266@psf.upfronthosting.co.za> Ezio Melotti added the comment: Here is another version (issue266B.diff) of the same patch that instead of adding an 'Add me' button under the input box, adds a [ + ] button on the right. Even if less obvious than the 'Add me' button, it's less invasive, it doesn't take another line and the layout doesn't when the button disappears. To make it more obvious, the text 'Add me to the nosy list' appears when the pointer is on the button. Another advantage is that some users might expect the 'Add me' button to submit the change immediately when it's still necessary to click on 'Submit changes'. _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: issue266B.diff Type: text/x-diff Size: 3198 bytes Desc: not available URL: From metatracker at psf.upfronthosting.co.za Sat Jun 19 18:03:49 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 19 Jun 2010 16:03:49 +0000 Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za> Message-ID: <1276963429.86.0.115219523426.issue312@psf.upfronthosting.co.za> Ezio Melotti added the comment: Here is a patch that adds a "jump to the last message" link on the right of the "Messages (N)" (just before the first message). Once clicked the link will "scroll" the page till the last message, using a simple anchor (i.e. issueXXXX#msgYYYYY). The patch is still incomplete, a "jump to the top" link should be added on the bottom of the page (maybe next the "History") and the link could look better. ---------- assignedto: -> ezio.melotti nosy: +amk status: unread -> in-progress _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: issue312.diff Type: text/x-diff Size: 1434 bytes Desc: not available URL: From metatracker at psf.upfronthosting.co.za Sat Jun 19 18:27:59 2010 From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou) Date: Sat, 19 Jun 2010 16:27:59 +0000 Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za> Message-ID: <1276964879.07.0.267287102469.issue312@psf.upfronthosting.co.za> Antoine Pitrou added the comment: Followup after a quick discussion on IRC: - using the "end" key brings you to the bottom of the page, which is almost the last message - making the "history" section folded by default would make "end" jump you to the last message directly - adding usability "features" can decrease overall usability by making the UI more cluttered, less intuitive, visually heavier and more cumbersone - Ezio's point that cellphones don't have an "end" key was countered by Jp Calderone mentioning that a cellphone-specific CSS can be designed, so as to better cater to their specific characteristics ---------- nosy: +pitrou _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Jun 19 20:13:38 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=) Date: Sat, 19 Jun 2010 18:13:38 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1276971218.08.0.147172842627.issue266@psf.upfronthosting.co.za> ?ric Araujo added the comment: I don?t know TAL at all but is it normal that the variable in this line onclick="add_to_nosy(the_current_username)" does not match the one in this previous line: tal:define="current_user request/user/username" More important remark: What about people without JavaScript? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Jun 19 20:25:21 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 19 Jun 2010 18:25:21 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1276971921.03.0.139057088078.issue266@psf.upfronthosting.co.za> Ezio Melotti added the comment: 'the_current_username' is just a placeholder and it is replaced by the tal:attributes in the previous line. The button won't be displayed for people without Javascript because it's hidden by default using CSS. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Jun 19 21:44:48 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=) Date: Sat, 19 Jun 2010 19:44:48 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1276976688.18.0.0414125619339.issue266@psf.upfronthosting.co.za> ?ric Araujo added the comment: I?m concerned that people without JavaScript won?t benefit from this improvement, and that people without JavaScript nor CSS will get the button but not the functionality. One way to look at Web development is to write HTML+CSS+JavaScript and think about graceful degradation, whereas another way is to write HTM+server-side code that work, and then add CSS and JavaSript as progressive enhancement. It?s a bit more work, since you have e.g. to dynamically add controls that trigger JavaScript callbacks or modify existing controls. Roundup is near entirely usable (and I mean not only possible to use, but really fine) without CSS, JavaScript nor frames, and it?s a good thing?. I won?t scream or ague to death if my concern is rejected. I wanted to express it, now that?s done, and it?s up to you to accept or reject it. Thanks for your work :) _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Jun 19 22:44:11 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sat, 19 Jun 2010 20:44:11 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1276980251.5.0.389347928366.issue266@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I think I like the "Add me" version better; the single plus gives no clue what it will do. As for JavaScript: I think it's fine to use it in this case. People without JS can still add themselves manually. If people are negatively affected by this change, they still can report that here (and failing any fix, we could revert the change). _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 20 18:36:43 2010 From: metatracker at psf.upfronthosting.co.za (A.M. Kuchling) Date: Sun, 20 Jun 2010 16:36:43 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1277051803.51.0.928010078672.issue266@psf.upfronthosting.co.za> A.M. Kuchling added the comment: I prefer 'Add me' instead of '+', but am worried that most people will not expect that submitting the form is necessary; most AJAX web sites will make the change immediately. Maybe different text could clarify this, but I can't think of an alternative wording. I suggest keeping all the JS code in one file (help_controls.js), so that there's one place to look for the definition of a particular function or handler. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Jun 25 21:04:16 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 25 Jun 2010 19:04:16 +0000 Subject: [Tracker-discuss] [issue304] Display of HTTP URLs is borked. In-Reply-To: <1256823316.36.0.698718751835.issue304@psf.upfronthosting.co.za> Message-ID: <1277492656.47.0.741487608429.issue304@psf.upfronthosting.co.za> Ezio Melotti added the comment: This should be fixed with r82219. ---------- assignedto: -> ezio.melotti status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Jun 26 01:35:12 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 25 Jun 2010 23:35:12 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1277508912.74.0.676383496931.issue266@psf.upfronthosting.co.za> Ezio Melotti added the comment: Here is a new patch (266C). > I prefer 'Add me' instead of '+', but am worried that most people will not expect that submitting the form is necessary; That's the reason why I don't like it. This new patch uses the [+] button (a few more developers on #python-dev prefer the [+]) and also has 'Add me to nosy (remember to Submit Changes)' as title="" text. > I suggest keeping all the JS code in one file (help_controls.js), so that there's one place to look for the definition of a particular function or handler. Since the other js file is not used by issue.item.html, I decided to put the js code in issue.item.js, also because the functions are specific to issue.item.html. This should make finding definitions even easier. > I think I like the "Add me" version better; the single plus gives no clue what it will do. I think that given the position, its purpose is quite obvious. The title="" text or even trying to press it to see what happens will clarify any doubt. > [...] people without JavaScript nor CSS will get the button but not the functionality. This is now fixed. The solution I adopted is to add an empty span that doesn't show up when CSS are not available, and then replace it with the button if JS is available. I tested it with a text browser (links) and it seems to work fine. I agree with MvL that people without JS can add themselves manually. I also solved a couple of compatibility problems with IE. The only remaining problem is that when a new issue is created the nosy list is empty and the button appears. I think it would be better if the user name would show up already when a new issue is created but I still have to figure out how to do it server-side. Another minor improvement is to write the username always at the beginning of the list. In this way it's easier to select and delete self from the nosy even without a [-] button. I suggest to commit the patch as is and see what people say. _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: issue266C.diff Type: text/x-diff Size: 3443 bytes Desc: not available URL: From metatracker at psf.upfronthosting.co.za Sat Jun 26 05:21:38 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 26 Jun 2010 03:21:38 +0000 Subject: [Tracker-discuss] [issue311] Change default search to make duplicate issues less likely In-Reply-To: <1262914574.94.0.0439579037453.issue311@psf.upfronthosting.co.za> Message-ID: <1277522498.4.0.639386596816.issue311@psf.upfronthosting.co.za> Ezio Melotti added the comment: Fixed the default search to use 'all' by default and make it available for non-logged-in users in r82240 and fixed the grouping in r82241. ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Jun 26 23:47:29 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 26 Jun 2010 21:47:29 +0000 Subject: [Tracker-discuss] [issue262] Ignore file content in 'All text' search In-Reply-To: <1238989669.77.0.307325287973.issue262@psf.upfronthosting.co.za> Message-ID: <1277588849.1.0.93273528349.issue262@psf.upfronthosting.co.za> Ezio Melotti added the comment: I thought about a few solutions to this problem. In the search page we could: 1) Add an "Attachment" field just after the "All text" and "Title" fields in the search page, and change the "All text" field to either search only in the messages or messages and title. This is more complicated but more flexible. 2) Have a single "Text" field with 3 check-boxes: "Messages", "Title", "Attachments". This won't allow searching different things in different places but it's easier to use. 3) Just add a "search in attachments" check-box and change the "All text" search to search only in messages and titles. The default search should just ignore files by default. ---------- nosy: +amk, ezio.melotti, loewis _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 27 00:21:54 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 26 Jun 2010 22:21:54 +0000 Subject: [Tracker-discuss] [issue285] Add issue title to issue links, avoid linking to bogus issues In-Reply-To: <1242322496.14.0.859560166441.issue285@psf.upfronthosting.co.za> Message-ID: <1277590914.71.0.484316020187.issue285@psf.upfronthosting.co.za> Ezio Melotti added the comment: > The attached patch: > * Fixes an 'integer too large' error in templating.py that causes issues to be undisplayable. How do you get this error exactly? > * Adds title attributes to Roundup's class links (e.g. 'version 1'). > * Moves in-message issue links of the form 'issue 123' from templating.py to local_replace.py. I'd rather see the opposite. IMHO roundup should add a link to #NNNN too. In local_replace there should be only Python-specific replaces (like links to the files and revisions). > * Adds issue titles to issue links in dependencies and message bodies. > * Adds the 'open' or 'closed' CSS classes to issue links. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 27 01:44:47 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 26 Jun 2010 23:44:47 +0000 Subject: [Tracker-discuss] [issue253] Remove outdated keywords In-Reply-To: <1237513464.32.0.072891570662.issue253@psf.upfronthosting.co.za> Message-ID: <1277595887.69.0.546391125986.issue253@psf.upfronthosting.co.za> Ezio Melotti added the comment: Here are some updated stats about some of the keywords: * 26backports: 8 issues * 64bits : 4 issues [0] * after mor. : 2 issues Since "[26backport] was clearly intended to tag backporting of py3 features to py2 (and thus misnamed to start with)" and now it's too late to add any features to 2.x, I think it could be already removed. I would remove 64bits too, since it doesn't seem really used and I don't think anyone needs to search 64bits-related issues (see also [0]). The "easy" and "buildbot" keyword are useful; the "after moratorium" and "gsoc" will probably be removed at some point anyway. Regarding needs/has test/patch/doc, I think that check-boxes would be a good idea. I'll try to do some experiment and see how it works. [0]: I'm not sure why #6673 has the 64bits keyword, and #8482 is a problem on 32 machines too (see last message), #1789 is just a doc patch now. ---------- nosy: +ezio.melotti _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 27 01:46:30 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 26 Jun 2010 23:46:30 +0000 Subject: [Tracker-discuss] [issue254] Roundup treats badly In-Reply-To: <1238038227.04.0.719265951876.issue254@psf.upfronthosting.co.za> Message-ID: <1277595990.62.0.536293747734.issue254@psf.upfronthosting.co.za> Ezio Melotti added the comment: This problem exists with ')' too. ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 27 02:18:10 2010 From: metatracker at psf.upfronthosting.co.za (Brett C.) Date: Sun, 27 Jun 2010 00:18:10 +0000 Subject: [Tracker-discuss] [issue253] Remove outdated keywords In-Reply-To: <1237513464.32.0.072891570662.issue253@psf.upfronthosting.co.za> Message-ID: <1277597890.63.0.106858563914.issue253@psf.upfronthosting.co.za> Brett C. added the comment: 26backport can definitely go. 64bits is marginally used and can go as well, IMO. And I look forward to the checkbox experiment as I suspect it will work out nicely. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 27 08:48:20 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sun, 27 Jun 2010 06:48:20 +0000 Subject: [Tracker-discuss] [issue254] Roundup treats badly In-Reply-To: <1238038227.04.0.719265951876.issue254@psf.upfronthosting.co.za> Message-ID: <1277621300.98.0.672653826107.issue254@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I disagree: ')' can be, and actually is, part of the URL. For example, Microsoft hosts URLs like http://msdn.microsoft.com/en-us/library/ms741540(VS.85).aspx ---------- nosy: +loewis _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 27 08:54:49 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sun, 27 Jun 2010 06:54:49 +0000 Subject: [Tracker-discuss] [issue253] Remove outdated keywords In-Reply-To: <1237513464.32.0.072891570662.issue253@psf.upfronthosting.co.za> Message-ID: <1277621689.95.0.0964754582194.issue253@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I have now retired these two keywords. ---------- status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jun 27 12:04:31 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sun, 27 Jun 2010 10:04:31 +0000 Subject: [Tracker-discuss] [issue254] Roundup treats badly In-Reply-To: <1238038227.04.0.719265951876.issue254@psf.upfronthosting.co.za> Message-ID: <1277633071.99.0.2876782946.issue254@psf.upfronthosting.co.za> Ezio Melotti added the comment: That's not a problem, it's easy to allow ')' inside the URL but not at the end. Some Wikipedia links also use ')' at the end (e.g. http://en.wikipedia.org/wiki/Python_(programming_language)), but I think it's more common to have links enclosed in () than links that contain and end with a ')' (however I think it might still be possible to distinguish between URLs enclosed in () and URLs that end with ')'). On a side note, on my instance of the tracker the '>' is not included in the link, let's see if here it is: . _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Jun 28 18:11:56 2010 From: metatracker at psf.upfronthosting.co.za (techtonik) Date: Mon, 28 Jun 2010 16:11:56 +0000 Subject: [Tracker-discuss] [issue341] API keyword In-Reply-To: <1277741516.74.0.997184171572.issue341@psf.upfronthosting.co.za> Message-ID: <1277741516.74.0.997184171572.issue341@psf.upfronthosting.co.za> New submission from techtonik : Need API keyword to search/filter API proposals. ---------- messages: 1698 nosy: techtonik priority: feature status: unread title: API keyword _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Jun 28 22:54:17 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Mon, 28 Jun 2010 20:54:17 +0000 Subject: [Tracker-discuss] [issue341] API keyword In-Reply-To: <1277741516.74.0.997184171572.issue341@psf.upfronthosting.co.za> Message-ID: <1277758457.1.0.340648884409.issue341@psf.upfronthosting.co.za> Martin v. L?wis added the comment: -1. There is no point in classifying rejected issues, plus I doubt that there are many issues that ought to be classified under this keyword. ---------- nosy: +loewis status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jun 29 00:20:35 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Mon, 28 Jun 2010 22:20:35 +0000 Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy list, assign issue to self In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za> Message-ID: <1277763635.61.0.759242121538.issue266@psf.upfronthosting.co.za> Ezio Melotti added the comment: I committed the last patch in r82348. I'm leaving this open waiting for some feedback. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jun 29 02:20:50 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Tue, 29 Jun 2010 00:20:50 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1277770850.0.0.825216886873.issue337@psf.upfronthosting.co.za> Martin v. L?wis added the comment: This is now fixed in r82353. ---------- status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jun 29 16:20:16 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=) Date: Tue, 29 Jun 2010 14:20:16 +0000 Subject: [Tracker-discuss] [issue341] API keyword In-Reply-To: <1277741516.74.0.997184171572.issue341@psf.upfronthosting.co.za> Message-ID: <1277821216.26.0.722557235551.issue341@psf.upfronthosting.co.za> ?ric Araujo added the comment: Also, PEP 0 and PEP 42 fill that purpose. ---------- nosy: +merwok _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jun 30 00:42:11 2010 From: metatracker at psf.upfronthosting.co.za (techtonik) Date: Tue, 29 Jun 2010 22:42:11 +0000 Subject: [Tracker-discuss] [issue341] API keyword In-Reply-To: <1277821216.26.0.722557235551.issue341@psf.upfronthosting.co.za> Message-ID: techtonik added the comment: On Tue, Jun 29, 2010 at 5:20 PM, ?ric Araujo wrote: > > Also, PEP 0 and PEP 42 fill that purpose. These are: 1. 10 years old 2. general public don't have access to propose enhancements to these _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jun 30 03:36:15 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 30 Jun 2010 01:36:15 +0000 Subject: [Tracker-discuss] [issue262] Ignore file content in 'All text' search In-Reply-To: <1238989669.77.0.307325287973.issue262@psf.upfronthosting.co.za> Message-ID: <1277861775.76.0.846046439325.issue262@psf.upfronthosting.co.za> Ezio Melotti added the comment: This patch includes both the previous patches but, instead of adding a text field that allows to ignore any pair of "class:property", it just adds an "Ignore attachments" checkbox just under the "All text" field in the search page. The checkbox is checked by default, meaning that the content of the attachment is not included in the search. Searching in the attachment is also turned off from the default search (the one in the top-right corner). Please review and comment. ---------- assignedto: -> ezio.melotti status: chatting -> testing _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: issue262.diff Type: text/x-diff Size: 3469 bytes Desc: not available URL: From metatracker at psf.upfronthosting.co.za Wed Jun 30 23:46:17 2010 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Wed, 30 Jun 2010 21:46:17 +0000 Subject: [Tracker-discuss] [issue342] remove "phone" field for users In-Reply-To: <1277934377.76.0.701119970252.issue342@psf.upfronthosting.co.za> Message-ID: <1277934377.76.0.701119970252.issue342@psf.upfronthosting.co.za> New submission from Georg Brandl : I don't think the "phone" field in the user info serves any useful purpose. Some users seem to faithfully put in their phone numbers, but I don't see how we would ever call a tracker user. Ergo, the field should probably just be removed, at least from the UI. ---------- messages: 1705 nosy: gbrandl priority: wish status: unread title: remove "phone" field for users _______________________________________________________ PSF Meta Tracker _______________________________________________________