Re: [gentoo-dev] Marking bugs for bugday?

[Alec Warner <antarus@gentoo.org>]

On Tue, Mar 2, 2010 at 11:36 AM, Sebastian Pipping <sping@gentoo.org> 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.  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 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.  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
>
>