Haiku is a new open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.

Fundraising 2014

Goal: $35,000
  $23,862

WHAT'S NEW IN HAIKU DEVELOPMENT

The Haiku source is continually built and released for testing purposes nearly every day. You can download and install these latest snapshots to check out the latest features and bug-fixes.

Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.

If you're OK with this, you can find further instructions at our Nightly image page.

From Bugs back to Wireless and Friends

Blog post by mmlr on Mon, 2011-11-28 02:04

As this week concludes I'd like to post an update on what I've been up to and what I'll be working on next. After fixing a few kernel issues and looking into some others I've come to a point where I'll gradually refocus back on some of the tasks I left open before mentally entering the kernel debugging land. In this blog post I'll also try to describe some of what I did this week to hopefully make it a bit more accessible.

University of Auckland: Scholarship awarded! Call for Students/Visitors!

News posted on Sat, 2011-11-19 17:08

Exciting times these are. Haiku, Inc. steadily marches towards being capable of funding a core developer for 12 months of contractual development. Thank you donors! BeGeistert 024 has spurred a flurry of commits, even continuing past the coding sprint. Google has accepted Haiku as a mentoring organization in its Google Code-in 2011 program. The version control system has been migrated from subversion to git. Thank you sys-admins! And on top of all this, the University of Auckland has awarded Alex "yourpalal" Wilson with a 2011/12 International Summer Scholarship for a research project in Haiku! And the university has placed an open call for additional students and visitors!

Greetings (mostly) from the Kernel (Debugging Land)

Blog post by mmlr on Thu, 2011-11-17 17:00

So what is going on right now in the time I spend on my Haiku contract? For the past two and a half weeks I've had my mind wrapped around various parts of the kernel. Things started out at BeGeistert and the coding sprint following it. The nice thing about the coding sprint is that you spend a lot of time with very knowledgeable people and can therefore tackle things that you would usually shy away from. In this case, Ingo Weinhold and I were seeing some random memory corruption problems and an apparent memory/pages leak. So we started investigating those by adding more debug functions into the relevant parts.

2011 Google Code-In Contest, Haiku Selected as One of Eighteen Participating Organzations

Blog post by scottmc on Thu, 2011-11-10 04:18

Haiku has been selected as one of eighteen organizations to participate in the Google Code-In 2011!

Once again Haiku has been selected to participate in Google Code-In. To read the announcement and to see what other organizations were selected see [1] below. Here's some basic information on the contest:


Google Code-In 2011 logo

Google's contest to introduce pre-university students to the many kinds of contributions that make open source software development possible, is starting on November 21, 2011. We are inviting students worldwide to produce a variety of open source code, documentation, training materials and user experience research for the organizations participating this year. These tasks include:

1. Code: Tasks related to writing or refactoring code
2. Documentation: Tasks related to creating/editing documents
3. Outreach: Tasks related to community management and outreach/marketing
4. Quality Assurance: Tasks related to testing and ensuring code is of high quality
5. Research: Tasks related to studying a problem and recommending solutions
6. Training: Tasks related to helping others learn more
7. Translation: Tasks related to localization
8. User Interface: Tasks related to user experience research or user interface design and interaction

Official Google Code-In website and to review the updated rules for 2011. [2]

Over the next couple of weeks we will be busy getting our task list in order and putting together a good group of Haiku mentors for this. Many of the tasks will be for translations, so we may still need a few more mentors to cover some of those tasks. If you are interested in mentoring please let us know on the mailing list. For a preview of some of the possible Haiku tasks, you can check the wiki page we used for gathering ideas. [3]

BeGeistert 024 + Coding sprint report

Blog post by PulkoMandy on Fri, 2011-11-04 12:17

I'm heading home from the BeGeistert event that just ended today.

For those who don't know, BeGeistert is the european meeting of all Haiku (and BeOS) developpers and enthusiasts. This year, Haiku has seen its third alpha release, and we feel that R1 shouldn't be too far.

So, what happened there ? Over the weekend we had multiple conferences. The first one on saturday morning was a discussion on Haiku's release process and roadmap for the future. We didn't have time to solve all the problems, but at least one important decision was taken : after delaying the switch to git to after alpha3, then after gsoc, we finally decided it was about time to actually flip the swith. This is scheduled for the 12th of November.

Speaking of Git, Oliver Tappe made a talk about how to use it and the main differences with the current Subversion, and presented the work done so that Haiku developpers don't get lost.

Then, there were talks from Ingo and Oliver about package management, with an impressive demo of the current status It's working, but there are some problems with it like deskbar replicants not working anymore because of the readonly nature of packages (that was solved later during the coding sprint).

Stippi presented us the layout API and some examples on how to use it. The Layout API is an extention to the interface kit that allows much more easier design of window layouts.

