Hi there! We're back for monthly (or almost) reports! I was at the JDLL in early april, and while preparing for that I didn't have time to write a report, and no one else did it. So here we go with a 2 month report, prepare for something a little longer than usual. This report covers hrev52945-hrev53094.
Code cleanups mt fixed various places where -Werror=class-memaccess was breaking the build. These are cases where we initialize a C++ object with memset, which is normally not allowed.
Welcome to the activity report for February 2019. This month has been quite busy for me with the annual visit to FOSDEM (read the report), and managing the application process for both GSoC and Outreachy (Haiku has been accepted to both programs this year).
We are already seeing candidates applying to both GSoC and Outreachy, so expect to read about new names in the reports in the coming months and during the summer!
Happy new year! It's 2019 and Haiku is still alive!
First of all, it's time to look at the stats for Haiku and Haikuports. As you can see, the activity for haikuports keeps growing (there are now 2x more commits to haikuports than to Haiku), and Haiku got slightly more commits in 2018, after two historically low activity years. Let's hope the trend continues and we can reach the high levels of activity of 2008-2010 again someday.
Welcome to the last activity report in 2018!
I notice that I have not written any report since july. Thanks to the other community members who took care of them during that period, as I was busy moving (again) to a new flat, and then visiting the USA for the GSoC mentor summit and germany for BeGeistert.
Anyway, this report covers hrev5263-hrev52615. We are past the beta release now, so unsurprisingly, the activity is mostly focused on bugfixes, but there are always some new things going on.
Hi there, it's time for the monthly report! (yes, I'm still out of inspiration for catchy headlines)
This report covers hrev52055-52140
Drivers waddlesplash completed his work synchronizing drivers with FreeBSD 11. The FreeBSD9 compatibility layer is now gone and all drivers are up to date again.
jessicah fixed a problem in the UEFI framebuffer driver (most of the code is shared with the "VESA" driver, although there is no VESA BIOS in this case).
Hi there, I'm back for an activity report!
Let's see what happened last month. This report covers hrev51986-52054
Donations and funding I just wanted to note that the 5 Haiku contributors who joined Liberapay are now part of a "team".
In case you missed it, Liberapay is a way to donate money to some Haiku contributors directly. They are an open source project, funded themselves by donations from their users, and with an interesting approach to funding free software and other commons creations.
Welcome to the fourth monthly report for 2018!
This report covers hrev51873-hrev51921.
32/64 bit hybrid support Let's start with the most exciting developments this month: Korli started work on a 32/64 bit hybrid. The idea is to run a 64bit system, but allow 32bit applications to run on it. While we are just at the very first steps, it is a good thing that this is being worked on, as it will allow us to move more smoothly towards 64bit support.
Welcome to the third monthly report for 2018!
This report covers hrev51833-hrev51872.
System Hrishi Hiraskar (one of our GSoC applicants) reworked the management of the shutdown phase. This revolves around both launch daemon and the BRoster, which collaborate together to coordinate system shutdown. Things must happen in a specific order to make sure all apps are properly terminated (leaving the user a chance to save his work if not done yet), and only then, system servers are stopped.
Welcome to the second monthly report for 2018!
This report covers hrev51791-hrev51832
Infrastructure There is a lot of invisible work in progress on getting the Haiku infrastructure migrated to a new server and streamlined to use containers and standardized setup. This will eventually allow to better share the work of system administration in a larger team, allowing to scale up the infrastructure.
Part of this work is updating our Pootle install, which will soon have a new version up in production.