| | 13 | = DRAFT Guidelines on Logo use = |
| | 14 | |
| | 15 | this is an attempt to define a process to allow software to use this logo. |
| | 16 | |
| | 17 | 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. |
| | 18 | |
| | 19 | = What rules should software follow = |
| | 20 | * It should work on the latest stable release of Haiku |
| | 21 | * It should work on gcc2 hybrid - other flavours of Haiku may be ignored |
| | 22 | * Only the x86,gcc2hybrid version of software may get the logo - other flavours must not use it |
| | 23 | * configuration files should go in home/config/settings; and the path should be obtained by the appropriate functions & constants, not hardcoded. |
| | 24 | * 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). |
| | 25 | * We can add other rules here... |
| | 26 | |
| | 27 | * HIG compliance ? |
| | 28 | |
| | 29 | = Similar documents elsewhere = |
| | 30 | * Apple App Store Review Guidelines |
| | 31 | |
| | 32 | = Process for allowing logo use = |
| | 33 | who should give the authorization for using the logo ? Haiku,Inc. ? The developpers ? |
| | 34 | 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 ? |
