Go to file
2015-04-03 02:07:55 +02:00
3rdparty checkstyle.vim: add catch to checked keywords 2014-11-26 13:27:33 +01:00
build Updated coreutils packages 2015-04-02 18:52:07 +02:00
data Add an icon for SD Card devices 2015-04-03 02:07:55 +02:00
docs Haiku Book: Make the layout introduction somewhat more professional. 2015-03-25 11:47:29 -04:00
headers Use B_PRId32. 2015-04-01 20:18:00 +02:00
src Network/DNSClientService: fixed missing error check. 2015-04-02 11:03:58 +02:00
.gitignore Update ACPICA to 20140724. 2014-08-23 16:30:50 +02:00
configure jam/arm: Add missing overo target board 2015-03-16 10:38:36 -05:00
Jamfile Added netcat packages for x86 and x86_64, use them. 2015-03-03 22:49:00 +01:00
Jamrules Merge branch 'gcc_syslibs' 2014-08-13 13:50:29 +02:00
makehaikufloppy
ReadMe.Compiling Interface Guidelines: migrate to docs/, use DocBookCSS. 2015-02-12 17:08:04 -05:00
ReadMe.md ReadMe: Convert to Markdown, various cleanup. 2015-02-11 18:56:15 -05:00

Haiku

Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs

Haiku is an 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.

Goals

  • Sensible defaults with minimal configuration required.
  • Clean, clear, concise code.
  • Unified desktop environment.

Trying Haiku

Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.

Compiling Haiku

See ReadMe.Compiling.

Contributing

Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!

Contributing code

If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.

If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:

Contributing documentation

The main piece of documentation that still needs work are the API docs (found in the tree at src/docs/user). Just find an undocumented class, write documentation for it, and submit a patch.

Contributing translations

See wiki:i18n.

Contributing software ports

See HaikuPorts.