BugZappers:meeting-agenda-list: Difference between revisions

Revision as of 16:04, 7 April 2009

Fix Me
The layout and information on this page could be improved and better presented.

Please add items you want to see on the meeting agenda to this list.

If you have an item on the agenda but can not attend the meeting, please coordinate with someone that will be attending.

Meeting reminders are sent out on Monday mornings, so please add items to this list before then if you would like them to be included in that email.

IRC Nick	Agenda Item and Description
John5342	triage trac instance on fedorahosted might be a better place for this list? should be more scalable and also allow for easier tracking of follow-ups, easier to just leave tickets open for things that aren't completed (roll over to following week). would fit nicely into a "Meeting agenda" milestone.
tk009	Introduction Email SOP - Confirm SOP format, wording and wiki implementation.
?	000-Not-Sure-What-Component-To-File-Against idea (avoid bugs getting filed against 0xFFFF inappropriately)
?	Possible BugZappers/How_to_Triage improvements: Add references to GreaseMonkey buttons in checklist instructions (adamw said he would do so) Reorganize (poelcat proposes http://fpaste.org/paste/7456 )
beland	User:Beland/Bugzilla_Legend Consensus seems to be to try come up with unified definitions across both RHEL and Fedora. adamw is sending email to fedora-devel-list (with draft to fedora-test-list) regarding this issue

@@ Line 20: / Line 20: @@
 |? || 000-Not-Sure-What-Component-To-File-Against idea (avoid bugs getting filed against 0xFFFF inappropriately)
 |-
-|beland
+|?
-|[[User:Beland/How_to_Triage]] to replace [[BugZappers/How_to_Triage]] ?
+|Possible [[BugZappers/How_to_Triage]] improvements:
-* If you have detailed comments, pl
+* Add references to GreaseMonkey buttons in checklist instructions (adamw said he would do so)
-* adamw emailing fedora-test-list with draft email to fedora-devel-list with outstanding questions, including process for deciding which bugs to upstream
+* Reorganize (poelcat proposes http://fpaste.org/paste/7456 )
-* Should a check for bugs filed in upstream Bugzillas be mandatory? (conflicting opinions so far)
-* Should NEW triagers be asked to do NEEDINFO updates in 30 and 60 days if needed, or should this be left to triagers following the NEEDINFO checklist?  (Beland doesn't, other people do)
-* We went over all sections up to 2.0.7 in the last meeting.  Please review the remainder of the document before the meeting if you haven't already, and have comments ready. You can also e-mail comments now, and non-controversial improvements will get implemented sooner.
-* After these issues are decided, is this draft ready to go live?
-* Later improvements:
-** Add references to GreaseMonkey buttons in checklist instructions (adamw said he would do so)
-** Reorganize (poelcat proposes http://fpaste.org/paste/7456 )
 |-
 |beland