Linked by Thom Holwerda on Sat 19th Apr 2008 23:39 UTC, submitted by TheNerd
BeOS & Derivatives Every now and then, the Haiku mailing lists explode with emails about something called the distribution guidelines. The Haiku guys set up a set of guidelines with regards to use of the Haiku trademarks and logos; the "Haiku" name may not be used in the distribution's name, official trademarks and logos must be excluded, but the Haiku icons and artwork may be used. In addition to these cosmetic and trademark issues, the guidelines explain what is needed in order to receive the official "Haiku compatible" logo.
Permalink for comment 310607
To read all comments associated with this story, please click here.
RE[2]: Comment by TheNerd
by kvdman on Sun 20th Apr 2008 20:45 UTC in reply to "RE: Comment by TheNerd"
kvdman
Member since:
2006-04-28

[q]nor do I see how any of this advances Haiku in any beneficial way.


The point of the Superpacks, now Senryu, was to provide users with a more fulfiling experience under a virtualized environment - to demonstrate Haiku's capabilities. Take the default images provided by haiku-filess.org. No proper graphics, burning, audio, or network support (explanation how to get networking running). What impression does that leave? Then they come with 150mb of free space. What can we do with 150mb these days? Why not increase, or make a growing disk of 10gb so we don't have to keep careful watch of space restrictions?

The other idea, was to bundle some tested, working, and popular BeOS applications to show that Haiku really does what it says, achieve binary compatibility... If a user of the images then decides to try some other applications on the disk image he can now actually download stuff to it because it's big enough, he/she can then file a bug report if it doesn't work as expected, because guess what? A browser is included.

I've tried many BeOS applications under Haiku, and many didn't work (many did too ;) . After testing failing binaries, I filed bug reports, which led to bugs being uncovered in Haiku, which led to Haiku becoming more stable and Haiku's vision of being binary compatible inch closer to its goal. This is what I hope for with these disk images.

For the developer edition, the hope was to cut down the time, size, and energy needed to setup a build environment in the hopes that the image would get into the hands of interested developers that may contribute to Haiku.

That's the purpose, and that's how I thought it would benefit Haiku; but clearly opinions differ.

Reply Parent Score: 1