Google Code-in Ideas 2012

This is the brainstorm page for the ​Google Code-In.

Translation tasks have been dropped from Google Code-In 2012, so there will be no translation tasks here. Google is reducing the number of orgs for 2012 down to 10 from a total of 18 orgs in 2011. Haiku may or may not be one of those 10. Also the difficultly levels will be removed and tasks should be created such that they would take about 2-4 hours to complete.

Developers and documenters: Suggested tasks can be added below if you have wiki edit rights.

Prospective Students: This page should give you an idea of what tasks may be available for Haiku, should we get selected for GCI 2012.

1. Code: Tasks related to writing or refactoring code

Resolve any open Haiku trac ticket	<== Need to search through these and create tasks for ones that students could handle
Resolve any open HaikuPorts trac ticket	<== Need to search through these and create tasks for ones that students could handle
Add Haiku native GUI to the cmake port, (​http://ports.haiku-files.org/ticket/236)
Bluetooth Stack/UI Improvements (​http://docs.google.com/View?id=dc8wsckv_6d8qdzbfz)
Implement a patch per Comment 2 in Bug:6746
Create a linux package (.deb / ppa) for bfs_fuse
Research and implement AMD SimNow HDD image build target
Update poorman to use layout manager https://dev.haiku-os.org/ticket/3787 3787

2. Documentation: Tasks related to creating/editing documents

Verify if all the steps mentioned in the "Welcome to Haiku" document are accurate, and suggest improvements.

Write an introduction for one of Haiku's kits for ​http://api.haiku-os.org

Write documentation for one class in API reference manual

3. Outreach: Tasks related to community management and outreach/marketing

Present a Haiku lightning talk (about 5 minutes long) at a local Linux User Group or similar interested group. (5 or so slides on a specific part of Haiku)

Present Haiku at a local Linux User Group or similar interested group. (20 or so slides and demo time)

Create a more gripping screenshot slideshow for the website.

4. Quality Assurance: Tasks related to testing and ensuring code is of high quality

Test all open trac tickets for Expander (6) and indicate whether they are still valid. Add extra information as needed.

Test all open trac tickets (0-6700) for MediaPlayer ShowImage (22) and indicate whether they are still valid. Add extra information as needed.

Test all open trac tickets (6700-8100)for MediaPlayer (21) and indicate whether they are still valid. Add extra information as needed.

Test all open trac tickets for ShowImage (15) and indicate whether they are still valid. Add extra information as needed.

Test all open trac tickets for StyledEdit(15) and indicate whether they are still valid. Add extra information as needed.

Test all open trac tickets for Terminal (28) and indicate whether they are still valid. Add extra information as needed.

5. Research: Tasks related to studying a problem and recommending solutions

Summarize past mailing list discussions on patch management issues.

Research the various virtualization programs and recommended settings to get Haiku to run on them. Installing Haiku to new and larger virtual-disk images, figure out which settings to use for which VM software and how to add the VMware add-ons, common issues and work-arounds

6. Training: Tasks related to helping others learn more

Make a video showing off queries (see #2119)

Make a video showing off Stack and Tile

Make a video showing off the power of Haiku's image translators, and other translators

Make a video showing how to write and build a C++ "Hello World" program using the BeAPI

Update the step by step build instructions on the Haiku web site to reflect the switch from svn to git, and verify that it works

7. User Interface: Tasks related to user experience research or user interface design and interaction

Check over the various apps included in Haiku, both with the fonts set to size 12 and set to size 18. Check the apps for text alignment report any issues you find. Keep a list of the apps that you checked over.

Check over the various apps include in Haiku, checking it with various languages set. Note any text alignment problems and report any issues you find. Keep a list of the apps that you checked over, and languages checked.

Check over the various apps included in Haiku, looking for instances of large/too small spacing between elements. Document these problems with annotated screenshots added as attachments in Trac.

Some Haiku apps/preflets use non-standard controls that could be replaced with standard ones, eg. custom progress bars etc.. Identify where these are used, so that they can be updated to use standard controls

Search Haiku's trac for issues related to the GUI and recheck them to see if they are still valid.