On Tue, Nov 17, 2009 at 7:02 AM, Atwin Calchand <[email protected]> wrote: > > Is there anything official that should be done to become part of qa? > How does it normally work? >
There is a number of ways in which you can help: testing daily ISOs, helping out in triaging bugs, testing proposed fixes... There's also a couple of places you can look for more information, on the Ubuntu Wiki: https://wiki.ubuntu.com/BugSquad -- BugSquad team, to help out with bug triage. https://wiki.ubuntu.com/Testing -- Testing Team, where you can help verifying that everything is in order in ISOs, in new applications, etc. Realistically, what you need to do is pretty much make a Launchpad profile if you don't already have one, including digitally signing the Code of Conduct (steps which apply to just about any team), and jumping in. Both the pages above list a couple of places where you can start to look. Among others, the https://wiki.ubuntu.com/BugSquad/GettingInvolved page has a link [1] to the LP search for bugs that don't have a package assigned to them yet. This can be a good place to start if you know your way around apt, and the general layout of packages and which one hold a specific tool. You should definitely also hang out in #ubuntu-bugs and/or #ubuntu-testing. [1] https://bugs.launchpad.net/ubuntu/+bugs?field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=none&field.has_no_package=on / Matt -- Ubuntu-qa mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
