From metatracker at psf.upfronthosting.co.za Thu Feb 4 16:36:08 2010 From: metatracker at psf.upfronthosting.co.za (Nicholas Riley) Date: Thu, 04 Feb 2010 15:36:08 +0000 Subject: [Tracker-discuss] [issue316] Users can't attach files on Jython tracker In-Reply-To: <1265297768.52.0.920463244949.issue316@psf.upfronthosting.co.za> Message-ID: <1265297768.52.0.920463244949.issue316@psf.upfronthosting.co.za> New submission from Nicholas Riley : Users are getting "You do not have permission to add a file" when they try to post patches. For example: http://bugs.jython.org/msg5491 ---------- messages: 1531 nosy: nriley priority: bug status: unread title: Users can't attach files on Jython tracker _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Feb 9 11:25:35 2010 From: metatracker at psf.upfronthosting.co.za (Izak Burger) Date: Tue, 09 Feb 2010 10:25:35 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B608EAD.20706@v.loewis.de> Message-ID: <4B713952.70806@upfrontsystems.co.za> Izak Burger added the comment: Martin v. L?wis wrote: > If that's how you would prefer to do it, it's fine with me. I would be > skeptical that everything can be tested, though, e.g. testing the email > setup might be tricky. > > OTOH, on systems that I have to manage, I just accepted to the downtime > and the potential aftermath that it caused, so skipping the test upgrade > would be fine with with me as well. We tested and it seems to upgrade cleanly and things work fine afterwards. My only concern in these cases are things that you compiled yourself, for example you compiled your own version of python2.4. This will be linked with the old library versions, which may or may not work afterwards. Our sysadmin says everything started up fine though, so I agree that these can be handled as they are discovered. The test upgrade took about half an hour. Can we schedule a time for the real thing, a time when someone with knowledge about the tracker can be on standby, preferably between 8 and 2 UTC? regards, Izak _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Feb 9 22:32:55 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Tue, 09 Feb 2010 21:32:55 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B713952.70806@upfrontsystems.co.za> Message-ID: <4B71D483.7020605@v.loewis.de> Martin v. L?wis added the comment: > My only concern in these cases are things that you compiled > yourself, for example you compiled your own version of python2.4. Are you sure about this? Where is this copy located, and where does it get used? I'd prefer to switch to Debian Python before the upgrade. > Can we schedule a time for the real thing, a time when someone with > knowledge about the tracker can be on standby, preferably between 8 and > 2 UTC? How about this Friday, 14:00 UTC? (I'm in GMT+1 myself as well) I could be around on IRC, say #tracker-discuss on freenode. I'd post an announcement to python-dev and python.org tomorrow. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Feb 10 08:35:36 2010 From: metatracker at psf.upfronthosting.co.za (Izak Burger) Date: Wed, 10 Feb 2010 07:35:36 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B71D483.7020605@v.loewis.de> Message-ID: <4B726304.50705@upfrontsystems.co.za> Izak Burger added the comment: Martin v. L?wis wrote: >> My only concern in these cases are things that you compiled >> yourself, for example you compiled your own version of python2.4. > > Are you sure about this? Where is this copy located, and where does it > get used? I'd prefer to switch to Debian Python before the upgrade. Sorry, I meant that to be an example, something that often happens to us on newer debian/ubuntu machines where python2.4 is no longer fully supported and many packages do not provide 2.4 components anymore. I didn't mean to imply you did such a thing, just that this is the only thing I am normally concerned about. If you're using the system python, great, just be advised that the default python has changed from 2.4 to 2.5 as far as I know. > How about this Friday, 14:00 UTC? (I'm in GMT+1 myself as well) I could > be around on IRC, say #tracker-discuss on freenode. I'd post an > announcement to python-dev and python.org tomorrow. I'll tell our sysadmin. I don't think there'd be a problem. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Feb 10 09:14:05 2010 From: metatracker at psf.upfronthosting.co.za (Izak Burger) Date: Wed, 10 Feb 2010 08:14:05 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B726304.50705@upfrontsystems.co.za> Message-ID: <4B726C0B.1020702@upfrontsystems.co.za> Izak Burger added the comment: Izak Burger wrote: >> How about this Friday, 14:00 UTC? (I'm in GMT+1 myself as well) I could >> be around on IRC, say #tracker-discuss on freenode. I'd post an >> announcement to python-dev and python.org tomorrow. > > I'll tell our sysadmin. I don't think there'd be a problem. Our sysadmin is unfortunately unavailable on Friday. Also, he requests that we do this on another day if possible, as upgrades done on a Friday afternoon tends to awaken Murphy and ruin your weekend. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Feb 11 10:54:21 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Thu, 11 Feb 2010 09:54:21 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <1264540410.57.0.767216150288.issue315@psf.upfronthosting.co.za> Message-ID: <1265882061.35.0.877849805758.issue315@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Next suggestion: Monday (15.2.), 14:00 UTC. Ok? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Feb 14 13:23:46 2010 From: metatracker at psf.upfronthosting.co.za (Edward Welbourne) Date: Sun, 14 Feb 2010 12:23:46 +0000 Subject: [Tracker-discuss] [issue299] "Your issues" page empty In-Reply-To: <1253179863.66.0.0238813023224.issue299@psf.upfronthosting.co.za> Message-ID: <1266150226.39.0.833045474666.issue299@psf.upfronthosting.co.za> Edward Welbourne added the comment: "Your issues" is the list of issues that have been assigned to you (i.e. the ones that you are supposed to resolve), not the issues that you have submitted. This is perfectly sensible, but the effect is perfectly incomprehensible for the first-time user - I found this bug because I was about to report the exact same issue. At least when the list is empty, the page should give some hint that it's listing the issues assigned to the user - if only by changing the title from "Your issues" (which could mean several things) to "Issues assigned to you". Somewhat better would be to have a "Your issues" page which actually lists each of the sets of issues one might think of as one's own - one table for issues assigned to you, one for issues you've reported, one for (other) issues you're nosying; each list initially restricted to open issues but with a link to the full list. Alternatively, the navigation panel's "Your issues" (above Your Details and Logout) could become a sub-list with entries "Assigned" (the present page), "Reported" and "Nosy". ... but the newcomer needs to have at least *some* reasonably easy way to find "where's that issue I just reported", or the whole thing is just baffling. You'll have to create a custom query; this isn't difficult though. Hard to comment on that: on bugs.python.org, the Help item for "Tracker Documentation" links to a FAQ-style page on wiki.python.org, from which isn't immediately obvious how to actually find documentation of the tracker itself; I haven't checked *every* link there but, at a cursory search, it doesn't appear to link to the "Roundup docs" page that this meta-tracker page offers as Help link. Adding that link to the python BTS's help sub-menu would be a smart move ! Further: the "Your issues" page has a "Your Queries" section, initially empty, and an edit link; which gives me a page in which to select from among a bunch of pre-existing queries, none of which is the one I want. There's a Search option, in two places on the page, but when I do such a search there's no (immediately visible) way to "Add this to Your Queries" or remember this query in some other way, for future use. If there's a way to do custom queries, and it's the only way to get at the list that a new user most obviously does want to see, there should be an easy way for the new user to discover this, right there on the front page. Requiring new users to read a reference manual is not part of a user-friendly interface: it will put off folk who might otherwise be making the vital contribution of providing feed-back on the quality of python (and its docs). The present "assigned to you" default screen is geared towards developers (those who fix stuff); but the experience needs to be friendlier towards testers (those who tell you what needs fixed). Even the overhead of having to register (and guess a username that might not yet be in use - the registration process gave me no obvious way to find out whether the username I wanted was avaiable; what'll happen to the next Eddy to come along ?) will put off a fair proportion of those who might have reported issues. A baffling home-page once logged in will take another bite out of their dedication ... ---------- nosy: +eddy _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Feb 14 13:42:29 2010 From: metatracker at psf.upfronthosting.co.za (Edward Welbourne) Date: Sun, 14 Feb 2010 12:42:29 +0000 Subject: [Tracker-discuss] [issue299] "Your issues" page empty In-Reply-To: <1253179863.66.0.0238813023224.issue299@psf.upfronthosting.co.za> Message-ID: <1266151349.85.0.891247332147.issue299@psf.upfronthosting.co.za> Edward Welbourne added the comment: when I do such a search there's no (immediately visible) way to "Add this to Your Queries" or remember this query in some other way, for future use. I have now found the way to do that - but it would have involved noticing a footnote on one form field, among about two dozen, whose purpose wasn't immediately obvious. In practice I only found it by reading the reference manual, which told me what I'd missed. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Feb 14 14:36:45 2010 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Sun, 14 Feb 2010 13:36:45 +0000 Subject: [Tracker-discuss] [issue299] "Your issues" page empty In-Reply-To: <1253179863.66.0.0238813023224.issue299@psf.upfronthosting.co.za> Message-ID: <1266154605.33.0.0991187646578.issue299@psf.upfronthosting.co.za> Georg Brandl added the comment: I agree with most of what you said. In particular, a direct link to the Roundup docs would be good, and renaming "your issues" to "issues assigned to you" (note however that that's from the default roundup template, and should therefore be reported to roundup). A sentence on how to create a query on the "edit queries" page is also a very good suggestion. Note that there is now OpenID support for those who don't want to remember another username and password, and that's as far as we can go. Accepting anonymous submissions would simply be asking too much of our volunteers: the amount of spam would increase dramatically, and there would be no way for the reporter to get notified of questions and the need for more information, which leaves many issues dangling even now. ---------- nosy: +gbrandl _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Feb 14 19:26:01 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sun, 14 Feb 2010 18:26:01 +0000 Subject: [Tracker-discuss] [issue299] "Your issues" page empty In-Reply-To: <1253179863.66.0.0238813023224.issue299@psf.upfronthosting.co.za> Message-ID: <1266171961.56.0.842516225955.issue299@psf.upfronthosting.co.za> Ezio Melotti added the comment: IMHO the "Your Issues" section could even be hidden to non-developers. It would even be better to have "Issues opened by you" for both devs and non-devs and "Your Issues" for devs only. ---------- nosy: +ezio.melotti _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Feb 14 19:33:53 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sun, 14 Feb 2010 18:33:53 +0000 Subject: [Tracker-discuss] [issue299] "Your issues" page empty In-Reply-To: <1253179863.66.0.0238813023224.issue299@psf.upfronthosting.co.za> Message-ID: <1266172433.97.0.930521044625.issue299@psf.upfronthosting.co.za> Martin v. L?wis added the comment: eddy: it would have been better had you reported that a) as a new issue, rather than commenting on an issue that was objectively resolved, and b) had reported each of your points as a separate issue. Most likely, nothing will happen on this issue for many months to come. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Feb 15 08:13:01 2010 From: metatracker at psf.upfronthosting.co.za (Izak Burger) Date: Mon, 15 Feb 2010 07:13:01 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <1265882061.35.0.877849805758.issue315@psf.upfronthosting.co.za> Message-ID: <4B78F54C.7070901@upfrontsystems.co.za> Izak Burger added the comment: Martin v. L?wis wrote: > Next suggestion: Monday (15.2.), 14:00 UTC. Ok? I'm sorry for replying this late. Yes, the suggested time is perfect. We also need to update the host on which this virtual machine runs, but we'll let you know when we do that. regards, Izak _______________________________________________________ PSF Meta Tracker _______________________________________________________ From martin at v.loewis.de Mon Feb 15 08:24:08 2010 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Mon, 15 Feb 2010 08:24:08 +0100 Subject: [Tracker-discuss] Tracker outage Message-ID: <4B78F698.2070208@v.loewis.de> Starting around 14:00 UTC today, we will take the trackers at bugs.python.org, bugs.jython.org, and psf.upfronthosting.co.za offline for a system upgrade. The outage should not last longer than four hours (probably much shorter). Regards, Martin From metatracker at psf.upfronthosting.co.za Mon Feb 15 08:29:19 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Mon, 15 Feb 2010 07:29:19 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B78F54C.7070901@upfrontsystems.co.za> Message-ID: <4B78F7CD.2020002@v.loewis.de> Martin v. L?wis added the comment: I have now announced the outage. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Feb 15 13:01:23 2010 From: metatracker at psf.upfronthosting.co.za (Izak Burger) Date: Mon, 15 Feb 2010 12:01:23 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B78F7CD.2020002@v.loewis.de> Message-ID: <4B7938E6.5070109@upfrontsystems.co.za> Izak Burger added the comment: I'm sorry, I missed the UTC bit in the original post. Can we start at 12 UTC (which is pretty much NOW) or within the hour, or postpone? regards, Izak _______________________________________________________ PSF Meta Tracker _______________________________________________________ From izak at upfrontsystems.co.za Mon Feb 15 13:07:02 2010 From: izak at upfrontsystems.co.za (Izak Burger) Date: Mon, 15 Feb 2010 14:07:02 +0200 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B78F7CD.2020002@v.loewis.de> References: <4B78F7CD.2020002@v.loewis.de> Message-ID: <4B7938E6.5070109@upfrontsystems.co.za> I'm sorry, I missed the UTC bit in the original post. Can we start at 12 UTC (which is pretty much NOW) or within the hour, or postpone? regards, Izak From izak at upfrontsystems.co.za Mon Feb 15 14:17:36 2010 From: izak at upfrontsystems.co.za (Izak Burger) Date: Mon, 15 Feb 2010 15:17:36 +0200 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B7938E6.5070109@upfrontsystems.co.za> References: <4B78F7CD.2020002@v.loewis.de> <4B7938E6.5070109@upfrontsystems.co.za> Message-ID: <4B794970.2060707@upfrontsystems.co.za> Hi again, Izak Burger wrote: > I'm sorry, I missed the UTC bit in the original post. Can we start at 12 > UTC (which is pretty much NOW) or within the hour, or postpone? We decided to go ahead and start a little earlier. The upgrade is done and all seems well. The whole upgrade apparently took 10 minutes or so. regards, Izak From metatracker at psf.upfronthosting.co.za Mon Feb 15 14:11:58 2010 From: metatracker at psf.upfronthosting.co.za (Izak Burger) Date: Mon, 15 Feb 2010 13:11:58 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <4B7938E6.5070109@upfrontsystems.co.za> Message-ID: <4B794970.2060707@upfrontsystems.co.za> Izak Burger added the comment: Hi again, Izak Burger wrote: > I'm sorry, I missed the UTC bit in the original post. Can we start at 12 > UTC (which is pretty much NOW) or within the hour, or postpone? We decided to go ahead and start a little earlier. The upgrade is done and all seems well. The whole upgrade apparently took 10 minutes or so. regards, Izak _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Feb 15 14:43:09 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Mon, 15 Feb 2010 13:43:09 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <1264540410.57.0.767216150288.issue315@psf.upfronthosting.co.za> Message-ID: <1266241389.06.0.0197215222724.issue315@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Thanks! I only looked at this now. Marking this issue as resolved, then. In case further problems are detected that require your attention, I'll create new issues. ---------- status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Feb 15 14:48:24 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Mon, 15 Feb 2010 13:48:24 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <1264540410.57.0.767216150288.issue315@psf.upfronthosting.co.za> Message-ID: <1266241704.02.0.821492316082.issue315@psf.upfronthosting.co.za> Martin v. L?wis added the comment: As a follow-up to this issue still, I'll update postgres to 8.3 shortly (so far, only 8.1 is running, which is still from etch). ---------- status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Feb 15 15:41:01 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Mon, 15 Feb 2010 14:41:01 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <1264540410.57.0.767216150288.issue315@psf.upfronthosting.co.za> Message-ID: <1266244861.76.0.0586950810131.issue315@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Database upgrade is now done as well. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Feb 15 15:42:53 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Mon, 15 Feb 2010 14:42:53 +0000 Subject: [Tracker-discuss] [issue315] Upgrade Debian installation In-Reply-To: <1266244861.76.0.0586950810131.issue315@psf.upfronthosting.co.za> Message-ID: <20100215154200.14464r31uprytr8k@webmail.df.eu> Martin v. L?wis added the comment: Checking whether email replies still work. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Feb 16 19:57:08 2010 From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda) Date: Tue, 16 Feb 2010 18:57:08 +0000 Subject: [Tracker-discuss] [issue316] Users can't attach files on Jython tracker In-Reply-To: <1265297768.52.0.920463244949.issue316@psf.upfronthosting.co.za> Message-ID: <1266346628.02.0.45624182939.issue316@psf.upfronthosting.co.za> Raghuram Devarakonda added the comment: There is another report of same issue today on jython-dev. ---------- nosy: +draghuram status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Feb 18 17:46:26 2010 From: metatracker at psf.upfronthosting.co.za (Gregory P. Smith) Date: Thu, 18 Feb 2010 16:46:26 +0000 Subject: [Tracker-discuss] [issue318] Can't login to bugs.python.org - Proxy Error from server In-Reply-To: <1266511586.73.0.160080920106.issue318@psf.upfronthosting.co.za> Message-ID: <1266511586.73.0.160080920106.issue318@psf.upfronthosting.co.za> New submission from Gregory P. Smith : I get the following instead when using either my direct username+password login or my openid (google) login. bugs.python.org username: gregory.p.smith (if that is relevant) Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /. Reason: Error reading from remote server Apache/2.2.9 (Debian) mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.9 OpenSSL/0.9.8g Server at bugs.python.org Port 80 ---------- messages: 1551 nosy: greg priority: urgent status: unread title: Can't login to bugs.python.org - Proxy Error from server _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Feb 18 22:38:28 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Thu, 18 Feb 2010 21:38:28 +0000 Subject: [Tracker-discuss] [issue318] Can't login to bugs.python.org - Proxy Error from server In-Reply-To: <1266511586.73.0.160080920106.issue318@psf.upfronthosting.co.za> Message-ID: <1266529108.23.0.704669835511.issue318@psf.upfronthosting.co.za> Martin v. L?wis added the comment: This happened because you had been the US/Pacific-New timezone. This is a bogus timezone not included in the stable Debian distribution anymore, causing an exception. I have now reset all user with that timezone to US/Pacific and removed the option from the UI. ---------- nosy: +loewis status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Feb 19 15:29:06 2010 From: metatracker at psf.upfronthosting.co.za (A.M. Kuchling) Date: Fri, 19 Feb 2010 14:29:06 +0000 Subject: [Tracker-discuss] [issue319] Add 'need review'/'has patch' queries to default template In-Reply-To: <1266589746.58.0.685271617656.issue319@psf.upfronthosting.co.za> Message-ID: <1266589746.58.0.685271617656.issue319@psf.upfronthosting.co.za> New submission from A.M. Kuchling : At the language summit, someone suggested to me that the tracker should make it easier to find a list of issues needing review or that have a ready-made patch. There are saved queries for these searches, but to access them you first need to register, and then go to the 'edit queries' page to have them displayed. That's a number of steps; we could document those steps, but no one would read them. It seems simpler to just add the queries to the default template. >From testing on a private installation of the tracker, I think I got the queries correct, but obviously the queries should be checked. ---------- files: add-queries.txt messages: 1553 nosy: amk priority: wish status: unread title: Add 'need review'/'has patch' queries to default template _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- diff -r e513b1f2b58b html/page.html --- a/html/page.html Thu Feb 18 21:22:54 2010 -0500 +++ b/html/page.html Fri Feb 19 09:13:18 2010 -0500 @@ -113,6 +113,32 @@ '@startwith': 0, })" i18n:translate="">Show Unassigned +

