Suggestion Box

At some point will Haiku implement some type of automated bug reporting process, similar to Windows Error Reporting? Many more bug reports would get into the system this way, since only a few users take the time to file through the current system.

Hi everyone,

Just like the real estate saying "location location location", I'm starting to wonder why if anyone really understands me when I say to them "platform platform platform"?

What I mean by this is really simple: Use a PC that is attractive, futuristic, well priced, and most importantly - well spec'ed for a solid base to build upon and speed up acceptance.

Here are just 2 examples of where I am personally going to use Haiku:

HP ENVY Recline 27 http://www.youtube.com/watch?v=a9WM5BacJvg

OR

LG Anllinone V960 Ultrawide http://www.youtube.com/watch?v=m0Y8q_9oYw4

I don't want to use Haiku on old hardware that sucks, I am going to use it on new hardware that is going to blow my visitors minds when they see it and use it.

I can already hear people stabbing at the keyboard, replying to me that "this isn't where or what Haiku is all about", but honestly - why not? Let go of your nostalgia and ideals of using it on any old hardware... it's time to move on!

Targeting Haiku to a more specific hardware set will increase the "known known" ratio by a factor of 10 at least. Then new, young, full of piss and vinegar developers can jump in and write some code for touch and full GPU acceleration - Or whatever.

Laying a road map is more than just API planning, it's looking a the big picture and trying to get the herd to move in that direction as easily as possible.

PCs of the past were very personal things - but now, I want "appliance PCs" all over my house. I don't want logins, I don't want OS X, I don't want iOS, I don't want Android, I don't want Win8... I don't want anything that "Phones Home".

Haiku, this is a HUGE opportunity. You could lead the way - by leading! So? Lead.

Choose a cool desktop and cool tabtop and then Lead the frigin way home down your roadmap to R1!

with the rise of the gpgpu and newer videocards allowing for sometimes hundreds of streams in parallel, it almost seems a waste to leave a dedicated videocard rendering to screen every cycle when you're not actively playing the latest billion-polygon 120fps stereoscopic doom clone rather than looking at each of these readily available pieces of drop-in hardware as a relatively inexpensive means of adding processors to a workstation for the purpose of handling any number of tasks. looking at developments like opencl and amd's heterogenous system architecture, it at least seems to be the direction that hardware vendors are pushing us, and with the processing, memory and bandwidth advantage that affords us i would say it's not a bad push. after all, at the moment it's about the only way to fit a multiprocessor computer into a mini-itx case, which in turn is the best solution for running a multiprocessor machine on the lowest wattage possible. now, i know there is nothing stopping anyone, at the application level, from taking advantage of these developments, but what about at the system level? what would that even look like? could it possibly be less work than hardware video drivers?

Program Rules

On October 9, 2013, we announced a new, experimental program that rewards proactive security improvements to select open-source projects. This effort complements and extends our long-running vulnerability reward programs for Google web applications and for Google Chrome.

Projects in scope

We intend to roll out the program gradually, monitoring the quality of the received submissions and the feedback from the developer community. Currently, the scope is limited to the following projects:

Open-source foundations of Chrome and Android: Chromium, Blink, AOSP
Security-critical, commonly used components of the Linux kernel (including KVM)
High-profile web and mail servers: Apache httpd, lighttpd, nginx, Sendmail, Postfix, Exim, Dovecot
Other high-impact network services: OpenSSH, OpenVPN, BIND, ISC DHCP, University of Delaware NTPD
Core infrastructure data parsers: libjpeg, libjpeg-turbo, libpng, giflib, zlib, libxml2
Other essential libraries: OpenSSL, Mozilla NSS
Toolchain security improvements for GCC, binutils, and llvm

More info @ http://www.google.com/about/appsecurity/patch-rewards/