I'm interested ---------------------------------------------------------- Chris Martin m: 0419812371 ----------------------------------------------------------
On Wed, May 19, 2010 at 12:58 PM, MoLE <[email protected]> wrote: > Count me in for the bug jam > > On 5/19/10, brett <[email protected]> wrote: > > On Mon, 17 May 2010 23:59:34 +1000 > > Mitch Towner <[email protected]> wrote: > > > >> -----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. > > > > > > I understand how this supports Ubuntu, I don't understand how this > promotes > > Ubuntu to the wider, non-Ubuntu community. I think it is a great idea and > > everyone, regardless of tech-spec, should get involved/be welcomed into > the > > fold, but I don't think it is a prime objective of a LoCo. > > > > jmo > > > > -- > > ubuntu-au mailing list > > [email protected] > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-au > > > > -- > Sent from my mobile device > > -- > ubuntu-au mailing list > [email protected] > https://lists.ubuntu.com/mailman/listinfo/ubuntu-au >
-- ubuntu-au mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
