Haiku

Hello there, here comes the activity report for the month of march 2015. This month there were 104 commits (hrev48848-hrev48952), 5 more than in the previous month. read more

The Haiku project is participating again in this year's "Semester of Code" (SoC) of the European VALS project. The SoC is similar to Google's GSoC, but without the financial incentive and more emphasis on the educational side. This is the second ... [More] installment of "SoC", the objective is still the same: Its goal is to connect higher education students with open source projects to introduce them to the cooperative nature of working within a group on a bigger project. For Haiku, besides potentially extending its feature set, it's another opportunity to spark the interest of new, eager developers with a chance to gain future regular contributors. There are currently 48 project proposals for Haiku on the VALS projects page. If you're a student and interested to take on a project, you have to act quick: the deadline for your application ends on April, 1st 2015! Sorry for the late notice... [Less]

Hello there! My contract has ended, but for now I have some free time to write a report every month about the ongoing development efforts from the Haiku team. I think this is a nice way to better see the work done, more so than looking at the roadmap ... [More] progress bars which tend to not move much. This month there were 91 commits (hrev48757-hrev48848). Let's see what's inside those. read more [Less]

Hi, As you probably have noticed, there were no weekly report in the previous weeks. The reason for this is that my contract is currently stopped. There is currently not enough money in Haiku's treasure chest to safely continue it. So, it's time to ... [More] me to get back to "real life" and a full-time job in a software development company. First of all I want to thank everyone who made this long contract possible by donating money to Haiku. It was a great experience for me, and a lot of fun as well. I did my best to move Haiku forward towards the R1 release. Unfortunately the beta 1 still isn't there, and we currently have 57 blocking tickets. It is a small number, but only the most complex or big issues are left. read more [Less]

Google has now announced the 24 winners for Google Code-In 2014, with Josef Gajdusek and Puck Meerburg being the two winners from Haiku. This is Puck's second time winning for Haiku. This year we got to pick our top 5 out of the top 10 students who ... [More] completed that most tasks for Haiku. Augustin Cavalier was selected as our backup winner, and Markus Himmel and Chirayu Desai were selected as finalist. Chirayu was a GCI 2013 winner with RTEMS, and made the jump to Haiku when RTEMS took this year off from GCI. This was the fifth year of Google's Code-In, and the fifth for Haiku. This year we had 6 students who completed 20 or more tasks, one more than in 2013. We had 36 students who completed three or more tasks and qualified for a Google Code-In T-Shirt, and 53 students who completed two or more tasks. This was the first year of having beginner tasks, aimed at lowering the bar to get more new students introduced into open source. Haiku had 149 total students complete at least one task, many of those were for the beginner tasks. We had 164 beginner tasks completed, which was mostly just to introduce students to booting and using Haiku. Other beginner tasks were to compile Haiku or to install and use Haikuporter to build a package from a recipe file. In total students completed a staggering 435 tasks this time for Haiku. read more [Less]

Hello there! As you may have noticed if you watch the commit list closely, my libbind work has not been merged yet. There are still some bugs to solve there, but I got sidetracked. I use BReferenceable in my DNS cache implementation to keep track of ... [More] the cache entries. BReferenceable is a class used in Haiku to implement reference counted objects. In C++, the language only has very simple memory management, in the form of the new and delete operators. Objects can be allocated on the stack (they are temporary and only last as long as the function they are declared in is executing), or on the heap (for long lived objects). Objects allocated on the stack are deleted automatically when the function exits, while objects allocated on the heap must be deleted manually. This is one of the annoying parts of C++: managing the lifetime of these objects, making sure they are deleted only once, and that no one will try to use them after deletion. read more [Less]

Hello world! Not much commits from me this week, as I'm still working on the libbind update, and I'm also doing some work for other customers. I got netresolv to build after implementing the missing getifaddrs function in Haiku - this is a non-POSIX ... [More] function, but it is available in Linux and all major BSDs. It enumerates all network addresses for all network interfaces on the system, similar to our BNetworkRoster and BNetworkInterface classes. read more [Less]

Hello world! I have not given any news from the Google Code-In for some time. It ends this week, and students have completed more than 400 tasks for Haiku. While this includes a lot of simple tasks (the simplest "getting started" ones involved just ... [More] booting Haiku and running StyledEdit), it means the students at least got to see what Haiku is. We have a more complete set of recipes in haikuporter waiting to be packaged. read more [Less]

Hello there, welcome to the first contract report for 2015! This report summarizes changes done since 19 of december as I was a bit away from keyboard for the winter break. But I'm back for another year of Haiku coding! read more

Hi! Work continues on putting Haiku in shape for the R1 release. This week I worked mostly on UI fixes to make our apps look a bit better. read more