Welcome to the Haiku development tracker
Logging in
To login you will need an account for this service. If you do not have an account, you can register one by clicking the link in at the top. When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the AccountVerificationEmail usually ends up there.
Using the tracker
- Read BugTrackerEtiquette. This mentions what content is appropriate, where to seek additional assistance, and peculiarities with our bug tracker.
- Read BugTrackerEtiquette. We mean it.
- ReportingBugs details what information to include on bug reports and how to obtain it.
- SubmittingPatches mentions the preferred way for creating patches.
Have a look at TicketLife for more information on what will happen to your ticket during its lifetime.
Browsing the source
You can find instructions on how to get the source with git. Developers: have a look at the GitStarted page for resources on getting started with developing in Git.
If you just want to have a look at the repository, we also have cgit set up for you.
Useful information
This Wiki stores some useful information that you might want to look at:
- EasyTasks contains a list of tasks that can be an entry point for new contributors.
- FutureHaikuFeatures lists functionality that would be well appreciated.
- FutureHaikuFileSystem is a place to brainstorm Haiku's file system after R1.
- APIChangesOnCompatibilityDrop is a collection of API changes we intend to make as soon as we drop BeOS backward compatibility.
- CodingGuidelines/VIM is a small script that will detect some guideline violations for vim.
- HaikuCodingStyleChecker is a python program that will detect some guideline violations.
- The Coding Guidelines are expected to be followed.
- Search Haiku's code on {OpenGrok: xref.landonf.org, or on github.com
