Blogs

Haiku monthly activity report - 04/2014

Blog post by PulkoMandy on Sat, 2015-04-25 17:59

A new month, a new report!

Statistics

The commit range this month is hrev48952-hrev49106. I got bored of doing the statistics by hand, so I've run the repo through gitstats instead. This gives more information than what I could do manually, including a listing of the most active commiters this month. Be sure to have a look at the results!

Haiku monthly activity report - 03/2015

Blog post by PulkoMandy on Sun, 2015-03-29 12:55

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.

Haiku monthly activity report - 02/2015

Blog post by PulkoMandy on Mon, 2015-03-02 09:38

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 progress bars which tend to not move much.

This month there were 91 commits (hrev48757-hrev48848). Let's see what's inside those.

End of contract - closing words.

Blog post by PulkoMandy on Wed, 2015-02-18 08:21

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 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.

Google Code-In 2014 Wrap Up Report

Blog post by scottmc on Fri, 2015-02-13 08:53

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 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.

Contract weekly report #61

Blog post by PulkoMandy on Fri, 2015-01-30 09:27

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 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.

Tracker-Layout has landed!

Blog post by waddlesplash on Tue, 2015-01-27 22:00
tracker_layout — the (semi)famous branch that rewrites Tracker to use the Layout Kit — has been merged.
Syndicate content