---

Note: Voting is not open yet.

Once voting is open, you will need to log in to vote and to view the results.

---

About this page

The intention of this page is to organize a vote, similar to wiki:R1/Alpha1Proposals. This vote is about requirements for R1 (Final). Voting 'must-have' for something means that you want R1 (Final) to be delayed until that and all other 'must-have' items are addressed.

Once the feature set is voted upon, a preliminary milestone for entering the beta cycles will be created. That preliminary milestone will include only the necessary features. Non-feature issues (such as bugs) will be reviewed as the beta milestone nears completion.

General Interest Poll

In addition to this page, a general interest poll (which is open to all) is available at the ​Haiku Website. The content is identical, and is an opportunity for each individual to effectively express their thoughts on this topic. As mentioned on that page, those results will be listed here after Sunday December 12th.

Definitions

must-have

This item will block the release of R1 (Final). Depending on what it is, it may also block entering the beta stage.

only-if-ready

This item will not block the release of R1 (Final) or any earlier releases. These items may be evaluated for inclusion in a particular release.

bundled application

This includes applications within the project's repository and the graphical applications included as OptionalPackages. Command line applications are not included in this definition.

This poll will remain open until Sunday December 12, 2010 (approximately 19:00 UTC)

Afterwards, the results of the #GeneralInterestPoll will be merged (and listed as such) on this page. A courtesy email will go out to the ​haiku-development mailing list

---

Proposals for R1 (Final)

In each of the following proposals, select either 'must-have' or 'only-if-ready'. Remember, R1 will certainly include each and every one of the 'must-have' items.

Prop #1 TTY Layer

• #35

Poll(Include in R1; must-have; only-if-ready)

---

Prop #2 PPP / dial-up support

• For 'hardware' (non-winmodem) modems
• ​open PPP tickets

Poll(Include in R1; must-have; only-if-ready)

---

Prop #3 bootman: support multiple drives

• hrev25044, #2477, #3545, #4503, #3443, #5595

Poll(Include in R1; must-have; only-if-ready)

---

Prop #4 IRQ routing

Necessary to configure and use hardware (like PCI devices) if the BIOS expects the OS to do it.

• #5

Poll(Include in R1; must-have; only-if-ready)

---

Prop #5 Haiku Book (API documentation)

Currently viewable at ​http://api.haiku-os.org/. This is split into (2) subsections. Vote for each subsection.

Prop #5a Only the parts that are inconsistent with the BeBook

Poll(Include in R1; must-have; only-if-ready)

Prop #5b In full, so as to make the BeBook obsolete

Poll(Include in R1; must-have; only-if-ready)

---

Prop #6 Haiku User Guide: pages for all bundled applications

Poll(Include in R1; must-have; only-if-ready)

---

Prop #7 Default sound effects

• possibly organized in a manner similar to Haiku Icon Contest

Poll(Include in R1; must-have; only-if-ready)

---

Prop #8 WiFi (WPA,WPA2 encryption)

Poll(Include in R1; must-have; only-if-ready)

---

Prop #9 WiFi (userland tools + ifconfig integration)

• Tools for discovering and joining wireless networks.
• command line integration

Poll(Include in R1; must-have; only-if-ready)

---

Prop #10 Public Layout API

• at least capable of being an "Experimental" API, as opposed to a "Finalized" API
• #5524, #5526

Poll(Include in R1; must-have; only-if-ready)

---

Prop #11 Layout API: All bundled applications to utilize layout api

• note: there is no master ticket for monitoring progress.

Poll(Include in R1; must-have; only-if-ready)

Prop #11a Tracker (tracker_layout branch)

Poll(Include in R1; must-have; only-if-ready)

---

Prop #12 Locale Kit: All bundled applications to be localized

• #4619

Poll(Include in R1; must-have; only-if-ready)

---

Prop #13 Networked Filesystem Integration (ftp, ssh, nfs, smb)

Poll(Include in R1; must-have; only-if-ready)

---

Prop #14 Debugger

• completed enough, so as to replace gdb as the default debugger

Poll(Include in R1; must-have; only-if-ready)

