Re: Bugsquad Meeting Minutes 2009-09-05

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aloha! :-)

I just wanted to keep you updated on the open issues from the last meeting:

On 06.09.2009 00:16, Tobias Mueller wrote:
> == "Old untouched bugs" ==
> [..,]
> 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)
> 
DONE! :-)

> == Make more clear the triager workflow ==
> [...]
> 
> 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
> 
Not yet

> == Set up a bot to notify us about new bugs in #bugs ==
> [,,,[
> 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)
> 
DONE



> == 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
> 
Mail proposal follows

Dear Maintainers :)

We, the Bugsquad, wonder, how accurate the Product Specific Instructions
on live.gnome.org currently are. You can find the at
http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines and
we kindly ask you to revisit the rules for your module.

For example it's not needed to ask for a stacktrace (of all threads)
because we ask the user to do that anyway
(http://live.gnome.org/GettingTraces/Details).

Requesting output from a special program (xrandr, gconf, ...) or a log
is a good idea though.

So please visit
http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines and
help us getting the most out of our bugreports :)

Thanks,
  Tobi
  for the GNOME Bugsquad


> == 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)
> 
And we finally have our product :)
https://bugzilla.gnome.org/browse.cgi?product=bugsquad
We actually try to use it as a ToDo tracker. It'll hopefully work out.
At least it's harder to forget things. Tracking todos via email is not
that easy (for me).

> 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"
> 
We'll see how much we'll get done on our next meeting ;-)

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

iEYEARECAAYFAkrP7xIACgkQPuBX/6ogjZ71eACfXUs/G81L1VLzmXvooX/rvTl3
GHoAnjLUwqC5XW+gb6L7OG/7z0W8F9hN
=VUbR
-----END PGP SIGNATURE-----