<html> <head> <style></style> </head> <body class='hmmessage'> Im certainly interested in this idea, its easy to do, helps ubuntu out, and helps the ubuntu-au members to get to know each other. Although iv never triaged a bug before, im willing to give it a shot and help others in the process.<div> </div><div>Ryan Macnish > Date: Mon, 17 May 2010 23:59:34 +1000 > From: mitch.towner.ubuntu@gmail.com > To: ubuntu-au@lists.ubuntu.com > Subject: Proposal - Ubuntu-AU BugJams > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In the IRC meeting it was agreed that we need to work together > collaboratively. One thing that we can do together is have an online > BugJam. This basically entails working together as a team on helping to > improve bug reports in Ubuntu's bug tracker - Launchpad [1]. If there is > enough interest/participation, Ubuntu-AU BugJams would initially be > every 2 months with the possibility or changing it to once a month in > the future. > > Many "not-so-technically-minded" people tend to shy away from this idea, > however it is actually easier to help out than it sounds! The whole idea > of "bug triage" is to improve bug reports. This can be performed in many > different ways. > > A *large* percentage of the bugs triagers have to deal with are not > assigned to the right package - a fair number do not have any package > assigned to them at all! One of the easiest ways to get involved in bug > triage is to simply look at [2] (a list of bugs that are not assigned to > a package) & assigning the bug report to the right package. Currently > there are 3165 bugs that need to be assigned to the right package. A > great resource that helps with this is [3]. There are also plenty of > helpful & friendly people in the #ubuntu-bugs IRC channel channel [4] > who are willing to offer assistance with trying to find the correct > package for a bug report. > > Another way that people who are new to bug triage can help out is by > confirming bugs are still valid by trying to reproduce them with the > latest version of the package that the bug is reported against. A good > way to get started with confirming bug reports is to focus on a package > that you are familiar with. Try to reproduce bug reports filed against > an older version of the package to see if the issue still exists in the > latest version of the package. Go to [5] to search for bugs in a > specific package. > > More detailed Bug Triage information can be found in the Bug Squad > Knowledge Base [6] & the "How to Triage" wiki page [7]. > > For those interested in participating in an Ubuntu-AU BugJam, please > reply to this list. Once we get an idea of the number of people > interested in participating, we can organise finer details such as a > date, if an online "how to triage" class would be beneficial, if people > who are local should meet face-to-face & have everyone collaborate > online, etc, etc. > > > > [1] https://launchpad.net/ > [2] http://is.gd/bWXr8 > [3] https://wiki.ubuntu.com/Bugs/FindRightPackage > [4] http://webchat.freenode.net/?channels=ubuntu-bugs > [5] https://bugs.launchpad.net/ > [6] https://wiki.ubuntu.com/BugSquad/KnowledgeBase > [7] https://wiki.ubuntu.com/Bugs/HowToTriage > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJL8Uu/AAoJENegJk0fbKNMnucIAILaw7ch4Se3602Eywc8xIf9 > cU8gMWx1WJ1xHiBs++2U/2NFjjCVPVD19IUQfwhd0Acm+obwVGqQvPIGK0IzQUtX > ALJdjHcWGhh/PbpWS/PaRj0nw5Iw0I/Qn9+rb1DZNqJTmEVIVxcv7COuEetL1C82 > 5/8kMYrGUIoQn3R7UVdoeNTbmmt4rs2kVEVDSCoibPEEmX3RNiMoGCEJr/BrzmwV > 5WUpAab/DPzWyGqzGRcpPa1JNhPdFaDhEBiEuo3/Fjt1XcX+CluRi+JQ06utqxiV > s1gQsj2zLer2hHa1A7d36fvc8LqvefNv2iqr0yxAO9tbRbsa7YNIQfteyJ0gwDA= > =GiDS > -----END PGP SIGNATURE----- > > -- > ubuntu-au mailing list > ubuntu-au@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-au </div> <hr />Find it at CarPoint.com.au <a href='http://clk.atdmt.com/NMN/go/206222968/direct/01/' target='_new'>New, Used, Demo, Dealer or Private?</a></body> </html>