According to ​How-to-proceed-with-the-Haiku-Compatible-logos, it looks like Stephan's Logo 5c, 3c, and 3d were the final selection.

We will collect potential "Haiku Compatible" logos on this page.

Stephan's Logo 1b	Stephan's Logo 2b

Stephan's Logo 5c	Stephan's Logo 3c	Stephan's Logo 3d

DRAFT Guidelines on Logo use

this is an attempt to define a process to allow software to use this logo.

The idea is a lot of software is either obsolete and running only on BeOS ; or weakly ported and using unixish style stuff. We want to avoid that, so the idea is to allow software to use this logo if it fits the guidelines.

What rules should software follow

• It should work on the latest stable release of Haiku
• It should work on gcc2 hybrid - other flavours of Haiku may be ignored
• Only the x86,gcc2hybrid version of software may get the logo - other flavours must not use it
• configuration files should go in home/config/settings; and the path should be obtained by the appropriate functions & constants, not hardcoded.
• The app must not write anything to the hard disk except in its own directory (/boot/app/appName, or whatever the user installed it), the configuration directories (home/config/settings, common/), unless the user explicitly asks for it (a save dialog is a good example).
• We can add other rules here...

• HIG compliance ?

Similar documents elsewhere

• Apple App Store Review Guidelines

Process for allowing logo use

who should give the authorization for using the logo ? Haiku,Inc. ? The developpers ? The rules should be simple enough so that we don't need a dev to check for them. But has the inc. resources for testing apps out ?