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 310654
To read all comments associated with this story, please click here.
RE[4]: Comment by TheNerd
by bbjimmy on Mon 21st Apr 2008 04:37 UTC in reply to "RE[3]: Comment by TheNerd"
bbjimmy
Member since:
2006-03-25

1) First of all, you need to acknowledge that this is pre-alpha software, and that by definition it is not feature complete, nor fully functional.


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

2) The VMware graphics driver is left out of the official nightly builds because it does not fully work when you go into KDL. Because the nightly builds are meant to be for testing/debugging, providing functionality in the kernel debbugger is more important


Sometimes testing requires video that works.

I think you are missing the fact that there is a very specific intended audience for the nightly builds, and that this audience is expected to understand what pre-alpha software is and will therefore not jump to the kind of conclusions that your question implies. That's how we portray and position the builds, not as demos or trials.


You seem to miss the point that the superpack does indeed position the software as pre-alpha, it just lets the software be seen by a larger group than your private little developer club. This is open source software. If you don't want others to try it, even pre-alpha, than maybe you should quit developing it and forget it exists. You can't control who will see your work unless you develop private closed source software.




Good point: but you do not need to create a distro for this. An applications pack the users can download would perfectly serve this purpose, and it would save you (and me) from the burden of having to deal with branding, trademarks, guidelines, etc. ;)


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


I do see your logic, but someone who will not spend time to setup their own development environment can hardly be considered as a serious candidate for Haiku development.


I detect some HAIKU / BeOS snobbery here. Who are you to say that there might not be a very talented and willing developer that will overlook HAIKU because the current devs are insuring and insisting that it is so damned difficult to get a working development environment up and running? You seem to think that a potential developer is willing to spend hours setting up a development environment when he does not even know what HAIKU is all about. GET REAL

Reply Parent Score: 2