This document explains the artistic subtleties of Haiku icons. If it leaves something unclear to you, that is, what rules to follow when designing an icon for the Haiku operating system, please bring the issue to our attention. Existing icons should give you a pretty good idea what directions to follow. This document is meant to define the distinctive look in further detail and to be a useful resource in case of doubt. Also, this document will hopefully provide you with help on what you should change if you have designed an icon and feel it doesn't seamlessly fit in with the rest of the system.
The document below outlines our code style guidelines. If you have suggestions for things that should be clarified better, etc. please let us know. Please don’t send us suggestions of the kind “I like this indenting style better, could we switch?”.
The information in the document below is extremely important. If you will be contributing code or patches to Haiku, you will need to strictly follow the code style guidelines. Code which doesn’t follow the guidelines below will not be accepted.
Developers are the driving force behind Haiku, and without them, we would not be where we are today.
It’s hard to put into words the pleasure of seeing something you’ve built help many other people.
Newcomers will need to know or be willing to learn C++, as well as the BeOS/Haiku API.
Getting Involved
The best way to get into developing on the Haiku project is to get to know the
environment and make yourself familiar with the system. If you have programmed
for BeOS before, getting into the Haiku API shouldn't be a problem. If you are
new to Haiku, try spending some time with easier tasks (see below).
It is much easier for us to help you with problems you encounter after you
chose a task than to assign one to you as we don't know what your exact skills
and preferences are. Usually, by running Haiku for a while you will easily find
out things that don't work as expected or that can be improved.
What do I need for coding?
As far as development environments are concerned, Haiku itself can be a very optimal and frictionless
development environment. Linux and some BSD-based systems also work perfectly fine and using those
operating systems can be more practical.
The Haiku Code Drive 2008 donation period is over now. Haiku fans from all over the world have shown an incredible outpour of support and donated a total of $7,765.67 in just two weeks ($7,472.42 net). Thank you so much to everyone!
The Haiku Code Drive 2008 donation period is over, but you can still show your support for the project by making a donation from here at any time.
List of donors
During the two weeks of donation drive, we received more than 120 donations from 24 countries. Shown below is a list of donors in the order that the donations were received. A few names have been removed by request; if you would prefer to be removed from this list, please contact us.
This year for Haiku Code Drive, the student selection process has been completely overhauled. Unlike last year, where a public vote was held to select the students, our mentors have determined the combinations of <student>-<project>-<mentor>. Since our requirements for Google Summer of Code were greatly improved upon from last year, our mentors were able to confidently decide which of those combinations have the highest chance of succeeding.
Full-text indexing and search tool for Haiku
- Student: Ankur Sethi
- Mentor: Rene Gollent
- Project Abstract
This page shows the candidate students and their projects for the Haiku Code Drive 2008:
Salvatore Benedetto
Project: BFS stress-testing, UDF port to new FS Haiku API
Mentor: Axel Dörfler
The aim of this project is quite different from the others. Instead of proposing to add a new feature, I'd like to work on something R1 related, like making sure that BFS is *STABLE*. Since I'm almost done with Dominic's book about BFS, what I have in mind is to run some tests to stress all the aspects of Haiku's BFS implementation and see where it fails in order to fix the problem and bring the file system a step closer to being stable. To achieve this, I propose to do the following:
This page shows the projects selected by the community to participate in the Haiku Code Drive 2008. The projects are listed in the order that the community ranked them through the Haiku Code Drive 2008 poll.
Salvatore Benedetto
Project: BFS stress-testing, UDF port to new FS Haiku API
Mentor: Axel Dörfler
The aim of this project is quite different from the others. Instead of proposing to add a new feature, I'd like to work on something R1 related, like making sure that BFS is *STABLE*. Since I'm almost done with Dominic's book about BFS, what I have in mind is to run some tests to stress all the aspects of Haiku's BFS implementation and see where it fails in order to fix the problem and bring the file system a step closer to being stable. To achieve this, I propose to do the following:
Our application to become a mentor organization for the Google Summer of Code 2007 has been approved!
This year 8 students worked on our projects, of which 7 succesfully completed the program.
- JiSheng Zhang - FireWire support
- Andre Grazia - Network preferences
- Lukasz Zemczak - .pkg file installer
- Krishna Kishore Annapureddy - Precaching algorithm
- Salvatore Benedetto - USB isochronous streams
- André Braga - O(1) scheduler with CPU affinity
- Hugo Santos - Network stack revamp and FreeBSD compatibility layer
- Ivo Vachkov - ICMP error handling and propagation (failed - student lacked time to work on the project)
Our application to become a mentor organization for the Google Summer of Code 2007 has been approved! Qualifying students can apply for our GSoC 2007 ideas listed here between now and March 26th, 2007. For details about how to apply, please check out Students: How to Apply for a Haiku Idea.
If you find an idea marked as "big" interesting but feel you cannot completed in time, feel free to suggest splitting it into smaller parts in your proposal.
