Google Summer of Code Ideas for Haiku

Work In Progress: 2010

Limitations:

• Should be peripheral projects that will not affect any time lines for the project.
• Published ideas need at least one person willing to be mentor.
• Maybe we can mention which ideas require a mentor to be found ?

Notes:

• Make sure every idea has a detailed explanation
• Create a list of small tasks -- or at least guidelines as the type of tasks that can be piggy-backed on another project
• Provide links to or at least mention:
  • relevant parts of the source tree
  • relevant chapters in BeBook
• existing bug tickets
• persons who can discuss the topic -- this is primarily for the admins, to help redirect inquiries.
  • eg. NickName is currently on IRC or AnotherNickName reads the mailing lists.

Actual Ideas

• Non R1 tasks: ​http://dev.haiku-os.org/wiki/FutureHaikuFeatures

• TTY Layer

• Remote app_server -- user-friendly integration

• Updating & Utilizing RamFS
  • detect available memory at boot.
  • create drives based on some rules
  • /tmp should be mounted as ramfs -- for both RW & RO medium
  • maybe a Preflet to control settings
  • create a true live cd experience.
    • keep settings on ramfs.
    • write to a secondary disk at shutdown or at 'sync'
    • read imagefile from disk to ramfs at boot

• Filesystems: general improvements
  • EXT, ReiserFS: write support
  • UFS2: Read (& Write) support
  • ZFS: Read (& Write) support

• Non-x86 Ports:
  • ARM
  • PowerPC

• Improving POSIX support

• Updating applications to use layout manager.

• Fix and improve Haiku's mail system (which ​tickets exactly has yet to be decided).

• 3rd Party Applications
  • ​IM Kit
  • ​Services Kit
  • WebKit based browser
  • OpenJDK

• Utilizing aspects of 3rd party software
  • Creating Text Translators from OpenOffice

• Integrating software into Haiku
  1. updating to use a jam build system
  2. complying with Haiku's Coding Guidelines
  3. layout manager
  4. HVIF icons
  5. Locale Kit
  6. possibly becoming an actual part of Haiku's source tree and not a 3rd party addition
  • ​InfoPopper -- as an actual notification_sever
    • ​Big discussion in May 2007
    • ​And some more in April 2008
    • ​Year++ with plan for integration
  • ​PecoRename or ​ReName!
  • ​Colors!
  • ​ClipUp

• Native GUI for:
  • Transmission
  • VLC

• Hardware profiling tool
  • an application for creating a hardware database.

• Language bindings in SWIG
  • python
  • perl
  • ...

• Maybe something involving HaikuPorts?
  • improving HaikuPorter to work more like FreeBSD's ports -- python programming

• Jam build system enhancements.
  • like what...? generic wrapper for autotools, makefiles. This would help integrate existing projects into Haiku's source tree or 3rdparty folder

• Enhancements for Virtualization Software

• Universal Spell Checker, built upon the WordServices SDK. note: see ​Spill Chucker

• Improving ​QT4 port ​http://qt-haiku.ru/

• IPv6 Mentor Needed!

• CUPS

• Gallium3d

2009

See official page here: ​http://www.haiku-os.org/community/gsoc2009/ideas