added header & rearranged page
in/on - there!
|Deletions are marked like this.||Additions are marked like this.|
|Line 11:||Line 11:|
|* [[QATeam/Meetings|Weekly IRC meetings]] Wednesdays at 17.00 UTC on #ubuntu-meeting|| * join [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|ubuntu-qa]] for discussion
* [[QATeam/Meetings|Weekly IRC meetings]] Wednesdays at 17.00 UTC in #ubuntu-meeting
How can I help?
Lucid Lynx Alpha One is coming Thursday, Dec 10th.
zsync will greatly speed up downloads of iso images
join #ubuntu-testing on freenode.net
join ubuntu-qa for discussion
Weekly IRC meetings Wednesdays at 17.00 UTC in #ubuntu-meeting
Thursdays UbuntuBugDay in IRC #ubuntu-bugs
LaptopTestingTeam helping users share their experiences with hardware like theirs.
Who is involved?
Working with the Ubuntu Community
Approved and "new" Local Community teams are natural partners in the testing process. As advocates and active users we know about the software and the perception of Ubuntu by people who are not computer experts. This perspective is extremely valuable. We hope this page provides a clear and concise jumping off point for active teams and users to help begin test Ubuntu.
A benefit of using open source software is the ability to participate in it's development. Contributions to the projects that Ubuntu distributes is encouraged, however most people are first introduced to a software package by using it. Every user can be seen as a software tester. Sometimes problems are noticed that can be reported. Open source software fundamentally depends upon people participating. You are in good company because an incredibly large and growing number of people do participate every day from all parts of the world. If nobody steps forward to report issues then busy, well intentioned developers may inadvertently overlook these unintended features in the software they provide.
There is an art/science to knowing how and where to report these problems. It takes effort to isolate an issue so that one of the various parties involved can fix it, though this gets easier with practice. A great feeling of satisfaction can be found when reporting problems and seeing them fixed. While the daily work of quality assurance can be under appreciated, experienced developers recognize the value of good bug reports and are very grateful.