What's New in Haiku development
The Haiku source is continually built and released for testing purposes nearly every day. You can download and install these latest snapshots to check out the latest features and bug-fixes.
Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.
If you're OK with this, you can find further instructions at our Nightly image page.
I have not used this blog in a while, except for the monthly activity report. But it's time for a clarification.
Lately, several people (some newcomers, some long time members of the community) have started contacting me by private messages (either by e-mail or IRC chat). Sometimes it was the right thing to do, there are parts of the code for which I'm indeed the best person to ask, and sometimes things are not to be discussed on public channels (for example, because it involves personal data that should stay private).
Hello and welcome to the (almost) monthly activity report for December 2019! December wasn't the busiest for Haiku code-wise, but nonetheless we saw a lot of Google Code-In contributions. This year marks the 10th anniversary of GCI, in which Haiku has participated since the very beginning.
On the non-coding side, GCI participants wrote new virtualization guides: alwayslivid wrote a guide on AWS and rewrote the old Xen one, trungnt2910 wrote a guide on qemu, R4H33M wrote a guide on Vultr and redsPL's (hey, that's me!
The last two months have been quite busy for me and I had no time to write up a report. Remember that everyone is welcome to contribute to the website and if you wand to write the report from time to time, this would be much appreciated, by me because I wouldn't need to do it, and by others because they will enjoy reading things written with a different style and perspective.
Another year, another Google Code-In! The Haiku project is proud to announce that it will be participating in the 2019 Google Code-In!
Together with 28 other open source projects, we'll mentor students between 13 and 17 years of age through a variety of large and small tasks. The aim is to introduce them to the work and community of open source projects, while benefitting ourselves from their work and energy, and maybe even by gaining future contributors.
Hi there, it's time for the monthly report!
This report covers hrev53461-hrev53529. Let's see what happened this month in Haiku.
Non-x86 support Some initial work for ARM64 was completed by kallisti5. This includes setting up the Haikuports package declarations, writing the early boot files, and in general getting the buildsystem going. Jaroslaw Pelczar also contributed several further patches (some of these still undergoing review), providing the initial interrupt handling support, and various stubs to let things compile
TLDR: pkgman install nodejs
As some have already known for a long time, many platforms have had support for writing software in JavaScript or TypeScript with the help of the Node.js runtime and over the years, much of the software written by developers these days have gradually been written in either of those languages. However, Haiku has lacked a Node.js port for quite sometime and it wasn't possible to run or develop JavaScript based software or libraries that depended on the Node.
Hi there, it's time for the monthly report again! This report covers hrev53338-hrev53461. It's been a busy month!
User interface Andrew Lindesay continue his work on HaikuDepot, tweaking the BarberPole look, adding a display of "usage conditions" (EULA, license, etc) from packages, Ryan Leavengood also worked in this area, making sure if you open an existing hpkg file with HaikuDepot, it will offer you to uninstall the package if it's currently installed.
