FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 03-02-2010, 07:59 PM
Ioannis Aslanidis
 
Default Marking bugs for bugday?

When am I getting control over that? Can infra help me?

On Tue, Mar 2, 2010 at 8:36 PM, 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 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
>
>



--
Ioannis Aslanidis
http://www.deathwing00.org
<deathwing00[at]gentoo.org> 0x47F370A0
 
Old 03-02-2010, 08:05 PM
Sebastian Pipping
 
Default Marking bugs for bugday?

On 03/02/10 21:47, Alec Warner wrote:
> I would recommend not hardcoding 10 seconds; but otherwise caching is good

What do you propose?



Sebastian
 
Old 03-02-2010, 08:28 PM
Alec Warner
 
Default Marking bugs for bugday?

I propose a value that you can set at runtime. We do this at work
with the gflags package (already in the tree) or a config file.

-A

On Tue, Mar 2, 2010 at 1:05 PM, Sebastian Pipping <sping@gentoo.org> wrote:
> On 03/02/10 21:47, Alec Warner wrote:
>> I would recommend not hardcoding 10 seconds; but otherwise caching is good
>
> What do you propose?
>
>
>
> Sebastian
>
>
 
Old 03-04-2010, 06:13 PM
Roy Bamford
 
Default Marking bugs for bugday?

On 2010.03.01 21:17, Ioannis Aslanidis wrote:
> Hello,
>
[snip]

