From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NmXtm-0005Fj-UR for garchives@archives.gentoo.org; Tue, 02 Mar 2010 19:36:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 06A4FE0F0B; Tue, 2 Mar 2010 19:36:52 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 2347EE0F04 for ; Tue, 2 Mar 2010 19:36:49 +0000 (UTC) Received: from [192.168.0.3] (g225028149.adsl.alicedsl.de [92.225.28.149]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 63D9E1B4014 for ; Tue, 2 Mar 2010 19:36:48 +0000 (UTC) Message-ID: <4B8D68CE.1050102@gentoo.org> Date: Tue, 02 Mar 2010 20:36:46 +0100 From: Sebastian Pipping User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100228 Thunderbird/3.0.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Marking bugs for bugday? References: <4B889D1F.3040304@gentoo.org> <201002282154.35130.hwoarang@gentoo.org> <4B8ACC34.7000600@gentoo.org> <20100228173504.78eea0b1@angelstorm> In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 0093fdec-d20a-400f-9c56-e550620dd9ba X-Archives-Hash: 5395f857d0f36f5cb451a5da1ee002ba On 03/01/10 22:17, Ioannis Aslanidis wrote: > getting control of bugday.gentoo.org and be able to upload our own > content would be great. The current page is said to generate one XML request per bug listed on the page for each request. From my experience trying to remove bugs from that page yesterday(?) (through clicking on "remove" buttons) I have the impression that it's true: Du to page reload times the site in it's current form is unusable in the very sense of the word. Ideas I have on a rather simple rewrite: - Split the bugday website into two pages: - Page "Open bugs" showing - open bugday-keyworded bugs (with date of the latest bugday) in randomized order - Page "Closed bugs" showing - closed bugday-keyworded bugs (with date of the latest bugday) in some sorted order - a ranking with closed bugs per participant (as that may not be the assignee such information could maybe be encoding into the status whiteboard, somewhere we can query it from easily if whiteboard fits for that) - Do one search request to bugzilla internally, only. Should be possible as we're now asking bugzilla for the list of bugs instead of asking for details on a list we pass in. - Simple caching of bugzilla requests for 10 seconds or so. Should not hurt the bugday experience much and reduce load further. I could imagine that an ugly prototype with rough-edges of that could take two days in plain Python. At the moment I cannot say when and if I have these two days, but maybe someone else with time is fire and flame for it by now? Sebastian