François Revol presented us a proposal for UXA, an unified extended attribute scheme to efficiently share attributes between different OSes. While many filesystems and OS now support attributes like Haiku (NTFS, ReiserFS, ...), they all use their ownscheme and the conversion from one to another isn't always a reversible process.

We also had a presentation of an application called VOPTOP, which is a nice peer-to-peer VoIP chat application. The main feature is it uses peer to peer routing to make the communication. This makes it needed to use encryption to make sure one pf the peers doesn't spy the communication.

Finally, Matt Madia told us about the status of Haiku, Inc. Besides helping with the funding of BeGeistert, they are paying mmlr for a full-time year working on Haiku, which is likely to bring us much nearer to R1. The donated amount to Haiku, Inc. this year was rather impressive, which makes it possible to think about more contracts for Haiku developpers, but also things such as giving Haiku shirts to people showing out Haiku at various free software conferences (to strenghten the image of the project).

Axel proposed a patch hour on sunday. An ongoing problem in Haiku is the unability to handle patches submitted by users on Trac. Our policy is to review the patch, and ask the author to improve it. Quite often several rounds of improvements are needed, and people don't react too fast or give up on the amout of work needed to get the patch in. So, the patches tend to accumulate in trac and never get commited. They get out of sync with svn trunk, and it is not possible to apply them anymore. So, Axel took the list of 144 patches waiting on Trac, and wrote the ticket id of each of them on a piece of paper. Each of us was given 5 tickets to look at and make a decision. Either cleanup and apply the patch, or reject it if it doesn't work. At the end of the hour, about 40 tickets were closed. Some of us continued looking at the list over the week, and now there is less than 80 patches left, so the list has decreased by half.

As the weekend was over, the coding sprint started. 9 developpers were present this year : Matt Madia, François Revol, me, Olivier Coursiere, Ingo Weinhold, Michael Lotz, Oliver Tappe, and Rene Gollent. With the imminent switch to Git, Matt worked on getting a buildbot running with it to replace Build-O-Matic that only does SVN. However, he ran into some weird problems with building the now 10 years old gcc2 on FreeBSD, so not everything is working yet. François worked on bringing the 68k port of Haiku back in compiling state, as it was broken by some architecture changes. This was a success, as we can now run KDL on the aranym emulator. The work stopped at needing a build of the ICU package, which is a bit painful to do for platforms other than x86. Olivier worked on Lazarus, a Qt-based Delphi clone that now mostly runs in Haiku. He also made some stress testing of Haiku by copying the OpenOffice sourcecode around. Eventually, he found a bug in DiskUsage and fixed it. Michael and Ingo started tracking a memory corruption bug that may be the cause for the few remaining cases of FS corruption. But this ended up in writing KDL tools for tracking memory use, which will come in useful to track memory leaks, looking at pages owners and similar stuff. Oliver worked on fixing our wchar_t support. He got it working but needs to test compatibility with BeOS applications. The change involves the compiler support for wchar_t, and any application using that needs to be rebuilt. If we can't get it working in a way compatible with BeOS, it's likely that only gcc4 built parts of the system will get the fix. Rene Gollent worked on some TODOs for the debugger. One part was saving and resoring the view layout of Debugger accross sessions. The other was starting to add a CLI mode. When both are done, Debugger will replace GDB as the default debugger for the system. The CLI mode is needed mostly to debug app_server crashes. I worked on various areas of the system, but most notably reworked (again) the notification windows (I'm now rather happy with the result), and fixed bugs in the game sound API which now seems to be working fine.

Overall this coding sprint week was very productive, with several hundred commits improving the Haiku codebase. This also apparently boosted donations to Haiku, Inc. quite a bit. I'm ready to attend the next one.

My first Month of Contract Work

Blog post by mmlr on Thu, 2011-10-27 07:54

As some of you know, I've started my contract work on Haiku pretty exactly one month ago. During that time I've been working on various things that I'd like to summarize in this post. In the future I plan on posting more but shorter entries, but since much has happened in this month this one is going to be a bit more elaborate.

Help secure 1,000 EUR for the Haiku Support Association

Forum thread started by humdinger on Fri, 2011-10-21 07:21

Hello there!

As you may know, the "Haiku Support Association e.V." (HSA) is organizing the regular BeGeistert meeting and the associated Code Sprint. We may engage in other activities to further Haiku development in the future, if anybody has a good idea, helps with its implementation and we have the necessary funds available... *)

Speaking of funds... we could need everyone's help:
Urias McCullough made us aware (thanks, mate!), that there's a program of the German DiBa bank that awards the top 1,000 German registered societies 1,000 EUR each. It's determined by vote, and that's where the Haiku community comes in.


UPDATE:
The voting is over. Alas, we didn't make it in the top 1000. With 1,595 votes we only made it to rank 1,827, while we'd have needed at least 7,902 votes for place 1,000... Anyway, thanks everyone for your support!


If you want the HSA to be among the top-1000 you'll have to: