How And For How Long Can An Application Become An (Associated) GNOME Application (Instead Of Being Mentioned In The Section TRASH)?

The most important fact at first: These are my own rules for accepting an application as an (Associated) GNOME Application And although I'm probably not able to list all of my rules I naturally allow myself to violate each of them. Remembering these aspects I can name why an application is in my opinion an associated GNOME application or (still) not (no more):

  1. The sources of the application must be published and reachable in form of a tarball, which must have a more or less explicite installation guide. (Being offered by cvs is too complicate for people being as simple as I am.)
  2. The sources must base on the library GTK and should base on the GNOME system. (Otherwise I would have to change the nice abbreviation GIG standing for «GNOME Installation Guide».)
  3. The sources must be compilable on the base of the last stable pure GNOME system. (Otherwise I would not have any reason to kill my computer and reinstall it from time to time.)
  4. The compiled application must not (too often) crash. (Otherwise I would have a stable Windows again.)
  5. The compiled application should have a release number of at least 0.5. (Otherwise the stable GNOME system psychologically can't evoke the illusion of being ready.)
  6. The application should still be developed. (Otherwise I wouldn't have an address to mail my fault-reports.)
  7. The purpose of the application should be in any sense valid for more than one or two people. (Otherwise my wife would have to point out that I'm doing senseless things.)

© Karsten Reincke, Osnabrück (Germany) 2000/2001/2002.