Changes

From Amahi Wiki
Jump to: navigation, search
no edit summary
= Problem =
The current testing program does not workwell. People How can we improve it to make it run smoothly? New people usually crave one app. Some people work towards fixing things and others simply do not participate in ittry too hard (filing bugs or researching). Some may be too busy, but they still want to help.  That could be due people just are impatient and do not want to try the app or 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.
= Known Issues =
* SSO between wiki,fourmsNot easy for users to see what bugs there are for a given app* Bugs have to be manually linked by the testmasters,in order for the app packager and bug tracker do not work well.other interested people to be notified = Ideas = * A "watch" button to an app to get notifications on the app progress/issues/news* Bug Tracker 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 is hard in should also be noted)* A link to find. the upstream application (Yes I know DONE - maybe make it is more visible?)* A Link to the list of known bugs.amahi.org but * A link on how to report a bug for someone who does not guess that I there is not 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 static link.new forum)
== Policy/ Procedure needed for it to work ==
= If you develop a wiki page for a policy please update this wiki with the link=
 
* There needs to be known stages for that the application needs to go though and what states the application is in should also be noted.
* Policy on what the application information page on the mainpage should contain.
* 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 for the application must contain more information =
* A link to the upstream application.(This is mostly for legal reasons).
* 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.
Trusted, Bots, Bureaucrats, emailconfirmed, Administrators
4,146

edits