Go to file
CruxBox bb6b48a9c3 FS Interface Docs: Made read_dir description clear
Small change in the docs to make the explanation of read_dir
functionality a little more clear.

Change-Id: I202eb0f70b38c78962ad9ca1d267995977c04951
Reviewed-on: https://review.haiku-os.org/c/haiku/+/2900
Reviewed-by: Axel Dörfler <axeld@pinc-software.de>
2020-06-11 10:39:35 +00:00
3rdparty docker/bootstrap: ensure work volume exec, fix dependencies 2020-05-21 14:03:24 +00:00
build arm64: Fix libroot math, add fix crosstools package revision 2020-06-10 00:44:14 +00:00
data Update translations from Pootle 2020-06-09 21:51:25 +00:00
docs FS Interface Docs: Made read_dir description clear 2020-06-11 10:39:35 +00:00
headers AutoDeleter: add operator [] for ArrayDeleter 2020-06-09 08:10:42 +00:00
src Fix typo in unicode block name 2020-06-10 14:55:26 +02:00
.editorconfig
.gitignore
.gitreview
configure configure: Use /bin/dash as JAMSHELL if available. 2020-05-29 23:11:47 -04:00
Jamfile Revert "Add gmp and mpfr to the regular image package set." 2020-06-03 04:11:40 +00:00
Jamrules
lgtm.yml
License.md
ReadMe.Compiling.md
ReadMe.md

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 web-based source code browsers:

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.

Contributing to our infrastructure

See Infrastructure.