The current testing program does not workwell. People do not participate in How can we improve it. That could be due people just are impatient and do not want to try the app or make it is difficult to contribute back. We can not fix the people who just want to test a app and are not willing to provide feedback or testing. This can cause a issue of a application being released to early with bugs. run smoothly?

= Known Issues =* SSO between wiki,fourms,New people usually crave one app. Some people work towards fixing things and bug tracker others simply do not work well.* Bug Tracker is try too hard to find. (Yes I know it is filing bugsor researching).amahi.org Some may be too busy, but for someone who does not guess that I there is not a static linkthey still want to help.)

== Policy/ Procedure needed for That could be due people just are impatient and do not want to try the app or it is difficult to work === If you develop contribute back. This can cause a wiki page for issue of a policy please update this wiki application being released to early with the link=bugs.

= Known Issues =* There needs to be known stages Not easy for that the application needs users to go though and what states the application is in should also be noted. * Policy on see what the application information page on the mainpage should contain. * Policy on what tests a application must past to get included. * Policy of of general testing procedures for most application.  * I know A lot of people hate policy. However bugs there MUST to be policy for testing. There is a reason are for ISO Certification. People like checklists if they don't have a checklist they do not know what to do. Each application should have a checklist of things actions someone needs to preform to make sure the application works. given app* Furthermore said checklist MUST Bugs have a template for all apps on recommended things to include. * Better use of be manually linked by the bug system. The bug system is great however we need to use it better. Each application should have at least its own category if not it's own subproject depending on testmasters, in order for the size app packager and complexity of the application. This is so reports can other interested people to be run on a specific application.  * Every application must have a place to discuss the application.notified

=Ideas = There needs to be a good template for applications on the wiki. ==The template MUST including the following information.* The name of the application* The Description of the application* The Features of the application.* The Status of the application. (Current Version and State ( Eg. HDA-ized app)* Information on how to install the application.* Information on how to uninstall the application. * Information on how to configure the application.* A link to the checklist for testing the application. This should be simple and easy to follow.* A link to known bugs. (If every bug has it's own category if we can run a report on that category a link to that would be the best).* Link to Upstream bug reporting system or support. Also we must include exception on what should not be forwarded upstream.

= The homepage * A "watch" button to an app to get notifications on the app progress/issues/news* A better way to know the app status than currently color coding (Re: There needs to be known stages for that the application needs to go though and what states the application must contain more information = is in should also be noted)* A link to the upstream application.(This is mostly for legal reasonsDONE - maybe make it more visible?).* A Link to the list of known bugs.* A link on how to report a bug for the application.* A link to the place of discussion of the application.(we do have some support for this - however, it's hard to create a new forum)