Removing Trademarks from non-official builds

[mmadia]

This ticket addresses the occurrences of the HAIKU logo and Haiku name within built images. (feel free to adjust/correct)

HAIKU Logo:

• AboutSystem logo
• Installer logo
• Boot Screen
• Desktop wallpaper
• Haiku3d

"Haiku" name

• AboutSystem text
• Installer text
• ScreenSaver : Haiku
• Terminal "Welcome to the Haiku shell."
• uname (though, i've no idea what to do about that)

The build system is capable of defining 3 levels of "HAIKU_DISTRO_COMPATIBILITY"

official	: HAIKU_DISTRO_COMPATIBILITY_OFFICIAL ;
compatible	: HAIKU_DISTRO_COMPATIBILITY_COMPATIBLE ;
default		: HAIKU_DISTRO_COMPATIBILITY_DEFAULT ;

In addition, official releases have "HAIKU_OFFICIAL_RELEASE" defined.

I would like to make use of these definitions and to create 2 new definitions

This code snippet for build/jam/BuildSetup, would be used as the name of the software. For non-Project builds, end-users would define these in UserBuildConfig.

ifdef HAIKU_DISTRO_COMPATIBILITY_OFFICIAL
ifdef HAIKU_OFFICIAL_RELEASE
	HAIKU_SOFTWARE_NAME ?= 'Haiku' ;
	HAIKU_SOFTWARE_HOMEPAGE ?= 'http://www.haiku-os.org' ;
else
	HAIKU_SOFTWARE_NAME ?= 'Haiku (development build)' ;
	HAIKU_SOFTWARE_HOMEPAGE ?= 'http://www.haiku-os.org' ;
endif
endif

This code snipped could be used in the various rdef files

ifdef HAIKU_DISTRO_COMPATIBILITY_OFFICIAL
ifdef HAIKU_OFFICIAL_RELEASE
	<HAIKU Logo>
else
	<HAIKU Logo greyscale> or <HAIKU Logo sans leaves>
endif
elif defined HAIKU_DISTRO_COMPATIBILITY_COMPATIBLE
	<HAIKU Leaf>
else
	<blank image>
endif

[axeld]

We could introduce special "development" logos that are based on the trademarked one, and allow ourselves to use it for our nightly builds. I don't think replacing the logo with the leaf is a good idea - those are still images built by the official source.

[pulkomandy]

Maybe it would make sense to replace uname output with "walter"... but it would make config.sub and config.guess from autotools get in trouble. Mac OS X says "Darwin" there, which is more or less their "free-for-use" name.

[xeon3d]

+1

I love the ideas expressed here and I'm hoping for an easy way to remove the branding from the builds. Not only would it help so that people who wanted to distribute Haiku but not infringe on the trademarks, it would also help in the way that people who want to build their custom version of Haiku (for distribution purposes or not) also not infringe on it.

[mmadia]

HAIKU logo stripped from boot loader, AboutSystem, Installer

[mmadia]

draft: HAIKU-w.i.p.-logo in boot-loader, AboutSystem, Installer for non-official-releases

[mmadia]

WIP patch

[mmadia]

Here's some images that show how the system degrades gracefully when the trademarked logos are removed from the prominent places. Even though Installer looks funny, it remains functional.

I tried replicating the look of the 'alpha 2' text for "W.I.P.", but can't figure out how the bucket-fill erases were done. Would such a logo be acceptable to denote "built (& provided) by the Project, but is not an official release"?

The attached patch shows the direction of implementation. Oh, src/apps/installer/InstallerWindow.cpp can be ignored -- for a while, I was considering making Installer display prettier when there's no logo.

A much larger concern is "Haiku" as text -- epecially as it's in countless catkeys.

[pulkomandy]

catkeys shouldn't be too much of a problem. It is possible to use the #ifdef system in the code and the translators will have to translate the string multiple times. IIRC the is already the case with some other things, for example the SSL conditional in the mail preferences. If SSL is not available at build time, the preflet uses some strings, while if it is enabled, there is other text. I think I made it work in such a way that all the catkeys are exported properly ; but I'm not sure anymore... I'll have to check.

[Wim]

Replying to mmadia:

I tried replicating the look of the 'alpha 2' text for "W.I.P.", but can't figure out how the bucket-fill erases were done.

Although I have never done it myself, here is a link to a tutorial to create a rubber stamp effect using inkscape: ​http://howto.nicubunu.ro/rubber_stamp_inkscape/

[axeld]

I think that "development" is better suited as "W.I.P.", as it's easier to understand, especially in other languages. I hope it fits on the logo, though :-)

[mmadia]

example HAIKU development logo for non-releases

[mmadia]

The following changesets are involved in removing the graphcial logos: hrev37738, hrev37739, hrev37740, hrev37741, hrev37742

Issues to deal with:

• What graphic to use for 'compatible'
• removing textual occurrences of 'haiku'
• possibly displaying the 'development' logo for boot splash

[phoudoin]

Development logo is since hrev38891 displayed on boot splash for official but non-release build. Like nightlies.

[phoudoin]

BTW, since hrev37742 Pulse app is considered a trademarked application !? IIRC, Pulse was released by Be Inc. as sample code. It can't be Haiku trademark.

[tonestone57]

Pulse and Mandelbrot are from Be Inc (not Haiku Inc) - open source license. Change hrev37742 should be fixed. Below links show Be Inc. copyright & license.

​http://dev.haiku-os.org/browser/haiku/trunk/src/apps/pulse/PulseWindow.cpp
​http://dev.haiku-os.org/browser/haiku/trunk/src/apps/mandelbrot/Mandelbrot.cpp

Not sure who created Playground but the other apps were done by Axel, Alex & Ralf. They appear to be under MIT license so should be allowed in distros too. Only Haiku3D should be excluded because currently uses Haiku logo. Replacing with non-Haiku logo in Haiku3D would allow this application in distros too I would think.

Because of MIT license (for these applications), distro makers can always compile and include these applications in their Haiku distro. So, why exclude them from distro release? ie: developers above coded the applications but MIT license allows anyone to take and use them how and where they want to.

[mmadia]

Replying to phoudoin:

BTW, since hrev37742 Pulse app is considered a trademarked application !? IIRC, Pulse was released by Be Inc. as sample code. It can't be Haiku trademark.

in the following line of ​build/jam/HaikuImage, only Haiku3d is marked out ... everything else on that line is included in the image when HAIKU_DISTRO_COMPATIBILITY ?= "default" ;

SYSTEM_DEMOS = BSnow Chart Clock Cortex FontDemo GLTeapot
	$(HAIKU_INCLUDE_TRADEMARKS)Haiku3d Mandelbrot Pairs Playground Pulse Sudoku
;

In other words, $(HAIKU_INCLUDE_TRADEMARKS) affects only the individual target that it prefixes.

[tonestone57]

Ok, thanks for clearing it up Matt. Me & phoudoin both missed it. Should have taken a better look at the code. :-)

[phoudoin]

Replying to tonestone57:

Should have taken a better look at the code. :-)

Yep, sorry about that mmadia. So, what default graphics to use for "compatible" distros?. The blue leaf?

[mmadia]

Replying to phoudoin:

So, what default graphics to use for "compatible" distros?. The blue leaf?

#6385 has more information about this -- from the mailing list archive about the haiku compatible logos designed by Stephan some time back to screenshots of some examples.

[mmadia]

The patch was been applied and never marked obsolete. Leaving the ticket open, as the name 'Haiku' is still hard coded within the source code.

[pulkomandy]

I think we are good enough here. "uname" still says Haiku but changing that at this point would be too much trouble.

[nielx]

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone