Article Index...

• Source Activity
• Ticket Updates
• Mailing List
• Nightly Images

What is Google Code-in ?

GCI is a contest for pre-university students (from 13 to 17 years old) with the goal to encourage young students to participate into open-source development. To achieve that goal, open-source organizations sets up various tasks and students are invited to claim them. Various prizes are awarded and, this year, each organizations are going to award two (2) grand prize winners amongst participating students.

When does the contest start ?

Students can starts claiming tasks on Monday, November 26 2012 at 9:00 AM PST / 17:00 UTC, to end on Monday, January 13th at 9:00 AM PST / 17:00 UTC.

What kind of tasks are available ?

A Task is a small amount of work, suitable for a 13 to 17 years old student, and should take approximately 2 hours to complete to the average participant. There are 5 categories of tasks :

1. Code: Tasks related to writing or refactoring code
2. Documentation/Training: Tasks related to creating/editing documents and helping others learn more
3. Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
4. Quality Assurance: Tasks related to testing and ensuring code is of high quality.
5. User Interface: Tasks related to user experience research or user interface design and interaction

Where do I sign-up ?

For more details about the program itself, and to register, please consult the contest's homepage :
www.google-melange.com/gci/homepage/google/gci2012

• Login or register to post comments
• 
• 
• 
• 
• 
• 

Due to the immediate testing efforts of HAIKU Release 1 Alpha 4, several critical bugs were detected by testers and reported on our bug tracker. On several hardware configurations, those issues prevented Haiku from booting properly. Since then, those bugs have been squashed and are resolved in this bugfix update, R1 Alpha 4.1.

There are two general issues fixed by this point release:

• Deskbar can freeze at boot-up on read-only media.
  Issue: Potential kernel level deadlocking issue in the network stack.
  Solution: The cause of the deadlock was found and corrected.
  Change: hrevr1alpha4-44701
• Users can see a kernel crash at boot-up on read-only media.
  Issue: Normalization never occurring on module image paths due to a bug in the hash table.
  Solution: Hash table code was fixed preventing duplicate module images from loading.
  Change: hrevr1alpha4-44700

We have replaced the R1A4 files on the website with R1A4.1 files to ensure these issues are thoroughly corrected. The archives are named "haiku-r1alpha4.1-*" and the image files contained within retain the "haiku-r1alpha4*" nomenclature.

If you have already installed R1A4, we recommend updating to R1A4.1. Thank you all for testing and supporting Haiku!

• 16 comments
• 
• 
• 
• 
• 
• 

The Haiku Project is excited to announce the availability of our fourth official alpha release. A year and four months have passed since the Alpha 3 and the Haiku Project has been busy. The main purpose of this release is to provide interested third party developers with a stable version for testing and development. To aid with that, Haiku includes a rich set of development tools.

• 16 comments
• Read more
• 
• 
• 
• 
• 
• 

As you may recall during August, Ingo Weinhold and Oliver Tappe were each accepted for two-month development contracts relating to package management[1]. Originally, their start dates were slated for sometime around November or December. Due to their current contractual obligations with other employers, they will not be able to begin as early as planned. The revised start date is now around February or March.

• mmadia's blog
• 1 comment
• 
• 
•