Bugsquad Meeting Minutes 2009-09-05

Dear follow Bugsquadders,

we had a meeting today and we are glad to present you our results. You 
can also see them at 
http://live.gnome.org/action/info/Bugsquad/Meetings/20090905.

I'd like to mention that we probably want to have a next meeting in 
around four to five weeks and that we need someone to find a date, 
announce it, prepare an agenda, etc. As I expect to be pretty busy the 
next couple of weeks, I'd happily delegate that :)

Please shout if I have forgotten anything or if you have any questions.



== "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 
https://code.launchpad.net/bugzilla.gnome.org. 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:
  - JavierJardon to open a bug (Done:
                        http://bugzilla.gnome.org/show_bug.cgi?id=594259)
  - TobiasMueller to sync stock response to TriageGuide and
    StockResponses (don't forget to mention "needinfo-trynewversion"
    Keyword)





== Make more clear the triager workflow ==
The sources of the TriagersDiagram have been uploaded and a typo has 
been fixed.
We also want more information on that diagram, like when to set to NEW.

ACTIONS:
  - JavierJardon to add diagram to TriageGuide (DONE)
  - AkhilLadda to enhance the diagram by some rough guidelines on, e.g.,
    when to set to NEW



== Set up a bot to notify us about new bugs in #bugs ==
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 
http://live.gnome.org/Bugsquad/TriageGuide/FindingDuplicates needs an 
update. We do not want any links to 
http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi anymore.

ACTIONS:
  - TobiasMueller to mention #bzbot and #bugs in the BugSquad page.
    (DONE)
  - JavierJardon to fix pages shown up in [1] and [2] (DONE)
  - TobiasMueller to update FindingDuplicates to mention the new s-d-f
    replacement (TODO: http://bugzilla.gnome.org/show_bug.cgi?id=594272)

[1] 
http://live.gnome.org/Bugsquad/TriageGuide?action=fullsearch&context=180&value=dup-finder&fullsearch=Text
[2] 
http://live.gnome.org/Bugsquad/TriageGuide?action=fullsearch&context=180&value=s-d-f&fullsearch=Text


== Cleaning BugStatus ==
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.
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 
http://live.gnome.org/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)".

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

ACTIONS:
  - TobiasMueller to write a mail to be send to maintainers or d-d-l to
    ask for reviewing their rules. (GnomeBug:594243)
  - Someone to send that mail



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

ACTIONS:
  - TobiasMueller to file a bug against bugzilla.gnome.org/products
    (DONE: http://bugzilla.gnome.org/show_bug.cgi?id=594245)


The meeting ended after three hours, the rest of the agenda is deferred:
    7. New project: BugsquadGoals
    8. Report conclusions here: [[Bugsquad/DirectiveDiscussion]]
    9. Future of Bugsquad/BugDays
   10. Mail Notifications
   11. Automatic CANEDIT permissions
   12. Enable votes in Bugzilla or a method to say "this bugs affects me"


Cheers,
   Tobi

_______________________________________________
gnome-bugsquad mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkqi8UgACgkQPuBX/6ogjZ6QUACfdzYLdr8WEMjUYN9sxWM3vX0/
E+IAnRmjosb093V10udegoJN50pVfhj+
=d/tc
-----END PGP SIGNATURE-----