> >> I agree that setting a few guidelines what makes an app a good Haiku >> citizen would help software sites to sort out the "bad apples". Why >> don't the people with the motivation to do this now band together, and >> come up with a checklist for this? >> > > May I suggest a a choice of logo certifications? > > 0: Common requirements: > --Doesn't affect compatibility or stability of the system or other > applications > --Interface properly asynchronous (judged by result, not method) > --Stable on official builds > --No accessing private OS facilities > --Only major versions carry the badge of honor > > 1. Haiku [version] Compatible: > --Runs on Haiku via interpreter or native with substantial non-native aspects > --Basic adherence to HIG > --Basic OS integration - doesn't look terribly out of place, no misuse of OS > facilities > ----Excepted when the interpreter is to blame for the inconsistent look > provided > ------the appearance difference does not hinder usability. > --Application developers can submit their app for public review. Users & > developers > ----alike vote to permit use of the logo. (Integrate with Haikuware). I don't think we need to burden the Haiku developers for that. Just publish the requirements and let app developers auto-rate their works. If an app is found to misuse the badge just remove it. For the other badges if they have a fee, you should call them "certified" or "certification" or something that sounds like it has value, not just "Haiku X native". What will the fee be used for and who will collect it? > -- Denis.