Bugsquad Meeting Minutes 2009-09-05

View: New views
2 Messages — Rating Filter:   Alert me  

Bugsquad Meeting Minutes 2009-09-05

by Tobias Mueller-6 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

signature.asc (267 bytes) Download Attachment

Re: Bugsquad Meeting Minutes 2009-09-05

by Tobias Mueller-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

-----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-----
_______________________________________________
gnome-bugsquad mailing list
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad