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 1NmZ0f-0008Ri-Tc for garchives@archives.gentoo.org; Tue, 02 Mar 2010 20:48:06 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 94576E1038; Tue, 2 Mar 2010 20:48:03 +0000 (UTC) Received: from mail-px0-f202.google.com (mail-px0-f202.google.com [209.85.216.202]) by pigeon.gentoo.org (Postfix) with ESMTP id 9568FE1030 for ; Tue, 2 Mar 2010 20:47:48 +0000 (UTC) Received: by pxi40 with SMTP id 40so234733pxi.9 for ; Tue, 02 Mar 2010 12:47:47 -0800 (PST) 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 Sender: antarus@scriptkitty.com Received: by 10.141.108.12 with SMTP id k12mr3575853rvm.214.1267562867760; Tue, 02 Mar 2010 12:47:47 -0800 (PST) In-Reply-To: <4B8D68CE.1050102@gentoo.org> References: <4B889D1F.3040304@gentoo.org> <201002282154.35130.hwoarang@gentoo.org> <4B8ACC34.7000600@gentoo.org> <20100228173504.78eea0b1@angelstorm> <4B8D68CE.1050102@gentoo.org> Date: Tue, 2 Mar 2010 12:47:47 -0800 X-Google-Sender-Auth: a396fc9b8b6bc236 Message-ID: Subject: Re: [gentoo-dev] Marking bugs for bugday? From: Alec Warner To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 2b79e06e-54fe-431a-b5d1-03cbc76fa922 X-Archives-Hash: ff7f89f32ae57cc17639e61ce67f070b On Tue, Mar 2, 2010 at 11:36 AM, Sebastian Pipping wrote= : > 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. =C2=A0From 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: > > =C2=A0- Split the bugday website into two pages: > =C2=A0 - Page "Open bugs" showing > =C2=A0 =C2=A0 - open bugday-keyworded bugs (with date of the latest bugda= y) > =C2=A0 =C2=A0 =C2=A0 in randomized order > =C2=A0 - Page "Closed bugs" showing > =C2=A0 =C2=A0 - closed bugday-keyworded bugs (with date of the latest bug= day) > =C2=A0 =C2=A0 =C2=A0 in some sorted order > =C2=A0 =C2=A0 - a ranking with closed bugs per participant > =C2=A0 =C2=A0 =C2=A0 (as that may not be the assignee such information co= uld > =C2=A0 =C2=A0 =C2=A0 maybe be encoding into the status whiteboard, somewh= ere > =C2=A0 =C2=A0 =C2=A0 we can query it from easily if whiteboard fits for t= hat) > > =C2=A0- Do one search request to bugzilla internally, only. > =C2=A0 Should be possible as we're now asking bugzilla for the list > =C2=A0 of bugs instead of asking for details on a list we pass in. > > =C2=A0- Simple caching of bugzilla requests for 10 seconds or so. > =C2=A0 Should not hurt the bugday experience much and reduce load > =C2=A0 further. I would recommend not hardcoding 10 seconds; but otherwise caching is good = ;) > > I could imagine that an ugly prototype with rough-edges of that could > take two days in plain Python. =C2=A0At 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 > >