From metatracker at psf.upfronthosting.co.za Fri Feb 19 17:37:38 2010 From: metatracker at psf.upfronthosting.co.za (A.M. Kuchling) Date: Fri, 19 Feb 2010 16:37:38 +0000 Subject: [Tracker-discuss] [issue268] Add contributor agreement and committer status information In-Reply-To: <1239216201.07.0.276549739609.issue268@psf.upfronthosting.co.za> Message-ID: <1266597458.84.0.852385219883.issue268@psf.upfronthosting.co.za> A.M. Kuchling added the comment: Small enhancement: currently the code shows a '*' on the issue page. The attached patch also shows the '*' on the user index page. Possibly controversial: the tooltip includes the date the agreement was signed. ---------- nosy: +amk _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- diff --git a/html/user.index.html b/html/user.index.html --- a/html/user.index.html +++ b/html/user.index.html @@ -56,7 +56,7 @@ username * + tal:content="user/username">username * From metatracker at psf.upfronthosting.co.za Fri Feb 19 21:12:51 2010 From: metatracker at psf.upfronthosting.co.za (A.M. Kuchling) Date: Fri, 19 Feb 2010 20:12:51 +0000 Subject: [Tracker-discuss] [issue268] Add contributor agreement and committer status information In-Reply-To: <1239216201.07.0.276549739609.issue268@psf.upfronthosting.co.za> Message-ID: <1266610371.58.0.372844201993.issue268@psf.upfronthosting.co.za> A.M. Kuchling added the comment: Oops, I misgenerated my previous patch. Attaching the correct version. _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- diff -r 7dabf3730e54 html/user.index.html --- a/html/user.index.html Thu Feb 18 21:22:55 2010 -0500 +++ b/html/user.index.html Fri Feb 19 15:10:30 2010 -0500 @@ -56,7 +56,7 @@ username + tal:content="user/username">username * From metatracker at psf.upfronthosting.co.za Sat Feb 20 17:09:29 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sat, 20 Feb 2010 16:09:29 +0000 Subject: [Tracker-discuss] [issue319] Add 'need review'/'has patch' queries to default template In-Reply-To: <1266589746.58.0.685271617656.issue319@psf.upfronthosting.co.za> Message-ID: <1266682169.68.0.177839208031.issue319@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Thanks for the patch. Committed as r78251 ---------- nosy: +loewis status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Feb 20 17:20:01 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sat, 20 Feb 2010 16:20:01 +0000 Subject: [Tracker-discuss] [issue268] Add contributor agreement and committer status information In-Reply-To: <1239216201.07.0.276549739609.issue268@psf.upfronthosting.co.za> Message-ID: <1266682801.8.0.880606286408.issue268@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Thanks for the patch. Committed as r78252. I don't worry about displaying the date as well - IIUC, the user index is available to coordinators, only, anyway. ---------- status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Feb 21 01:02:21 2010 From: metatracker at psf.upfronthosting.co.za (A.M. Kuchling) Date: Sun, 21 Feb 2010 00:02:21 +0000 Subject: [Tracker-discuss] [issue319] Add 'easy' query to default template In-Reply-To: <1266589746.58.0.685271617656.issue319@psf.upfronthosting.co.za> Message-ID: <1266710541.22.0.990411579662.issue319@psf.upfronthosting.co.za> A.M. Kuchling added the comment: Here's a further revision, to be applied atop the current code. Most seriously, the searches may have worked on my little 3-issue database, but turn out to be wrong on the live server; @filter needs to be the empty string, and @action needs to be supplied. There's also a sneaky trap; the keyword IDs in my test installation of Roundup are not the same as those in the live tracker. The new patch fixes both issues. Second, today someone made the obvious suggestion that I stupidly missed: also add the query for 'easy' items. The other keywords -- 64bit, 26backport, etc. -- don't seem useful. The links are now ordered as 'Create New', 'Show Open', 'Show Easy', 'Show Unassigned', 'Show Needing Review', 'Show Having Patch'. You may wish to rearrange. Third, it adds between the words so 'Needing Review' isn't broken across lines. (I kind of want to remove some of the standard site links -- ABOUT, NEWS, etc. -- since they're pushing the 'Issues' section far down the page. But maybe that requires more thought.) ---------- status: resolved -> chatting title: Add 'need review'/'has patch' queries to default template -> Add 'easy' query to default template _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- diff --git a/html/page.html b/html/page.html --- a/html/page.html +++ b/html/page.html @@ -104,6 +104,19 @@ tal:attributes="href python:request.indexargs_url('issue', { '@sort': '-activity', '@group': 'priority', + '@columns': columns, + '@action': 'search', + '@filter': '', + 'keywords': 6, + 'status': 1, + '@dispname': i18n.gettext('Show Easy'), + '@startwith': 0, + })" + i18n:translate="">Show Easy +

Show Unassigned

Show Needing Review

+ i18n:translate="">Show Needing Review