Gentoo Archives: gentoo-dev

From: Alec Warner <antarus@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Marking bugs for bugday?
Date: Tue, 02 Mar 2010 20:48:06
Message-Id: b41005391003021247n7e174f9bnc53eb67b3c4306db@mail.gmail.com
In Reply to: Re: [gentoo-dev] Marking bugs for bugday? by Sebastian Pipping
1 On Tue, Mar 2, 2010 at 11:36 AM, Sebastian Pipping <sping@g.o> wrote:
2 > On 03/01/10 22:17, Ioannis Aslanidis wrote:
3 >> getting control of bugday.gentoo.org and be able to upload our own
4 >> content would be great.
5 >
6 > The current page is said to generate one XML request per bug listed on
7 > the page for each request.  From my experience trying to remove bugs
8 > from that page yesterday(?) (through clicking on "remove" buttons) I
9 > have the impression that it's true: Du to page reload times the site in
10 > it's current form is unusable in the very sense of the word.
11 >
12 > Ideas I have on a rather simple rewrite:
13 >
14 >  - Split the bugday website into two pages:
15 >   - Page "Open bugs" showing
16 >     - open bugday-keyworded bugs (with date of the latest bugday)
17 >       in randomized order
18 >   - Page "Closed bugs" showing
19 >     - closed bugday-keyworded bugs (with date of the latest bugday)
20 >       in some sorted order
21 >     - a ranking with closed bugs per participant
22 >       (as that may not be the assignee such information could
23 >       maybe be encoding into the status whiteboard, somewhere
24 >       we can query it from easily if whiteboard fits for that)
25 >
26 >  - Do one search request to bugzilla internally, only.
27 >   Should be possible as we're now asking bugzilla for the list
28 >   of bugs instead of asking for details on a list we pass in.
29 >
30 >  - Simple caching of bugzilla requests for 10 seconds or so.
31 >   Should not hurt the bugday experience much and reduce load
32 >   further.
33
34 I would recommend not hardcoding 10 seconds; but otherwise caching is good ;)
35
36 >
37 > I could imagine that an ugly prototype with rough-edges of that could
38 > take two days in plain Python.  At the moment I cannot say when and if I
39 > have these two days, but maybe someone else with time is fire and flame
40 > for it by now?
41 >
42 >
43 >
44 > Sebastian
45 >
46 >

Replies

Subject Author
Re: [gentoo-dev] Marking bugs for bugday? Sebastian Pipping <sping@g.o>