Difference between revisions of "Tester program"
| Line 1: | Line 1: | ||
= Call for Action: Improvements Needed! = | = Call for Action: Improvements Needed! = | ||
| − | <div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: # | + | <div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FDD; margin: 3px 3px 1em 3px;"> |
The tester program is in trouble and needs your help. At the moment people want to join it to test one app they like. Mostly. Then the app does not quite work (it's under testing!), and this puts more support load on the team. This means this program is really not contributing as much we'd like and does not pull it's own weight. | The tester program is in trouble and needs your help. At the moment people want to join it to test one app they like. Mostly. Then the app does not quite work (it's under testing!), and this puts more support load on the team. This means this program is really not contributing as much we'd like and does not pull it's own weight. | ||
Revision as of 09:42, 22 August 2010
Call for Action: Improvements Needed!
The tester program is in trouble and needs your help. At the moment people want to join it to test one app they like. Mostly. Then the app does not quite work (it's under testing!), and this puts more support load on the team. This means this program is really not contributing as much we'd like and does not pull it's own weight.
We're looking for ideas to re-invigorate it and re-energize this program. How can we make this more exciting and contribute to have people in the program help more across apps, across bugs, etc.
Ideas:
- Running "app of the week" sprints for apps and all the testers testing it until it works, then we move on to the next app (maybe we vote on apps that go next)
- Providing some sort of incentive, like credits for testing (exchangeable for something TBD), or credits for bugs ...
- or ... what can we do that is creative, fun for everyone and productive?
Contents
Becoming Tester
To become a tester, email team@... asking to become a tester, explaining your interest in the program, especially 'if you are wiling to take a lead position to invigorate this program.
Tester Program
By popular demand, we have started a tester program!
What does that mean?
It means that you get to play with new apps as soon as they become beta, before they are released to the entire Amahi community at large.
Testing apps is a valuable form of contribution to the Amahi community, as apps may have small issues here and there as they become ready for release.
Testing helps the application packagers improve the applications that get released. This is very important as the applications grow. Check out the latest apps at:
http://www.amahi.org/apps
We will make announcements about the latest apps added to the app gallery soon.
How to Become an Application Tester
If you are a contributor already (i.e. have packaged an app), you know what it takes, so you send us an email and we'll sign you right up.
Otherwise, we like to know you a bit and would like to interact via IRC, since that is the main avenue for feedback, so just let us know via IRC!
The only requirement is that you actively participate in the testing, you rate the apps (very important) and send feedback and report bugs at:
http://bugs.amahi.org/
Thanks go to rampage and the community in the IRC channel for helping organize the apps and contributing to their testing so far, encouraging the implementation of this program! Please review the Testing page on what to test for with beta releases.
