Hello!
The previous report involved a lot of travelling around and attending various
events and conferences. This month is quite different as some of us are locked
home due to the ongoing pandemic. We already know some of the next planned
events such as the JDLL and FLISOL are cancelled (for good reasons).
Anyway, the activity on Haiku has not slowed down, so let’s see what’s happening
there. This report covers hrev53875-hrev53995.
Hi there!
It’s time for the monthly report for January (and half of February as well).
This report convers hrev53715-hrev53874 and some real world activities.
Unit Tests
It’s about time the unit tests for Haiku get some serious attention and fixes.
Kyle Ambroff-Kao is currently working on them and fixing various issues.
This month he fixed problems in the app and support kits tests, identifying
deviations fro, BeOS, some on purpose, some that could be regressions.
This 2019/2020 Google Code-in (GCI) was the 10th iteration in as many years and according to Google’s stats it was the most successful yet: In 7 weeks 3,566 students from 76 countries finished 20,840 tasks for 29 open source organizations!
Haiku was one of those organizations - the only open source project, by the way, that participated in all 10 editions of GCI - and we had our share of dedicated students that completed numerous tasks, big and small. You may have noticed the increased updates on the HaikuPorts commits page, that got even more busy than usual. Other tasks resulted in new and updated documentation, guides and videos. Projects at HaikuArchives saw bugfixes and new features. Apps were tested and new issues were discovered and filed at their bugtracker.
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!) wrote guides on VMware ESXi and DigitalOcean. Other than that, Vrondir made a KVM tutorial video and Zotyamester made a VMware Workstation video.
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.
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.js runtime. Now I can say that Node.js is available for Haiku and can be downloaded from HaikuDepot on 64 bit (32 bit support is being worked on). The version which is currently available is 12.3.1 and is already being updated to the latest version at the time of this writing to 12.10.0 and support for the upcoming LTS version is also coming to HaikuPorts. Several patches have been upstreamed by members of the HaikuPorts team to projects such as libuv (cross-platform async I/O library), GN, etc and we hope to upstream to larger projects like V8 (Google’s JavaScript engine used in Chromium and QtWebEngine) and the Node.js project, which will ease the bringup of a future Node LTS release for Haiku.
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.
Introduction
Hey there beautiful person reading this post. We are in the endgame now (Ha get it avengers reference!). Yes, Google summer of code 2019 is coming to an end. Phew couldn’t say how 3 months passed by, but this is one of my most memorable experiences I will never forget. So let me wrap GSOC with this final report. Buckle up tight it’s going to be a long post…