> Bug Day, followed by an announcement the week before and a reminder
> the day before. This needs to happen in publicly visible places (and
> has happened in some of them as far as I recall): forums, gentoo-
> user,
> gentoo-dev, gentoo-announce, gentoo-dev-announce, the newsletter
> (dead?) and the website. Having people related to the Bug Day project
> posting to their blogs can help a lot in this case as well.
[snip

> Regards.
>
>
[snip]
>
>
> --
> Ioannis Aslanidis
> http://www.deathwing00.org
> <deathwing00[at]gentoo.org> 0x47F370A0
>

I used to do the announces, sometimes under the psudonym of Welps PA.
I can chip in again and with some of the organisation and the
announces.

Its definately worth saving bugday - it brings devs and users closer
together.

sping was looking at "two days in plain Python" - do we need a
developer to do that or could that be one of the bugs for bugday ?
I realise that gentoo.org will host it, so we need to validate it but
that should be much less time than writing the code.

--
Regards,

Roy Bamford
(Neddyseagoon) an member of
gentoo-ops
forum-mods
trustees
 
Old 03-06-2010, 01:45 PM
Robert Buchholz
 
Default Marking bugs for bugday?

On Tuesday 02 March 2010, Sebastian Pipping wrote:
> On 03/02/10 20:28, Nathan Zachary wrote:
> >> This looks like overkill to me. One keyword should be enough, and
> >> for supplementary information "Status Whiteboard" could be used.
> >
> > I agree. Simply having the BUGDAY keyword should be sufficient,
> > and more information can be provided elsewhere in the report.
>
> If more than one keyword is commonly considered overkill I would at
> least request the whiteboard for it: "somewhere in the report"
> involves more than zero searching for it.

Some people use the whiteboard for their own marking of bugs (e.g.
security, and myself). If you add more information in there, you might
be breaking other people's marking / sorting algorithms.

I'd say one keyword BUGDAY is enough. Any bug editor can set and remove
it and the bug history will show who set and removed it when. Sorting
any syntax is taken care of by Bugzilla that way. It seems to me problem
you seem to try to solve (review of bugs) can also be tackled with tools
displaying new bugs that have the keyword set and just removing the
keyword. If bugs are repeatedly spammed with BUGDAY comments, talk to
the spammers or leave a comment.



Robert
 
Old 03-06-2010, 02:26 PM
Ioannis Aslanidis
 
Default Marking bugs for bugday?

Well, I personally would prefer to have two keywords at least, one for
candidates and another for confirmed bugs. Otherwise it will be a real
trouble for us to sort things out. If adding more than one keywords
breaks anything, then I can tell you now it is already broken.

The only thing that could make me thing that one keyword is enough, is
that an actual comment is added every time a keyword is being added or
removed off a bug, to be able to keep track of these changes.

On Sat, Mar 6, 2010 at 3:45 PM, Robert Buchholz <rbu@gentoo.org> wrote:
> On Tuesday 02 March 2010, Sebastian Pipping wrote:
>> On 03/02/10 20:28, Nathan Zachary wrote:
>> >> This looks like overkill to me. One keyword should be enough, and
>> >> for supplementary information "Status Whiteboard" could be used.
>> >
>> > I agree. *Simply having the BUGDAY keyword should be sufficient,
>> > and more information can be provided elsewhere in the report.
>>
>> If more than one keyword is commonly considered overkill I would at
>> least request the whiteboard for it: "somewhere in the report"
>> *involves more than zero searching for it.
>
> Some people use the whiteboard for their own marking of bugs (e.g.
> security, and myself). If you add more information in there, you might
> be breaking other people's marking / sorting algorithms.
>
> I'd say one keyword BUGDAY is enough. Any bug editor can set and remove
> it and the bug history will show who set and removed it when. Sorting
> any syntax is taken care of by Bugzilla that way. It seems to me problem
> you seem to try to solve (review of bugs) can also be tackled with tools
> displaying new bugs that have the keyword set and just removing the
> keyword. If bugs are repeatedly spammed with BUGDAY comments, talk to
> the spammers or leave a comment.
>
>
>
> Robert
>



--
Ioannis Aslanidis
http://www.deathwing00.org
<deathwing00[at]gentoo.org> 0x47F370A0
 
Old 03-06-2010, 06:09 PM
David Leverton
 
Default Marking bugs for bugday?

On Saturday 06 March 2010 15:26:10 Ioannis Aslanidis wrote:
> Well, I personally would prefer to have two keywords at least, one for
> candidates and another for confirmed bugs.

This sounds like the sort of thing Bugzilla's "flags" mechanism is for.

http://www.bugzilla.org/docs/2.22/html/flags-overview.html
 
Old 03-06-2010, 07:22 PM
Ioannis Aslanidis
 
Default Marking bugs for bugday?

Now that's what I wanted. Thanks!

On Sat, Mar 6, 2010 at 8:09 PM, David Leverton <levertond@googlemail.com> wrote:
> On Saturday 06 March 2010 15:26:10 Ioannis Aslanidis wrote:
>> Well, I personally would prefer to have two keywords at least, one for
>> candidates and another for confirmed bugs.
>
> This sounds like the sort of thing Bugzilla's "flags" mechanism is for.
>
> http://www.bugzilla.org/docs/2.22/html/flags-overview.html
>
>



--
Ioannis Aslanidis
http://www.deathwing00.org
<deathwing00[at]gentoo.org> 0x47F370A0
 
Old 03-07-2010, 03:30 AM
Sebastian Pipping
 
Default Marking bugs for bugday?

On 03/06/10 20:09, David Leverton wrote:
> This sounds like the sort of thing Bugzilla's "flags" mechanism is for.
>
> http://www.bugzilla.org/docs/2.22/html/flags-overview.html

Good idea!

What I wonder now is:
- Will it work with our very instance of Bugzilla?
- Can certain flag states be required when searching?
- Can we get their current value out using ctype=rdf output

All "yes" makes it work.



Sebastian
 
Old 03-07-2010, 11:23 AM
David Leverton
 
Default Marking bugs for bugday?

On Sunday 07 March 2010 04:30:55 Sebastian Pipping wrote:
> What I wonder now is:
> - Will it work with our very instance of Bugzilla?

The security team uses (or at least has used in the past) flags on Gentoo
Bugzilla.

> - Can certain flag states be required when searching?

It looks like you need to use the "Advanced Searching Using Boolean Charts"
section on the search page - you can select "Flag", "is equal to", and type
the flag name/state, for example "Assigned_To?" for one of the
above-mentioned security flags. Note that the "normal" search fields still
apply, so you need to deselect all the options in the "Status" list before
that particular example will produce any results.

> - Can we get their current value out using ctype=rdf output

I don't think you can with the RDF, but the "XML" button on the search results
page includes the flags (and a whole lot of other information), so if you're
going to rewrite the bugday software anyway you could consider using that
instead, if it would give sufficient benefit. It seems that if you're
requesting it programmatically you'd have to do the search, get the bug IDs
and explicitly pass them to the XML generator, though, which makes things a
little more awkward.
 

Thread Tools




All times are GMT. The time now is 04:24 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org