---

Prop #15 Include Jamfile-Engine

• #5360

Poll(Include in R1; must-have; only-if-ready)

---

Prop #16 Stack & Tile as default decorator

Poll(Include in R1; must-have; only-if-ready)

---

Prop #17 Video mode setting drivers (nvidia, ati, intel)

Poll(Include in R1; must-have; only-if-ready)

---

Prop #18 Multi-head support in app_server

• including independent DPI for each head

Poll(Include in R1; must-have; only-if-ready)

---

Prop #19 BWebView API

• requires importing WebKit as an OptionalBuildFeature

Poll(Include in R1; must-have; only-if-ready)

---

Prop #20 Services Kit

Poll(Include in R1; must-have; only-if-ready)

---

Prop #21 WebPositive Related

This is split into several subsections. Vote for each subsection. Create additional sub-items as desired.

Prop #21a HTML5 video + audio support

Poll(Include in R1; must-have; only-if-ready)

Prop #21b User agent faking

• #6633

Poll(Include in R1; must-have; only-if-ready)

Prop #21c SSL cert enhancements

• #6493

Poll(Include in R1; must-have; only-if-ready)

Prop #21d Implement caching

Poll(Include in R1; must-have; only-if-ready)

Prop #21e Implement password management

Poll(Include in R1; must-have; only-if-ready)

---

Prop #22 BNotification API

• #1245

Poll(Include in R1; must-have; only-if-ready)

---

Prop #23 Finalizing new driver architecture

Poll(Include in R1; must-have; only-if-ready)

---

Prop #24 Updating drivers to utilize new driver architecture

Poll(Include in R1; must-have; only-if-ready)

---

Prop #25 Network preflet rewrite

Poll(Include in R1; must-have; only-if-ready)

---

Prop #26 OpenSound + Native Driver co-existance

• #6798, Testing required.

Poll(Include in R1; must-have; only-if-ready)

---

Prop #27 Boot failure issues

• All known bugs that cause boot failures on supported hardware to be resolved

Poll(Include in R1; must-have; only-if-ready)

---

Prop #28 Driver issues (gfx, audio)

• All known bugs that render supported hardware useless to be resolved. (eg, distorted display)

Poll(Include in R1; must-have; only-if-ready)

---

Prop #29 IPv6 network support

Poll(Include in R1; must-have; only-if-ready)

---

Prop #30 Haiku Upgrade Management

• To allow/ease the process of updating an existing Haiku installation.

Poll(Include in R1; must-have; only-if-ready)

---

Prop #31 Package Management

Poll(Include in R1; must-have; only-if-ready)

---

Prop #32 Isochronous USB transfers

• #1045

Poll(Include in R1; must-have; only-if-ready)

---

---

​Unscheduled

The following items are generally considered 'only if ready' (or definitely post-R1).

• (Up until voting starts): Feel free to move them to actual propositions.
• (Once voting starts): add additional unscheduled items.

1. Session management
2. Content based search
3. Hardware 3D acceleration
   • 3D accelerated app_server
4. Tracker rewrite/refactoring
   • separate view mode code
   • add more view modes
5. Multi-user support
6. 64 bit support
   • #1141
7. Keyboard shortcut and gestures management (Spicy Keys has been integrated as "Shortcuts", needs improvements.)
8. Keyboard and Mouse settings associated with hardware
9. Concurrent user support in input and app_server
10. Remote app_server (has been implemented, but could use more user-friendly integration)
11. More POSIX compatibility
12. Replacing the C library
    • #1907
    • ​haiku-development:PATCH-libroot-improvements
13. Power management
14. I/O APICs (implemented, but the interrupt mapping for PCI interrupts that has to be read through ACPI is yet missing)
15. Floppy drive support
16. Media Acceleration library (common routines to be used by media plugins that can be replaced by OpenCL, SSE or the like)
17. New file system - FutureHaikuFileSystem
18. API changes after dropping BeOS backwards compatibility - ​APIChangesOnCompatibilityDrop
19. Calendar / Scheduling application (and server?)
20. Gamepad/joystick support ​ML thread