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.
Thread beginning with comment 310658
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by TheNerd
by koki on Mon 21st Apr 2008 05:37 UTC in reply to "RE[4]: Comment by TheNerd"
koki
Member since:
2005-10-17

He does ... did you look at the screenshot of the about window?


I don't think you understand the point that I am trying to make. It is not the lack of disclaimers, but the fundamental fact that there is an intent to provide an end user experience from pre-alpha software that is problematic. You are creating an expectation that Haiku
is not ready to meet yet.

Sometimes testing requires video that works.


Yes, and that's exactly why the Haiku developers decided to remove the VMWare video driver from the official builds, because it is not fully functional in KDL.

Actually, he does. This is the only way new testers can test and report on broken software.


Why? A software package that people can download would serve exactly the same purpose. As a matter of fact, that's what the Haikuware superpack started as at the beginning. Now that I think of it, it may be even be possible for Karl to work with the developers so that such an application package can be included as an option in the Haiku build process. This is what third party application maintainers are doing (ie., Vision, Wonderbush, Firefox, Pe, etc.), and it works well.

I detect some HAIKU / BeOS snobbery here...


You are probably reading too much into all this. This is open source: the code is online; the development tools are available; there is also a reasonable amount of documentation available on our website; and we have a very friendly and responsive community on mailing lists as well as IRC happy to help. Any eager developer would most likely be able to get started with development with relative ease; your mileage may vary depending on your skills, but it is not as difficult as you want to make it sound.

According to you, the superpack is intended to address people not willing to make the investment currently required to get started. From what we have seen so far during the life of our project, anyone not willing to make such an initial investment is very unlikely to become a serious candidate for Haiku development.

HTH.

Reply Parent Score: 1