Version 11 (modified by nielx, 14 years ago) ( diff )

Announcement: password changes

Welcome to the Haiku development tracker

Please note that on Monday the 9th of June, will require new login credentials. The connection between the user accounts of the main website and the accounts on this service will be discontinued in order to prepare a move to a new server. If you have ever logged in on this website, you will automatically receive an e-mail with your new password. See the news post on the main website for more information.

Logging in

To login you will need an account for the Haiku website. You can use the same username and password for this tracker and the website. If you would like to report a bug, you can register for this account.

Reporting bugs

Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on you to give us some input on how things work at your end. Since this is a very early product, it is very likely that you will encounter bugs. We thank you for taking the time to report these. Since our time is limited, we need accurate information. Follow these guidelines to create helpful bug reports:

  1. Before reporting a bug please make sure that it does not yet exist. You can also use the search function for this.
  2. After you have established this is a unique bug, make your information as accurate as possible:
    1. Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).
    2. Mention which revision from SVN you are running. You can find this out in the 'About Haiku' application, in the Deskbar menu.
    3. Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.
    4. Describe what steps to you need to perform in order to expose the bug. This will help developers reproduce the bug.
    5. Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot. If it is a hardware problem, include a copy of the syslog file.
  3. After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding non-descriptive comments.
  4. Remember, reporting a bug is not something you do spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Stay around to answer these. Consider your participation 'done' when the bug is marked as 'fixed'. Together we can improve Haiku, bit by bit.

Browsing the source

This installation provides a way for you to browse through the source. Use the Browse Source button in the navigation bar above to start at the root of the source tree.

Useful information

This Wiki stores some useful information that you might want to look at:

  • ApiDocumentationStatus contains a list of the current work on the API documentation. Also, have a look at the team page.
  • EasyTasks contains a list of tasks that can be an entry point for new contributors.
Note: See TracWiki for help on using the wiki.