Differences

This shows you the differences between two versions of the page.

--- bugbusting [2008/01/24 09:17] – add link to Debugging page MarkLinimon
+++ bugbusting [2020/04/18 08:26] (current) – Add child page macro to page bottom KubilayKocak
@@ Line 1: / Line 1: @@
-==== The Problem ====
+%%FreeBSD%% has a way for users to submit [[https://bugs.freebsd.org/bugzilla/query.cgi|Problem Reports]].  This page gives an introduction to what happens next.  (If you're not familiar with how to write a good Problem Report, please [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/|start here]].)
-Currently we are not doing as well at handling Problem Reports as we could.  So, how can we fix this?
-The main problem is that we have more PRs coming in than we have volunteers working on fixing them.  This is due to several reasons:
+There is also a good, although slightly out-of-date, reference on how we expect %%FreeBSD%% committers to
+[[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/|handle PRs]].
-  * We have no "culture" of bugbusting.
+Note: we are still learning as we are going!
-  * Bugbusting is not as much fun as adding new features.
-  * We have never figured out a way to let our non-committers help us.
-  * We have not done a good job of managing our users' expectations of what the developers can reasonably accomplish.
-==== Our current status ====
-  * The ports PRs have automated systems written to both assign them to committers (when possible), to notify maintainers, and to remind maintainers if they have not responded.  In addition, a 2-week timeout period has been adopted.  Thus, the ports PRs tend to have fairly good clearance rate, and are in relatively reasonable shape.
-  * The other PRs (in particular bin/ and i386/) tend to have a much lower clearance rate, and are not in good shape.
-==== What has been done recently ====
-  * We have created a way for non-committers to get access to GNATS.  While this is reserved for the most persistent volunteers, it has produced good results.
-  * We have done some ["Bugathons"] to try to get more people involved.
-  * We have advocated more active use of the #freebsd-bugbusters IRC channel.
-  * We have started closing some of the PRs that have little hope of being addressed (in particular, the "how do I make XYZ work" type), and recommending that they instead ask questions on the mailing lists.  This will help us focus more on actual bugs.
-  * Several people have been contacting PR submitters and asking whether the problems still exist.  (For problems in bin/, this is more often true than you might expect).  A large number of obsolete PRs have been closed.
-  * We have been eliminating duplicate PRs.
-None of these has been a complete success yet.
-==== What we still need to do ====
+==== Places To Start ====
-  * Get more committers looking at the recommended PRs, and getting them committed.
-  * Figuring out more ways for non-committers to help us.
+  * [[BugBusting/Resources]]
-  * Attract more attention to the mailing list and IRC channel, to try to create more of a "culture".
-==== Resources ====
+If you are unfamiliar with bugbusting on %%FreeBSD%%, this is where you should start; in particular, the Web Resources section.  (Yes, there is a lot of detail on that page; you may wish to simply browse it.)
-  * The bugmeister team, bugmeister@%%FreeBSD%%.org (responsible for the maintenance of the database and associated code)
-  * Weekly postings of bug summaries to freebsd-bugs@%%FreeBSD%%.org (including overall, PRs by tag, PRs with patches)
+  * [[Bugathons]]
-  * Weekly posting of "PRs recommended for committer evaluation" to freebsd-bugs@%%FreeBSD%%.org
-  * Weekly reminders of assigned PRs, to each assignee
+Bugathons are events where we get people to join us on IRC on #freebsd-bugbusters on EFNet at a specific time.  We try to go through the current PRs and close as many of them as we can.  Watching one of these in progress is a good way to learn how we approach things.
-  * Auto-assignment of ports PRs (run by EdwinGroothuis)
-  * freebsd-bugbusters# IRC channel on EFNet
+  * [[BugBusting/HowToHelp]]
-  * Information about ["Debugging"] with %%FreeBSD%%
+This suggests some ideas on how you can help.  It includes information for both committers and non-committers.
+  * [[BugBusting/Volunteers]]
+This is our sign-up list for the Bugathons (and bugbusting in general).  It tries to be a central place to find out who is active and what their interests and expertise are.  Feel free to send information to linimon@%%FreeBSD%%.org if you would like to join us.
+==== Further Information ====
+  * [[BugBusting/StateOfBugbusting]]
+This page talks about the state of bugbusting on %%FreeBSD%%, and discusses ideas for how we can improve.
+  * [[BugBusting/TipsAndTricks]]
+This page includes some details about what we have added on to GNATS recently.  (This documentation should move to the [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/|Handling PRs]] article).
+  * [[Bugathons/PRsWithPatches]]
+Some commentary on dealing with PRs that have been flagged as having patches in them.
+  * [[BugBusting/Brainstorming]]
+A to-do list, based on suggestions made in the last few Bugathons.
+==== Pages On The Web ====
+  * [[http://www.freebsd.org/support/bugreports.html|Problem Report Submission]] form
+  * [[http://www.freebsd.org/cgi/query-pr.cgi|Problem Report query]] form
+==== Notes ====
+The original text in this page has moved to [[BugBusting/StateOfBugbusting|BugBusting/StateOfBugbusting]].
+  * [[BugBusting/Brainstorming|Brainstorming]]
+  * [[BugBusting/Commonly_reported_issues|Commonly_reported_issues]]
+  * [[BugBusting/HowToHelp|HowToHelp]]
+  * [[BugBusting/Resources|Resources]]
+  * [[BugBusting/StateOfBugbusting|StateOfBugbusting]]
+  * [[BugBusting/TipsAndTricks|TipsAndTricks]]
+  * [[BugBusting/Volunteers|Volunteers]]