Bug Triage Meeting
irc.freenode.net #fedora-meeting
Tuesday @ 14:00 UTC/10 AM EDT
See you there!
Below is a new attempt on my part to better report the events our
meetings. I'll be able to carry this for a bit, but then would like
some help doing the weekly summaries and posting to the list.
John
---------------------------------------
Recap and full IRC transcript found here:
https://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2008-Sep-30
Please make corrections and clarifications to the wiki page.
= Bug Triage Meeting :: 2008-09-30 =
== Attendees ==
* poelcat
* John5342
* ke4qqq
* jlaska
* jds2001
* mcepl
== NEW->ASSIGNED ==
* Some people believe a different way should be implemented to indicate
that a bug is ''triaged''
** How many people is unclear
** Issue a survey?
*
https://www.redhat.com/archives/fedora-test-list/2008-September/msg00493.html
* Alternatives:
*# new bugzilla state
*# new flag
*# use existing ''Triaged'' keyword
* poelcat to talk to Red Hat bugzilla people to find out what feasible
options are
== Status of Greasemonkey Scripts ==
* Comphappy was making updates a few weeks ago
* No one knows the status
== Generating New Involvement ==
* Do we state the benefits of bug triage anywhere?
* Creating consistent meeting summaries and sending back to the list
* Publish "success stories"
* Need to resolve controvery about NEW->ASSIGNED as that may discourage
people from helping out
* Unclear if weekly meeting reminders help
== FEver Bugs ==
* quite a few being auto-filed
* http://fedoraproject.org/wiki/PackageMaintainers/FEver
* What about having following attributes on these bugs auto-set?
** ''FutureFeature'' keyword
** ASSIGNED (triaged)
== IRC Transcript ==
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
