Things discussed on 2009-09-05

Date	2009-09-05 14:00 UTC
Participants	andre, chromy, cosimoc, fabio, lakhil, jjardon, Muelli

"Old untouched bugs"

We don't have a stockanswer lying in bugzilla-newer by now because we have upgraded the bugzilla. Also the new bugzilla lies at Launchpad. But we still need to sync the StockResponse to the TriageGuide. We could agree on a special keyword when setting to NEEDINFO, because you can search these NEEDINFOs more easily, and thus close them more easily after the six weeks.

ACTIONS	Status
TobiasMueller to sync new StockResponse to Bugsquad/TriageGuide/StockResponses	DONE
TobiasMueller to mention to set untouched bugs to NEEDINFO and to close after six weeks in Bugsquad/TriageGuide (Mention to set keyword "needinfo-trynewversion")	DONE
JavierJardon to open a bug to have stock responses again	DONE

Make more clear the triager workflow

../../TriageGuide/Diagram_triagers.png may help We also want more information on that diagram, like when to set to NEW.

ACTIONS	Status
JavierJardon to add diagram to Bugsquad/TriageGuide	DONE
AkhilLaddha to enhance the diagram by some rough guidelines on, e.g., when to set to NEW	TODO

Set up a bot to notify us about new bugs in #bugs

DISCUSSED

As we have much traffic on bugzilla, we don't want #bugs to be spammed. Also, we have #bzbot. We need to document that though. Other documentation is broken as well: simple-dup-finder doesn't exist anymore and thus /Bugsquad/TriageGuide/FindingDuplicates needs an update. We do not want any links to http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi anymore.

ACTIONS	Status
TobiasMueller to mention #bzbot and #bugs in the BugSquad page.	DONE
JavierJardon to fix pages shown up http://live.gnome.org/Bugsquad/TriageGuide?action=fullsearch&context=180&value=dup-finder&fullsearch=Text and http://live.gnome.org/Bugsquad/TriageGuide?action=fullsearch&context=180&value=s-d-f&fullsearch=Text	DONE
TobiasMueller to update FindingDuplicates to mention the new s-d-f replacement	DONE

Cleaning BugStatus

Bugsquad/BugStatus and merging with Bugsquad/TriageGuide

DISCUSSED

it's not a good idea anymore

Add ApplicationSpecificInstructions to the TriageGuide

The proposal is to move GettingTraces/ApplicationSpecificInstructions to the Bugsqad namespace under TriageGuide.

DISCUSSED

No changes: As we are in charge of maintaining those pages, it might be a good idea to have them in the Bugsquad namespace. But one has to move each and every page manually and there's little benefit in actually moving the pages. Actually one would have to update the backreferences like stock responses to link to the new page. So we're not going to do anything unless anybody brings this up again

Refactor ProductSpecificGuidelines

We have a bloated page at Bugsquad/TriageGuide/ProductSpecificGuidelines with many rules to obey. But simply deleting isn't an option because the information is actually necessary. So try to get rid of unneccessary rules such as "If possible get a backtrace from the user with all thread backtraces (i.e. using 'bt thread apply all' instead of 'bt' in GDB)".

DISCUSSED

We thus ask the maintainers to have a look at http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines and clean their stuff up

ACTIONS	Status
TobiasMueller to write a mail to be send to maintainers or d-d-l to ask for reviewing their rules	TODO

Bugsquad module in bugzilla

DISCUSSED

It might be a good thing to have an own module to keep track of assigned tasks.

ACTIONS	Status
TobiasMueller to file a bug against bugzilla.gnome.org/products	DONE

The rest has been deferred to the next meeting.

Logs

../bugsquad-meeting-log-2009-09-05.txt