Go to file
2015-07-13 18:13:48 +02:00
3rdparty recipe.syntax.vim: Update following SRC_URI/SRC_FILENAME change 2015-07-02 19:28:11 +02:00
build Updated gcc package for x86_64. 2015-07-13 06:47:26 +02:00
data Update translations from Pootle 2015-07-11 06:40:05 +02:00
docs BRoster docs: force be_roster to link, lang cleanup 2015-07-07 16:22:31 -07:00
headers Implement BMediaRoster::GetNodeAttributesFor 2015-07-13 18:13:48 +02:00
src Implement BMediaRoster::GetNodeAttributesFor 2015-07-13 18:13:48 +02:00
.gitignore .gitignore: add .pyc and .pyo files. 2015-06-19 15:40:40 -04:00
configure arm: Initial Cubieboard4 work 2015-04-11 16:53:04 -05:00
Jamfile Add a feature for expat. 2015-06-10 23:31:55 +02:00
Jamrules build: delete DocumentationRules. 2015-06-22 13:20:07 -04:00
ReadMe.Compiling.md ReadMe.Compiling: specify Bison 2.4 as the minimum. 2015-06-22 13:20:01 -04:00
ReadMe.md ReadMe: HaikuPorts has moved to GitHub. 2015-06-30 10:03:49 -04: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 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.