From b8a3f47f120dda4c4d9bf29d0492bdadf8bc6d56 Mon Sep 17 00:00:00 2001 From: Kyle Auble Date: Fri, 13 Jul 2012 16:26:17 -0500 Subject: Moved AppDB notes from contributing page to wiki --- templates/en/contributing.template | 34 +--------------------------------- 1 file changed, 1 insertion(+), 33 deletions(-) diff --git a/templates/en/contributing.template b/templates/en/contributing.template index a2a0b18..0d019f3 100644 --- a/templates/en/contributing.template +++ b/templates/en/contributing.template @@ -20,7 +20,7 @@
  1. Creating fonts
  2. Drawing icons
  3. -
  4. Application owners
  5. +
  6. Maintaining applications
  7. Bug hunting and support
@@ -43,38 +43,6 @@ -

Application database: application maintainers

- -

Another very important aspect of Wine testing is to use or test real - applications regularly and report regressions as soon as possible to the Wine - developers. This way regressions are caught early, while the set of changes - to search through is still small and the Wine developer who made the change - still around. Another reason why your contribution is especially - valuable is that Wine developers probably do not have access to the - application (they cannot buy all the applications out there) or do not know - it well enough to test it properly.

-

You can help even further by becoming an 'application maintainer', that is by - maintaining that application entry in the Application Database. Many - applications can be made to run (or run better) by using just the right mix - of native (Windows) and built-in (Wine) libraries. By testing the application - with various library mix and then documenting your results in the - corresponding Application Database entry, you will help other Wine users be - productive with that application, thus making Wine useful to a greater number - of people.

-

Required skills:

- -

Bug hunting and support

Because there are so many Windows applications out there, and because very few of them work perfectly, we get a lot of questions from users, -- 1.7.9.5