In what is by now a tradition, Adrien (Pulkomandy) has published his monthly activity report for Haiku's development, this time for September. Last month we saw developers working, as usual, on different fronts, from the app_server to user interface, from drivers to media.

Notable examples include the reworking of _res, on the network side of things as well as improvements for the WebKit (both on and off branch) and improvements on font sensitivity, this affecting several applications.

As usual, to get the full monty, click the link above and enjoy the read. Kudos to all the developers involved in the project.

Hi everyone. Just a quick note to apologize for the downtime, unfortunately it happened just as I left for a 2 week vacation abroad, so had no way to access the server and sort things out. 

Back now and so is the site.


It's that day of the year once more, the day where we celebrate another Haiku birthday! This time around, it's turning 14 and... awwww... it's growing a little peach fuzz on its chin, how cute.

During this time of the year, Haiku usually sees a hike in dev activity - due in part to holidays from their jobs - and this year it was no exception. You can get an overview of last month's work by reading Adrien's summary.

Congratulations to all involved, past and present, and here's to another 14 years at least, hopefully with R1 out by then ;-)

Adrien, aka Pulkomandy, published yesterday the latest monthly activity report for Haiku. It seems July was quite a busy month (yay), with lots of changes committed to the tree. from applications to packages and building tools.

The change with the most impact is the fixes for the network problems users (including myself) have been experiencing since several revs ago, which basically prevented Haiku to get on the network.

Nicely done everyone, keep it up.

Axel has been working on this for a while now, and a couple of days ago he finally introduced it to the Haiku world in a blog post, the new launch_daemon. This daemon will replace the current shell based boot process, with the goal of making it flexible, giving the user choice of what or what not to load, after the daemon comes into play. At the moment you can, for example, have software startup automatically, or prevent system components to launch. For what's down the road, Axel would like to implement, among other features, the possibility to monitor running services and use the syslog for error reporting.

According to Axel, basic functionality is already in place, allowing Haiku to boot using the launch_daemon as it's been doing so far (without it), and he plans to merge his work into the main repository in the next few days. Looking forward to see how things progress from this point onward, good stuff.

As it had been discussed/announced earlier, there have been some changes at Haiku Inc's board of directors. Bruno (BGA) and Matthew (mmadia) have stepped down from their respective positions of vice-president and secretary, having been replaced by René (DeadYak) and Alexander (kallisti5), also respectively. According to the link above, the board have already working on some pending projects, so let's hope news will come out shortly.

You can also find the meeting minute over at the Haiku Inc's website.

There's been a flurry of activity over at Haiku for the past couple of weeks, which is how we like it! Adrien posted his regular monthly update, tracking what the devs have been working now. René, aka Yak Man, continues working on the debugger and wrote a blog post about the latest developments, namely the fact that you're now able to edit memory using it.

Jessica's been busy as well, not only adding TeX Live (mammoth size indeed) and LyX packages to the repository, but also improving Haiku's support for GPT partitions! This will make life easier for those who want to install Haiku onto a GPT partition, no more need for hacks and workarounds.

Last and definitely not least, a new dev contract has begun and Waddlesplash is now working on the packaging infrastructure. His contract is for a six weeks full-time work and he already posted his first weekly update.

Nicely done to everyone, congrats.

Many of you might recall the image editor Refraction, created by Frans van Nispen of Xentronix (also the creator of SampleStudio). At the time this was created for BeOS and Zeta but unfortunately it was last updated 10 years ago. Well there's now some in the community who would like to open-source Refraction so it can be easily updated and kept current. And for that they've created a crowd funding campaign, which you can check out here.

The amount is steep though. According to Frans, it'll take €10,000 to open-source it and at the moment only USD $570 have been pledged, which comes to around €510, so there's a long way to go. If you feel this is a worthy cause, head over to the link above and add your pledge. You can also view the discussion going on in the Haiku's site's forum, by going here.

Thanks to Matthias, aka Paradoxon, for the tip.

Adrien has posted another monthly update, giving us an overview of what the devs have been up to during April. He goes over work done on packages for Haiku Depot, on the user interface and other areas. A very interesting tidbit he shared, regards work being done outside of the tree, specifically Axel's work on a launch daemon. If this comes to fruition, it'll replace the venerable boot script, allowing for more flexibility and faster boot times, among other improvements. Looking forward to see the results.

On a side note, and something Adrien also mentioned, BeBits is now offline (same for Haikuware), which is sad news, for this site had been with us for such a long time... I'm curious though, with Haiku Depot and more and more software being made available through it, is there a big demand for an external software site? Drop me a line with your thoughts.

The development team behind the proprietary Static Code Analyzer for C and C++, PVS, ran it through Haiku's code and have now published part 1 of their report. They cover errors and warnings they found in different parts of the code (including.. Cortex) but I'm guessing we have to wait for part 2 for the final conclusion. This doesn't seem to be very different from what Haiku already has in place with the Coverity scans, but if it helps squash bugs or just improve the code quality, no complaints.

Thanks to Dmitriy for the tip!

Update: The second part of the analysis, along with the conclusion, is now up and available for you to read.